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.
Created the EJB and webservices. Created teh BPEL project. Created the BPEL Proceess. Created all required schema and wsdl for the bpel project Copied the wsdl generated from the webservices to the BPEL Project Created teh Composite Application and test case. When I deply the CA I get the following Msg: run the test case I get the following msg: Starting suId : CompositeApp4-com.sun.httpsoapbc-1.0-2 Cannot activate endpoint {http://loanprocessor.sun.com/}LoanProcessorService,LoanProcessorPort,outbound Reason: Endpoint has already been activated. Activating endpoints Activated endpoints Activating endpoints Attempt to create Grizzly connector at 18,181 Grizzly failed to stop. ALL Cannot register MBean for the Protocol grizzlyHttpProtocol.selectorRegisterProtocol WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 18181 Grizzly connector created at 18,181 Prepared inbound endpoint {http://j2ee.netbeans.org/wsdl/LoanRequestor}service1,port1,inbound mapped to context /LoanRequestor Activated endpoints Started : CompositeApp4-com.sun.httpsoapbc-1.0-2 The test fails: <faultstring>Unable to located activated endpoint for service connection {http://j2ee.netbeans.org/wsdl/LoanRequestor}service1 port1.</faultstring>
Created attachment 33856 [details] the loanapplication
this usually means the app was already deployed to AS. There is a big tech note on this issue in the Beta2 user guide written by me and Dmitry. You cannot deploy the same endpoint twice from different CompositeApp projects. Plese see the developer guide for details on how to get around this.
Mike, I don't even get to deploy it once.
I used the latest Milestone, latest nightly build and have not seen this problem Today. The difference that I see is Populate Catalog was not working. Now it is working. Please hold on to this bug till I try couple more scenarios on todays build. Thanks.
I have not seen this in the latest nightly build 060919_8. I suppose it is fixed. I will close this for now.
I was able to reproduce this with 2006-09-18 build with JDK 1.5.0_08 on WinXP The following appears in appserver log when I try to deploy the composite application as described in the steps to reproduce. I used the projects purely from the attached file without any modification to the source. --------------------------------------------------------- Service unit failed to load deployment Error while loading C:\as90.jee\domains\domain1\jbi\system\deployment\CompositeApp4\com.sun.bpelse-1.0-2_CompositeApp4-LoanRequestor\LoanRequestor2.bpel Exception Details:Parsing error encountered in file :C:\as90.jee\domains\domain1\jbi\system\deployment\CompositeApp4\com.sun.bpelse-1.0-2_CompositeApp4-LoanRequestor\META-INF\catalog.xml, message :Premature end of file. com.sun.jbi.engine.bpel.impl.BPELSEException: Error while loading C:\as90.jee\domains\domain1\jbi\system\deployment\CompositeApp4\com.sun.bpelse-1.0-2_CompositeApp4-LoanRequestor\LoanRequestor2.bpel Exception Details:Parsing error encountered in file :C:\as90.jee\domains\domain1\jbi\system\deployment\CompositeApp4\com.sun.bpelse-1.0-2_CompositeApp4-LoanRequestor\META-INF\catalog.xml, message :Premature end of file. at com.sun.jbi.engine.bpel.EngineHelper.loadDefinitions(EngineHelper.java:152) at com.sun.jbi.engine.bpel.EngineHelper.deploy(EngineHelper.java:214) at com.sun.jbi.engine.bpel.BPELSEDeployer.init(BPELSEDeployer.java:141) at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:149) at com.sun.jbi.framework.Operation.run(Operation.java:86) at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXException: Parsing error encountered in file :C:\as90.jee\domains\domain1\jbi\system\deployment\CompositeApp4\com.sun.bpelse-1.0-2_CompositeApp4-LoanRequestor\META-INF\catalog.xml, message :Premature end of file. at com.sun.wsdl.model.uri.impl.CatalogResolverImpl$CatalogParserHandler.fatalError(CatalogResolverImpl.java:117) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.wsdl.model.uri.impl.CatalogResolverImpl.<init>(CatalogResolverImpl.java:69) at com.sun.bpel.model.BPELParseContext.setCatalog(BPELParseContext.java:68) at com.sun.bpel.model.BPELParseContext.setCatalog(BPELParseContext.java:83) at com.sun.jbi.engine.bpel.EngineHelper.loadDefinitions(EngineHelper.java:129) ... 5 more JBIFW2460: Unexpected exception java.lang.NullPointerException occurred on init for Service Unit init. The exception has no message text. JBIFW2500: ServiceUnitManager stack trace follows: java.lang.NullPointerException at com.sun.jbi.engine.bpel.BPELSEDeployer.unRegisterBPsWithEngine(BPELSEDeployer.java:365) at com.sun.jbi.engine.bpel.BPELSEDeployer.init(BPELSEDeployer.java:153) at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:149) at com.sun.jbi.framework.Operation.run(Operation.java:86) at java.lang.Thread.run(Unknown Source) Cannot activate endpoint {http://loanprocessor.sun.com/}LoanProcessorService,LoanProcessorPort,outbound Reason: Endpoint has already been activated. Cannot register MBean for the Protocol grizzlyHttpProtocol.selectorRegisterProtocol
Mike, Please leave my name from the Assigned field. thanks, sherry
The problem was caused by the bug in the "populate catalog" action. In some cases, it created an empty file which is not as a valid xml file. We will fix this problem asap... To work around this bug, one can delete the retrieved directory in LoandRequstor project and don't invoke populate catalog action before deploying the project.
Problem due to populate catalog generating empty catalog.xml file is fixed.Please get the latest enterprise build and test.
Verified in the latest build 060925 and found that no exception getting during deployment