[JBoss JIRA] Created: (JBOSGI-406) NPE in AbstractDeployableContainer.uninstallSupportBundles with Equinox
by Thomas Diesler (JIRA)
NPE in AbstractDeployableContainer.uninstallSupportBundles with Equinox
-----------------------------------------------------------------------
Key: JBOSGI-406
URL: https://jira.jboss.org/browse/JBOSGI-406
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Caused by: java.lang.NullPointerException
at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.getBundle(EmbeddedDeployableContainer.java:214)
at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.getBundleState(EmbeddedDeployableContainer.java:181)
at org.jboss.arquillian.osgi.internal.AbstractDeployableContainer.uninstallBundleList(AbstractDeployableContainer.java:145)
at org.jboss.arquillian.osgi.internal.AbstractDeployableContainer.uninstallSupportBundles(AbstractDeployableContainer.java:97)
at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.undeploy(EmbeddedDeployableContainer.java:122)
at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:61)
at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:47)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBOSGI-282) Review DEBUG level logging volume
by Thomas Diesler (JIRA)
Review DEBUG level logging volume
---------------------------------
Key: JBOSGI-282
URL: https://jira.jboss.org/jira/browse/JBOSGI-282
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.x
http://blogs.jboss.org/blog/dimitris/2005/04/01/AC08547736BD16504BEC955AE...
Another factor that isDebugEnabled() has been abused is due to the fact that in many cases we (developers) have used DEBUG for high traffic logging, that should really be TRACE. The reason being, we (developers) are usually lazy to enable the TRACE level in log4j.xml while developing, and we prefer to just use debug() instead, that we know it will work by default!
"If the user doesn't like this, she can turn if off", while the idea should really be, "I need to enable TRACE while I do development, and save server.log from being filled up with garbage, and the user from getting lost inside my verbose traces".
* ERROR - A definite problem
* WARN - Likely a problem, but can live with it
* INFO - Common notifications, lifecycle stuff
* DEBUG - Low volume debug
* TRACE - High volume debug
--
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
13 years, 8 months
[JBoss JIRA] Created: (JBOSGI-331) Start Level TCK Failure: testActivatorChangeBundleStartLevel()
by David Bosschaert (JIRA)
Start Level TCK Failure: testActivatorChangeBundleStartLevel()
--------------------------------------------------------------
Key: JBOSGI-331
URL: https://jira.jboss.org/browse/JBOSGI-331
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.0.0 Beta8
Reporter: David Bosschaert
The following Start Level Service TCK test fails: org.osgi.test.cases.startlevel.junit.StartLevelControl.testActivatorChangeBundleStartLevel()
This is caused by a bundle which increases its own start level in the BundleActivcator.start(). This should cause the bundle to get stopped (on a different thread), but because the starting of the bundle hasn't finished yet the stop() seems to get ignored which causes the test to fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months