Ondrej Chaloupka created REMJMX-168: --------------------------------------- Summary: JMX proxy connection is released sooner than the client asks for closing it Key: REMJMX-168 URL: https://issues.redhat.com/browse/REMJMX-168 Project: Remoting JMX Issue Type: Bug Components: Connection Affects Versions: 3.0.3.Final, 3.0.2.Final Reporter: Ondrej Chaloupka Assignee: Darran Lofthouse We started to hit the issue on Narayana transaction recovery testing. Reported as JBEAP-18109. It seems to be caused by changes made at REMJMX-160. What we hit: It seems the JMX connection *is closed* too soon - before the client decides to release it. When client creates a JMX proxy, then does not use it for a while and then it runs the JMX calls again such attempt fails. Our test does: * The transaction recovery test creates the JMX proxy at some point to verify content of object store. * Then there is some idle time where the JMX proxy is not utilized. * When the testsuite tries to verify the content of object store once again on the same JMX proxy that attempt fails. When I used the {{Executors.newFixedThreadPool}} (https://github.com/ochaloup/remoting-jmx/commit/7ec37c8a09f4d8229ee8263ad...) the issue disappeared. -- This message was sent by Atlassian Jira (v7.13.8#713008)