[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ] Abhishek Apoorva commented on REMJMX-84: ---------------------------------------- we took below mentioned steps to replace the xion jar files. We are using single jboss-client jar to connect to different jboss server. 1. we deleted xion directory (including files and all its subfolder) from d:/client/jboss-client.jar. 2. copied the xnio-api-3.2.2.Final,xnio-nio-3.2.2.Final jar files at d:/client/ location. Then we have started jboss server and our client application. But still after some time we have found that we are intermittently getting "java.lang.RuntimeException: Operation failed with status WAITING" exception on client side. We have also not able to see any concrete error or useful logs on jboss side. If server is not able to create a jmx connection then I think it should log error with some meaningful data. Our application : Our application is periodically connecting to Jboss-jmx server (Let say in every 60 seconds). Our appplication referring to jboss-client-jar that resides on d:/client/ location. 1. We are trying to get an object of connecting JMXConnector using JMXConnectorFactory. 2. we are getting value of some specified mbeans. 3. After this we are disconnecting our jmx connector. 4. same steps are repeated in every 60 seconds. Sample program to fetch mBean information. void createConnection(String port,String name) { Hashtable environment = new Hashtable(); environment.put("remote.connection.default.connect.timeout", 5000); String urlString = "service:jmx:remoting-jmx://localhost:"+port; JMXConnector connector=null ; try { JMXServiceURL serviceURL = new JMXServiceURL(urlString); connector = JMXConnectorFactory.connect(serviceURL, environment); logger.log(0,new Date()+" successful "+name); // Fetching mBean information here. } catch (Exception e) { logger.logStackTrace(0, e); } finally{ if(connector!=null) { try { connector.close(); logger.log(0,"closing connection"); } catch (IOException e) { logger.logStackTrace(0, e); } } } } -- This message was sent by Atlassian JIRA (v6.2.3#6260)