On 12/10/18 20:43, areddy wrote:
Oct 12 14:08:20 chester-2932397692-1zrnb chester-job-worker
[0x559f87f2e4f0]:0 <- @close(24) [error=@error(29)
[condition=:"amqp:decode-error", description="Could not decode AMQP frame:
hex:
0000013202000000005314d0000000120000000452007000000128a00332393752000053704500537345005377b1000001007b227061796c6f6164223a207b2274797065223a202263616c6c222c202272656d6f74655f6964223a202243413033393031393564643461333539313934386165373966623337333238366265222c202264617461223a207b2274797065223a202263616c6c222c20226964223a203235323833327d7d2c2022637265617465644174223a2022323031382d31302d31325431383a30383a31332e373035303030222c20226e616d65223a20226c696e6b5f6d657373616765222c20226964223a202236613938373635642d343762662d346636622d613165612d353438633238373764363964222c2022636f7272656c6174696f6e4964223a206e756c6c7d"]]
Oct 12 14:08:20 chester-2932397692-1zrnb chester-job-worker ERROR
ERROR:proton:Could not decode AMQP frame: hex:
0000013202000000005314d0000000120000000452007000000128a00332393752000053704500537345005377b1000001007b227061796c6f6164223a207b2274797065223a202263616c6c222c202272656d6f74655f6964223a202243413033393031393564643461333539313934386165373966623337333238366265222c202264617461223a207b2274797065223a202263616c6c222c20226964223a203235323833327d7d2c2022637265617465644174223a2022323031382d31302d31325431383a30383a31332e373035303030222c20226e616d65223a20226c696e6b5f6d657373616765222c20226964223a202236613938373635642d343762662d346636622d613165612d353438633238373764363964222c2022636f7272656c6174696f6e4964223a206e756c6c7d
Oct 12 14:08:20 chester-2932397692-1zrnb chester-job-worker
[0x559f87f2e4f0]:0 -> @close(24) []
Oct 12 14:08:20 chester-2932397692-1zrnb chester-job-worker
[0x559f87f2e4f0]: <- EOS
Oct 12 14:08:20 chester-2932397692-1zrnb chester-job-worker
[0x559f87f2e4f0]: -> EOS
I am not seeing any connection_closed or transport_error events, so i'm
unable to cleanup/reconnect properly.
What events is my MessageHandler supposed to receive when the connection is
closed by remote ?
on_connection_error should be called for the close with error
Why does activemq randomly complain about frames ? Is there something wrong
with the frame ?
Based on the hex included in the error on close, the frame looks fine to
me. (You could run wireshark to get a second opinion).
You say it is 'randomly' closing the connection. Does that mean that
sometimes similarly structured messages are successfully sent and
accepted by the broker?
It is using the list0 type (i.e. a code for an empty list) for
properties and header. I wonder if that is causing problems on the other
side. (You could try adding a property and e.g. a ttl to it and see if
that alters anything. Of course if other similar messages are succeeding
then that is unlikely to be the issue).
What version of activemq are you using?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
