Bug 1072227 - [QE] (6.2.x) Wrong handling of --debug argument by standalone.[sh|bat] scripts
Summary: [QE] (6.2.x) Wrong handling of --debug argument by standalone.[sh|bat] scripts
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Scripts and Commands
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: EAP 6.2.4
Assignee: Jeff Mesnil
QA Contact: Petr Kremensky
Nidhi
URL:
Whiteboard:
Depends On: 1063289
Blocks: eap62-cp04-blockers
TreeView+ depends on / blocked
 
Reported: 2014-03-04 07:02 UTC by Petr Kremensky
Modified: 2014-06-30 13:15 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
This release of JBoss EAP 6 carries a bug where-in the shell script for running EAP in standalone mode (+standalone.sh|bat+) does not use the default port (port 8787) when the script is used with `debug` argument without a port number. As a result execution of the script with `debug` argument results in an error and does not start the server. A possible workaround for this issue is to specify a port number when the script is used with the `debug` argument: ---- standalone.[sh|bat] --debug [port number] ---- This issue is expected to be resolved in a future release of the product.
Clone Of: 1063289
Environment:
Last Closed: 2014-06-30 13:15:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1072228 0 unspecified CLOSED [QE] (6.2.2) standalone.sh fails to start server with debug argument on solaris 10 hosts 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFLY-2261 0 Major Resolved standalone.sh --debug without port number not working 2016-04-07 04:09:44 UTC

Internal Links: 1072228

Description Petr Kremensky 2014-03-04 07:02:58 UTC 
+++ This bug was initially created as a clone of Bug #1063289 +++

Description of problem:
 Standalone server start script is handling --debug argument in wrong manner. Port 8787 should be used by default, but it isn't.

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

How reproducible:
 Always

Steps to Reproduce:
 1. Navigate into $EAP_HOME/bin directory.
 2. Run: standalone.[sh|bat] --debug 

Actual results:
- shell script
 Server fail to with following error:
 ERROR [stderr] (main) JBAS015801: Invalid option ''
- batch script
 random empty port is used

Expected results:
 Server will start with debugger attached to 8787 port.

Additional info:
 Workaround: always specify the port number.

--- Additional comment from Permaine Cheung on 2014-02-10 09:12:30 EST ---

Brian, please look into this. Thanks!

--- Additional comment from Jeff Mesnil on 2014-02-24 04:13:17 EST ---

PR for upstream branch https://github.com/wildfly/wildfly/pull/5948

--- Additional comment from Jeff Mesnil on 2014-02-25 03:11:24 EST ---

PR for jboss-eap 6.x https://github.com/jbossas/jboss-eap/pull/970
Comment 1 Permaine Cheung 2014-03-04 19:29:00 UTC 
Jeff, can you please submit a PR for 6.2.x? Thanks!
Comment 3 Petr Kremensky 2014-05-09 06:56:59 UTC 
This is working only on RHEL.

./standalone --debug

HP-UX:
./standalone.sh[28]: shift: bad number
Solaris10:
./standalone.sh: cannot shift
Solaris11:
./standalone.sh[28]: shift: (null): bad number
Windows2k8:
server starts, but default port 8787 is not used (java opts passed by script: ...-agentlib:jdwp=transport=dt_socket,address=""...)
Comment 6 Petr Kremensky 2014-06-18 06:39:16 UTC 
No changes since 6.2.3. standalone.[bat|sh] scripts are identical to previous version.
Note You need to log in before you can comment on or make changes to this bug.