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 203868 - Forgetting server configuration
Summary: Forgetting server configuration
Status: RESOLVED DUPLICATE of bug 198414
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.0.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 01:45 UTC by MacCoombe
Modified: 2011-10-26 23:00 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 MacCoombe 2011-10-18 01:45:21 UTC 
I have installed NetBeans 7.0.1 on Win XP SP3 machine with a pre-existing GlassFish 3.0.1 install (which was installed as part of a previous NB 6.9 install).

I am able to configure access to the GlassFish instance using tools > servers, in-place deploy etc works fine so the configuration is demonstrably OK. However, when I close and reopen NB, the GF server has disappeared from NB's server list and needs to be re-added.

I have found an indirect reference to a Windows-only behaviour that might cause this issue (see http://forums.netbeans.org/post-104148.html#104148), but have been unable to track down any concrete bug report etc to back up that claim.
Comment 1 MacCoombe 2011-10-18 01:48:00 UTC 
I should also note that I don't intend to suggest this issue is isolated to only GF installs - I simply don't have any other server to test this issue against.
Comment 2 Vince Kraemer 2011-10-26 16:44:39 UTC 
I have not been able to reproduce this issues. please attach the NB message.log file to this issue.
Comment 3 Vince Kraemer 2011-10-26 22:54:03 UTC 

*** This bug has been marked as a duplicate of bug 198414 ***
Comment 4 MacCoombe 2011-10-26 23:00:49 UTC 
(In reply to comment #2)
> I have not been able to reproduce this issues. please attach the NB message.log
> file to this issue.

I'm afraid I've since moved to a new machine with a fresh install of NB 7.0.1 (which does not exhibit the offending behaviour), so unfortunately I no longer have any logs to provide.

However, I see you've marked this bug as a dupe of 198414 (which does include logs), so I imagine that's ok. :)