BPEL Processes interacting on different servers.

Hi All,
I have a very silly problem.
Iam using SOA v10.1.3.3.
I have 2 BPEL processes Process1 on Server1 and Process2 on Server2.
My Process1 calls Process2.
But when I execute the Process1 in the BPEL console, it keeps on waiting at Recieve step for reply from Process2 which is on another server.
These two servers are on the same LAN.
I have not made any other configurations anywhere.
Please help me if I need to configure anything for this to work.
Thanks,
Deepti

have you tried
ping server 2 (on server 1)
ping server 1 (on server 2)
Are you sure, that process 1 really invokes process 2? Can you see the instance on server 2?
Have you tried to add a java:exec -> checkpoint() in process 2?

Similar Messages

BPEL and ESB in different Servers

Hi ,
What is the advantage of having BPEL PM and ESB installed in different servers ?

In my knowledge it has it own merits and demerits
IF (BPEL and ESB) installed in dfferent OC4Js (JVMs)
Merits
1) Individual JVM for each component means more memory allocation and support from JVM
2) More number of processes can be deployed.
DeMerits
1) ESB and BPEL communication can happen via SOAP over HTTP only whereas had these been deployed in the same JVM (oc4j) it can do native communication.
Edited by: cdmnagaraj on Apr 22, 2009 5:17 AM

Single BPEL process to server different system?

Hi All,
I have one source system and have three target system.
Source System - S1 (Oracle System)
Target System - T1, T2, T3 (oracle System)
I need to pass supplier data from S1 to T1, T2, T3.
I need to create only one single BPEL process to acheive this.
Current design is to transfer data from S1 to T1, T2, T3 using database adapter (Having three db adpater and passing same payload to three).
I am not happy with the design to have three adpater (say if we have 10 different system then we may need 10 adapter). Can anybody please suggest any other way around using BPEL or ESB.
Thanks and Regards,
Sreejit

Example Assignment
<assign name="Init_InsertStagingData">
<copy>
<from expression="/eis/DB/TEST_UK"/>
<to variable="endpointReference"
query="/ns3:EndpointReference/ns3:Address"/>
</copy>
<copy>
<from variable="endpointReference"/>
<to partnerLink="InsertStagingData"/>
</copy>
</assign>
Endpoint Reference Schema
<element name="EndpointReference">
<complexType>
<sequence>
<element name="Address" type="string" minOccurs="0" nillable="true" />
</sequence>
</complexType>
</element>
--Prasanna

Pointing deployed BPEL process to call different version of another BPEL

Hi All,
I have deployed BPEL x calls BPEL y( version 1.0)
Now I wanted to point BPEL x to BPEL y (version 2.0) and this should happen with out redeploying BPEL x
I am okay to bounce server .
Is there any solution ?
Thansk,
Praveen

Guys why are you not understanding his question. I think he wrote quite clearly.
He has 3 BPEL process deployed in version 1.0
and
have 2/3 BPEL deployed in version 2.0
now what he wants is BEPL process with version 10.0 should always call 1.0 and the one with 2.0 always call 2.0. IS that too difficult to understand???
Praven what i suggest as alternate for time till you get actual solution being is
1. In version 2.0 before you deploy hard code partner links with version 2.0
2. Deploy bpel with version 2.0
3. Go and set version 1.0 of all bpel as default
now since 1.0 are all default 1.0 will call 1.0
in 2.0 since you hardcoded partnerlinks it will call 2.0
in future don't mess thnsg up :)) and use dynamic binding.

ESB and BPEL in different servers

Hi ,
Is there any performance based advantage when we have BPEL and ESB in different servers ?

If you seperate them, it will have impacht on the perfromance. Services are called over the network, assuming BPEL and ESB are on different servers. Otherwise they can call each other via native binding if ESB and BPEL are in the server and container.
Marc
http://orasoa.blogspot.com

Clear wsdl cache every time a bpel process call is made.

Hi All,
I have a bpel process which gets input xml of the size of 6MB. This bpel process interacts with a java component using the WSIF approach to reorder the xml input recieved.
The strange problem that i am currently encountering right now is for each time the bpel process execution time scales up. For example, the first time i fired the request, the bpel process took 29 seconds to completely execute. The second time it took 39 seconds and the third time it has taken around 56 seconds to execute.
When i cleared the wsdl cache from within the bpel console, the execution again came down to around 21 seconds.
Can i know which is the property which we can set in bpel.xml file of the bpel process to clear the wsdl cache each time a request is fired.
Thanks in Advance,
Vijay S

Jay,
You don't say how these links on the menu page are constructed. If you are using an apex list then for each list entry there would be a target page section in which you would put the target page ID in the Clear Cache field. For example, if the link goes to a page in the current application, say page 10, then you'd put 10 in the Clear Cache field.
If you are building a link yourself, just put 10 (for page 10) in the clear-cache position of the f?p URL, e.g.,
f?p=&APP_ID.:10:&APP_SESSION.::NO:10:P10_ITEM:&SOME_ITEM.
Scott

How to Deploy BPEL Processes

How can we deploy pre-built BPEL processes/solutions across different machines. For e.g., I have received a pre-built BPEL process/solution from one of my colleagues. What are the steps I need to take to deploy it to my local machine. I tried using the BPEL Console (Clicking on Deploy New Process) and proving the "bpel_*.jar" from the output folder of the prebuilt solution but I get errors since the code was compiled and deployed on a different machine. I can fix the bpel.xml and the directory structure and deploy successfully. However, this would be a limitation since I'll have to perform the fix every time I need to deploy the code across environments. Can someone help me with this? Thanks!

What error do you see if you simply copy the jar file in the deploy directory of your server? [My guess is that the error are due to links to other WSDL and schema files or locations that might be hard coded in the BPEL.XML in which case you want to either try to make as many links as possible relative or have a shared tomcat server where you host WSDLs and XSDs shared between multiple environment (a mini repository)]
Note: the deploy function in the BPEL console simply copies the jar that is uploaded in the deploy directory. . -Edwin

Deploying SOA components on different servers/domains

Is it possible to disassemble components developed on the SOA/ADF suite of JDeveloper and deploy them in different domains? i.e deploy adf web application in one domain, deploy bpm in a different domain and bpel processes in a different domain? Will this arrangement work?
In other words..i have a adf web application with some task flows. one of the task flow embeds the task list task flow of the bpm component.This works well when both web and the bpm applications are deployed to the same domain/server. Will this work if i put either of them in a different server/domain?
Please provide your thoughts?

Hi
Yes. You can Deploy any SOA/BPM Application in 2 Different Domains provided you have the Deployers for all the projects created properly. Ideally, any SOA/BPM Workflow application should have just 2 things to deploy: Workflow SCA JAR File (.JAR) and one EAR (that has all the stuff except for Workflow JAR File). The below link gives the ideal way of deployment.
Re: deploying a large Oracle BPM Application with multiple UI projects
As per above link, you can always deploy workflow sca jar file in ONE domain. And the TaskForms and all the supported Projects in totally different Domain at different host and port. This should work.
The most important file that links actual TASK from Workflow Project to the corresponding TaskDetails JSPX Page in TaskForms Project is this file:
/yourSOABPMApp/yourTaskFlowUIProject/adfmsrc/hwtaskflow.xml
Also, once deployed, look at the contents of the Table named in WFTASKDISPLAY in your XXX_SOAINFRA schema associated with your soa/bpm Domain. This table stores the above relationship and also stores the actual host and port of the domain hosting the Taskforms.
http://docs.oracle.com/cd/E17904_01/integration.1111/e10224/bp_designtf.htm#CACDDJDA
Thanks
Ravi Jegga

Urgent: Same BPEL code, different servers, different results in deployment

Hi everybody,
I need some urgent assistance as I am nearing a Go-live deadline.
I have some BPEL code (10.1.3.3) which I attempt to deploy from JDeveloper (10.1.3.4).
When I deploy to development environment it deploys fine.
When I try to deploy to test environment I get the following error:
[Error ORABPEL-10902]: compilation failed
[Description]: in "bpel.xml", XML parsing failed because "undefined part element.
In WSDL at "file:/oradata/OracleAS_1/bpel/domains/outboundnoterepository/tmp/.bpel_RealWSDL_1.0_75ea24906b156b639e4531aa3ef007fb.tmp/nrwsdl/nr/RCMR_AR000002NR01.wsdl", message part element "{urn:hl7-org:v3}MCCI_IN002200NR01" is not defined in any of the schemas.
Please make sure the spelling of the element QName is correct and the WSDL import is complete.
This makes no sense to me. If there was a problem with the "{urn:hl7-org:v3}MCCI_IN002200NR01" element it should be the same whether I deploy to development or test environment.
The only thing I have changed is the endpoint of an invokation from the process - and I even tried not changing that to no avail.
Does anyone have any idea what is going on here?
Your help is much appreciated!
Kind regards,
Mathias

