CDV ❯ Window just closes when running dso-env.bat on Windows
-
Bug
-
Status: Closed
-
2 Major
-
Resolution: Fixed
-
Kit & Installation
-
-
kkannaiy
-
Reporter: amiller
-
September 02, 2008
-
0
-
Watchers: 2
-
February 12, 2013
-
September 23, 2008
Description
http://forums.terracotta.org/forums/posts/list/1354.page
“I am new to Terracotta and i tried to configure Terracotta with JBoss application server. I followed the steps in the Start up guide. But when i try to execute dso-env.bat it doesn’t work. And if try to run without -q paramter the window just closes. Can some please help me with this. I am running jdk1.6.0_06 and jboss-4.0.5.GA in windows environment. Or if there is some other post please point me to that. “
I am using Terracotta-2.6.2.
Comments
Juris Galang 2008-09-03
Richard Dizmang 2008-09-18
Missed one… …skeletons/shared-base/common/tools/sessions/configurator-sandbox/tomcat5.0/stop.bat line 39
Juris Galang 2008-09-23
missed one call to exit without a /b, file: kits/skeletons/shared-base/common/tools/sessions/configurator-sandbox/tomcat5.0/stop.bat
fixed in:
- r10229 (2.7)
- r10230 (trunk)
Kalai Kannaiyan 2008-10-31
Tested with Terracotta 2.7.1-nightly, as of 20081030-161014 (Revision 10718 by cruise@WXPMO0 from 2.7), it is working as expected.
Steps:
- Install the kit
- Navigate to /install-root/bin and execute dso-env.bat
Actual:
C:\Program Files\Terracotta\terracotta-2.7.1-nightly-rev10718\bin>dso-env.bat Starting BootJarTool… 2008-10-31 12:21:01,000 INFO - Terracotta 2.7.1-nightly, as of 20081030-161014 ( Revision 10718 by cruise@WXPMO0 from 2.7) 2008-10-31 12:21:01,562 INFO - Configuration loaded from the Java resource at ‘/ com/tc/config/schema/setup/default-config.xml’, relative to class com.tc.config. schema.setup.StandardXMLFileConfigurationCreator. -Xbootclasspath/p:”C:\Program Files\Terracotta\terracotta-2.7.1-nightly-ee-rev10 718\bin..\lib\dso-boot\dso-boot-hotspot_win32_160_07.jar” -Dtc.install-root=”C: \Program Files\Terracotta\terracotta-2.7.1-nightly-rev10718\bin..”
dso-env calls boot-jar-path, but since an error occured (eg: missing TIMs) boot-jar-path’s branched to call an EXIT which actually exits CMD.EXE instead of the current script (boot-jar-path)
added /B switch to all calls to EXIT (rev 9948 in trunk) - This switch specifies to exit the current batch script instead of CMD.EXE. If executed from outside a batch script, it will quit CMD.EXE