[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated JBOSGI-519:
----------------------------------

    Fix Version/s: Awaiting WildFly Support

    
> InitialContextFactoryBuilder already registered in AS
> -----------------------------------------------------
>
>                 Key: JBOSGI-519
>                 URL: https://issues.jboss.org/browse/JBOSGI-519
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Enterprise OSGi, WildFly
>            Reporter: Thomas Diesler
>              Labels: jndi
>             Fix For: Awaiting WildFly Support
>
>
> In AS we see 
> {code}
> 09:59:52,782 INFO  [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set
> 	at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_29]
> 	at org.apache.aries.jndi.startup.Activator.start(Activator.java:76)
> 	at org.apache.aries.jndi.priv.Activator.start(Activator.java:38)
> 	at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300)
> 	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223)
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488)
> 	at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:44)
> 	at org.jboss.test.osgi.example.jndi.JNDITestCase.testOSGiNamingContext(JNDITestCase.java:91)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira