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 42678 - no tomcat start on os/2
Summary: no tomcat start on os/2
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC OS/2
: P4 blocker (vote)
Assignee: Sherold Dev
Depends on: 44136 49487
  Show dependency tree
Reported: 2004-05-01 14:11 UTC by marco
Modified: 2005-09-05 10:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Contain a .cmd file for start tomcat 4/5 on os/2 and eComstation (5.02 KB, application/octet-stream)
2004-07-12 21:41 UTC, marco

Note You need to log in before you can comment on or make changes to this bug.
Description marco 2004-05-01 14:11:18 UTC
I use java1.4.2 from innoteck but when I lunch
tomcat 5 from runtime or jsp file. THe server not
start (I found in moniror this message:
non a valid executable) and monitor stop loading
on 90%
Comment 1 Marek Fukala 2004-05-03 06:28:52 UTC
Have you tried to check whether the has an execution
right? In case of the bundler tomcat server it is stored in
Comment 2 Martin Grebac 2004-05-03 08:40:37 UTC
Another suggestion might be to use a fresh user directory - this might
help if you used a pre-release version of 3.6 (like a dev build or beta).
Comment 3 marco 2004-05-04 18:44:14 UTC
The status message display also error=0 when try start tomcat server.

Is possible for you change the start up script for loading a
catalina.cmd (A OS/2 executable command line) I think the problem is
in java_home directory that not set correctly!
Comment 4 marco 2004-06-29 20:39:15 UTC
I test the same problem on nb 4.0 When lunch a tomcat the nb lunch
catalina.bat in os/2 enviroment the bat file isen't a script file
(OS/2 use .cmd script file)

Is possible include a script on

this a cmd version of file.... little modify on classpath.cmd file are

and verify the os for lunch correct script.... or lunc tomcat in same
mode of 3.5.1 that works ok on OS/2
Comment 5 marco 2004-07-12 21:41:16 UTC
Created attachment 16211 [details]
Contain a .cmd file for start tomcat 4/5 on os/2 and eComstation
Comment 6 marco 2004-07-12 21:43:58 UTC
I post a .cmd file tha I use for lunch tomcat on os/2 
The only my modify is the set correct java_home end path in start of
file classpath.cmd

I find in source code that only catalina.bat and are set
for lunch a tomcat on pres button I think that insert a .cmd is
possible and isn't difficult!
Comment 7 Pavel Buzek 2004-07-21 19:57:52 UTC
As Marek pointed out I would prefer to first find out if you really
cannot use the .sh scripts. IMO these are designed for os/2 (at least and contain notes about os/2). I do not
want to create workaround if there is a standard solution.

Can you find out if there are execution rights for bin/*.sh in tomcat
on you machine? If not, can you try setting them and then test if it
Comment 8 marco 2004-07-22 21:32:03 UTC
I try with nb 3.6 and I set a and how a
executable file.
When I lunch a tomcat server the monitor window display a red string
that say me : 
- e:\netbeans\jakarta-tomcat-5.1.19\bin\ are not a valied
executable -

Same problem with daily nb 4.0 version but the file is catalina.bat

I don't see where are a note for os/2 in and

Comment 9 Sherold Dev 2004-07-29 15:32:57 UTC
Since OS/2 is not officially supported by NetBeans nor Tomcat, this
issue will not be fixed for now.
Comment 10 lkishalmi 2004-09-22 14:33:33 UTC
I've proted the complete set of Tomcat launchers to OS/2 REXX.
I've sent them to jakarta tomcat. If we are lucky it will be in the
5.0.29 version. So this issue could be fixed.
Comment 11 zikmund 2004-09-22 14:36:52 UTC
Could you please fill the URL by the Tomcat's bug link?
Comment 12 lkishalmi 2004-09-22 14:45:21 UTC
Here you are!
Comment 13 lkishalmi 2004-10-01 23:32:46 UTC
I've reopened this issue as I see some hope that it could be fixed.
However at P4.
Comment 14 Sherold Dev 2005-08-02 17:15:07 UTC
Closing as WONTFIX. As a workaround we have added an ability to specify a custom
catalina startup script in the Tomcat customizer.