Random 404 Errors in Turbine Application

[Dave Everson <dj...@mygolftrac.com>]

Hi,

I'm looking for some pointers to help us hunt down the source/reason for
random 404 errors our users are getting during the use of a Turbine 2.2
web application. 

The 404 occurs randomly throughout the web application.  When the user
clicks on a link or submit button, they are presented with the 404 error
page.  While on the error page, if they hit the refresh button, the
correct page appears. 

Needless to say, our users find this annoying. 

The users are not being timeout out due to inactivity.  That is
currently set to two hours. 

I have searched through both the Apache Web Server and Turbine logs for
some information as to why this is happening, but I can't find any
useful information. 

Our Turbine 2.2 web application is deployed along with Tomcat 4.0 and
Apache Web Server (which handles SSL) on a Windows 2000 machine.  The
AJP Connector is used to communicate between Apache Web Server and
Tomcat.   Our user base is relatively small right now, around 20 users.
The users are using a variety of different browsers and bandwidth
speeds.  They all seem to have the 404 errors.  

Has anyone else seen this in their applications?  Can anyone give me
some pointers on where to look to resolve these random 404 errors?  Is
there any debugging settings in Turbine, Tomcat, or Apache that we can
set to help capture more detailed log info?  Any assistance is greatly
appreciated. 

Thanks!
Dave




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Random 404 Errors in Turbine Application

[Rostislav Beloff <ro...@plesk.com>]

Hi,

If you are using mod_ssl with apache I recommend you to check paragraph
"When I connect via HTTPS to an Apache+mod_ssl+OpenSSL server with Microsoft
Internet Explorer (MSIE) I get various I/O errors. What is the reason ? " in
their FAQ.

URL is  http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49

Thanks,
Ros

----- Original Message -----
From: "Dave Everson" <dj...@mygolftrac.com>
To: <tu...@jakarta.apache.org>
Sent: Wednesday, June 26, 2002 7:00 AM
Subject: Random 404 Errors in Turbine Application


> Hi,
>
> I'm looking for some pointers to help us hunt down the source/reason for
> random 404 errors our users are getting during the use of a Turbine 2.2
> web application.
>
> The 404 occurs randomly throughout the web application.  When the user
> clicks on a link or submit button, they are presented with the 404 error
> page.  While on the error page, if they hit the refresh button, the
> correct page appears.
>
> Needless to say, our users find this annoying.
>
> The users are not being timeout out due to inactivity.  That is
> currently set to two hours.
>
> I have searched through both the Apache Web Server and Turbine logs for
> some information as to why this is happening, but I can't find any
> useful information.
>
> Our Turbine 2.2 web application is deployed along with Tomcat 4.0 and
> Apache Web Server (which handles SSL) on a Windows 2000 machine.  The
> AJP Connector is used to communicate between Apache Web Server and
> Tomcat.   Our user base is relatively small right now, around 20 users.
> The users are using a variety of different browsers and bandwidth
> speeds.  They all seem to have the 404 errors.
>
> Has anyone else seen this in their applications?  Can anyone give me
> some pointers on where to look to resolve these random 404 errors?  Is
> there any debugging settings in Turbine, Tomcat, or Apache that we can
> set to help capture more detailed log info?  Any assistance is greatly
> appreciated.
>
> Thanks!
> Dave
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Random 404 Errors in Turbine Application

["Nikhil G. Daddikar" <ng...@celoxis.com>]

Are you hosted with an ISP on a shared server? If yes, it's just the load on the machine. We had similar problems and had the exact symptoms that you described. The request never reaches tomcat. You can check that by looking at the logs. However, once we moved to a dedicated server, it's gone. The environment is the same as before.

We've been running on Turbine for a long time and had no problems. 

-n.