You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Anders Bengtsson (JIRA)" <ji...@apache.org> on 2006/08/08 14:57:23 UTC
[jira] Created: (AMQ-870) Broker fails to deliver messages after
restart
Broker fails to deliver messages after restart
----------------------------------------------
Key: AMQ-870
URL: https://issues.apache.org/activemq/browse/AMQ-870
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.0.1
Environment: java version "1.5.0_07", Ubuntu Linux 6.06
Reporter: Anders Bengtsson
Attachments: debug-output.txt, TestFailingReconnectScenario.java
We're running two networked brokers, B1 and B2, with a producer connected to B1 and a consumer to B2. Forwarding messages through this initially works fine.
If we re-start broker B2, everything seems to re-connect, but we no longer get any messages to the consumer.
If we instead re-start broker B1, everything works fine.
I've attached a JUnit test-case illustrating the two scenarios, a working re-start of B1 and a breaking re-start of B2.
Also attached is parts of a log from running the unit test.
I'm suspicious about log lines like these, but don't know if they are related to the problem:
[2006-08-08 14:36:16] DEBUG: [DemandForwardingBridge] Ignoring sub ConsumerInfo
{commandId = 4, responseRequired = true, consumerId = ID:descartes-49241-1155040510241-5:2:1:1, destination = topic://SOME.TOPIC, prefetchSize = 32766, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = false, selector = null, subcriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = [ID:descartes-49241-1155040510241-1:5], optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null} already subscribed to matching destination
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-870) Broker fails to deliver messages after
restart
Posted by "Anders Bengtsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-870?page=comments#action_36743 ]
Anders Bengtsson commented on AMQ-870:
--------------------------------------
There's a comment in AMQ-776 ( https://issues.apache.org/activemq/browse/AMQ-776#action_36535 ) about this scenario too.
> Broker fails to deliver messages after restart
> ----------------------------------------------
>
> Key: AMQ-870
> URL: https://issues.apache.org/activemq/browse/AMQ-870
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0.1
> Environment: java version "1.5.0_07", Ubuntu Linux 6.06
> Reporter: Anders Bengtsson
> Attachments: debug-output.txt, TestFailingReconnectScenario.java
>
>
> We're running two networked brokers, B1 and B2, with a producer connected to B1 and a consumer to B2. Forwarding messages through this initially works fine.
> If we re-start broker B2, everything seems to re-connect, but we no longer get any messages to the consumer.
> If we instead re-start broker B1, everything works fine.
> I've attached a JUnit test-case illustrating the two scenarios, a working re-start of B1 and a breaking re-start of B2.
> Also attached is parts of a log from running the unit test.
> I'm suspicious about log lines like these, but don't know if they are related to the problem:
> [2006-08-08 14:36:16] DEBUG: [DemandForwardingBridge] Ignoring sub ConsumerInfo
> {commandId = 4, responseRequired = true, consumerId = ID:descartes-49241-1155040510241-5:2:1:1, destination = topic://SOME.TOPIC, prefetchSize = 32766, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = false, selector = null, subcriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = [ID:descartes-49241-1155040510241-1:5], optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null} already subscribed to matching destination
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-870) Broker fails to deliver messages after
restart
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-870?page=all ]
Rob Davies reassigned AMQ-870:
------------------------------
Assignee: Rob Davies
> Broker fails to deliver messages after restart
> ----------------------------------------------
>
> Key: AMQ-870
> URL: https://issues.apache.org/activemq/browse/AMQ-870
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0.1
> Environment: java version "1.5.0_07", Ubuntu Linux 6.06
> Reporter: Anders Bengtsson
> Assigned To: Rob Davies
> Attachments: debug-output.txt, TestFailingReconnectScenario.java
>
>
> We're running two networked brokers, B1 and B2, with a producer connected to B1 and a consumer to B2. Forwarding messages through this initially works fine.
> If we re-start broker B2, everything seems to re-connect, but we no longer get any messages to the consumer.
> If we instead re-start broker B1, everything works fine.
> I've attached a JUnit test-case illustrating the two scenarios, a working re-start of B1 and a breaking re-start of B2.
> Also attached is parts of a log from running the unit test.
> I'm suspicious about log lines like these, but don't know if they are related to the problem:
> [2006-08-08 14:36:16] DEBUG: [DemandForwardingBridge] Ignoring sub ConsumerInfo
> {commandId = 4, responseRequired = true, consumerId = ID:descartes-49241-1155040510241-5:2:1:1, destination = topic://SOME.TOPIC, prefetchSize = 32766, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = false, selector = null, subcriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = [ID:descartes-49241-1155040510241-1:5], optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null} already subscribed to matching destination
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-870) Broker fails to deliver messages after
restart
Posted by "Anders Bengtsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-870?page=comments#action_36783 ]
Anders Bengtsson commented on AMQ-870:
--------------------------------------
I've tried the same test-case with 4.0.2 RC3, which fails too, but in a very different way. With 4.0.2 RC3 there is some other problem with the restart, which causes the test to hang instead of failing.
> Broker fails to deliver messages after restart
> ----------------------------------------------
>
> Key: AMQ-870
> URL: https://issues.apache.org/activemq/browse/AMQ-870
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0.1
> Environment: java version "1.5.0_07", Ubuntu Linux 6.06
> Reporter: Anders Bengtsson
> Assigned To: Rob Davies
> Attachments: debug-output.txt, TestFailingReconnectScenario.java
>
>
> We're running two networked brokers, B1 and B2, with a producer connected to B1 and a consumer to B2. Forwarding messages through this initially works fine.
> If we re-start broker B2, everything seems to re-connect, but we no longer get any messages to the consumer.
> If we instead re-start broker B1, everything works fine.
> I've attached a JUnit test-case illustrating the two scenarios, a working re-start of B1 and a breaking re-start of B2.
> Also attached is parts of a log from running the unit test.
> I'm suspicious about log lines like these, but don't know if they are related to the problem:
> [2006-08-08 14:36:16] DEBUG: [DemandForwardingBridge] Ignoring sub ConsumerInfo
> {commandId = 4, responseRequired = true, consumerId = ID:descartes-49241-1155040510241-5:2:1:1, destination = topic://SOME.TOPIC, prefetchSize = 32766, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = false, selector = null, subcriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = [ID:descartes-49241-1155040510241-1:5], optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null} already subscribed to matching destination
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira