[
https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on REMJMX-84:
----------------------------------------
Firstly if you are a supported customer I would suggest raising a support case through the
customer portal, the support engineers will be able to work with you to perform further
diagnostics on exactly where time is being spent.
However, as a bug report the information supplied here up until this point is extremely
vague - we have a generic error message that tells us a time out has occurred and a vague
description as to how that error is being experienced.
If you are able to reproduce on a clean WildFly 8 installation and provide some clear
steps as to how to reproduce this - ideally with a sample client then I can take a further
look. But at this point the cause of your delay could just as easily be something
specific to your own installation, for all I know garbage collection could be occurring at
the time you get the intermittent time out.
Finally if you are not able to describe steps to reproduce a forum post may be the best
way to ask for some community support in getting to the bottom of the delayed requests.
Jboss JMX: Operation failed with status WAITING
------------------------------------------------
Key: REMJMX-84
URL:
https://issues.jboss.org/browse/REMJMX-84
Project: Remoting JMX
Issue Type: Bug
Environment: jboss-as-7.1.1.Final on windows server
Reporter: Abhishek Apoorva
Assignee: Darran Lofthouse
Fix For: 2.0.1.CR1
Version : jboss-as-7.1.1.Final on windows server
I am getting below mentioned strange issue intermittently while fetching
Jboss JMX Mbean.
Can anyone help me to find the real cause of the issue? Secong thing is why it is coming
intermittently either it should come always or it should not come at all.
JMXConnectorFactory.connect(serviceURL, environment);
While executing above mentioned line system is throwing below mentioned exception.
{noformat}
May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with
status WAITING
at
org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
at
com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
at
com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
at
com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
at
com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
at
com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
at java.lang.Thread.run(Unknown Source)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)