Bug 131711 - Create User shows stack trace when login conflicts with existing login
Summary: Create User shows stack trace when login conflicts with existing login
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/R&D
Version: RHN Devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike McCune
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: rhnMilestone1
TreeView+ depends on / blocked
 
Reported: 2004-09-03 13:58 UTC by Michael Bowman
Modified: 2007-04-18 17:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-12-03 18:09:58 UTC


Attachments (Terms of Use)

Description Michael Bowman 2004-09-03 13:58:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040803 Firefox/0.9.3

Description of problem:
http://localhost:8080/newlogin/CreatePersonal.do?account_type=create_personal

When trying to create a new user with a login that already exists, we
get a Tomcat stacktrace.

We should be sending the user back to the input form with a "username
already exists" message.



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


How reproducible:
Always

Steps to Reproduce:
1.http://localhost:8080/newlogin/CreatePersonal.do?account_type=create_personal
2. create a user
3. attempt to create another user with the same login as created in step 2
    

Actual Results:  HTTP 500 - Tomcat Stacktrace

Expected Results:  Send back to form with error message

Additional info:

Comment 1 Chip Turner 2004-09-07 20:01:26 UTC
okay I've added code to protect against the user already existing, but
the error messaging is odd; seems stuck or something inside of tomcat.
 the checks are in and use the same error paths the rest of the code
does, but someone else more familiar with it needs to have a look

Comment 2 Mike McCune 2004-11-02 01:28:12 UTC
Nice (when reproducing this bug):

Unrecoverable Stack Overflow: addr=b73623a9, ee=8801e38, er=b3369b00
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/tmp/javacore.20041101.203140.15849.txt
JVMDG215: Dump Handler has Processed Exception Signal 11.



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