Bug 1132210 - [QA] (6.3.1) Clean shutdown of server with deployed JMS bridge throws org.hornetq.api.core.HornetQInterruptedException: java.lang.InterruptedException
Summary: [QA] (6.3.1) Clean shutdown of server with deployed JMS bridge throws org.hor...
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: CR1
: EAP 6.3.1
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
Depends On: 1009409 1016141
Blocks: eap631-blockers, eap631-payload, eap63-cp01-blockers 1132169
TreeView+ depends on / blocked
Reported: 2014-08-20 22:03 UTC by Jimmy Wilson
Modified: 2014-10-13 18:37 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1009409
Last Closed: 2014-10-13 18:37:04 UTC
Type: Bug

Attachments (Terms of Use)

Description Jimmy Wilson 2014-08-20 22:03:24 UTC
+++ This bug was initially created as a clone of Bug #1009409 +++

Description of problem:
When EAP 6.2.0.ER1 server with deployed JMS bridge is shutdowned (ctrl-c)  then following error is logged:

13:28:44,049 ERROR [stderr] (pool-4-thread-1) Exception in thread "pool-4-thread-1" org.hornetq.api.core.HornetQInterruptedException: java.lang.InterruptedException
13:28:44,054 ERROR [stderr] (pool-4-thread-1) Exception in thread "pool-4-thread-2" 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$BatchTimeChecker.run(JMSBridgeImpl.java:2162)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	at java.lang.Thread.run(Thread.java:662)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) Caused by: java.lang.InterruptedException
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	at java.lang.Object.wait(Native Method)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$BatchTimeChecker.run(JMSBridgeImpl.java:2149)
13:28:44,055 ERROR [stderr] (pool-4-thread-1) 	... 3 more
13:28:44,056 ERROR [stderr] (pool-4-thread-2) org.hornetq.api.core.HornetQInterruptedException: java.lang.InterruptedException
13:28:44,056 ERROR [stderr] (pool-4-thread-2) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1946)
13:28:44,056 ERROR [stderr] (pool-4-thread-2) 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
13:28:44,056 ERROR [stderr] (pool-4-thread-2) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
13:28:44,056 ERROR [stderr] (pool-4-thread-2) 	at java.lang.Thread.run(Thread.java:662)
13:28:44,056 ERROR [stderr] (pool-4-thread-2) Caused by: java.lang.InterruptedException
13:28:44,056 ERROR [stderr] (pool-4-thread-2) 	at java.lang.Object.wait(Native Method)
13:28:44,057 ERROR [stderr] (pool-4-thread-2) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1938)
13:28:44,057 ERROR [stderr] (pool-4-thread-2) 	... 3 more

Attached configuration of servers + server.log (with TRACE logs from server with deployed bridge)

--- Additional comment from Miroslav Novak on 2013-09-18 07:37:27 EDT ---

--- Additional comment from Clebert Suconic on 2013-09-18 11:27:54 EDT ---


This is ignorable.. I'm not going to cut a release just because of this, so this will be on EAP 6.next (either 6.3, 6.2.1.. etc)

If something else more critical appears we will include it on the cut.

--- Additional comment from John Doyle on 2013-09-18 11:38:27 EDT ---

Clebert, this is flagged for 6.2.0. If you're going to push it to a later release you should put a devel_ack-, not a +.

--- Additional comment from Clebert Suconic on 2013-09-18 11:45:16 EDT ---

I marked it for 6.3.0...

If I ever do another cut off for 6.2 (say another issue is found, then it will be sent on 6.2)... I have no plans to make any more cuts on 6.2 unless an at least Urgent issue is found.

Anyway, this seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1003913, which would probably fix this anyways. I'm adding a further minor change on the component just in case.

--- Additional comment from Clebert Suconic on 2013-09-18 11:53:13 EDT ---

I will mark this with NACK then.. which I may change it if we do another component cut.

--- Additional comment from Miroslav Novak on 2013-10-22 09:27:23 EDT ---

I can see that PR is in HQ 2.3.9 (in EAP 6.2.0.ER6) and there is still problem the same exception:

15:06:57,089 ERROR [stderr] (pool-4-thread-2) Exception in thread "pool-4-thread-2" Exception in thread "pool-4-thread-1" org.hornetq.api.core.HornetQInterruptedException: java.lang.InterruptedException
15:06:57,089 ERROR [stderr] (pool-4-thread-2) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1946)
15:06:57,090 ERROR [stderr] (pool-4-thread-2) 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
15:06:57,090 ERROR [stderr] (pool-4-thread-2) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
15:06:57,090 ERROR [stderr] (pool-4-thread-2) 	at java.lang.Thread.run(Thread.java:662)
15:06:57,091 ERROR [stderr] (pool-4-thread-2) Caused by: java.lang.InterruptedException
15:06:57,091 WARN  [org.hornetq.jms.server] (pool-4-thread-3) HQ122004: JMS Bridge Will retry after a pause of 1,000 ms
15:06:57,091 ERROR [stderr] (pool-4-thread-2) 	at java.lang.Object.wait(Native Method)
15:06:57,091 ERROR [stderr] (pool-4-thread-2) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1938)
15:06:57,091 ERROR [stderr] (pool-4-thread-2) 	... 3 more
15:06:57,091 ERROR [stderr] (pool-4-thread-1) org.hornetq.api.core.HornetQInterruptedException: java.lang.InterruptedException
15:06:57,092 ERROR [stderr] (pool-4-thread-1) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$BatchTimeChecker.run(JMSBridgeImpl.java:2162)
15:06:57,092 ERROR [stderr] (pool-4-thread-1) 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
15:06:57,092 ERROR [stderr] (pool-4-thread-1) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
15:06:57,092 ERROR [stderr] (pool-4-thread-1) 	at java.lang.Thread.run(Thread.java:662)
15:06:57,092 ERROR [stderr] (pool-4-thread-1) Caused by: java.lang.InterruptedException
15:06:57,092 ERROR [stderr] (pool-4-thread-1) 	at java.lang.Object.wait(Native Method)
15:06:57,093 ERROR [stderr] (pool-4-thread-1) 	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$BatchTimeChecker.run(JMSBridgeImpl.java:2149)
15:06:57,093 ERROR [stderr] (pool-4-thread-1) 	... 3 more

--- Additional comment from Miroslav Novak on 2014-07-07 04:02:52 EDT ---

This issue is valid for EAP 6.3.0.ER9. Setting jboss-eap-6.4 ? flag and target version as this should be fixed to EAP 6.4 release.

--- Additional comment from Miroslav Novak on 2014-07-07 04:18:26 EDT ---

--- Additional comment from Miroslav Novak on 2014-07-07 04:19:32 EDT ---

Just noticed that "source" server for JMS bridge cannot be cleanly shutdowned when source server was shutdowned first. Attaching thread dump from "source server".

--- Additional comment from Andy Taylor on 2014-07-21 09:59:50 EDT ---

im looking at this too

--- Additional comment from Andy Taylor on 2014-07-22 08:48:10 EDT ---

fixed in https://github.com/hornetq/hornetq/pull/1720

--- Additional comment from  on 2014-07-22 16:18:24 EDT ---

To be clear this was fixed on the 2.3.x branch of HornetQ via commit e93149fb6e797ea6d300aaf9603d51499452c269.

Comment 2 Miroslav Novak 2014-08-28 13:21:46 UTC
Thanks Andy for the fix! Verified in EAP 6.3.1.CP.CR1.

Note You need to log in before you can comment on or make changes to this bug.