Description of problem: I am unable to start standalone server with --debug [PORT] argument on Solaris 10 hosts. SunOS 5.10 Generic_142910-17 i86pc i386 i86pc [user@host bin]$ ./standalone.sh --debug ./standalone.sh: cannot shift [user@host bin]$ ./standalone.sh --debug 8787 ./standalone.sh: bad substitution SunOS 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T1000 [user@host bin]$ ./standalone.sh --debug ./standalone.sh: cannot shift [user@host bin]$ ./standalone.sh --debug 8787 ./standalone.sh: bad substitution Version-Release number of selected component (if applicable): EAP 6.3.0.DR0 How reproducible: Always Steps to Reproduce: 1. Navigate to $JBOSS_HOME/bin and run: ./standalone.sh --debug [PORT] Actual results: Server fails to start Expected results: Server will start with debugger attached to $PORT (8787 if no $PORT)
Brian, please investigate. Thanks!
I am not sure that this is a duplicate of bug 1063289. Difference: BZ1063289 -command [user@host bin]$ ./standalone.sh --debug -result Server fails to start with ERROR [stderr] (main) JBAS015801: Invalid option '' -workaround [user@host bin]$ ./standalone.sh --debug 8787 server starts with debugger attached to port 8787 BZ1064763 Solaris 10 specific [user@host bin]$ ./standalone.sh --debug Server fails to start with ./standalone.sh: cannot shift [user@host bin]$ ./standalone.sh --debug 8787 Server fails to start with ./standalone.sh: bad substitution
This is also a problem on HP-UX ./standalone.sh --debug fails to start a server with ./standalone.sh[28]: shift: bad number
Jason, can you please reassign accordingly? I'm not sure who can help with looking into this one. Thanks!
*** 6.3.0.ER9 *** Solaris10: ./standalone --debug ./standalone.sh: cannot shift ./standalone --debug 7878 ./standalone.sh: bad substitution Solaris11: ./standalone --debug ./standalone.sh[28]: shift: (null): bad number HP-UX: ./standalone --debug ./standalone.sh[28]: shift: bad number
*** Bug 1199194 has been marked as a duplicate of this bug. ***
PR: https://github.com/jbossas/jboss-eap/pull/2399
Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup. No new test is needed, we have this covered.
Verified on EAP 6.4.1.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.