You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/08/29 09:43:35 UTC

DO NOT REPLY [Bug 51735] New: welcome page deadlock at startup

https://issues.apache.org/bugzilla/show_bug.cgi?id=51735

             Bug #: 51735
           Summary: welcome page deadlock at startup
           Product: Tomcat 7
           Version: 7.0.16
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: andrew.chapman@brighterworking.com
    Classification: Unclassified


I have two tomcat servers:
- Server 1 has a welcome page which checks for a certain URL parameter and if
it is missing redirects to server 2. 
- Server 2 checks for the same URL parameter and if it is present redirects to
server 1.

My tomcat 7.0.16 installations seem to check the welcome page during start-up.
Where the result is a redirect, they also seem to check the redirect URL
responds correctly. If the response is bad, the server waits a while and then
retries.

Unfortunately, this means that if both servers go down then neither can start.
They both end up rechecking their welcome page forever (or until a server
start-up timeout).

It would be nice if the start-up checks on the welcome page passed if an
external redirect (i.e. to a host not served by this instance) was received as
the result.

I don't have the source code available, but the stack leading to the welcome
page stack is:

StandardHostValve.invoke(Request, Response) line: 164    
ErrorReportValve.invoke(Request, Response) line: 100    
AccessLogValve.invoke(Request, Response) line: 563    
StandardEngineValve.invoke(Request, Response) line: 118    
CoyoteAdapter.service(Request, Response) line: 403    
Http11Processor.process(SocketWrapper<Socket>) line: 301    
Http11Protocol$Http11ConnectionHandler.process(SocketWrapper<Socket>,
SocketStatus) line: 162    
Http11Protocol$Http11ConnectionHandler.process(SocketWrapper<Socket>) line: 140 
JIoEndpoint$SocketProcessor.run() line: 309    
ThreadPoolExecutor$Worker.runTask(Runnable) line: 886    
ThreadPoolExecutor$Worker.run() line: 908    
TaskThread(Thread).run() line: 662    

In case it's relevant, I'm also using various bits of spring security and
struts2 filters around the welcome page.

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

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

DO NOT REPLY [Bug 51735] welcome page deadlock at startup

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51735

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Mark Thomas <ma...@apache.org> 2011-08-29 10:28:15 UTC ---
(In reply to comment #0)
> My tomcat 7.0.16 installations seem to check the welcome page during start-up.

Nope. That will be the application.

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

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

DO NOT REPLY [Bug 51735] welcome page deadlock at startup

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51735

--- Comment #2 from Andy Chapman <an...@brighterworking.com> 2011-08-29 11:55:19 UTC ---
Thanks. 

Just in case anyone else gets this, it looks like it was the Eclipse server
launcher which seems to check the context URL as part of it's checks that the
server has started (I think).

If I generate a WAR of the application and stick it into a naked Tomcat 7
install I don't get the same behaviour.

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

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

DO NOT REPLY [Bug 51735] welcome page deadlock at startup

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51735

Andy Chapman <an...@brighterworking.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew.chapman@brighterwork
                   |                            |ing.com

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

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