Hi. today I experienced that when sending messages to the broker sending failed with the response "illegal-argument: Value for replyText is too large(320)". In a thread from November 2018 (named qpid-cpp-0.35 errors) I see other users getting the same error message when unexpected things happen in the broker.
In my case this happened due to an inproper shutdown causing the queue to be "operational", but not possible to write dusable messages to. In the syslog I found error like: 2019-05-14 09:04:28 [Broker] warning Exchange some.topic cannot deliver to queue 440d04db-7fb6-3424-a83c-b70014fa32a0: Queue 440d04db-7fb6-3424-a83c-b70014fa32a0: MessageStoreImpl::store() failed: jexception 0x010b LinearFileController::getCurrentSerial() threw JERR__NULL: Operation on null pointer (/var/tmp/portage/net-misc/qpid-cpp-1.39.0/work/qpid-cpp-1.39.0/src/qpid/linearstore/MessageStoreImpl.cpp:1226) 2019-05-14 09:04:28 [Broker] error Connection exception: framing-error: Queue 440d04db-7fb6-3424-a83c-b70014fa32a0: MessageStoreImpl::store() failed: jexception 0x010b LinearFileController::getCurrentSerial() threw JERR__NULL: Operation on null pointer (/var/tmp/portage/net-misc/qpid-cpp-1.39.0/work/qpid-cpp-1.39.0/src/qpid/linearstore/MessageStoreImpl.cpp:1226) 2019-05-14 09:04:28 [Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:57954 closed by error: Queue 440d04db-7fb6-3424-a83c-b70014fa32a0: MessageStoreImpl::store() failed: jexception 0x010b LinearFileController::getCurrentSerial() threw JERR__NULL: Operation on null pointer (/var/tmp/portage/net-misc/qpid-cpp-1.39.0/work/qpid-cpp-1.39.0/src/qpid/linearstore/MessageStoreImpl.cpp:1226)(501) 2019-05-14 09:04:28 [Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:57954 closed by error: illegal-argument: Value for replyText is too large(320) For a client, just getting "illegal-argument: Value for replyText is too large" back as an error when sending is not the most useful info and I suspect, especially after reading the mentioned thread from November, there might be a bug in how the error responses to the client is generated causing the actual error to be masked by another error. Also, there seems to be a possibility that the Qpid broker will start wth broken queues, causing it to fail only when messages are written to that queue, including some null pointer problems. Are any of these known issues or is it the expected behavior? -- Thanks, -- Paul
