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 38598 - Webmodule behaviour broken after removal and subsequent add of the default server instance.
Summary: Webmodule behaviour broken after removal and subsequent add of the default se...
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-10 17:51 UTC by Marek Fukala
Modified: 2004-02-17 10:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Relevant part of the IDE log. (13.57 KB, text/plain)
2004-01-10 17:52 UTC, Marek Fukala 		Details
A threaddump (11.79 KB, text/plain)
2004-02-16 15:44 UTC, Marek Fukala 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Fukala 2004-01-10 17:51:50 UTC 
I know that this situation is quite weird, but I
hope this information can help to find another
bugs in the code. 
Please try to follow these steps:
1) remove the default tomcat instance
2) add it back (set the tomcat install dir into
the $IDE_HOME/jakarta-tomcat-5.0.16 and shared
directory to the
$USER_DIR/jakarta-tomcat-5.0.16_base. Enter the
admin name and password too. (set all properties
to their original values (before the removal).
3) start the server
4) convert sample dir into a webmodule
5) click on WEB-INF node or try to open its
properties.

You will get a buch of exceptions informing you
that there is something rotten in the code ;-).

I am not sure which module this bug belongs to so
I am assigning it simply to the web module.
Comment 1 Marek Fukala 2004-01-10 17:52:27 UTC 
Created attachment 12817 [details]
Relevant part of the IDE log.
Comment 2 Martin Grebac 2004-02-03 12:32:57 UTC 
Will have a look at it.
Comment 3 Martin Grebac 2004-02-13 12:09:37 UTC 
Works for me now. I believe this was fixed by recent Milan and Pavel's
fixes (for bundled tomcat port reading/writing and context root).
Reopen if not.
Comment 4 Marek Fukala 2004-02-16 15:43:57 UTC 
I have tried to deploy some modules after the removal/add of the
default instance and since that the deployment is broken.
Try this:
1) mount a webmodule
2) execute it
3) remove the default tomcat instance
4) add it back
5) execute the wm again

This causes that during the second execution the tomcat is tarted but
then the progress bar stucks in the middle without any message or
exception.
Note that newly added (after the removal/add) webmodule CAN be executed.
Comment 5 Marek Fukala 2004-02-16 15:44:57 UTC 
Created attachment 13452 [details]
A threaddump
Comment 6 Marek Fukala 2004-02-17 10:26:10 UTC 
The problem is likely not caused only by the simple add/remove of the
default server instance. I have filled a separate bug #40141 for this
problem and closing this as works for me.