Thursday, November 26, 2009

JRMC JRockit mission control, unable to connect console

still investigating on this problem, most likely I have not set -Xmanagement when running the WebLogic server... Thanks to the developers for the immense clarity of the error message.

Oh yes of course, you should change your startWebLogic.cmd adding
set JAVA_OPTIONS=%JAVA_OPTIONS% -Xmanagement:ssl=false,authenticate=false,port=7099

once you restart weblogic, you should see this:
[INFO ][mgmnt  ] Remote JMX connector started at address esp50ws112345:7099
[INFO ][mgmnt  ] Local JMX connector started

Of course make sure you specify 7099 (and NOT 7001) in the JRMC client new connection parameters.


This was the original error message:

Could not open Management Console for frparmat01.acme.dns:8765.
  com.jrockit.mc.rjmx.ConnectionException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
    java.io.EOFException]
    com.jrockit.mc.rjmx.ConnectionException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
        java.io.EOFException]
        at com.jrockit.mc.rjmx.ConnectionManager.connect(ConnectionManager.java:63)
        at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect(StartConsole.java:38)
        at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:74)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
        java.io.EOFException]
        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:229)
        at com.jrockit.mc.rjmx.internal.RJMXConnection.setupServer(RJMXConnection.java:537)
        at com.jrockit.mc.rjmx.internal.RJMXConnection.connect(RJMXConnection.java:144)
        at com.jrockit.mc.rjmx.internal.RJMXConnectorModel.establishConnection(RJMXConnectorModel.java:111)
        at com.jrockit.mc.rjmx.internal.RJMXConnectorModel.connect(RJMXConnectorModel.java:154)
        at com.jrockit.mc.rjmx.ConnectionManager.innerConnect(ConnectionManager.java:95)
        at com.jrockit.mc.rjmx.ConnectionManager.connect(ConnectionManager.java:61)
        ... 3 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
        java.io.EOFException]
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
        at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1817)
        at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1787)
        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:259)
        ... 10 more
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
        java.io.EOFException
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
        at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
        at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:93)
        ... 15 more
    Caused by: java.io.EOFException
        at java.io.DataInputStream.readByte(DataInputStream.java:243)
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
        ... 19 more

No comments: