Bug 152376

Summary:	Freshly started tomcat produces server error
Product:	[Retired] Red Hat Network	Reporter:	David Lutterkort <lutter>
Component:	RHN/Web Site	Assignee:	David Lutterkort <lutter>
Status:	CLOSED NOTABUG	QA Contact:	Fanny Augustin <fmoquete>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhn400	CC:	hbrock, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-07-06 20:58:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	147875

Description David Lutterkort 2005-03-29 00:38:34 UTC

Description of problem:
When tomcat is first restarted (with service tomcat5 restart), any click on a
Java link (e.g., user list) produces a Server Error. After a minute or so, the
site magically starts working.

How reproducible:


Steps to Reproduce:
1. Restart tomcat
2. Click on any of the Java links -> server error
3. Get coffee; try same links again -> success

Actual results:


Expected results:


Additional info:

Comment 1 David Lutterkort 2005-04-14 17:53:20 UTC

After some thought, what I think is happening is that Apache takes a moment to
reconnect to the new Tomcat through ajp13; if that's the case, then this is NOTABUG.

It would be good though to verify that (a) the error is generated by Tomcat and
(b) caused by ajp13 reconnecting and not anything more sinister.

Comment 2 Bret McMillan 2005-06-17 16:47:40 UTC

to dlutter for verification

Comment 3 Jesus M. Rodriguez 2005-07-05 17:38:05 UTC

Did you look in catalina.out and ensure that the rhn.xml file was processed
before clicking on the java link?  I've had a similar problem, but have found
that the rhn webapp hasn't been started yet.

Comment 4 David Lutterkort 2005-07-06 20:58:16 UTC

From what I can tell, this is the cause for the error, that Tomcat isn't fully
up yet and/or Apache hasn't (re)connected to Tomcat yet. Therefore, Marking as
NOTABUG