History | Log In     View a printable version of the current page. Get help!  
Issue Details (XML | Word)

Key: JBPAPP-253
Type: Bug Bug
Status: Resolved Resolved
Resolution: Done
Priority: Minor Minor
Assignee: Fernando Nasser
Reporter: Jimmy Wilson
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JBoss Enterprise Platform App Edition

Run.sh fails if -c command line argument is 10 or more arguments down

Created: 22/Jul/07 05:10 PM   Updated: 07/Nov/07 11:08 AM  Due: 27/Jul/07
Component/s: App Server
Affects Version/s: 4.2.0.GA
Fix Version/s: 4.3.0.GA
Security Level: Public (Everyone can see)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File command-line.txt (0.3 kb)
2. File run.sh (7 kb)

Environment: A unix environment using the run.sh script is required.

Affects: Release Notes
Workaround: Workaround Exists
Workaround Description: Place -c <server config> in the first 9 command line arguments or use the attached run.sh script that contains the fix.
Help Desk Ticket Reference: https://na1.salesforce.com/50030000003P4nI


 Description  « Hide
There is a bug in run.sh that prevents JBoss startup (the script goes into an endless loop) if -c is 10 or more arguments down in the list.

See attached command-line.txt for a sample command line that causes this behavior.

See attached run.sh that fixes the problem.





 All   Comments   Work Log   Change History   Subversion Commits      Sort Order:
Jimmy Wilson [22/Jul/07 05:14 PM]
This is an example command line, but in reality any command line arguments will do.

Jimmy Wilson [22/Jul/07 05:15 PM]
This run.sh script corrects the problem.

Jimmy Wilson [22/Jul/07 05:30 PM]
Change has been committed to https://svn.jboss.org/repos/jbossas/branches/JBPAPP_4_2_0_GA_CP/ as of revision 64191.

Dimitris Andreadis [23/Jul/07 03:48 AM]
If this affects the community version as well, a jira must be opened and the problem fixed in Branch_4_2 and HEAD, too.

Jimmy Wilson [23/Jul/07 01:45 PM]
It doesn't (at least as of 4.2.0.GA). I'll double- check 4.2.1.GA as well. There's a loop added in the script for the EAP version to determine which server configuration to use (production is the "default" instead of defautl).

Dimitris Andreadis [23/Jul/07 02:12 PM]
Ok thanks Jimmy.

BTW that shows why is bad to make local changes in the EAP, as they are not as much tested as the community versions. :)

Fernando Nasser [08/Aug/07 03:57 PM]
Must also go into the JBPAPP_4_2 branch (4.2.1+).

Alex Pinkin [21/Aug/07 04:46 PM]
JBPAPP-312 is now used for tracking CP

Alex Pinkin [29/Oct/07 03:08 PM]
did this fix go into JBPAPP_4_2 branch?

Fernando Nasser [07/Nov/07 11:08 AM]
r65305 | fnasser@redhat.com | 2007-09-11 17:15:24 -0400 (Tue, 11 Sep 2007)

merged this in what is being used for EAP 4.3 BETA