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 33610 - UI and functional defects with Internal Tomcat node in the Server Registry
Summary: UI and functional defects with Internal Tomcat node in the Server Registry
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: -S1S-
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-14 13:51 UTC by Alexei Mokeev
Modified: 2004-01-12 13:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Window with defect (31.82 KB, image/jpeg)
2003-05-14 13:54 UTC, Alexei Mokeev 		Details
Duplicate entries (48.76 KB, image/jpeg)
2003-05-14 13:57 UTC, Alexei Mokeev 		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 Alexei Mokeev 2003-05-14 13:51:31 UTC 
Sometimes "Internal Tomcat" node becomes unusual and shown 
just as "server" instead of "Internal Tomcat (JWSDP 1.0_01
[Not Running])".
Sometimes it contains two localhost:8081 instances.
After restart(without removing userdir) this problem 
usually disappear. Unfortunately there is not exact way to 
reproduce it.
Please see attached 1.jpg and 2a.jpg for details.

Reproduced with S1S 5 RC2 build.
Comment 1 Alexei Mokeev 2003-05-14 13:54:29 UTC 
Created attachment 10292 [details]
Window with defect
Comment 2 Alexei Mokeev 2003-05-14 13:57:13 UTC 
Created attachment 10293 [details]
Duplicate entries
Comment 3 Milan Kuchtiak 2003-05-14 15:00:21 UTC 
I guess, this might happen when playing with module
installation/uninstallation.

Nevertheless, the additional information would be useful.
Comment 4 Milan Kuchtiak 2003-05-14 15:02:40 UTC 
It seems that except of some UI defects this doesn't cause the
functional issues.
Comment 5 Milan Kuchtiak 2004-01-12 13:29:31 UTC 
Tomcat4 plugin was replaced by Tomcat5 plugin.
This issue isn't relevant to new plugin.
There is a different implementation of server instances in new server API.
Comment 6 Milan Kuchtiak 2004-01-12 13:30:29 UTC 
Tomcat4 plugin was replaced by Tomcat5 plugin.
This issue isn't relevant to new plugin.
There is a different implementation of server instances in new server API.