[JBoss JIRA] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS
by Thomas Diesler (JIRA)
Thomas Diesler created JBOSGI-519:
-------------------------------------
Summary: 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 Services
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.2
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBOSGI-545) Uninstalling last user bundle stops Framework.INIT service
by Thomas Diesler (JIRA)
Thomas Diesler created JBOSGI-545:
-------------------------------------
Summary: Uninstalling last user bundle stops Framework.INIT service
Key: JBOSGI-545
URL: https://issues.jboss.org/browse/JBOSGI-545
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.1.0
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.2.0
This leaves the Framework in an inconsistent state and may lead to
{code}
java.lang.NullPointerException
at org.jboss.osgi.framework.internal.FrameworkProxy.stopInternal(FrameworkProxy.java:228)
at org.jboss.osgi.framework.internal.FrameworkProxy.stop(FrameworkProxy.java:216)
at org.jboss.osgi.framework.internal.FrameworkProxy.stop(FrameworkProxy.java:196)
at org.jboss.test.osgi.framework.launch.PersistentBundlesTestCase.testInstalledBundle(PersistentBundlesTestCase.java:109)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBOSGI-547) ClassNotFoundException: org.osgi.service.log.LogService in org.apache.felix.eventadmin:1.2.6
by Thomas Diesler (JIRA)
Thomas Diesler created JBOSGI-547:
-------------------------------------
Summary: ClassNotFoundException: org.osgi.service.log.LogService in org.apache.felix.eventadmin:1.2.6
Key: JBOSGI-547
URL: https://issues.jboss.org/browse/JBOSGI-547
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.2.0
{code}
10:10:42,640 WARN [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011018: Error while firing service event REGISTERED for: ServiceState{service.id=46, objectClass=[org.osgi.service.log.LogReaderService]}: java.lang.NoClassDefFoundError: org/osgi/service/log/LogReaderService
at org.apache.felix.eventadmin.impl.adapter.LogEventAdapter.serviceChanged(LogEventAdapter.java:120)
at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:512)
at org.jboss.osgi.framework.internal.ServiceManagerPlugin.registerService(ServiceManagerPlugin.java:198)
at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:309)
at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:297)
at org.apache.felix.log.Activator.start(Activator.java:119)
at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:321)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:245)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:491)
at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:250)
at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:131)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months