Scott M Stark wrote:
This has been fixed by only unregistering the deployment UCL if the deployment
actually created the UCL as opposed to inherit the UCL from its containing
deployment. The current NPE behavior is an artifact of class loading that
is ocurring now, not any specific behavior
] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod
Sent: Thursday, January 08, 2004 12:06 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Web integration (clustering) updates
I am able to reproduce the problem, but after spending a good bit of time trying to
find the bug, I am at a loss. Here
Tom Elrod wrote:
I am able to reproduce the problem, but after spending a good bit of
time trying to find the bug, I am at a loss. Here is what I have found
so far (Scott maybe you would be able to figure it out based on this
info?).
The LoaderRepository variable, repository, within
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Remy Maucherat
Sent: Sunday, January 18, 2004 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Web integration (clustering) updates
I ended up giving up, and modifying Tomcat a little
?
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom
Elrod
Sent: Thursday, January 08, 2004 12:06 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Web integration
Scott M Stark wrote:
The class loading failure is due the associated deployment being
destroyed and the class loader removed from the repository. The
class loader reference is invalid, so look into why the class
loader is being used after its deployment is destroyed.
We need to get the web
The class loading failure is due the associated deployment being
destroyed and the class loader removed from the repository. The
class loader reference is invalid, so look into why the class
loader is being used after its deployment is destroyed.
We need to get the web integration tests running
Hello Rémy,
Would it be possible to switch to TC 5 for JB 3.2.4 (assuming there's
someone to test and bugfix the clustering code) ? I did add the JSR 77
stats, so the web console works and has the same stats as with TC 4.1 now.
It is not my decision but in a recent e-mail (virtual hosting)
Scott M Stark wrote:
The class loading failure is due the associated deployment being
destroyed and the class loader removed from the repository. The
class loader reference is invalid, so look into why the class
loader is being used after its deployment is destroyed.
This was working before the
Sacha Labourey wrote:
Hello Rémy,
Would it be possible to switch to TC 5 for JB 3.2.4 (assuming there's
someone to test and bugfix the clustering code) ? I did add the JSR 77
stats, so the web console works and has the same stats as with TC 4.1 now.
It is not my decision but in a recent e-mail
I would qualify JMX 1.2 as a major addition, so maybe it
would be a good
idea to change the numbering scheme (3.2.3 was a minor update, 3.2.2
wasn't, and 3.2.4 isn't going to be one either).
I agree, I didn't expected the JMX 1.2 migration, that was quite a big move,
I was impressed by so
Hello!
Am Mit, den 07.01.2004 schrieb Remy Maucherat um 07:01:
IMO, the TC 5 code which I ported should be kept in sync (it's in
src/main/org/jboss/web/tomcat/tc5/session). Also, would it be possible
to test it so that the TC 5 integration has the same features as TC 4.1
? I don't quite
Was my fault for not giving more notice. I e-mailed a few people
directly before the commit, but should have notified the list before hand.
Will be working on the classloader problem later today (sorry for
negative impact on you Remy). Hope to have it fixed by end of day.
-Tom
Sacha
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Remy Maucherat
Sent: Wednesday, January 07, 2004 12:38 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Web integration (clustering) updates
Scott M Stark wrote:
The class loading is the same, the bigger recent change was a refactoring
No, your refactoring didn't break anything, as I did test it earlier.
of the embedded web service into the web container service and a deployer.
I would this is the source of the behavior change. What
Sent: Wednesday, January 07, 2004 8:39 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Web integration (clustering) updates
Scott M Stark wrote:
The class loading is the same, the bigger recent change was a
refactoring
No, your refactoring didn't break anything, as I did test it earlier
Tom Elrod wrote:
So is this still an issue? If so, how do I reproduce (will look at it
tonight)?
The value of looking into this is that it could possibly be a
regression. Otherwise, the workaround is good enough :)
- Use the TC 5 SAR instead of the TC 4.1 SAR
- In the server.xml of the SAR,
17 matches
Mail list logo