[OPENIDM-8091] java.io.IOException: Thread signal failed displayed in felix console when shutting down Created: 18/Apr/17  Updated: 20/Apr/17  Resolved: 20/Apr/17

Status: Closed
Project: OpenIDM
Component/s: Module - OSGi Container / Framework integration
Affects Version/s: OpenIDM 5.5.0
Fix Version/s: OpenIDM 5.5.0

Type: Bug Priority: Major
Reporter: Mark Gibson Assignee: Dirk Hogan
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OpenIDM version "5.5.0-SNAPSHOT" (revision: 2ac08ae) jenkins-OpenIDM - postcommit-2568 origin/master



 Description   

When shutting down IDM, felix console displays

java.io.IOException: Thread signal failed
	at sun.nio.ch.NativeThread.signal(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.implCloseSelectableChannel(ServerSocketChannelImpl.java:292)
	at java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:234)
	at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:115)
	at org.eclipse.jetty.server.ServerConnector.close(ServerConnector.java:359)
	at org.eclipse.jetty.server.AbstractNetworkConnector.shutdown(AbstractNetworkConnector.java:107)
	at org.eclipse.jetty.server.ServerConnector.shutdown(ServerConnector.java:341)
	at org.eclipse.jetty.server.Server.doStop(Server.java:404)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
	at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.stop(JettyServerImpl.java:209)
	at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Started.stop(ServerControllerImpl.java:277)
	at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.stop(ServerControllerImpl.java:77)
	at org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:339)
	at org.ops4j.pax.web.service.internal.Activator$3.run(Activator.java:294)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)


 Comments   
Comment by Dirk Hogan [ 20/Apr/17 ]

This is a jvm issue - the stack trace occurs in java's NIO implementation. I found similar issues:
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4785384
http://www-01.ibm.com/support/docview.wss?uid=swg1PK70995

All of them point to a very intermittent jvm bug. It is likely that this issue was encountered on java 7. Now that we are on java 8, it makes sense to close this bug and re-open if reproduced.

Generated at Thu Feb 25 15:59:28 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.