Bug 199892 - (rhn411-hmmpretty) RHN shows error 500 , sometimes.. hmm pretty.
RHN shows error 500 , sometimes.. hmm pretty.
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jesus M. Rodriguez
Mike McCune
Depends On:
Blocks: 199445
  Show dependency treegraph
Reported: 2006-07-24 00:37 EDT by Wade Mealing
Modified: 2007-04-18 13:46 EDT (History)
1 user (show)

See Also:
Fixed In Version: rhn411
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-02 11:39:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Exception shown on customer facing site. (2.96 KB, text/plain)
2006-07-24 00:37 EDT, Wade Mealing
no flags Details

  None (edit)
Description Wade Mealing 2006-07-24 00:37:18 EDT
Description of problem:

RHN shows internal error 500 on some logins, problem is not consistant. 
Difficult to reproduce.

Version-Release number of selected component (if applicable):

Current customer facing website.

How reproducible:

One out of 20 login attempts.. maybe.. Log in and out, for a  bit, try again
soon, maybe just close the page while logged in, then attempt to log in again.

Steps to Reproduce:
1. Visit rhn.redhat.com , log in.
2. close window ( do not log out )
3. visit http://rhn.redhat.com in same browser.
Actual results:

Error 500, see attachment.

Expected results:

RHN to display default login page.

Additional info:

Not reproducable every time.
I'm not going to clear my cache and cookies, because customers should not have
to "Clear cache and cookies".  We have html headers for setting for not caching
files (see META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE" ) and also one can set a
time limit on cookies.
Comment 1 Wade Mealing 2006-07-24 00:37:19 EDT
Created attachment 132894 [details]
Exception shown on customer facing site.
Comment 2 Kevin A. Smith 2006-07-24 09:33:00 EDT
I think I see the cause of this. The LocalizationService does not handle calls
to getMessage() with a null messageId well. It should detect null messageIds and
return the results of a call to getMissingMessageString().

For anyone interested, look at the following lines in LocalizationService: 259,
621, and 314.

I have a fix for this on my box, just waiting for review.
Comment 3 Jesus M. Rodriguez 2006-08-02 11:39:03 EDT
This has been pushed to production already.
Comment 4 Beth Nackashi 2006-08-07 16:49:38 EDT
changing the current release from rhn4101 to rhn411

Note You need to log in before you can comment on or make changes to this bug.