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 146278 - Restarting V3 in profile mode brings the server to normal mode
Summary: Restarting V3 in profile mode brings the server to normal mode
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Sun Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-05 07:02 UTC by dpkumar
Modified: 2009-09-17 00:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dpkumar 2008-09-05 07:02:09 UTC
NB:NetBeans IDE Build 200809031401
GFV3:b-22
JDK:jdk1.6.0

Steps to reproduce:
-Install NB and GF V3-b22.
-Open IDE and register GF V3 server.
-Start V3 in server in Profile node.
-Check the server resource node--->which is not expandable.
-Check 'View Admin console'.
-Restart server.


ISSUE:
After restarting server in profile mode, able to expand the resource node and able to deploy the application selecting
'Run' target where as in V2 which is not allowable.
-Even able to view the admin console.
Comment 1 _ pcw 2008-09-09 15:31:32 UTC
I reproduced this.  Definitely some weird state changes going on due to confusion over profile mode.
Comment 2 Vince Kraemer 2008-12-01 23:35:13 UTC
is this a manifestation of the server state issues that the current v3 plugin has? if it is we will be working on this
in the 7.0 time frame...
Comment 3 Vince Kraemer 2009-09-16 23:55:40 UTC
Assigned engineer: please correct the tm value.  nb 6.7 has shipped, so a tm of
6.7  is invalid at this point
Comment 4 Vince Kraemer 2009-09-16 23:59:57 UTC
assign outher half of pcw's issues
Comment 5 Vince Kraemer 2009-09-17 00:47:18 UTC
The restart item is disabled... so I do not think this can be reproduced any more.

please reopen this issue with detailed steps if you can reproduce this with recent builds of v3 and NB 6.8...