[
https://issues.apache.org/jira/browse/CXF-8259?focusedWorklogId=423804&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-423804
]
ASF GitHub Bot logged work on CXF-8259:
---------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/20 22:43
Start Date: 16/Apr/20 22:43
Worklog Time Spent: 10m
Work Description: reta commented on pull request #659: CXF-8259: Blocked
thread of JMS transport during jboss shutdown
URL: https://github.com/apache/cxf/pull/659
CC @ffang
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 423804)
Remaining Estimate: 0h
Time Spent: 10m
> Blocked thread of JMS transport during jboss shutdown
> -----------------------------------------------------
>
> Key: CXF-8259
> URL: https://issues.apache.org/jira/browse/CXF-8259
> Project: CXF
> Issue Type: Bug
> Components: JMS
> Affects Versions: 3.3.5, 3.3.6
> Reporter: Alessandro Proscia
> Assignee: Andriy Redko
> Priority: Major
> Attachments: jboss.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have a soap over jms webservice implemented with a camel route (Camel
> 3.2.0) and CXF that uses activemq as message broker. The webservice is
> deployed on a jboss eap 7.1 with jdk 1.8. Following the CXF upgrade from
> version 3.3.4 to 3.3.5 (and also with 3.3.6), jboss hangs on shutdown due to
> a blocking thread of CXF:
> "ServerService Thread Pool – 82" #231 prio=5 os_prio=0 tid=0x0000000002981800
> nid=0x66d2 waiting for monitor entry [0x00007f0d60d2f000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:42)
> Therefore, we can have to kill the Jboss process to complete the shutdown.
> The connection to activemq is managed by a resource adapter on jboss. Url is
> configured with a failover as follows:
> failover://(tcp://amqdev.internal:61616,tcp://amqdev.internal:61616,tcp://amqdev.internal:61616)?timeout=1000&initialReconnectDelay=2000&maxReconnectAttempts=2
> Attached you can find the thread dump taken from logs.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
