[ 
https://issues.apache.org/jira/browse/ARTEMIS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586815#comment-15586815
 ] 

ASF GitHub Bot commented on ARTEMIS-805:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/849

    ARTEMIS-805 old JMS clients failing on new broker

    Old JMS clients are getting a CCE related to 
SessionBindingQueryResponseMessage

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-805

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/849.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #849
    
----
commit 3f4d7ee7bf6009fb14f9caea0dd2204860a9ddaf
Author: Tomas Hofman <thof...@redhat.com>
Date:   2016-10-17T14:31:27Z

    ARTEMIS-805 old JMS clients failing on new broker
    
    Old JMS clients are getting a CCE related to 
SessionBindingQueryResponseMessage

----


> ClassCastException: SessionBindingQueryResponseMessage_V2 cannot be cast to 
> SessionBindingQueryResponseMessage_V3
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-805
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-805
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Tomas Hofman
>            Assignee: Justin Bertram
>
> If Artemis 1.4.0 standalone JMS client tries to connect to 1.1.0 server then 
> ClassCastException is trhown during creating of producer on session. 
> Client logs following error:
> {code}
> WARN: AMQ212052: Packet 
> PACKET(SessionBindingQueryResponseMessage_V2)[type=-8, channelID=15, 
> packetObject=SessionBindingQueryResponseMessage_V2, exists=true, 
> queueNames=[jms.queue.InQueue], autoCreateJmsQueues=false] was answered out 
> of sequence due to a previous server timeout and it's being ignored
> java.lang.Exception: trace
>       at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:386)
>       at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:307)
>       at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.addressQuery(ActiveMQSessionContext.java:296)
>       at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.addressQuery(ClientSessionImpl.java:360)
>       at 
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:305)
>       at ProducerTransSession.run(ProducerTransSession.java:53)
> Producer got exception and ended:java.lang.ClassCastException: 
> org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionBindingQueryResponseMessage_V2
>  cannot be cast to 
> org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionBindingQueryResponseMessage_V3
> {code}
> This is breaking backward compatibility of JMS clients.
> This was originally reported as JBoss EAP issue: 
> https://issues.jboss.org/browse/JBEAP-6317



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to