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

Gordon Sim updated PROTON-62:
-----------------------------
    Component/s:     (was: proton-c)

This is still an issue for proton-c, so I have cloned a new JIRA for tracking 
that: PROTON-723

> Proton(-j) does not support attaching to the transaction coordinator
> --------------------------------------------------------------------
>
>                 Key: PROTON-62
>                 URL: https://issues.apache.org/jira/browse/PROTON-62
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>            Reporter: Hiram Chirino
>            Assignee: Rafael H. Schloming
>              Labels: api, transactions
>
> Got at:
> Caused by: java.lang.ClassCastException: 
> org.apache.qpid.proton.type.transaction.Coordinator cannot be cast to 
> org.apache.qpid.proton.type.messaging.Target
>       at 
> org.apache.qpid.proton.engine.impl.TransportImpl.handleAttach(TransportImpl.java:977)
>       at 
> org.apache.qpid.proton.engine.impl.TransportImpl.handleAttach(TransportImpl.java:59)
>       at org.apache.qpid.proton.type.transport.Attach.invoke(Attach.java:389)
>       at 
> org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:1090)
>       at 
> org.apache.qpid.proton.engine.impl.FrameParser.input(FrameParser.java:409)
>       at 
> org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:156)
>       at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:120)
>       ... 5 more
> and I think the frame being processed was the following (hex):
> 00 00 00 6a 02 00 00 01 00 53 12 c0 5d 0a a1 11 74 78 6e 43 
> 6f 6e 74 72 6f 6c 6c 65 72 4c 69 6e 6b 43 42 50 00 50 00 00 
> 53 28 c0 01 00 00 53 30 c0 35 01 e0 32 02 a3 17 61 6d 71 70 
> 3a 6c 6f 63 61 6c 2d 74 72 61 6e 73 61 63 74 69 6f 6e 73 17 
> 61 6d 71 70 3a 6d 75 6c 74 69 2d 74 78 6e 73 2d 70 65 72 2d 
> 73 73 6e 40 40 43 



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

Reply via email to