[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-293) Cannot start example-jndi on Felix

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Tue Mar 30 11:39:37 EDT 2010


     [ https://jira.jboss.org/jira/browse/JBOSGI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-293:
----------------------------------

    Fix Version/s:  JBossOSGi 1.0.x
                       (was: JBossOSGi 1.0.0 Beta7)


> Cannot start example-jndi on Felix
> ----------------------------------
>
>                 Key: JBOSGI-293
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-293
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Integration (Felix)
>            Reporter: Thomas Diesler
>             Fix For:  JBossOSGi 1.0.x
>
>
> Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
> 	at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1682)
> 	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1753)
> 	at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1108)
> 	at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1098)
> 	at javax.naming.InitialContext.createSubcontext(InitialContext.java:464)
> 	at org.jboss.test.osgi.example.jndi.bundle.JNDIExampleActivator.start(JNDIExampleActivator.java:46)
> 	at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:640)
> 	at org.apache.felix.framework.Felix.activateBundle(Felix.java:1700)
> 	at org.apache.felix.framework.Felix.startBundle(Felix.java:1622)
> 	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
> 	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
> 	at org.apache.aries.jmx.framework.Framework.startBundle(Framework.java:298)
> Caused by: java.lang.ClassNotFoundException: org.jnp.server.NamingServer_Stub (no security manager: RMI class loader disabled)
> 	at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:375)
> 	at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
> 	at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
> 	at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91)
> 	at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-osgi-issues mailing list