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.
[netbeans41 FCS + plugin builds 20-May] I was able to build and deploy simple EJB module with one session bean to weblogic server. Then I did some changes and tried to deploy again. However, got a error: weblogic.management.ManagementException: Current deployment is already set Deployment FAILED: weblogic.management.ManagementException: Current deployment is already set E:\work\StalessTest\nbproject\build-impl.xml:281: Deployment failed. BUILD FAILED (total time: 1 second) User, can't undeploy Apps from IDE. Therefore, the app should be undeployed before deployment.
The main cause of this issue is actually in j2eeserver module. The current implementation of weblogic deployment uses plain jsr88 (no directory or incremental deployment). Weblogic server does not support redeploy operation - this is perfectly legal (DeploymentManager returns false from isRedeploySupported()). J2EEServer needs to do undeploy/deploy in this case. This is a bug that I will fix. Second problem is that even with that I am getting an error from weblogic: <29.7.2005 18:49:58 EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating distribute operation for application, enterpriseapplication2.ear [archive: C:\Documents and Settings\pb97924\EnterpriseApplication2\dist\enterpriseapplication2.ear], to examplesJMSServer examplesServer ReliableWseeSAFAgent WseeJMSServer .> [Deployer:149034]An exception occurred for task [Deployer:149026]distribute application enterpriseapplication2.ear on examplesJMSServer,WseeJMSServer,examplesServer,ReliableWseeSAFAgent.: [Deployer:149169]Requires server restart for completion.. Requiering restart for redeploy is wierd...
The j2eeserver will use undeploy/deploy if redeploy is not supported: /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/TargetServer.java,v <-- TargetServer.java new revision: 1.41; previous revision: 1.40
Fixed in trunk for the local server (the plugin uses autodeployment). I am not sure it can be fixed for remote server where the plugin uses weblogic jsr88 (see my comment from Fri Jul 29 22:56:49).
*** Issue 59796 has been marked as a duplicate of this issue. ***
*** Issue 62064 has been marked as a duplicate of this issue. ***
This is no longer a defect because the remote server support has been removed for 5.0. When added again (issue 64128) this problem has to be resolved.
Later resolution should not be used.
Marking as Won't Fix.
Ok, whatever is the reason why LATER should not be used but is still offered as an option, I just want to clarify that this issue _should_ be fixed _later_ if possible. Leaving the status as is.