[JBPAPP-6920] in 5.1.1 run.bat has typos that prevent finding run.conf.bat when not executed from the bin directory - JBoss Issue Tracker

XML

Word

Printable

Steps to Reproduce:

Hide

start run.bat from out side the bin directory

Show
start run.bat from out side the bin directory
Affects:

Release Notes
Workaround Description:

Hide

edit run.bat, and correct line 12 to read: set "DIRNAME=%~dp0%"

Show
edit run.bat, and correct line 12 to read: set "DIRNAME=%~dp0%"
Estimated Difficulty:
Low
Release Notes Text:

Hide
A syntax error was discovered in the <filename>run.bat</filename> batch file distributed with JBoss Enterprise Application Server 5.1.1. When run on Windows Server, if <filename>bin</filename> directory was not the current directory, <filename>run.bat</filename> failed to call the associated <filename>run.conf.bat</filename>. The batch file has now been corrected and <filename>run.conf.bat</filename> is called as intended.

Show
A syntax error was discovered in the <filename>run.bat</filename> batch file distributed with JBoss Enterprise Application Server 5.1.1. When run on Windows Server, if <filename>bin</filename> directory was not the current directory, <filename>run.bat</filename> failed to call the associated <filename>run.conf.bat</filename>. The batch file has now been corrected and <filename>run.conf.bat</filename> is called as intended.
Release Notes Docs Status:
Documented as Resolved Issue
Docs QE Status:
NEW

Line 12 of run.bat as delivered with JBoss EAP 5.1.1:

set "DIRNAME=!~dp0!"

Of course this should be:

set "DIRNAME=%~dp0%"

This prevents run.bat to find the run.conf.bat file when not executed from within the actual bin directory

blocks

SOA-3342 run.bat change in behavior

is duplicated by

JBPAPP-7114 run.bat change in behavior

relates to

JBPAPP-7060 run.conf.bat is ignored when placed inside a server profile