can't connect remote to jconsole Jboss AS 7.1.1

[micros]

I have installed Jboss AS 7.1.1

i'm trying to connect remote to Jconsole with this URL service:jmx:remoting-jmx://<hostname>:9999

Interesting is that when i try to connect and i run jconsole from Jboss bin folder it's connect without problem

but when i have tried to connect from jconsole from Java/ bin folder stareted jconosle with the same url i can't connect

i have tried with port 4447 aslo. ii have created user and password with add-user.bat but i can't login

the strange is why with jboss jconsole i can connect , but with java jconsole i can't

[dlofthouse]

Not strange at all   The jconsole script we supply adds the required jars for the connection to the classpath so when you switch back to the vanila script you no longer have the reuqired jars on the classpath.

I would suggest unzipping a JBoss installation on the client machine and trying again with our supplied scripts.

[micros]

But then why when i use jboss as 6.1 i can login with same url from jconsole in java folder and from jconsole in jboss folder. but in jboss as 7.1.1 I can't

[micros]

Hi Darran,

Thank you for your answer but i have aditional questons

"The jconsole script we supply adds the required jars for the connection to the classpath so when you switch back to the vanila script you no longer have the reuqired jars on the classpath."

if i want to connect from jconsole or other clinet remotely which  jars i must add to classpath and sorry for my stupid  question but i'm a beginer in Java, what i must write and where to add these jars to classpath?

[dlofthouse]

JBoss AS 6 is still using plain RMI for jconsole so doens't require different jars but in AS 7 the native communications now use Remoting.

When you start the jconsole script from within the JBoss AS 7 distribution there should be a message output showing the jars on the classpath - if not have a look within the script itself and there is a list of the modules that we search for jars to build up a classpath.

[micros]

when I ran jconsole from Jboss folder in cmd it showed list of these jar files

C:\Java\jdk1.6.0_33\lib\jconsole.jar;C:\Java\jdk1.6.0_33\lib\tools.jar;C:\jboss-as-7.1.1.Final\modules\org\jboss\remoting3\remoting-jmx\main\remoting-jmx-1.0.2.Final.jar;

C:\jboss-as-7.1.1.Final\modules\org\jboss\remoting3\main\jboss-remoting-3.2.3.GA.jar;C:\jboss-as-7.1.1.Final\modules\org\jboss\logging\main\jboss-logging-3.1.0.GA.jar;

C:\jboss-as-7.1.1.Final\modules\org\jboss\xnio\main\xnio-api-3.0.3.GA.jar;C:\jboss-as 7.1.1.Final\modules\org\jboss\xnio\nio\main\xnio-nio-3.0.3.GA.jar;

C:\jboss-as-7.1.1.Final\modules\org\jboss\sasl\main\jboss-sasl-1.0.0.Final.jar;

C:\jboss-as-7.1.1.Final\modules\org\jboss\marshalling\main\jboss-marshalling-1.3.11.GA.jar;C:\jboss-as-7.1.1.Final\modules\org\jboss\marshalling\river\main\jboss-marshalling-river-1.3.11.GA.jar

if am I right i must add these jar files to clssspath of default jconsole

but default jconsole from Java is starts from jconsole.exe when is bat file it's easy to add but where i must add these jar files to this jconosole.

[micros]

Hi Darran,

I added all jar and module files to classpath, but i still can't login  i received this exceptio, but interesting is that i'm trying to connect with host name but in the exception it shows that try to connect to localhost that isn't correct

com.segue.monitoring.jmx.common.exception.RtException: Unable to connect

          at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:312)

Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:

          java.net.ConnectException: Connection refused: connect

          at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)

          at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)

          at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)

          at sun.rmi.server.UnicastRef.newCall(Unknown Source)

          at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)

          at com.segue.monitoring.jmx.common.client.RemoteDataSourceClient.connect(RemoteDataSourceClient.java:216)

          at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:300)

Caused by: java.net.ConnectException: Connection refused: connect

          at java.net.PlainSocketImpl.socketConnect(Native Method)

          at java.net.PlainSocketImpl.doConnect(Unknown Source)

          at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

          at java.net.PlainSocketImpl.connect(Unknown Source)

          at java.net.SocksSocketImpl.connect(Unknown Source)

          at java.net.Socket.connect(Unknown Source)

          at java.net.Socket.connect(Unknown Source)

          at java.net.Socket.<init>(Unknown Source)

          at java.net.Socket.<init>(Unknown Source)

          at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)

          at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)

          ... 7 more

[dlofthouse]

To get this to work for you I would really suggest taking a JBoss AS7 installation and unzipping it on the client machine so that you can at least use that to establish the connection and verify that the remote connectivity is working for you.

Now for this last error - I don't recognise the package but it does seem as though you may have something else also integrating with jconsole - what URL are you using?  Are you using a Remoting-JMX URL?  If so this other library could be intercepting the attempt to connect.

[micros]

I'm trying to connect remotely from SIlkPerformer this is our product for performance testing. I added as a predifined data source .

I use this URL service:jmx:remoting-jmx://hostname:9999

when i try to connect it has and other parameters like a

Registry lookup: JSR-160/RMI

Protocol: i set remote for protocol

Context factory: i added org.jboss.naming.remote.client.InitialContextFactory

Connector name: jmx/rmi/RMIAdaptor

all these parameters creates this URL service:jmx:remoting-jmx://hostname:9999

i also added to classpat all neede jars from jconsole starting which i saw

when i added all needed jars i received other strange exception

com.segue.monitoring.jmx.common.exception.RtException: Unable to connect
at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:312)
Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Failed to create remoting connection
javax.naming.NamingException: Failed to create remoting connection [Root exception is org.jboss.remoting3.UnknownURISchemeException: No connection provider for URI scheme "service" is installed]
at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:121)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.segue.monitoring.jmx.common.runtime.DataSourceBase.createContext(DataSourceBase.java:41)
at com.segue.monitoring.jmx.jboss.datasource.JBossDataSource.bootstrap(Unknown Source)
at com.segue.monitoring.jmx.common.runtime.RemoteDataSourceBase.bootstrap(RemoteDataSourceBase.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)