DO NOT REPLY [Bug 23811] New: - Erratic "The servlet container is temporary unavailable or being upgraded" message

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23811>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23811

Erratic "The servlet container is temporary unavailable or being upgraded" message

           Summary: Erratic "The servlet container is temporary unavailable
                    or being upgraded" message
           Product: Tomcat 4
           Version: Unknown
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: chartwig@reservit.com


We're using Apache2/mod_jk2 in front of two JBoss/Jetty servers set up for
session replication...

Sometimes we just get a blank (empty) response page, sometimes this message, and
the rest of the time mod_jk2 works just fine...
When we encounter this message, hitting Reload almost always works...
We could not determine exactly why/when this message arises : we were making
load balancing/failover testing on production systems... while some of our
clients were using the system (and getting errors !)...
We had to go back to the good old apache proxy pass method (without load
balancing of course).

Of course, at the time this message appeared, we had one or two Jetty servers up
and running... The load is really modest, and is usually served by only one
machine ! This does not require severe load to happen...

Note: if you type "The servlet container is temporary unavailable or being
upgraded" in google.com, you'll see many sites gots this kind of message too
(while beeing indexed by google !!!)... some of them may have seen the same bug
? or maybe their servlet container was dead...

Thanks for any info !
Chris

PS: If you think there is a chance this error comes from the Jetty AJP13
handler, please tell us so, and we'll try to switch to Tomcat... We're using
Jetty since our tests proved session replication in Jetty (with JavaGroups) is
much faster than Tomcat's EJB based session replication...
PPS: I can email you our JK2 config files...

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