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.
Product Version: NetBeans IDE Dev (Build 200706120000) Java: 1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\jlin\.netbeans\dev When running the test cases of the TRS sample, only hasHotel passed, all the other test cases failed. The following is the output for hasAirline: <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode xmlns="">SOAP-ENV:Server</faultcode> <faultstring xmlns="">Processing Error. Fault Name is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault and Fault Value is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault</faultstring> <faultactor xmlns=""/> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The following is in server.log: Pattern for exchange Id 14362582533400-47328-134009930701450049 is http://www.w3.org/2004/08/wsdl/in-out Sending a one way outbound message to the NMR. MessageExchangeId is 14362582533400-47328-134009930701610050, service name is {tres}Vehicle, endpoint name is VehicleReservationServiceRole_partnerRole. Exception in calling out only. com.sun.xml.ws.client.ClientTransportException: HTTP Status-Code 404: Not Found - Not Found at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:205) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:137) at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:104) at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:79) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) at com.sun.xml.ws.client.Stub.process(Stub.java:234) at com.sun.xml.ws.client.dispatch.DispatchImpl.invokeOneWay(DispatchImpl.java:201) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:607) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:505) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:194) at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:61) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Pattern for exchange Id 14362582533400-47328-134009930701610050 is http://www.w3.org/2004/08/wsdl/in-only System exception occured while executing a business process instance. com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: com.sun.xml.ws.client.ClientTransportException: HTTP Status-Code 404: Not Found - Not Found at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:403) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:300) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:125) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:144) at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:76) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:759) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:261) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:742) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:490) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:274) at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:158) Caused by: com.sun.xml.ws.client.ClientTransportException: HTTP Status-Code 404: Not Found - Not Found at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:205) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:137) at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:104) at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:79) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) at com.sun.xml.ws.client.Stub.process(Stub.java:234) at com.sun.xml.ws.client.dispatch.DispatchImpl.invokeOneWay(DispatchImpl.java:201) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:607) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:505) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:194) at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:61) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) com.sun.bpel.model.meta.impl.RInvokeImpl@8eb1a8={<?xml version="1.0" encoding="utf-8" ?> <invoke name="ReserveVehicle" partnerLink="Vehicle" portType="vres:VehicleReservationPortType" operation="reserveVehicle" inputVariable="ReserveVehicleIn"> <correlations> <correlation set="ItineraryCorrelator"/> </correlations> </invoke>} [Fatal Error] :1:1: Content is not allowed in prolog. Fault Processing Error. Fault Name is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault and Fault Value is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault is not handled in the current scope. Sending faults for the pending requests in the current scope before propagating the fault to the enclosing scope. Setting MessageEx id 14362582533400-47328-134009930701450049 with error: Processing Error. Fault Name is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault and Fault Value is {http://sun.com/wsbpel/2.0/process/executable/fault}systemFault
This is against GlassFish b50. The log message for a successful hasHotel run is: Pattern for exchange Id 162721095449539-12861-134009934586500118 is http://www.w3.org/2004/08/wsdl/in-out Sending Reply for MessageEx id 162721095449539-12861-134009934586500118 Pattern for exchange Id 162721095449539-12861-134009934586500118 is http://www.w3.org/2004/08/wsdl/in-out
Vladimir, please work on it with Nikita. probably the reason is the standard BPEL faults were uncommented.
I tried to deploy and test SOA samples, Async, Sync and TRS: everything works fine. Build 765, GlassFish v2 Build 50.
verified in Build 200707151200