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 99479 - Unable to stop Personal domain
Summary: Unable to stop Personal domain
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-30 00:53 UTC by davisn
Modified: 2007-04-10 00:26 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 davisn 2007-03-30 00:53:34 UTC 
The IDE could not stop the Application Server Personal domain (eg, domain2)

STEPS TO REPRODUCE:
1. Install Netbean IDE 551, build 03/30/07
2. Install AppServer 9.1 SDK, build 03/30/07
3. Add personal domain (domain2) to Servers list
   From the Netbean IDE, select Runtime tab > right click at Servers > select
Add Server
    Server: "Sun Java ...Application Server"
    Name: test-domain2
    Click Next and enter: 
    Platform Location: c:\sun\SDK503_10
    Create Personal Domain
    Click Next 
    Domain Folder: c:\sun\SDK503_10\domains\domain2
    Click Next
       Admin UserName: admin
       Admin Password: adminadmin
    Click Finish
4. Right click test-domain2, select Start to startv server
5. After the domain2 started, select Stop menu
BUG:
    Can't stop domain2
Comment 1 Nitya Doraisamy 2007-04-05 02:43:27 UTC 
Please attach ide's log and server.log
Comment 2 Nitya Doraisamy 2007-04-09 23:26:45 UTC 
Unable to reproduce. Davis, you were able to stop the domain when we were
debugging 100041.

Please attach the logs requested if you are still seeing this issue
Comment 3 davisn 2007-04-10 00:11:47 UTC 
I was not able to reproduce the problem with the latest Netbean 551 RC1 build
either. The problem was caused probably from using the old Netbean build. You
can close the bug
-davis
Comment 4 Nitya Doraisamy 2007-04-10 00:26:48 UTC 
User confirms description of issue had wrong build date and was using a older
build which had this issue.