commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35774] - [logging] TCCL problem in J2EE Container
Date Wed, 03 Aug 2005 05:42:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35774>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35774





------- Additional Comments From michael.kopp@gmx.at  2005-08-03 07:42 -------
1. The J2EE Spec does not specify which classloader the TCCL should contains.
only that it should be there.
2. Most AppServers won't have JCL in the common-classloader, jboss is the
exception I would say. The common classloader there contains way to much.

jboss seems to ignore the TCCL most of the time.
It all comes down to the fact that we cannot know what the TCCL contains at a
given time. Because it is not defined!
I had this problem now in:

- jmx-console calling mbean with Web TCCL
- jmx-console calling mbean calling ejb with Web TCCL in the ejbCreate call!!!
- instantiation of ManagedConnectionFactory/ManagedConnection (JCA) by jboss JCA
Pool Loader with jboss TCCL

Of course this is all in jboss, but as it is defined nowhere (at least I
couldn't find it) I consider TCCL not reliable!!

And many more. I changed the 1.0.4 commons-logging the way it is described in my
patch and replaced it in jboss and all other apps. Now it works as expected.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message