activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonas Lim (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-870) Broker fails to deliver messages after restart
Date Thu, 19 Jul 2007 09:03:46 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonas Lim resolved AMQ-870.
---------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0

Ran the test case on trunk rev:  557391  and it passed. 

Just need to modify the test case a bit to remove the failover  option as it's no longer supported
in the latest version. 

> 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
>            Assignee: Jonas Lim
>             Fix For: 5.0.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message