My guess on this one is that you are sending using the async send mode and
closing the connection very quickly after a send which results in an
incomplete frame on the wire.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AmqpProtocolException-Could-not-decode-AMQP
/AmqpProtocolException-Could-not-decode-AMQP-frame-tp4680794p4680826.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The error would see to indicate something like that is happening. Are
you sure your client isn't picking up a JMS library other than the one
you think
/AmqpProtocolException-Could-not-decode-AMQP-frame-tp4680794p4680904.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Does the error means that the client is sending different AMQP version
message than what ActiveMQ can understand. My understanding is that ActiveMQ
only supports AMQP 1.0.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AmqpProtocolException-Could-not-decode-AMQP-frame
-Could-not-decode-AMQP-frame-tp4680794.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
.2283324.n4.nabble.com/AmqpProtocolException-Could-not-decode-AMQP-frame-tp4680794.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
What versions ?
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter
Versions:
1. ActiveMQ - 5.9.1
2. Qpid Jms Client for AMPQ 1.0 - version 0.26
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AmqpProtocolException-Could-not-decode-AMQP-frame-tp4680794p4680798.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 05/01/2014 06:47 PM, gurilubana wrote:
Versions:
1. ActiveMQ - 5.9.1
2. Qpid Jms Client for AMPQ 1.0 - version 0.26
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AmqpProtocolException-Could-not-decode-AMQP-frame-tp4680794p4680798.html
Sent from the ActiveMQ - User
