Thanks for letting us know!
On 28.10.2009 16:23, Bocalinda wrote:
> Hi again Rainer,
>
> It seems some of our software updates must have solved the issue, as it's
> been working perfectly now for several weeks.
> I think we may conclude that it didn't had to do with the the clustering
> implement
Hi again Rainer,
It seems some of our software updates must have solved the issue, as it's
been working perfectly now for several weeks.
I think we may conclude that it didn't had to do with the the clustering
implementation.
I feel sorry that you put time into patching the issue. In case the prob
Hi Rainer,
I'm sorry for the long delay in getting back to you.
I got sidetracked by another issue and wasn't able to look into this
earlier.
However, the bad news is that the administrators didn't allow me to apply
the patch as it is a production server.
I can apply it to pre-production, but the
Wow, that's what is called a quick turn around! :)
Thanks. I'll try as soon as possible and let you know.
2009/10/3 Rainer Jung
> On 03.10.2009 18:11, Bocalinda wrote:
> > Hi Rainer.
> >
> >
> >> I remember problems with clustering which were of the following kind:
> >> session replication data
On 03.10.2009 18:11, Bocalinda wrote:
> Hi Rainer.
>
>
>> I remember problems with clustering which were of the following kind:
>> session replication data was received on a node although the context
>> wasn't yet fully initialized.
>>
>> Maybe we run into classloader troubles in that case?
>>
>>
Hi Rainer.
> I remember problems with clustering which were of the following kind:
> session replication data was received on a node although the context
> wasn't yet fully initialized.
>
> Maybe we run into classloader troubles in that case?
>
> This could only happen if another node in the clus
let
> /services/*
>
>
>
> Apache-Axis Admin Servlet Web Admin
> AxisAdminServlet
>
> org.apache.axis2.transport.http.AxisAdminServlet
>
> 100
>
>
>
> AxisAdminServlet
> /axis2-admin/*
k.web.NavegationPACKFilter
Navegation PACK Filter
*
2009/10/3 Caldarale, Charles R
> > From: Bocalinda [mailto:bocali...@gmail.com]
> > Subject: Re: Connection between ListenerStart and clustering
> >
> > > it turns out there are 2 libraries in my web-in
> From: Bocalinda [mailto:bocali...@gmail.com]
> Subject: Re: Connection between ListenerStart and clustering
>
> > it turns out there are 2 libraries in my web-inf/lib
> > containing a class definition for that:
> >
> > spring-2.5.6.jar and spring-web-2.5.6.jar
> I currently don't have access to the server to check catalina_home/lib
> contents, but I do have the webapp.war here. So I did a grep for the
> ContextLoaderListener and it turns out there are 2 libraries in my
> web-inf/lib containing a class definition for that:
>
> spring-2.5.6.jar and spring-
> Different messages arriving in a different order, for one. Classes are
> only loaded on demand, not simply because they exist in a defined library.
>
> > I would suppose the classloading ritual is a serial process,
> > instead of a parallel process.
>
> Nope. In a multi-threaded environment, yo
> From: Bocalinda [mailto:bocali...@gmail.com]
> Subject: Re: Connection between ListenerStart and clustering
>
> What causes timing issues?
Different messages arriving in a different order, for one. Classes are only
loaded on demand, not simply because they exist in a defined l
> > If I'm not wrong Tomcat loads it classes in the following order:
> > 1. bootstrap
> > 2. classpath classes
> > 3. webapps classes/libs
> > 4. common libs
> > 5. shared libs
>
> As I recall, the webapp classloader takes precedence over the system
> classloader (the -cp path handler), but I'd hav
> From: Bocalinda [mailto:bocali...@gmail.com]
> Subject: Re: Connection between ListenerStart and clustering
>
> If I'm not wrong Tomcat loads it classes in the following order:
> 1. bootstrap
> 2. classpath classes
> 3. webapps classes/libs
> 4. common libs
>
t what it is.
>
> Thanks
>
> 2009/10/2 Caldarale, Charles R
>
> > From: Bocalinda [mailto:bocali...@gmail.com]
>> > Subject: Re: Connection between ListenerStart and clustering
>> >
>> > The class mentioned is actually there
>> > java.lang.No
: Bocalinda [mailto:bocali...@gmail.com]
> > Subject: Re: Connection between ListenerStart and clustering
> >
> > The class mentioned is actually there
> > java.lang.NoClassDefFoundError:
> > org/springframework/web/context/ContextLoaderListener
>
> Is the cl
> From: Bocalinda [mailto:bocali...@gmail.com]
> Subject: Re: Connection between ListenerStart and clustering
>
> The class mentioned is actually there
> java.lang.NoClassDefFoundError:
> org/springframework/web/context/ContextLoaderListener
Is the class perhaps in too man
Hi, I'm back again.
I figured out why I got a ListenerStart Error, or at least, I got a nicer
error message.
However, I don't get it why my Tomcat servers start sometimes without
problems, and other times show the ListenerStart Error.
After restarting Tomcat a few times, the problem automatically
Ok thanks!
2009/10/2 Filip Hanik - Dev Lists
> Correct, not denying nor confirming. I'm informing you that your log files
> would tell you what the actual error is :)
>
> Filip
>
>
> On 10/02/2009 10:32 AM, Bocalinda wrote:
>
>> Hi Filip.
>>
>> I'm using version 6.0.20.
>> You are not denying th
Correct, not denying nor confirming. I'm informing you that your log
files would tell you what the actual error is :)
Filip
On 10/02/2009 10:32 AM, Bocalinda wrote:
Hi Filip.
I'm using version 6.0.20.
You are not denying that the clustering could cause a ListenerStart Error,
is that correct?
Hi Filip.
I'm using version 6.0.20.
You are not denying that the clustering could cause a ListenerStart Error,
is that correct?
2009/10/2 Filip Hanik - Dev Lists
> listenerStart error will have a stack trace in another log file depending
> on what version of Tomcat you are using.
> That stack t
listenerStart error will have a stack trace in another log file
depending on what version of Tomcat you are using.
That stack trace will take out the guess work of what actually went wrong
best
Filip
On 10/02/2009 10:12 AM, Bocalinda wrote:
Hi again,
I obviously meant ListenerStart Error.
Hi again,
I obviously meant ListenerStart Error.
2009/10/2 Bocalinda
> Hi List,
>
> Maybe this is a very stupid question, but I am wondering whether a
> ListenerStart of an application could be related in any possible way to
> problems with the Tomcat cluster?
>
> Thanks in advance.
>
>
Hi List,
Maybe this is a very stupid question, but I am wondering whether a
ListenerStart of an application could be related in any possible way to
problems with the Tomcat cluster?
Thanks in advance.
24 matches
Mail list logo
