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 13415 - WebModule execution is not possible after exection of another webmodule.
Summary: WebModule execution is not possible after exection of another webmodule.
Status: CLOSED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: PC Linux
: P1 blocker (vote)
Assignee: Damian Frach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-09 10:47 UTC by Marek Fukala
Modified: 2003-07-02 08:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
The ConnectException (1.25 KB, text/plain)
2001-07-09 11:55 UTC, Marek Fukala 		Details
Thread dump created during Tomcat stopping timeout. (12.78 KB, text/plain)
2001-07-10 15:37 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 2001-07-09 10:47:50 UTC 
[010707, jdk1.3.0, rh linux 6.2]
How to reproduce:
1) execute a JSP in a webmodule or the webmodule (should work)
2) execute a JSP in another webmodule or execute the wm directly -> currently
running tomcat server must be terminated and a new one must be started. 
The 'Progress Monitor' dialog appears and shows the progress. The running server
is terminated but no new one is started (the some happens when no server is
running). After a timeout the dialog shows message: 'The Tomcat server process
is not running correctly' and after a very short time disappears.
Even if the Tomcat server is not running the execution window shows tomcat
server process.
After terminating the process an attached exception is printed into server
output tab.
Comment 1 Marek Fukala 2001-07-09 11:55:12 UTC 
Created attachment 1826 [details]
The ConnectException
Comment 2 Damian Frach 2001-07-09 13:02:32 UTC 
-
Comment 3 Marek Fukala 2001-07-10 15:34:19 UTC 
The bug is not exactly reproducible - it happens in some circumstances
which seems to be related with threads timing and their synchronization.
Comment 4 Marek Fukala 2001-07-10 15:37:31 UTC 
Created attachment 1841 [details]
Thread dump created during Tomcat stopping timeout.
Comment 5 Petr Jiricka 2001-07-17 17:34:28 UTC 
Fixed on 2001-07-17
Comment 6 Marek Fukala 2001-07-24 15:09:54 UTC 
verified in 010723_1
Comment 7 Quality Engineering 2003-07-02 08:28:16 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.