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.
Create an EJB Create a Webservice Deploy the webservice Redeploy the webservice. It gives you the following msg in the output window: init: deps-jar: compile: library-inclusion-in-archive: Building jar: D:\sherrydev\SOA\delet\LoanProcessor\dist\LoanProcessor.jar dist: pre-run-deploy: Distributing D:\sherrydev\SOA\delet\LoanProcessor\dist\LoanProcessor.jar to [localhost:4848_server] Start registering the project's server resources Finished registering server resources deployment started : 0% deployment finished : 100% Deploying application in domain completed successfully Rollback failed Trying to create reference for application in target server failed; Application reference LoanProcessor already exists in server instance server. D:\sherrydev\SOA\delet\LoanProcessor\nbproject\build-impl.xml:338: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 11 seconds) I have to undeploy and then redeploy
*** Issue 84829 has been marked as a duplicate of this issue. ***
*** Issue 84828 has been marked as a duplicate of this issue. ***
Did you deploy LoanProcessor module from IDE? Are you able to reproduce this every time?
which nb build? Which IDE build? Which JDK on both? The only thing I guess is the OS...
I used milstone19: http://balui.sfbay/kits/oriondev/main/cokemilestone20/installers/ jdk1.5.0_03 Jave EE 5 SDK nightly Ide build: http://balui.sfbay.sun.com/kits/oriondev/coke_soa/Build060913_13/ To reproduce the bug first deploy the ejb then exit IDE and then start IDE, start AS. Redeploy.
*** Issue 84822 has been marked as a duplicate of this issue. ***
I am trying to reproduce this, but not having much success. I did the following: 1. Create a standard Java EE 5 EJB Module project, targeting my GF instance. this creates a project called EJBModule4... 2. right click on the project node select New->Web Service item this opens a dialog box 3. I set the Package field to 'foo' and click finish. a new file opens in the editor 4. I set the insert cursor inside the file between the curly braces and select the Web Service->Add Operation item from the menu this opens a dialog 5. I accept the defaults this adds 'operation()...' to the file 6. Select Deploy from right-click menu of project node. the server starts. the module deploys 7. I exit the ide. this stops the server 8. I start the ide. the usual susp... windows appear 9.I start the server from the runtime tab. the log view opens and displays the start up messages. 10. I select the Deploy item from the project's right-click menu the deployment is successful. Obviously, you did something different. Please provide additional details or instructions.
RE: comments from barkodar Wed Sep 13 21:23:34 can you provide the link to the files that you installed? the first link has about 60 files... 3 of which are likely candidates for me to try to use. The other link just has a bunch of directories.... I am confused... Also, is this issue something that you are seeing in NetBeans 5.0 or 5.5?
Cannot reproduce in latest Nb5.5 build. But because it happens in "pre-run-deploy:" task I guess it is a Coke related issue.
I am using Coke milestone Build 20 (060912_2) is available at: http://balui.sfbay/kits/oriondev/main/cokemilestone20/installers/ Idenightly build:http://balui.sfbay.sun.com/kits/oriondev/coke_soa/Build060914_8/ I have the EJB module which I will atach it, I am trying to redeploy and I get the following msg: init: deps-jar: compile: library-inclusion-in-archive: Building jar: D:\sherrydev\SOA\del2\LoanProcessor\dist\LoanProcessor.jar dist: pre-run-deploy: Distributing D:\sherrydev\SOA\del2\LoanProcessor\dist\LoanProcessor.jar to [localhost:4848_server] Start registering the project's server resources Finished registering server resources deployment started : 0% deployment finished : 100% Deploying application in domain completed successfully Rollback failed Trying to create reference for application in target server failed; Application reference LoanProcessor already exists in server instance server. D:\sherrydev\SOA\del2\LoanProcessor\nbproject\build-impl.xml:338: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 14 seconds)
log: deployed with moduleid = LoanProcessor ADM1082:Creating the application reference failed - Detailed Message: com.sun.enterprise.deployment.backend.IASDeploymentException: Application reference LoanProcessor already exists in server instance server. at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getAndValidateDeploymentTarget(DeploymentServiceUtils.java:1024) at com.sun.enterprise.deployment.phasing.PEDeploymentService.associate(PEDeploymentService.java:402) at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.createApplicationReference(ApplicationsConfigMBean.java:668) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336) at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77) at $Proxy1.invoke(Unknown Source) at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297) at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56) at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142) at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109) at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Undeployment of component [LoanProcessor] failed. Application LoanProcessor is referenced by server and must be referenced by no server instances or clusters. JBISE6006: JavaEEServiceEngine: End Point : Service Name: [LoanProcessorService] , Endpoint Name: [LoanProcessorPort] disabled successfully JBISE6007: JavaEEServiceEngine: End Point : Service Name: [LoanProcessorService] , Endpoint Name: [LoanProcessorPort] removed successfully CORE5024: EJB module [LoanProcessor] unloaded successfully! DeployedItemRef postDeregistration failed. Load Balancer Monitoring MBeans might be lying around if this application is being load balanced UTIL6040: Error attempting to delete C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-modules\LoanProcessor\META-INF\wsdl\LoanProcessorService.wsdl UTIL6041: Performing gc to try to force file closures UTIL6042: Attempt to delete C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-modules\LoanProcessor\META-INF\wsdl\LoanProcessorService.wsdl succeeded after 2 retries wsgen successful DPL5306:EJB Web Service Endpoint [LoanProcessor] listening at address [http://arash.sfbay.sun.com:8080/LoanProcessorService/LoanProcessor] deployed with moduleid = LoanProcessor ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable ejb/LoanProcessor] LDR5010: All ejb(s) of [LoanProcessor] loaded successfully!
Created attachment 33958 [details] ejb module
Created attachment 33961 [details] new log file is attached
spoke to user. It sounds like these are the missing details... user has an istall of: http://balui.sfbay/kits/oriondev/main/cokemilestone20/installers/java-tools-bundle-main-060912_2-windows.exe Then... unzips http://balui.sfbay.sun.com/kits/oriondev/coke_soa/Build060914_8/zips/ide-coke_soa-060914_8.zip clears their userdir starts the IDE that comes from the zip this is 'Restart IDE' Registers the app server that was created when the installer ran. Reopens the attached project (which has already been deployed on their AS) tries to do a deploy.
can reproduce this, when the user clears the user directory and has deployed applications. As best I can tell, the user needs to: create an project deploy the project shutdown clear their user directory restart the ide reregister the server reopen their existing project deploy The workaround for this is to undeploy the module using the runtime tab. subsequent deploys will function correctly
vince kraemer wrote: > http://www.netbeans.org/issues/show_bug.cgi?id=84827 > > I think it should be lowered to p3. the filer concurred. > > I will leave it up to you. > +1 Ludo > vbk lowering to p3 this needs to be examined completely in 6.0
I tried this several times and cannot reproduce this either. I redeployed EJB 3 or 4 times in one session and each time was successful. What is the status of the bug, are we keeping it open for further evaluation?
read Additional comments from vkraemer.
Stepan: the IDE decides to use the equivalent of distribute instead of redeploy based on data kept by the j2eeserver layer in the userdir, right? Does the j2eeserver layer attempt to synchronize the model of the deployed apps in the userdir with the actual content of an app server? Shouldn't it? I guess I could hack something for this into the serverplugin, but it seems like every plugin would have to have a similar hack...
Seems to be ralated to issue 91792.
I can't reproduce the issue with steps in desc16 (current netbeans 6.0 build). Everything works fine on Sun App Server, GF1 and GF2. Any suggestions, Vince?
Can anyone still reproduce the issue? I'm not able to reproduce it.
No response and not reproducible. Closing as WORKSFORME.