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.
Steps to reproduce: - create a new Asynchronous sample project - compile and deploy the project - run test scenario (NewTestcase0) Result: Test gets FAILED. Testcase: NewTestcase0(org.netbeans.modules.compapp.catd.ConfiguredTest): FAILED Passed. Threads count Sucess: <0> Error: <0> Not completed: <1> Details: <Concurrent test thread 0> did not complete. Sucess rate 0/1 junit.framework.AssertionFailedError: Passed. Threads count Sucess: <0> Error: <0> Not completed: <1> Details: <Concurrent test thread 0> did not complete. Sucess rate 0/1 at org.netbeans.modules.compapp.catd.ConfiguredTest.testConcurrentSOAPRequest(ConfiguredTest.java:515) Test org.netbeans.modules.compapp.catd.ConfiguredTest FAILED
*** Issue 80779 has been marked as a duplicate of this issue. ***
Got the following error in server.log when the testcase was run: Unknown exception occured while executing a business process instance. org.apache.commons.jxpath.JXPathException: No pointer for xpath: /typeA/id at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getPointer(JXPathContextReferenceImpl.java:402) at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getPointer(JXPathContextReferenceImpl.java:392) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluatePropertyAlias(CorrelationManagerImpl.java:309) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluateVals(CorrelationManagerImpl.java:290) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.getCorrIds(CorrelationManagerImpl.java:376) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.processStartElement(CorrelationManagerImpl.java:441) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.ReceiveUnitImpl.consumeMesg(ReceiveUnitImpl.java:131) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.ReceiveUnitImpl.doAction(ReceiveUnitImpl.java:118) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:60) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:144) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:82) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:75) at com.sun.jbi.engine.bpel.core.bpms.bpelImpl.runtime.BPELInterpreter.interpret1(BPELInterpreter.java:480) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:642) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:235) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:577) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.processRequest(EngineImpl.java:155) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:435) at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:229) |#] Associate element with owner XML document first! failed to parse the file BPELRuntimeException: faultCode=OTHER_ERROR
Fixed in the installer build 060728.
verified the bug is fixed in continuous build 060728_24 + app server installed in nighly build 060728