Re: Error while trying to create a connection on a remote open-jms

That stack trace is not particularly helpful. Can you print out the root 
nested exception?

Gehl, Pascal wrote:
> Hi,
>
> I get this exception when trying to create a connection on a open-jms
> installed on a different machine in the same LAN.
>
>  javax.naming.CommunicationException: Failed to get registry service for
> URL: rmi://158.228.178.232:1099 [Root exception is
> java.rmi.ConnectIOException: Failed to create connection; nested
> exception is: 
> 	org.exolab.jms.net.connector.ResourceException: Failed to create
> invocation handler]
> 	at
> com.adopt.core.common.jms.JMSCommunicator.setListener(JMSCommunicator.ja
> va:615)
> 	at
> com.adopt.core.common.jms.JMSCommunicator.<init>(JMSCommunicator.java:14
> 5)
> 	at
> com.adopt.core.common.jms.SecureJMSCommunicator.<init>(SecureJMSCommunic
> ator.java:118)
> 	at
> com.adopt.core.client.communicator.ClientSecureJMSCommunicator.<init>(Cl
> ientSecureJMSCommunicator.java:104)
> 	at
> com.adopt.core.client.communicator.ClientSecureJMSCommunicator.<init>(Cl
> ientSecureJMSCommunicator.java:71)
> 	at
> com.adopt.core.client.communicator.SecureClientJMSFactory.get(SecureClie
> ntJMSFactory.java:93)
> 	at
> com.adopt.core.client.cache.ClientCacheMessageListener.buildCommunicator
> (ClientCacheMessageListener.java:61)
> 	at
> com.adopt.core.client.cache.ClientCacheMessageListener.activate(ClientCa
> cheMessageListener.java:75)
> 	at
> com.adopt.core.client.cache.DefaultClientCache.instance(DefaultClientCac
> he.java:89)
> 	at
> com.adopt.core.client.communicator.DefaultClientJMSDelegator.<init>(Defa
> ultClientJMSDelegator.java:66)
> 	at
> com.adopt.core.client.communicator.DefaultClientJMSDelegator.<clinit>(De
> faultClientJMSDelegator.java:64)
> 	at
> com.adopt.afc.client.planner.plugins.category.DefaultClientCategoryManag
> er.<init>(DefaultClientCategoryManager.java:34)
> 	at
> com.adopt.afc.client.planner.plugins.category.DefaultClientCategoryManag
> er.<clinit>(DefaultClientCategoryManager.java:36)
> 	at
> com.adopt.afc.client.planner.plugins.employee.EmployeeFilter.<init>(Empl
> oyeeFilter.java:46)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) 
>
> Weird thing is that connecting to the exact same open-jms installation
> on my desktop works perfectly.
>
> The openjms.policy contains.
>
> // grant all users all permissions. This should be modified for
> deployment
> grant {
>   permission java.security.AllPermission;
> };
>
> thanks 
> Pascal Gehl
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> openjms-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openjms-user
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV