otbutz commented on issue #2647: URL: https://github.com/apache/activemq/issues/2647#issuecomment-6194183923
I gave it a shot and i fear this isn't going to be a simple fix. The ExceptionListener of the ActiveMQConnection created within the ActiveMQEndpointWorker would need to distinguish between a real connection error and a WorkRejectedException. Doing a full tear down of consumer, connection and session pool is probably a bad idea. We would also need to retain the connection somehow as a dump retry of `connectWork` is also going to obtain a new connection from the MessageResourceAdapter. As for ServerSessionImpl.start() we might want to have a dedicated session scoped retry path? -- 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
