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 65132 - Deployment fails with monitor enabled on 5.5.9
Summary: Deployment fails with monitor enabled on 5.5.9
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-26 15:37 UTC by Jaroslav Pospisil
Modified: 2005-10-03 14:57 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (119.83 KB, image/png)
2005-09-26 15:39 UTC, Jaroslav Pospisil
Details
Outputs and logs (26.98 KB, text/plain)
2005-09-26 15:41 UTC, Jaroslav Pospisil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2005-09-26 15:38:00 UTC
Build 200509251930

1)Add external Tomcat 5.5.9 with private Catalina basedir
2)Enable HTTP Monitor for newly added Tomcat
3)Create web module on this Tomcat
4)Run it
5)ERROR: Deployment fails and error message appears
Server is visual as running,but after clicking on Web Applications node,there is
nothing displayed.Server could be normally stopped and after disabling of
monitor it runs again.
I'm attaching screenshot of error message and all logs.
Comment 1 Jaroslav Pospisil 2005-09-26 15:39:10 UTC
Created attachment 25187 [details]
screenshot
Comment 2 Jaroslav Pospisil 2005-09-26 15:41:15 UTC
Created attachment 25188 [details]
Outputs and logs
Comment 3 Petr Jiricka 2005-10-03 11:41:28 UTC
Tomcat 5.5.9 is widely used, and this blocks the integration of 5.5.9 to
NetBeans, so I am raising this to P2. Stepan, could you please look at it? Thanks.
Comment 4 Sherold Dev 2005-10-03 14:57:43 UTC
This issue was installation specific and was caused by the port conflict between
the Tomcat and NetBeans internal HTTP server, which is used by the HTTP Monitor
- both servers were configured to use the same 8082 port.

Since the standard Tomcat distribution uses the 8080 port, this is not a real
issue -> closing as invalid.