|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
In our Java-002 Slave, the following threads are active:
H2 File Lock Watchdog E:/Jenkins/workspace/Build/Model_Build_JEE_developerIntegration/dependency-check-data/cve.2.9.lock.db id=4613 (0x1205) state=TIMED_WAITING cpu=0%
at java.lang.Thread.sleep(Native Method)
at org.h2.store.FileLock.run(FileLock.java:493)
at java.lang.Thread.run(Thread.java:724)
H2 TCP Server (tcp://10.7.64.161:57006) id=4615 (0x1207) state=RUNNABLE cpu=0% (running in native)
at java.net.DualStackPlainSocketImpl.accept0(Native Method)
at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:131)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:198)
at java.net.ServerSocket.implAccept(ServerSocket.java:530)
at java.net.ServerSocket.accept(ServerSocket.java:498)
at org.h2.server.TcpServer.listen(TcpServer.java:244)
at org.h2.tools.Server.run(Server.java:549)
at java.lang.Thread.run(Thread.java:724)
This also causes a huge amount of java heap usage in the Slave. It appears that this plug-in causes the logic to run in the slave instead of an external process.