5 p.m.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
I am using library code in a BundleActivator that tries to load resources via ClassLoader.
The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString ont he class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
5:02 p.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce updated AS7-2165:
---------------------------
Attachment: jboss-osgi-bug.zip
Simple Maven project w/ reproducer.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString ont he class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce updated AS7-2165:
---------------------------
Steps to Reproduce:
Attached is a simple Maven project to build and deploy a reproducer. Unzip this project
and:
{quote}
mvn clean package jboss-as:deploy
{quote}
The bundle activator has several System.out.println() statements to show the status of
resolved resources.
For comparison, do this in both 7.0.2 and 7.0.1 and note the difference in behavior.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString ont he class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
5:51 p.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce updated AS7-2165:
---------------------------
Description:
I am using library code in a BundleActivator that tries to load resources via ClassLoader.
The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
was:
I am using library code in a BundleActivator that tries to load resources via ClassLoader.
The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString ont he class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
4:23 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler resolved AS7-2165.
---------------------------------
Resolution: Out of Date
Thanks for the excellent bug report. This issue is fixed in master already
{code}
11:18:03,567 INFO [org.jboss.modules] JBoss Modules version 1.0.3.GA
11:18:03,912 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
11:18:03,987 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!"
starting
...
11:20:26,204 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread
1-2) OSGi Framework started
11:20:26,210 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread
1-2) Install bundle: jboss.osgi.bug:1.0.0
11:20:26,235 INFO [stdout] (MSC service thread 1-4) thread context classloader:
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@329f671b (roots:
/home/tdiesler/git/jboss-as/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/modules)
11:20:26,236 INFO [stdout] (MSC service thread 1-4) resource URL: null
11:20:26,237 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
11:20:26,248 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-23-0-0/document.txt
11:20:26,248 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-23-0-0/document.txt
11:20:26,249 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread
1-4) Bundle started: jboss.osgi.bug:1.0.0
{code}
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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:35 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce reopened AS7-2165:
----------------------------
My apologies, I don't think I described the issue clearly.
Here's the behavior I expect (from 7.0.1 - note the first line):
{code}
08:26:11,670 INFO [stdout] (MSC service thread 1-4) no thread context classloader
08:26:11,670 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:26:11,671 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-20-0-0/document.txt
{code}
And here's the behavior that I changed in 7.0.2:
{code}
08:27:26,202 INFO [stdout] (MSC service thread 1-4) thread context classloader:
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@45e67e6a (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
08:27:26,206 INFO [stdout] (MSC service thread 1-4) resource URL: null
08:27:26,207 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:27:26,207 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-21-0-0/document.txt
{code}
In 7.0.1 there was no thread context ClassLoader, so the library code would instead use
the class ClassLoader and correctly finds my resource.
In 7.0.2 there is a thread context ClassLoader, so the library code uses it, but my
resource is not found via the thread context ClassLoader.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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:37 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce edited comment on AS7-2165 at 10/20/11 10:36 AM:
-----------------------------------------------------------
My apologies, I don't think I described the issue clearly.
Here's the behavior I expect (from 7.0.1 - note the first line):
{code}
08:26:11,670 INFO [stdout] (MSC service thread 1-4) no thread context classloader
08:26:11,670 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:26:11,671 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-20-0-0/document.txt
{code}
And here's the behavior that changed in 7.0.2:
{code}
08:27:26,202 INFO [stdout] (MSC service thread 1-4) thread context classloader:
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@45e67e6a (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
08:27:26,206 INFO [stdout] (MSC service thread 1-4) resource URL: null
08:27:26,207 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:27:26,207 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-21-0-0/document.txt
{code}
In 7.0.1 there was no thread context ClassLoader, so the library code would instead use
the class ClassLoader and correctly finds my resource.
In 7.0.2 there is a thread context ClassLoader, so the library code uses it, but my
resource is not found via the thread context ClassLoader.
was (Author: tpesce):
My apologies, I don't think I described the issue clearly.
Here's the behavior I expect (from 7.0.1 - note the first line):
{code}
08:26:11,670 INFO [stdout] (MSC service thread 1-4) no thread context classloader
08:26:11,670 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:26:11,671 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-20-0-0/document.txt
{code}
And here's the behavior that I changed in 7.0.2:
{code}
08:27:26,202 INFO [stdout] (MSC service thread 1-4) thread context classloader:
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@45e67e6a (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
08:27:26,206 INFO [stdout] (MSC service thread 1-4) resource URL: null
08:27:26,207 INFO [stdout] (MSC service thread 1-4) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
08:27:26,207 INFO [stdout] (MSC service thread 1-4) resource URL:
bundle://jboss.osgi.bug-21-0-0/document.txt
{code}
In 7.0.1 there was no thread context ClassLoader, so the library code would instead use
the class ClassLoader and correctly finds my resource.
In 7.0.2 there is a thread context ClassLoader, so the library code uses it, but my
resource is not found via the thread context ClassLoader.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
4:27 p.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce commented on AS7-2165:
--------------------------------
Thomas - I've tested this against a current clone of your Git repo and I still see the
same unexpected behavior as with 7.0.2.
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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:36 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-2165:
-------------------------------------
Yes - sorry I missed that. Indeed, the OperationStepProcessor in AS7 now sets the TCCL.
I'll fix it in the OSGi layer. In the meanwhile can you not set the TCCL to null in
your Activator?
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
4:35 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-2165:
-------------------------------------
Done
{code}
11:32:58,236 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread
1-4) Install bundle: jboss.osgi.bug:1.0.0
11:32:58,261 INFO [stdout] (MSC service thread 1-2) no thread context classloader
11:32:58,262 INFO [stdout] (MSC service thread 1-2) class classloader:
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
11:32:58,263 INFO [stdout] (MSC service thread 1-2) resource URL:
bundle://jboss.osgi.bug-23-0-0/document.txt
11:32:58,264 INFO [stdout] (MSC service thread 1-2) resource URL:
bundle://jboss.osgi.bug-23-0-0/document.txt
11:32:58,264 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread
1-2) Bundle started: jboss.osgi.bug:1.0.0
11:32:58,394 INFO [org.jboss.as.server.controller] (pool-2-thread-1) Deployed
"bug-1.0.jar"
{code}
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
11:30 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Tim Pesce commented on AS7-2165:
--------------------------------
Thanks!
I have worked around this in current builds by setting the TCCL to the classloader of the
Activator Class:
{code}Thread.currentThread().setContextClassLoader(getClass().getClassLoader());{code}
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
2:40 a.m.
[
https://issues.jboss.org/browse/AS7-2165?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-2165:
--------------------------------
Fix Version/s: 7.1.0.Beta1
Git Pull Request: https://github.com/jbossas/jboss-as/pull/494 (was:
https://github.com/jbossas/jboss-as/pull/494)
Thread context ClassLoader set to unexpected value
--------------------------------------------------
Key: AS7-2165
URL: https://issues.jboss.org/browse/AS7-2165
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.2.Final
Environment: Java 1.6.0_26, Mac OS 10.6.8
Reporter: Tim Pesce
Assignee: Thomas Diesler
Labels: classloader
Fix For: 7.1.0.Beta1
Attachments: jboss-osgi-bug.zip
I am using library code in a BundleActivator that tries to load resources via
ClassLoader. The logic in the library looks something like this:
# if thread context ClassLoader exists use it
# else use ClassLoader for this class
The thread context ClassLoader differs from the class ClassLoader. The resources packaged
in my bundle are not available to the thread context ClassLoader, but they are available
to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library
code used the class ClassLoader and correctly loaded the resources.
Here's what toString on the thread context ClassLoader shows:
{quote}
ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader
@67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules)
{quote}
Here's the toString on the class ClassLoader:
{quote}
HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service
Module Loader
{quote}
--
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
4763
days inactive
4769
days old
11 comments
8 participants
participants (8)
-
Thomas Diesler (Commented) (JIRA) -
Thomas Diesler (Resolved) (JIRA)
-
Thomas Diesler (Updated) (JIRA)
-
Tim Pesce (Commented) (JIRA)
-
Tim Pesce (Created) (JIRA)
-
Tim Pesce (Issue Comment Edited) (JIRA)
-
Tim Pesce (Reopened) (JIRA)
-
Tim Pesce (Updated) (JIRA)