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 86832 - deployment may not deploy to the right server instance
Summary: deployment may not deploy to the right server instance
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Identity (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Peter Liu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-10 07:34 UTC by Peter Liu
Modified: 2006-10-20 01:44 UTC (History)
0 users

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 Peter Liu 2006-10-10 07:34:05 UTC
How to reproduce:

1. Deploy to a local instance.
2. Switch to another server instance in the wsp or wsc panel.
3. Deploy to the new instance.  
4. In the ant output, you'll see that the ServerProperties is still pointing to
the local instance.

Note that this can happen randomly depending on whether garbage collection
happens before or not.  This is due to caching of the amconfig.xml file which
for some reason is not up to date.
Comment 1 Peter Liu 2006-10-10 07:35:00 UTC
Need to figure out why the cache AMConfig instance is not up to date. 

Comment 2 Peter Liu 2006-10-11 05:10:20 UTC
Checked fixes into release55_dev branch.

IDE:-------------------------------------------------
IDE: [10/10/06 9:09 PM] Committing "Identity Profile API" started
Checking in AMConfigManager.java;
/cvs/identity/profileapi/src/org/netbeans/modules/identity/profile/api/configurator/impl/file/Attic/AMConfigManager.java,v
 <--  AMConfigManager.java
new revision: 1.1.2.7.2.3; previous revision: 1.1.2.7.2.2
done
IDE: [10/10/06 9:09 PM] Committing "Identity Profile API" finished
IDE: [10/10/06 9:09 PM] Diffing "AMConfigManager.java" finished
Comment 3 Peter Liu 2006-10-11 05:20:35 UTC
The issue here is that the path string used to look up the AMConfig from the
cache may contain a mixture of forward and backward slashes depending on whether
it's coming from the deploy task or the ui panel. That cause multiple instances
of the same AMConfig to be cached resulting in inconsistent values. The fix is
to normalize the path string used to look up the AMConfig from the cache.
Comment 4 Peter Liu 2006-10-11 23:33:58 UTC
changes reviewed and checked into release55 branch.
Comment 5 _ hlu 2006-10-12 21:49:15 UTC
closed the wrong one.
Comment 6 _ hlu 2006-10-12 21:50:16 UTC
change back to the old status.
Comment 7 _ hlu 2006-10-20 01:44:56 UTC
Tested with EP build20061015 and have not seen the problem. Close the bug.