Hello f1fan,
just to be sure, are you getting the same message stating
{noformat}
In WSDL at "file:/oradata/OracleAS_1/bpel/domains/outboundnoterepository/tmp/.bpel_RealWSDL_1.0_75ea24906b156b639e4531aa3ef007fb.tmp/nrwsdl/nr/RCMR_AR000002NR01.wsdl", message part element "{urn:hl7-org:v3}MCCI_IN002200NR01" is not defined in any of the schemas.
{noformat}
when deploying your process? Or is it just a different behavior when deploying to different servers?
The first issue might arise from an import statement in the wsdl file having a location that could not be resolved on the BPEL server. Do you use imports and if so, are you using a URL or a local relative path?
Cheers,
Marco

Running BPEL process on different engine

Hi,
I need to proof the platform independence of BPEL, therefore i need to run my oracle jdeveloper bpel process on different engine like ActiveBPEL or Sun OpenESB engine as part of NetBeans Enterprise Pack. Any idea how to migrate my project to any other engine?
Thx, Marian Petrik

ok,
Oracle conforms to the BPEL standards, but the deployment, the so called BPEL Suitecases (jar files). Furthermore the bpel.xml file is vendor specific, so using other BPEL engines, you have to conform to their syntax.
To solve this issue, you could doing this by using JDeveloper and deploy and test as normal (against Oracle BPEL PM). Than use the ant-tool to create/collect the .bpel file can create the appropriate files for other engines.

Problem calling different versions of BPEL process from an ESB

We are currenlty having a problem calling a BPEL process from an ESB service.
We initially developed the solution and the two communicated correctly, however it was necessary to make some changes to the BPEL process and we subsequently redeployed the BPEL process incrementing the version number.
However the ESB service when initiated was still calling the initial version of the ESB service.
Is there any way of making the ESB call the default BPEL process version as configured from the BPEL console.

You can accomplish this task by invoking SOAP Service in ESB that points to current WSDL of BPEL process, for example:
http://localhost:8888/orabpel/default/SOAOrderBooking/SOAOrderBooking?wsdl
instead of
http://localhost:8888/orabpel/default/SOAOrderBooking/1.0/SOAOrderBooking?wsdl
This information is accessible in Metalink Note: 430206.1

How many different way can we call a BPEL process

Hi Guys,
How many ways can we call a BPEL process
I know 3 ways
1 ) Thru PLSQL 2) using Java API 3) From another BPEL Process.
are there any other ways .... if so what are they ..... .
Thanks
Tom...

Hi Tom,
your normal BPEL process (a regular process you create with the "new BPEL process" wizard), can be configured in Oracle application server to be accessible
- via SOAP over HTTP or
- via JMS
since it is has a WSDL based service interface.
JDeveloper as well allows additionally more options for starting a BPEL process such as a file based interface, an e-mail as a starter etc.
Still, I like to see the ESB as a virtualizer of the endpoint protocol, so I suggest you model the BPEL process regularly, exposing its functionality through WSDL and use ESB services that wrap your BPEL process to deal with the actual endpoints.
Cheers,
Hajo

Bpel Process invoking different BPEL process

Hi all
We have a situation here. It goes like this.
We have a requirement to call another BPEL process from ours. The calling process is fine. But the called process threw a lot of error due to which we discarded it and created a new process. We have mapped the same to the original calling process. Now,even after undeploying the discarded process, our main process is still calling the old process that is not even there on server and is constantly completinh in an unintended manner.
If anyone has faced this issue previously, kindly throw some light on this.
Vijay

I don't understand "mapped the same to the original calling process." If you created a new callED process with the same name as the original callED process, you will want to replace the callED processl partnerlink and WSDL in the callING process, as another poster suggested.
If the new callED process has the same name and exactly the same WSDL as the old one, you could be able to get away without changing the callING process. You have to be very careful to clear the old/bad callED process from the server. This may be overkill, but I suggest doing this in the BPEL console:
- Select the old/bad process in the BPEL console, go to the Manage tab, select Undeploy.
- Go to the Administration tab, Actions subtab, hit the Clear WSDL Cache button.
- Delete all files from your JDeveloper BPEL project output folder and recompile.
- Deploy your process to the BPEL server.
Good Luck!

Can't invoke WS from BPEL process: Unable to locate activated endpoint

