This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 26158 - Cannot launch Tomcat
Summary: Cannot launch Tomcat
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC OS/2
: P4 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-31 17:19 UTC by _ gtzabari
Modified: 2003-02-04 14:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2002-07-31 17:19:26 UTC
3.4 RC1

  When executing JSPs I get:

java.io.IOException: DosCreateProcess:
D:\java131\jre\..\bin\java OS/2 rc = 479 reason = ''
	at java.lang.OS2Process.create(Native Method)
	at java.lang.OS2Process.<init>(OS2Process.java:76)
	at java.lang.Runtime.execInternal(Native Method)
	at java.lang.Runtime.exec(Runtime.java:582)
	at java.lang.Runtime.exec(Runtime.java:505)
	at java.lang.Runtime.exec(Runtime.java:471)
	at
org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:229)
	at
org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:132)
	at
org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:293)
	at
org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:304)
[catch] at
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.createNewTomcatProcess(Tomcat40Installation.java:863)
	at
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.startServerInExecMode(Tomcat40Installation.java:823)
	at
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.synchronizeStart(Tomcat40Installation.java:963)
	at
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.incrementalDeploy(Tomcat40Installation.java:600)
	at
org.netbeans.modules.tomcat.tomcat40.Tomcat40Instance.deploy(Tomcat40Instance.java:260)
	at
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.doDeploy(DefaultServerInstanceManager.java:136)
	at
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.startExecution(DefaultServerInstanceManager.java:150)
	at
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.serverInstanceStartExecution(DefaultServerInstanceManager.java:101)
	at
org.netbeans.modules.j2ee.impl.DefaultExecPerformer.startExecution(DefaultExecPerformer.java:105)
	at
org.netbeans.modules.web.execution.WebDefaultExecPerformer.startExecution(WebDefaultExecPerformer.java:256)
	at
org.netbeans.modules.j2ee.impl.ServerExecutor.execute(ServerExecutor.java:74)
	at
org.netbeans.modules.j2ee.impl.ServerExecutor.execute(ServerExecutor.java:64)
	at
org.netbeans.modules.j2ee.impl.ExecSupport.start(ExecSupport.java:125)
	at
org.netbeans.modules.j2ee.impl.ServerExecSupport.start(ServerExecSupport.java:141)
	at
org.openide.actions.ExecuteAction.execute(ExecuteAction.java:139)
	at
org.openide.actions.ExecuteAction.execute(ExecuteAction.java:236)
	at
org.openide.actions.ExecuteAction.performAction(ExecuteAction.java:101)
	at
org.openide.util.actions.NodeAction.performAction(NodeAction.java:179)
	at
org.openide.util.actions.NodeAction.actionPerformed(NodeAction.java:170)
	at
org.netbeans.core.ModuleActions$1.run(ModuleActions.java:100)
	at org.openide.util.Task.run(Task.java(Compiled
Code))
	at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java(Compiled
Code))

   The problem is that you should be using
"d:\java131\jre\bin\java" not
"D:\java131\jre\..\bin\java".  I've set the
priority to P2 because I can't find a workaround;
this commandline doesn't seem to be configurable
anywhere.
Comment 1 David Strupl 2002-08-01 09:08:05 UTC
Please evaluate. If there is any problem in core please reassign back.
Comment 2 _ rkubacki 2002-08-01 09:45:19 UTC
Explorer -> Runtime tab -> server registry -> find node of given
instance (likely Internal server) and update its properties. As there
is possibility to configure this I am decreasing priority and we will
check what is apropriate value for this platform.
Comment 3 _ gtzabari 2002-08-01 15:23:19 UTC
Confirmed. Problem is {jdk.home} which is incorrect for OS/2. As a
result all references to that variable (beyond the scope of Tomcat)
will break.

I believe this is a problem in core. Please reassign if you agree.
Also consider increasing the priority since multiple modules might be
affected.
Comment 4 _ gtzabari 2002-08-01 15:23:58 UTC
Confirmed. Problem is {jdk.home} which is incorrect for OS/2. As a
result all references to that variable (beyond the scope of Tomcat)
will break.

I believe this is a problem in core. Please reassign if you agree.
Also consider increasing the priority since multiple modules might be
affected.
Comment 5 _ rkubacki 2002-09-06 17:22:34 UTC
Milan, can you find some way how to configure the default value
properly on all platforms?
Comment 6 Milan Kuchtiak 2002-09-09 09:12:59 UTC
{jdk.home} was replaced by {java.home} in Tomcat Executor 
end Tomcat Debugger.
Comment 7 Milan Kuchtiak 2002-09-09 09:14:43 UTC
I cannot test the behaviour on OS/2.The change I've made 
should help. If not - please reopen the bug and write some 
comment.