JMX NameNotFoundException exception regression in EAP 6.1 Alpha?

[alexc099]

It sure looks like this bug is back in EAP 6.1 Alpha. (That's assuming it ever left. Downloading AS 7.1.2 Final is tricky to say the least.) Anyone else hitting it?

Also, in spite of the fact that it says it is fixed in AS 7.1.2 I am still hitting it in AS 7.1.3 (EAS 6.0.1).

And AS 7.1.2 (EAS 6.0.0)

[alexc099]

Ah, I see the issue now. From the bug report:

"The reason it works for me in 7.1.0.Final is that JBoss uses the remoting-jmx JSR-160 connector now, which basically bypasses the problem when connecting to another JBoss server. However, the problem is still very much there when connecting to any other servers/apps over the standard RMI connector."

So, essentially it's not possible for an application running on AS 7 to connect to another server or application via JMX. This pretty much kills our evaluation of AS 7 in under a day, which is convienent I suppose.

[jaikiran]

Alex, could you add a bit more details on what exact problem you are running into?

[alexc099]

Sure. I've got an application that I've tried deploying on AS 7.1.0 Final, AS 7.1.1 Final, AS 7.1.2 (EAP 6.0), AS 7.1.3 (EAP 6.0.1) and EAP 6.1 Alpha. On all of them when my application tries to connect to an external, non JBoss server via JMX I get an IOException caused by a javax.naming.NameNotFoundException with the message rmi://10.0.2.159:4001/jmxrmi -- service jboss.naming.context.java.rmi:."10.0.2.159:4001".jmxrmi. This code works fine in a vanilla Tomcat deployment.

From what I can tell in reading the comments in the JIRA the fix only addressed connecting to another JBoss server. Connecting to a non-JBoss server is still an issue. The workaround suggested in the comments would require us to patch JDK6 which won’t fly in production.

[alexc099]

Linked to related issues.

[baranowb]

Which part of workaround would require a patchwork in JDK6?