Infinite loop restarting web app

[JWM]

I made a change to a jar file for a web app and uploaded it using my normal
process.  Immediately after refreshing the jar on the server, Tomcat went
into an infinite loop restarting the app (See snippit from stdout log
below).  

Any ideas what could have caused this?  I erased the jars and re-uploaded
and it works fine now.  Must have been something got corrupted in the jar
during ftp.  But even so, I wouldn't expect tomcat to go into an infinite
loop.

This looped for a LONG time before I caught it (ok... should have checked it
after the upload... but it was a tiny fix, and I've never seen anything like
this before). 

Is there any way to specify that tomcat should simply give up if an app
doesn't start after 'n' tries within a couple of minutes?

(BTW... I'm on Tomcat 5.5.7)

Oct 17, 2006 1:09:50 AM org.apache.catalina.loader.WebappClassLoader
modified
INFO: Additional JARs have been added : 'entity.jar'
Oct 17, 2006 1:09:50 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
AbandonedObjectPool is used
([EMAIL PROTECTED])
   LogAbandoned: false
   RemoveAbandoned: true
   RemoveAbandonedTimeout: 60
Oct 17, 2006 1:10:01 AM org.apache.catalina.loader.WebappClassLoader
modified
INFO: Additional JARs have been added : 'entity.jar'
Oct 17, 2006 1:10:01 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
AbandonedObjectPool is used
([EMAIL PROTECTED])
   LogAbandoned: false
   RemoveAbandoned: true
   RemoveAbandonedTimeout: 60
Oct 17, 2006 1:10:11 AM org.apache.catalina.loader.WebappClassLoader
modified
INFO: Additional JARs have been added : 'entity.jar'
Oct 17, 2006 1:10:11 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
AbandonedObjectPool is used
([EMAIL PROTECTED])
   LogAbandoned: false
   RemoveAbandoned: true
   RemoveAbandonedTimeout: 60
Oct 17, 2006 1:10:22 AM org.apache.catalina.loader.WebappClassLoader
modified
INFO: Additional JARs have been added : 'entity.jar'
Oct 17, 2006 1:10:22 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
AbandonedObjectPool is used
([EMAIL PROTECTED])
   LogAbandoned: false
   RemoveAbandoned: true
   RemoveAbandonedTimeout: 60


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Dead links on Tomcat Connectors page

[JWM]

There are some dead links on the Tomcat Connectors doc page.

On page: http://tomcat.apache.org/connectors-doc/ go to the heading for
"Installation" then Apache 2.0.x.  It contains the following link that
returns a 404.

http://tomcat.apache.org/connectors-doc/install/apache2.html




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Accessing context info for other running apps?

[JWM]

>From one webapp, I need to find out if another webapp is installed, and if
so, what its context root is.  I know the Tomcat manager app has access to
info on all running apps.  Is that info accessible by other apps.  If so,
where would I find the documentation on classes, etc.?

Thanks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Inter-webApp communication?

[JWM]

I understand the architecture of webApps is that they are intended to be
self-contained and not aware of other webApps in the system.  However, I
have two loosely-coupled webApps that periodically need to crosslink to each
other.  I have some relatively heavyweight objects that I would like to pass
from one webApp to the other.  Since the session objects are different for
the two webApps, that let's that out.  I know I could serialize the object
and use the database, filesystem, or even pass it across as a form
parameter.  But that will be a performance nightmare and will require
periodic cleaning after sessions go away.  And it just seems like overkill
to simply get an object passed within the same JVM.  Combining the webApps
into one is not an option either.

First question is whether there is some architected way to pass a java
object from one webApp to another (same user logged on via single signon).
In lieu of that, is there some sort of "you really shouldn't do this, but if
you must... here's how..."?  Or am I stuck with db, filesystem, cookie, etc.
approach?

Thanks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Single SignOFF?

[JWM]

I'm using the single signon authenticator for cross-web-app authentication.
For logoff, I was simply killing the session.  But that only kills the one
session where the call was made.  How do I log a user off of all logged on
sessions?

 

Thanks.

 

Single Sign-off?

[JWM]

I'm using the single signon authenticator for cross-web-app authentication.
For logoff, I was simply killing the session.  But that only kills the one
session where the call was made.  How do I log a user off of all logged on
sessions?

Thanks.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]