forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Updated: (FOR-272) Forrest 0.6 Interaction with Tomcat 5.0.27
Date Fri, 05 Nov 2004 15:42:39 GMT
The following issue has been updated:

    Updater: David Crossley (mailto:crossley@apache.org)
       Date: Fri, 5 Nov 2004 9:42 AM
    Changes:
             Component changed to Launch servlet WAR
             Component changed from Other
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-272?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-272

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-272
    Summary: Forrest 0.6 Interaction with Tomcat 5.0.27
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Launch servlet WAR
   Versions:
             0.6

   Assignee: 
   Reporter: Michael Hare

    Created: Thu, 2 Sep 2004 9:06 AM
    Updated: Fri, 5 Nov 2004 9:42 AM
Environment: Windows XP, Apache 2.0.50 + Tomcat 5.0.27 + JK2 2.0.4

Description:
Once I put the configuration file for Forrest 0.6 into Tomcat's
catalina/localhost directory, I can no longer access several of my
other applications such as Xindice, or the JSP and Servlet examples that
ship with Tomcat. I can't even access the Tomcat Home Page using
http://myurl.com:8080

I get HTTP Status 503 (Application Not Currently Available) for each of
these.

If I remove the conf file, then Tomcat responds again.

I did not have this problem with a similar conf file and Forrest 0.5.1

Please see http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message