-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
-
Severity 3 - Minor
A version bump of HipChat core and HipChat JIRA caused tomcat to get stuck while shutting down. Taking a thread dump revealed that there were three non-daemon threads causing the JVM to wait for them:
"Thread-34" prio=10 tid=0x0a190000 nid=0x253 runnable [0x9d6fe000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) at sun.nio.ch.EPollArrayWrapper.poll(Unknown Source) at sun.nio.ch.EPollSelectorImpl.doSelect(Unknown Source) at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source) - locked <0xc69060e0> (a sun.nio.ch.Util$2) - locked <0xc69060d0> (a java.util.Collections$UnmodifiableSet) - locked <0xc6905ed0> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(Unknown Source) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:366) at org.apache.http.impl.nio.conn.PoolingClientAsyncConnectionManager.execute(PoolingClientAsyncConnectionManager.java:117) at org.apache.http.impl.nio.client.AbstractHttpAsyncClient.doExecute(AbstractHttpAsyncClient.java:464) at org.apache.http.impl.nio.client.AbstractHttpAsyncClient.access$000(AbstractHttpAsyncClient.java:101) at org.apache.http.impl.nio.client.AbstractHttpAsyncClient$1.run(AbstractHttpAsyncClient.java:485) Locked ownable synchronizers: - None
- blocks
-
JRASERVER-29891 HipChat Plugin errors "Can not forward a request to HipChat API" without HipChat being configured
- Closed