remay commented on issue #1731: URL: https://github.com/apache/activemq/issues/1731#issuecomment-3983931133
> Also note that the exception handling on the DB failure does not end up logged because the catch clause re-throws the exception, but only AFTER the point that the deadlock occurs. > > (UPDATE: on further review of my notes, this may not be correct - the exception may be logged elsewhere; needs verification) @artnaseef In this particular case the IO Exception was logged (~15 minutes == tcp timeout + small amount after the TCP issue) and just before the deadlock occurred. I believe this is where it was logged within the JBDCMessageStore|::adMessage() method: https://github.com/apache/activemq/blob/main/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/JDBCMessageStore.java#L165 But I agree with you that other errors might not be logged if they triggered the same deadlock. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
