WebTomcat servers crashed with hprof files on two user oneclicks
Article ID: 247930
Updated On:
Products
Issue/Introduction
Webtomcat has crashed on the OneClicks leaving large java core files. Hprof stack shows:
One instance of “java.util.TaskQueue” loaded by “<system class loader>” occupies 2,882,558,624 (91.54%) bytes. The instance is referenced by java.util.TimerThread @ 0x6c0b9a038 Websocket Ping Timer , loaded by “<system class loader>”.
The thread java.util.TimerThread @ 0x6c0b9a038 Websocket Ping Timer keeps local variables with total size 19,560 (0.00%) bytes.
The memory is accumulated in one instance of “java.util.TimerTask[]”, loaded by “<system class loader>”, which occupies 2,882,558,600 (91.54%) bytes.
Thread Stack
Websocket Ping Timer
at org.webswing.server.api.services.swinginstance.impl.SwingInstanceImpl.disconnectPrimaryWebSession(Ljava/lang/String;)V (SwingInstanceImpl.java:219)
at org.webswing.server.api.services.swinginstance.impl.SwingInstanceImpl.browserDisconnected(Ljava/lang/String;)V (SwingInstanceImpl.java:168)
at org.webswing.server.api.services.websocket.impl.BrowserWebSocketConnectionImpl.onClose(Ljavax/websocket/Session;Ljavax/websocket/CloseReason;)V (BrowserWebSocketConnectionImpl.java:164)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; (Method.java:498)
at org.apache.tomcat.websocket.pojo.PojoEndpointBase.onClose(Ljavax/websocket/Session;Ljavax/websocket/CloseReason;)V (PojoEndpointBase.java:107)
at org.apache.tomcat.websocket.WsSession.fireEndpointOnClose(Ljavax/websocket/CloseReason;)V (WsSession.java:767)
at org.apache.tomcat.websocket.WsSession.doClose(Ljavax/websocket/CloseReason;Ljavax/websocket/CloseReason;Z)V (WsSession.java:715)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(BLjava/nio/ByteBuffer;ZJ)V (WsRemoteEndpointImplBase.java:325)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(BLjava/nio/ByteBuffer;Z)V (WsRemoteEndpointImplBase.java:262)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPing(Ljava/nio/ByteBuffer;)V (WsRemoteEndpointImplBase.java:176)
at org.apache.tomcat.websocket.WsRemoteEndpointBase.sendPing(Ljava/nio/ByteBuffer;)V (WsRemoteEndpointBase.java:55)
at org.webswing.server.api.services.websocket.impl.AbstractWebSocketConnection$1.run()V (AbstractWebSocketConnection.java:54)
at java.util.TimerThread.mainLoop()V (Timer.java:555)
at java.util.TimerThread.run()V (Timer.java:505)
Environment
Release : 21.2
Component : Spectrum OneClick
Cause
Code issue in WebTomcat
Resolution
The WebSwing team provided new Webswing war files with a resolution. Please open a new case and request the updated ware files from defect DE538831
1. Stop webtomcat and take backup of the existing spectrum.war and admin.war files(from $WEBTOMCAT/webapps dir) and put it outside of $SPECROOT.
2. Delete the spectrum and admin folders and spectrum.war and admin.war files from $WEBTOMCAT/webapps directory.
3. Place the new war files under this $WEBTOMCAT/webapps directory.
4. Start webtomcat and it will extract these war files to directories
Additional Information
Files are attached to DE538831
Feedback
