connect through JNDI Jboss AS 7.1.1| JBoss.org Content Archive (Read Only)

1 2 Previous Next 26 Replies Latest reply on Sep 18, 2012 9:30 AM by venkman Go to original post

15. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 5, 2012 6:50 AM (in response to nickarls)

Hi Nicklas,
Then what do you propose me to do?
Actions
16. Re: connect through JNDI Jboss AS 7.1.1

nickarls Sep 5, 2012 6:59 AM (in response to micros)

Wait until Jaikiran drops by and gives you the correct solution ;-)

What are you trying to do with the remote connection?
Actions
17. Re: connect through JNDI Jboss AS 7.1.1

jaikiran Sep 5, 2012 7:20 AM (in response to micros)

Like Nicklas says, what exactly are you doing in the client program? Can you show us some of the code on the client side and what it's trying to do?
Actions
18. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 5, 2012 7:23 AM (in response to nickarls)

We have tools for performance testing Silk Performer we trying to can connect to Jboss Jmx and draw graph.
i must conect from client machine to remote server where is installed Jboss
i have filed where i can add aditional classpath field for Registry lookup: JNDI, protocol i set remote , Context factory: org.jboss.naming.remote.client.InitialContextFactory
I have fileds where i set path to java and field where i set path to jboss server. All this create my URL remote://hostname:port and i set credentials and try to login

I don't write own client
Actions
19. Re: connect through JNDI Jboss AS 7.1.1

jaikiran Sep 5, 2012 7:29 AM (in response to micros)

Anton Yanchev wrote:

We have tools for performance testing Silk Performer we trying to can connect to Jboss Jmx and draw graph.
i must conect from client machine to remote server where is installed Jboss
Here's an example (which remotely uses JMX to get HornetQ statistics) http://middlewaremagic.com/jboss/?p=1940. See if that helps.
Actions
20. Re: connect through JNDI Jboss AS 7.1.1

jaikiran Sep 5, 2012 7:33 AM (in response to micros)

Anton Yanchev wrote:

I don't write own client
Oh so you mean, you have some kind of GUI or other such tool (http://www.borland.com/products/silkperformer/) which asks for the params to connect to the server? I haven't used that tool but if it uses JMX then the URL to use is

service:jmx:remoting-jmx://" + host + ":" + port;
Take a look at the previous article that I pointed you to, to understand what the port value should be.
Actions
21. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 5, 2012 7:35 AM (in response to jaikiran)

Yes that is a tool
Actions
22. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 5, 2012 8:30 AM (in response to jaikiran)

i read this article how to enable 4447 port and i have tried service:jmx:remoting-jmx://" + host + ":" + port; but i received this 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:684)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
          at javax.naming.InitialContext.init(InitialContext.java:242)
          at javax.naming.InitialContext.<init>(InitialContext.java:216)
          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:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:601)
          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
          at sun.rmi.transport.Transport$1.run(Transport.java:177)
          at sun.rmi.transport.Transport$1.run(Transport.java:174)
          at java.security.AccessController.doPrivileged(Native Method)
          at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
          at java.lang.Thread.run(Thread.java:722)
Caused by: org.jboss.remoting3.UnknownURISchemeException: No connection provider for URI scheme "service" is installed
          at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:265)
          at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
          at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
          at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
          at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
          at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
          at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
          at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
          at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
          ... 22 more

          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:353)
          at sun.rmi.transport.Transport$1.run(Transport.java:177)
          at sun.rmi.transport.Transport$1.run(Transport.java:174)
          at java.security.AccessController.doPrivileged(Native Method)
          at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
          at java.lang.Thread.run(Thread.java:722)
          at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
          at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
          at sun.rmi.server.UnicastRef.invoke(Unknown Source)
          at com.segue.monitoring.jmx.jboss.datasource.RemoteDataSource_Stub.bootstrap(Unknown Source)
          at com.segue.monitoring.jmx.common.client.RemoteDataSourceClient.bootstrap(RemoteDataSourceClient.java:265)
          at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:301)
Caused by: 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:684)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
          at javax.naming.InitialContext.init(InitialContext.java:242)
          at javax.naming.InitialContext.<init>(InitialContext.java:216)
          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:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:601)
          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
          at sun.rmi.transport.Transport$1.run(Transport.java:177)
          at sun.rmi.transport.Transport$1.run(Transport.java:174)
          at java.security.AccessController.doPrivileged(Native Method)
          at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
          at java.lang.Thread.run(Thread.java:722)
Caused by: org.jboss.remoting3.UnknownURISchemeException: No connection provider for URI scheme "service" is installed
          at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:265)
          at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
          at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
          at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
          at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
          at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
          at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
          at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
          at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
          ... 22 more

          at com.segue.monitoring.jmx.common.runtime.RemoteDataSourceBase.bootstrap(RemoteDataSourceBase.java:189)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:601)
          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
          at sun.rmi.transport.Transport$1.run(Transport.java:177)
          at sun.rmi.transport.Transport$1.run(Transport.java:174)
          at java.security.AccessController.doPrivileged(Native Method)
          at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
          at java.lang.Thread.run(Thread.java:722)
Actions
23. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 8, 2012 1:13 AM (in response to micros)

can some one help me with this exeception it's very imporant for me
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]

i have done research in internet but i didn't find anything
Actions
24. Re: connect through JNDI Jboss AS 7.1.1

venkman Sep 18, 2012 9:30 AM (in response to micros)

Exactly the same here.

Have you got a solution?

Edit: In my case, it was a wrong serverurl (no "remote://") . I'm migrating from 4 to 7 and there're so much changes... .
Actions
25. Re: connect through JNDI Jboss AS 7.1.1

micros Sep 18, 2012 9:25 AM (in response to venkman)

I didn't find solution
Actions
26. Re: connect through JNDI Jboss AS 7.1.1

venkman Sep 18, 2012 9:30 AM (in response to micros)

answer above mentioned.
Actions

1 2 Previous Next

Go to original post