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 149367 - Wrong message about invalid login/password appears after refreshing
Summary: Wrong message about invalid login/password appears after refreshing
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 135189 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-07 13:43 UTC by Roman Mostyka
Modified: 2009-04-08 19:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screenshot of wrong message under GlassFish's node. (10.81 KB, image/jpeg)
2008-10-07 13:44 UTC, Roman Mostyka 		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 Roman Mostyka 2008-10-07 13:43:14 UTC 
1. Built NetBeans from fresh sources.
2. Installed GlassFish bundled with NetBeans distribution.
3. Started build NetBeans and registered GlassFish with valid username/password.
4. Expanded GlassFish's node.

Result: Node under server's node contains message that user name or password is wrong, but they aren't wrong. I was able
to expand this node, but after refreshing I got this message.
Comment 1 Roman Mostyka 2008-10-07 13:44:09 UTC 
Created attachment 71285 [details]
Screenshot of wrong message under GlassFish's node.
Comment 2 Vince Kraemer 2008-10-28 00:23:38 UTC 
it looks like the server is stopped at a breakpoint, actually.
Comment 3 Roman Mostyka 2008-10-28 10:30:45 UTC 
If it is stopped on a breakpoint, shouldn't it's node be expandable anyway?
Comment 4 Vince Kraemer 2008-10-28 15:43:35 UTC 
The node cannot expand because the source of the data (the app server) is blocked.
Comment 5 Vince Kraemer 2008-11-14 22:02:24 UTC 
this should be fixed in 7.0. it is also fixable in 7.0
Comment 6 Vince Kraemer 2008-11-14 23:29:00 UTC 
*** Issue 135189 has been marked as a duplicate of this issue. ***
Comment 7 Vince Kraemer 2009-04-08 19:14:10 UTC 
I just tried to reproduce this with a recent build of 6.7 and could not.

Reopen with more detailed steps to reproduce, if you still run into this with 6.7