JBoss shutdown hangs on IBM MQ ServerSessionImpl

Solution Verified - Updated

Environment

  • JBoss Enterprise Application Platform (EAP) 6.4.5 and earlier

Issue

  • We see our JBoss shutdown hang on IBM MQs com.ibm.mq.connector.inbound.ServerSessionImpl.close like so:
"MSC service thread 1-27" prio=10 tid=0x00007fbeec088000 nid=0xee74 in Object.wait() [0x00007fbf3d988000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000007667b79a0> (a com.ibm.mq.connector.inbound.ServerSessionImpl$IsInUseLock)
	at java.lang.Object.wait(Object.java:503)
	at com.ibm.mq.connector.inbound.ServerSessionImpl.close(ServerSessionImpl.java:290)
	- locked <0x00000007667b79a0> (a com.ibm.mq.connector.inbound.ServerSessionImpl$IsInUseLock)
	at com.ibm.mq.connector.inbound.ServerSessionPoolImpl.closeInternal(ServerSessionPoolImpl.java:645)
	at com.ibm.mq.connector.inbound.ServerSessionPoolImpl.close(ServerSessionPoolImpl.java:583)
	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.stopDeliveryASF(MessageEndpointDeployment.java:583)
	at com.ibm.mq.connector.inbound.MessageEndpointDeployment.stop(MessageEndpointDeployment.java:482)
	at com.ibm.mq.connector.ResourceAdapterImpl.endpointDeactivation(ResourceAdapterImpl.java:476)
	- locked <0x0000000790acc5b0> (a java.util.HashMap)
	at org.jboss.jca.core.rar.EndpointImpl.deactivate(EndpointImpl.java:235)
	at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.deactivate(MessageDrivenComponent.java:216)
	at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.stopDelivery(MessageDrivenComponent.java:230)

Resolution

  • Upgrade to EAP 6.4.6+

Root Cause

Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.