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 13764 - the tomacat output is not read
Summary: the tomacat output is not read
Status: CLOSED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Damian Frach
URL:
Keywords:
: 19750 22387 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-07-19 18:32 UTC by L Martinek
Modified: 2003-07-02 08:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (14.93 KB, text/plain)
2001-07-19 18:32 UTC, L Martinek 		Details
Thread dump from tomcat output window (8.62 KB, text/plain)
2001-07-19 18:34 UTC, L Martinek 		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 L Martinek 2001-07-19 18:32:11 UTC 
[010718_1]
Tested on Windows2000, doesn't occur on Linux.

If you have some CVS filesystem mounted then Tomcat starts very slowly. If the CVS filesystem is webmodule then Tomcat starts even 
slower. You haven't to execute JSP from CVS filesystem, you can execute it from local filesystem. Crucial is just presence of CVS 
filesystem.

To reproduce:
1. Mount some local filesystem, convert it into webmodule, create JSP and execute it.
2. Mount some CVS filesystem, convert it into webmodule.
3. Execute with force reload the JSP. 
Progress monitor stalls with message about starting tomcat and after some long time red message appears in progress monitor saying that 
tomcat isn't started correctly, but tomcat will be running.
4. Unmount CVS filesystem.
5. Execute (force reload) JSP. Now execution is still slow.
6. Execute (force reload) JSP again. Now execution is fast.
Comment 1 L Martinek 2001-07-19 18:32:57 UTC 
Created attachment 1921 [details]
Thread dump
Comment 2 L Martinek 2001-07-19 18:34:20 UTC 
Created attachment 1922 [details]
Thread dump from tomcat output window
Comment 3 Damian Frach 2001-10-22 16:27:55 UTC 
problem is caused: the tomacat output is not read

- the synchronize method is blocking; it waits for server start
- but the tomcat is blocked, because output strems cache are full and 
the tomcat waits for the stream flushing

solution:
- the IDE will read the server output during the synchronize
Comment 4 Jan Chalupa 2001-11-27 17:37:05 UTC 
Target milestone -> 3.3.1.
Comment 5 Damian Frach 2002-01-28 12:39:30 UTC 
work around:

problem is caused, the tomcat output is too long
if you minimize the tomcat output, everythink will be OK
the maximum number is about 8000 characters
Comment 6 Milan Kuchtiak 2002-01-28 12:41:29 UTC 
*** Issue 19750 has been marked as a duplicate of this issue. ***
Comment 7 Damian Frach 2002-01-29 08:12:49 UTC 
*** Issue 19750 has been marked as a duplicate of this issue. ***
Comment 8 Damian Frach 2002-01-29 08:14:42 UTC 
because the 19750 is duplication of this bug and its priority is P2
Comment 9 Damian Frach 2002-01-29 14:55:32 UTC 
fixed
Comment 10 Damian Frach 2002-01-29 15:06:18 UTC 
fixed only in the orion_ea brench
Comment 11 Petr Jiricka 2002-01-30 18:08:16 UTC 
A patch for branch release33 (NB 3.3.1) was committed to branch 
bugfix_13734 on file

j2eeserver/src/org/netbeans/modules/j2ee/impl/DefaultServerInstanceMan
ager.java
Comment 12 Damian Frach 2002-04-15 12:59:54 UTC 
*** Issue 22387 has been marked as a duplicate of this issue. ***
Comment 13 Quality Engineering 2003-07-02 08:25:22 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verify.
Comment 14 Quality Engineering 2003-07-02 08:27:39 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.