On 14/05/2019 10:46 am, Pål Skjager Løberg wrote:
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?
No, neither of these is the correct behaviour.
I have committed a fix for the first issue:
https://issues.apache.org/jira/browse/QPID-8313
For the issue with the journal recovery, I'd need to defer to the
expert. Kim, can you recommend any diagnostics to figure out what would
cause the problems in the queues on recovery? i.e. errors such as:
jexception 0x010b LinearFileController::getCurrentSerial() threw
JERR__NULL: Operation on null pointer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
