activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Karpe (JIRA)" <>
Subject [jira] Created: (AMQ-1336) Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...
Date Mon, 23 Jul 2007 15:55:48 GMT
Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...

                 Key: AMQ-1336
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.1.1
         Environment: Windows
            Reporter: Ashwin Karpe
         Attachments:, exercise_setup.bat

I am using version

When I start the master and slave Broker everything starts correctly. No errors etc.

When I start the consumer, no issues there either...

However when I start the producer on every invocation, I find the following error popping
up on the master brokers console...

10:08:39 ERROR Slave Failed
     [java] java.lang.AssertionError: Unsupported Method
     [java]     at org.apache.activemq.transport.TransportSupport.request(
     [java]     at org.apache.activemq.transport.TransportFilter.request(
     [java]     at org.apache.activemq.transport.TransportFilter.request(
     [java]     at org.apache.activemq.transport.MutexTransport.request(
     [java]     at
     [java]     at
     [java]     at
     [java]     at
     [java]     at
     [java]     at org.apache.activemq.command.MessageAck.visit(
     [java]     at
     [java]     at$1.onCommand(
     [java]     at org.apache.activemq.transport.TransportFilter.onCommand(
     [java]     at org.apache.activemq.transport.WireFormatNegotiator.onCommand(
     [java]     at org.apache.activemq.transport.InactivityMonitor.onCommand(
     [java]     at org.apache.activemq.transport.TransportSupport.doConsume(
     [java]     at
     [java]     at

The funny thing is that I cannot explain why this happens, everything behaves correctly i.e
the fail-over does happen when the master dies. 

Please use the attachment to re-create the issue. Not sure what this wierd problem is...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message