I have a simple Calculator Web Service deployed on Glassfish, that I can access with any kind of SOAP client (e.g. soapUI). I have then created a BPEL process that invokes this external Web Service (which happens to run on the same Glassfish server, but that's largely irrelevant I suppose). I can instantiate and invoke the BPEL process (I've tried it with a dummy assign earlier just to make sure, and it runs successfully), but the BPEL process doesn't seem to be able to locate the external Web Service. I get the following fault:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
<faultcode>ns2:Server</faultcode>
<faultstring>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</faultstring>
<detail>
<ns2:exception class="java.lang.RuntimeException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
<message>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube$AsyncProviderCallbackImpl" file="AsyncProviderInvokerTube.java" line="114" method="sendError"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="136" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
<ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
<ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
<ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
</ns2:stackTrace>
<ns2:cause class="javax.jbi.messaging.MessagingException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="492" method="addressExchange"/>
<ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="326" method="doExchange"/>
<ns2:frame class="com.sun.jbi.messaging.DeliveryChannelImpl" file="DeliveryChannelImpl.java" line="209" method="send"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="268" method="sendInOut"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="479" method="executeSOAP"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="215" method="execute"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="134" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
<ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
<ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
<ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
</ns2:stackTrace>
</ns2:cause>
</ns2:exception>
</detail>
</ns2:Fault>
</S:Body>
</S:Envelope>
For good measure, here's the WSDL (and partner link defn) for the external WS:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="CalculatorWSExternal" targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal" xmlns:ns="http://calculator.me.org/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal">
<xsd:import namespace="http://calculator.me.org/" schemaLocation="CalculatorWSService.xsd"/>
</xsd:schema>
</types>
<message name="addRequest">
<part name="add" element="ns:add"/>
</message>
<message name="addReply">
<part name="addResponse" element="ns:addResponse"/>
</message>
<portType name="CalculatorWSExternalPortType">
<operation name="add">
<input name="input1" message="tns:addRequest"/>
<output name="output1" message="tns:addReply"/>
</operation>
</portType>
<binding name="CalculatorWSExternalBinding" type="tns:CalculatorWSExternalPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="add">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CalculatorWSExternalService">
<port name="CalculatorWSExternalPort" binding="tns:CalculatorWSExternalBinding">
<soap:address location="http://localhost:8080/CalculatorApp/CalculatorWSService"/>
</port>
</service>
<plnk:partnerLinkType name="CalculatorWSExternal1">

<plnk:role name="CalculatorWSExternalPortTypeRole" portType="tns:CalculatorWSExternalPortType"/>
</plnk:partnerLinkType>
</definitions>
Any help? I've seen someone post a similar problem on the forum at http://forum.java.sun.com/thread.jspa?threadID=5273187&messageID=10157363#10157363
but I haven't seen any answers. Thanks!
Edited by: tboubez on Jun 9, 2008 10:56 AM

Check the ports of Web services and those of BPEL, as Hambo have different communication ports.
Normally Webservices point to the port 8080 and BPEL to 18181 or 9084.
Check and I accounts.
Greetings.

BPEL process times out when SOAP-ENV:Fault is received from service.

Hi - I have a BPEL process identical to one in 10.1.2.0.2. If I execute the same test, the BPEL console displays the following on the console for version 10.1.2.0.2.
<Response>Clientwhen invoking endpointAddress 'http://galileo.wlgore.com:5555/soap/default', [ISS.0088.9134] Exception occurred while processing the body of the messageAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: [ISS.0088.9134] Exception occurred while processing the body of the message faultActor: http://galileo.wlgore.com:5555/soap/default faultNode: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <className>com.wm.pkg.art.error.DetailedServiceException</className>
     <message lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) 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:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534) </message>
</Response>
With this version, however, we either receive "java.lang.IllegalStateException: "Cannot call setRollbackOnly() current thread is NOT associated with a transaction" or a timeout error.
I captured the return message from both servers and it is identical (shown below):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
     <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
               <faultcode>SOAP-ENV:Client</faultcode>
               <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
               <faultactor>http://galileo.wlgore.com:5555/soap/default </faultactor>
               <detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
                    <webM:exception>
                         <webM:className>com.wm.pkg.art.error.DetailedServiceException</webM:className>
                         <webM:message xml:lang="">="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) 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:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534)</webM:message>
                    </webM:exception>
               </detail>
          </SOAP-ENV:Fault>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks,
RM

We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

BPEL Processes interacting on different servers.

Similar Messages

Maybe you are looking for