You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Ashwin Karpe (JIRA)" <ji...@apache.org> on 2007/07/23 17:55:48 UTC

[jira] Created: (AMQ-1336) Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...

Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...
----------------------------------------------------------------------

                 Key: AMQ-1336
                 URL: https://issues.apache.org/activemq/browse/AMQ-1336
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.1.1
         Environment: Windows
            Reporter: Ashwin Karpe
         Attachments: Exercise3_Failover.zip, exercise_setup.bat

I am using version 4.1.2.4.

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(TransportSupport.java:71)
     [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
     [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
     [java]     at org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49)
     [java]     at org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363)
     [java]     at org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345)
     [java]     at org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320)
     [java]     at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
     [java]     at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:
491)
     [java]     at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
     [java]     at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
     [java]     at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
     [java]     at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
     [java]     at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133
)
     [java]     at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
     [java]     at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
     [java]     at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
     [java]     at java.lang.Thread.run(Thread.java:595)

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.

[jira] Resolved: (AMQ-1336) Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-1336.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 5.4.0)
         Assignee: Rob Davies

We no longer support the 4.x branches

> Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...
> ----------------------------------------------------------------------
>
>                 Key: AMQ-1336
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1336
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Windows
>            Reporter: Ashwin Karpe
>            Assignee: Rob Davies
>         Attachments: Exercise3_Failover.zip, exercise_setup.bat
>
>
> I am using version 4.1.2.4.
> 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(TransportSupport.java:71)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320)
>      [java]     at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
>      [java]     at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:
> 491)
>      [java]     at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
>      [java]     at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
>      [java]     at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
>      [java]     at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
>      [java]     at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133
> )
>      [java]     at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
>      [java]     at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>      [java]     at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
>      [java]     at java.lang.Thread.run(Thread.java:595)
> 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.

[jira] Updated: (AMQ-1336) Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-1336:
----------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...
> ----------------------------------------------------------------------
>
>                 Key: AMQ-1336
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1336
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Windows
>            Reporter: Ashwin Karpe
>             Fix For: 5.3.0
>
>         Attachments: Exercise3_Failover.zip, exercise_setup.bat
>
>
> I am using version 4.1.2.4.
> 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(TransportSupport.java:71)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320)
>      [java]     at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
>      [java]     at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:
> 491)
>      [java]     at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
>      [java]     at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
>      [java]     at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
>      [java]     at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
>      [java]     at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133
> )
>      [java]     at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
>      [java]     at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>      [java]     at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
>      [java]     at java.lang.Thread.run(Thread.java:595)
> 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.

[jira] Commented: (AMQ-1336) Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...

Posted by "Manish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44140#action_44140 ] 

Manish commented on AMQ-1336:
-----------------------------

Hi,
  

   I am using activemq 4.1. i am also getting same issue. Please resolve it as soon as possible.

Regards,
Manish



> Assertion Error in the AMQ Broker in a pure "Master/Slave" scenario...
> ----------------------------------------------------------------------
>
>                 Key: AMQ-1336
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1336
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Windows
>            Reporter: Ashwin Karpe
>             Fix For: 5.2.0
>
>         Attachments: Exercise3_Failover.zip, exercise_setup.bat
>
>
> I am using version 4.1.2.4.
> 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(TransportSupport.java:71)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.TransportFilter.request(TransportFilter.java:88)
>      [java]     at org.apache.activemq.transport.MutexTransport.request(MutexTransport.java:49)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendSyncToSlave(MasterBroker.java:363)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.sendToSlave(MasterBroker.java:345)
>      [java]     at org.apache.activemq.broker.ft.MasterBroker.acknowledge(MasterBroker.java:320)
>      [java]     at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
>      [java]     at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:
> 491)
>      [java]     at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
>      [java]     at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
>      [java]     at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
>      [java]     at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
>      [java]     at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133
> )
>      [java]     at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
>      [java]     at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>      [java]     at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
>      [java]     at java.lang.Thread.run(Thread.java:595)
> 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.