I tried to connect to the jmx interface. A custom jmx transport is needed, so I downloaded WildFly's latest version and launch the provided jconsole.sh. But the connection fails with the message in server.log: 2016-05-03 11:17:17,995 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-1-thread-1) Unexpected internal error: java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1234) [rt.jar:1.7.0_101] at java.util.regex.Matcher.reset(Matcher.java:308) [rt.jar:1.7.0_101] at java.util.regex.Matcher.<init>(Matcher.java:228) [rt.jar:1.7.0_101] at java.util.regex.Pattern.matcher(Pattern.java:1088) [rt.jar:1.7.0_101] at org.jboss.as.jmx.BlockingNotificationMBeanServer.isInExposedModelControllerDomains(BlockingNotificationMBeanServer.java:319) [wildfly-jmx-8.2.1.Final.jar:8.2.1.Final] at org.jboss.as.jmx.BlockingNotificationMBeanServer.addNotificationListener(BlockingNotificationMBeanServer.java:183) [wildfly-jmx-8.2.1.Final.jar:8.2.1.Final] at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.addNotificationListener(ServerProxy.java:208) at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.access$3200(ServerProxy.java:201) at org.jboss.remotingjmx.protocol.v2.ServerProxy$AddNotificationListenerHandler.handle(ServerProxy.java:430) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75) [wildfly-jmx-8.2.1.Final.jar:8.2.1.Final] at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70) [wildfly-jmx-8.2.1.Final.jar:8.2.1.Final] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_101] at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_101] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [wildfly-controller-8.2.1.Final.jar:8.2.1.Final] at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70) [wildfly-jmx-8.2.1.Final.jar:8.2.1.Final] at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_101] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_101]
The provided /usr/share/ovirt-engine-wildfly/bin/jconsole.sh don't work either, but return no messages or log any where. If I launch it as root, it can connect directly to the pid, but just generate a stack in console.log and then fails the connection.
Moving to first RC, since things should not be targeted to second one at this point.
Ondro, could you please try to investigate status of using jconsole in WildFly 10 used in oVirt 4.0?
When connecting to PID, do you run jconsole as same user as user which owns the process you are trying to attach?
service:jmx:http-remoting-jmx://localhost:8706/ works fine for me with Wildfly10 and Java 8.
When you have a identity problem using jconsole with usual connectors, connection is simply denied. I don't get a full stack exception. But I will try again with latest 3.6.6
Ok, works for me on a 3.6.6 with an URL service:jmx:remote+http://host:port (http-remoting-jmx is deprecated) and a code with dependency in the pom.xml : <dependency> <groupId>org.jboss.remotingjmx</groupId> <artifactId>remoting-jmx</artifactId> <version>2.0.1.Final</version> </dependency>
More informations, If i connect with custom java code, from a remote workstation, that just does connection.getMBeanCount(); it succeeds. It I connect from the same workstation, using jconsole with $JAVA_HOME/bin/jconsole -J-Djava.class.path=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/jconsole.jar:jmxcli.jar I still get the same error stack. The remote workstation is a mac os 10.11 and the jvm used is: $ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home I have still not migrated to ovirt 4.0, I think I will wait 4.1.
Closed due to capacity, if still reproduce, please reopen.