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 38596 - Externally added tomcat server start problem
Summary: Externally added tomcat server start problem
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-10 16:15 UTC by Marek Fukala
Modified: 2004-03-15 13:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The IOE (838 bytes, text/plain)
2004-01-10 17:16 UTC, Marek Fukala
Details
The part of the catalina log with the NCDFE (4.86 KB, text/plain)
2004-01-14 17:01 UTC, Marek Fukala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Fukala 2004-01-10 16:15:53 UTC
To reproduce:
1) install the Tomcat 5.0.16 on your system
2) run IDE and open the 'Add new server instance'
dialog (from runtime/server registry/tomcat server
instancies node)
3) fill up the tomcat installation directory 
4) start the server

The server is started but with wrong CATALINA_BASE
property. It is set to the some directory as the
CATALINA_HOME instead of the directory within
netbeans user dir.

See the server output in the IDE window for details.
Comment 1 Marek Fukala 2004-01-10 17:16:18 UTC
Oops, I have just realized that the $CATALINA_BASE set to the
$USER_DIR/jakarta-tomcat-5.0.16_base is not mandatory for making the
deployment working. I am sorry.
Regardless, there is another problem which prevents me to use the
externall tomcat installation. After the server is started a
java.io.FileNotFoundException: http://localhost:8080/manager/list is
printed into IDE log and nothing works. You cannot deploy, even browse
the deployed contexts. Its caused by the fact that there is no web
application deployed after the start of the server (including the
manager).
If I run the tomcat from the console everything works fine.
Is there any way how to get know what command is used to run the
server? (currently I guess that this information is not visible
anywhere, at least I cannot find it).
Comment 2 Marek Fukala 2004-01-10 17:16:44 UTC
Created attachment 12816 [details]
The IOE
Comment 3 Pavel Buzek 2004-01-13 18:50:33 UTC
I'll look at this.
Comment 4 Pavel Buzek 2004-01-14 05:13:21 UTC
The command use is $catalina_home\bin\catalina.bat run (.sh on linux,
stop instead of run to stop the server)

The reason why I am calling manager/list when starting the server is
to make sure it really is already running -- this is important when
starting and immediately deploying to it. It is a workaround, I admit.
But the manager should be autoloaded by default. The problem is
probably somewhere else...

What is the port that you use for the externally added server? I
susspect it is not 8080? At least when I test with 8080 it works just
fine. But when I change the port in server.xml to 8082 it does not
work. This mean there is hardcoded 8080 somwhere (I will check
tomorrow).... But then again I think that you would notice that the
error message "java.io.FileNotFoundException:
http://localhost:8080/manager/list" is a little suspicious if you use
another port, so please let me know.


Comment 5 Marek Fukala 2004-01-14 16:51:19 UTC
Hi Pavel,
I guess I have discovered what is wrong. The problem is caused by the
fact, that the IDE adds a monitor filter section into conf/web.xml
(even if I explicitly check the option - what is in fact a different
bug) and then the server initialization fails with
NoClassDefFoundError for a schema2beans class (the exception from
tomcat log is attached). It seems to me that the forgets to copy a jar
with these beans during the server instance creation???

There is another subsequent problem that the tomcat cannot be started
externally since the web.xml contains the monitor servlet declaration.

I am sorry that I didn't look into the catalina log yestarday :-(
Comment 6 Marek Fukala 2004-01-14 17:01:51 UTC
Created attachment 12888 [details]
The part of the catalina log with the NCDFE
Comment 7 Pavel Buzek 2004-01-17 06:17:49 UTC
so far I fixed this part at least:

> (even if I explicitly check the option - what is in fact 
> a different bug) 
Comment 8 Pavel Buzek 2004-01-17 06:31:23 UTC
and the fix of the main problem was even easier ;-)
thanks for the tip - you were right
Comment 9 Marek Fukala 2004-03-15 13:14:24 UTC
verified