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 135876 - Different behavior of Tomcat when Glassfish is running
Summary: Different behavior of Tomcat when Glassfish is running
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-27 13:45 UTC by Petr Dvorak
Modified: 2008-09-17 14:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
When Glassfish is running (28.04 KB, image/png)
2008-05-27 13:46 UTC, Petr Dvorak 		Details
When Glassfish is NOT running (39.27 KB, image/png)
2008-05-27 13:46 UTC, Petr Dvorak 		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 Petr Dvorak 2008-05-27 13:45:39 UTC 
Product Version: NetBeans IDE Dev (Build 200805221203)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11
System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb)

Steps to reproduce:

1. Start NetBeans. Install Glassfish V2 and Apache Tomcat 6 so that you see both in the Services view. Make sure you set
the usernames and passwords at this point.
2. Change Tomcat password to some invalid value using the Properties window (invoked via pop-up menu)

OPTIONAL STEP (result depends on whether you do this or not): Start Glassfish

3. Start Tomcat (maybe you will have to go to properties and change the default port 8080 to some other one).
4. Expand the Tomcat nodes in services view

-> YOU DID OPTIONAL STEP: A dialog prompting for username and password is shown.
-> YOU DIDN'T DO THE STEP: A warning dialog is displayed.

See the screenshots.
Comment 1 Petr Dvorak 2008-05-27 13:46:08 UTC 
Created attachment 61974 [details]
When Glassfish is running
Comment 2 Petr Dvorak 2008-05-27 13:46:35 UTC 
Created attachment 61975 [details]
When Glassfish is NOT running
Comment 3 Vince Kraemer 2008-06-18 23:42:05 UTC 
the gf integration plugin installs a dialog to let the user recover from situations where there is an authorization
failure. I think that is a better choice then telling the user to go someplace else to fix the problem...

the Tomcat server integration should be improved to behave in a manner similar to that of the GF plugin
Comment 4 Petr Dvorak 2008-06-19 09:05:00 UTC 
I still think this is a defect, as the issue is not about different behavior of Tomcat from Glassfish, but about
different behaviour of Tomcat (when GF is running) from the very same Tomcat (when GF is not running)... (Do the steps
from the first description, once with the optional step and once without it...).

If this is really just an enhancement, I think it is worth to increase a priority, as ENHANCEMENT+P3=not(IMPLEMENTED)....
Comment 5 Petr Hejl 2008-08-27 11:11:30 UTC 
This seems to be already fixed in current builds.
Comment 6 Petr Dvorak 2008-09-17 14:31:00 UTC 
I am not able to reproduce the issue in 200809170201 - if someone still experience it, please reopen. Verified for now.