[JBoss JIRA] (JBOSGI-560) NullPointerException in AbstractBundleState#ensureResolved if debug logging is enabled
10:23 a.m.
Rico Neubauer created JBOSGI-560:
------------------------------------
Summary: NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
10:48 a.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Rico Neubauer updated JBOSGI-560:
---------------------------------
Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/3 (was:
https://github.com/jbosgi/jbosgi-framework/pull/3)
Affects Version/s: JBossOSGi 1.3.0
Component/s: Core Framework
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.3.0
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
12:37 p.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-560:
---------------------------------------
Thanks Rico
Code in question
{code}
if (LOGGER.isDebugEnabled()) {
BundleWiring wiring = getCurrentBundleRevision().getWiring();
LOGGER.tracef("Required resource wires for: %s",
wiring.getResource());
for (Wire wire : wiring.getRequiredResourceWires(null)) {
LOGGER.tracef(" %s", wire);
}
LOGGER.tracef("Provided resource wires for: %s",
wiring.getResource());
for (Wire wire : wiring.getProvidedResourceWires(null)) {
LOGGER.tracef(" %s", wire);
}
}
{code}
It should really be LOGGER.isTraceEnabled(), but that's a minor thing.
More interesting is what could possibly lead to a condition where the wiring is null. Our
test suites run with DEBUG enabled and we don't see the NPE. Adding a not null check
is probably not the right fix.
The stack trace suggests that there is some dynamic import happening. Do you have a bundle
deployment that allows me to reproduce this issue?
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.3.0
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
12:39 p.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-560:
----------------------------------
Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/3 (was:
https://github.com/jbosgi/jbosgi-framework/pull/3)
Affects Version/s: (was: JBossOSGi 1.1.0)
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
12:39 p.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-560:
----------------------------------
Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/3 (was:
https://github.com/jbosgi/jbosgi-framework/pull/3)
Affects Version/s: JBossOSGi 1.1.0
(was: JBossOSGi 1.3.0)
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
9:10 a.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Rico Neubauer commented on JBOSGI-560:
--------------------------------------
Hi, will try to get more information on the wiring being null - do not have an easy bundle
deployment yet, which I could give as an example.
Nevertheless, since it _may_ occur, IMO different behavior depending on log levels is a
bad thing and should be avoided in any case - especially uncatched runtime exceptions.
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
9:18 a.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-560:
---------------------------------------
will try to get more information on the wiring being null
merci
should be avoided in any case
I work on the assumption that BundleRevision.getWiring() is guaranteed to be not null for
resolved bundles. Unless we decide to deviate from this guarantee we cannot have code
paths that work on the opposite.
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
10:16 a.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Rico Neubauer commented on JBOSGI-560:
--------------------------------------
De rien.
On first sight it looks like wiring is null for every fragment bundle. Will prepare an
easy host- and fragment-bundle to prove it.
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
3:21 p.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Rico Neubauer edited comment on JBOSGI-560 at 5/24/12 9:20 AM:
---------------------------------------------------------------
De rien.
On first sight it looks like wiring is null for every fragment bundle. Will prepare an
easy host- and fragment-bundle to prove it.
Edit: Not true in general. It does occur with fragments, however not reproducible with a
simple bundle+fragment. Will continue investigating.
was (Author: MrEasy):
De rien.
On first sight it looks like wiring is null for every fragment bundle. Will prepare an
easy host- and fragment-bundle to prove it.
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
6:34 p.m.
[
https://issues.jboss.org/browse/JBOSGI-560?page=com.atlassian.jira.plugin...
]
Thomas Diesler resolved JBOSGI-560.
-----------------------------------
Fix Version/s: (was: JBossOSGi 1.2.0)
Resolution: Cannot Reproduce Bug
Please reopen when we can reproduce this.
NullPointerException in AbstractBundleState#ensureResolved if debug
logging is enabled
--------------------------------------------------------------------------------------
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method
org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a
NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at
org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at
org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at
org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
4334
days inactive
4419
days old
jboss-osgi-issues@lists.jboss.org
10 comments
2 participants
participants (2)
-
Rico Neubauer (JIRA) -
Thomas Diesler (JIRA)