activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Fernandez (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1464) AMQ 5.0 Fanout Regression
Date Mon, 22 Oct 2007 18:06:24 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40462
] 

Joe Fernandez commented on AMQ-1464:
------------------------------------

Hmm, here is what the fanout transport reference page states.

"The Fanout transport layers reconnect and replication logic on top of any
of the other transports. It is used replicate commands to multiple brokers."

Perhaps I am missing it, but nowhere in the documentation does it state that
the fanout can only be used for Topics.

My apologies for not properly interpreting the purpose of the fanout and
thus not using it in a logical manner; however, we do have a need to have a
producer "replicate" a message to two completely different systems and we
want the message consumed only once on each of those systems. The two
systems are completely separate from one another (i.e., the brokers and
consumers on those systems are not interconnected).  




> AMQ 5.0 Fanout Regression  
> ---------------------------
>
>                 Key: AMQ-1464
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1464
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.0.0
>         Environment: AMQ 5.0 - the 10/10/07 SNAPSHOT
>            Reporter: Joe Fernandez
>            Assignee: Hiram Chirino
>             Fix For: 4.1.1
>
>
> On 4.1.1, the fanout transport works as expected. My producer is fanning out message
sends (queues) to two unrelated message brokers and clients connected to both those brokers
get the messages.
> However, when I run the same exact test under 5.0 (the 10/10 SNAPSHOT), fanout no longer
works as expected   Only the 5.0 broker that my producer first connects with gets the messages.
The second broker never gets the messages and hurls this exception.
> ERROR Service      - Async error occurred: java.lang.IllegalStateException: Cannot remove
a consumer that had not been registered: ID:DIEGO-3739-1192470567781-0:0:-1:1
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered:
ID:DIEGO-3739-1192470567781-0:0:-1:1
>         at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(
> TransportConnection.java:547)
>         at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
>         at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:281)
>         at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
>         at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67)
>         at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:134)
>         at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:124)
>         at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
>         at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:183)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:170)
>         at java.lang.Thread.run(Thread.java:595)
> Joe
>  

-- 
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