Two FTPAdapters triggers one BPEL-Process in Cluster

I have defined two ftp-adapters getting two different csv-files (different file structures) of the ftp-server. These ftp-adapters triggering a bpel-process starting with a pick-activity containing two onmessage-branches. In the first onmessage-branch there is a transformation transforming format A into a common format. In the second onmessage-branch there is a transformation transforming format B into a common format. With this common format some other actions are processed (not relevant for this problem).
Because i have a clustered environment (cluster of two soa-suite installations 10.1.3.1) i want only one clusternode triggering my bpel-process. so i set the property clusterGroupId of the activationAgent inside of the bpel.xml. Because i have two triggering ftp-adapters i defined two different clusterGroupIds to prevent to have a influence between this two ftp-adapters.
The problem is that the application-server now is logging every second the following warning and i don't know if this is a problem or not. both ftp-adapter works fine but i think it will not work in cluster.
WARNING: discarded message from different group "unbarring_group" (our group is "barring_group"). Sender was10.32.7.156:16325
Jun 26, 2007 2:05:39 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "unbarring_group" (our group is "barring_group"). Sender was10.32.7.156:16325
Jun 26, 2007 2:05:40 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "barring_group" (our group is "unbarring_group"). Sender was10.32.7.156:16321
Jun 26, 2007 2:05:41 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "barring_group" (our group is "unbarring_group"). Sender was10.32.7.156:16321
Jun 26, 2007 2:05:43 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "barring_group" (our group is "unbarring_group"). Sender was10.32.7.156:16321
Jun 26, 2007 2:05:43 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "barring_group" (our group is "unbarring_group"). Sender was10.32.7.156:16321
Jun 26, 2007 2:05:48 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "unbarring_group" (our group is "barring_group"). Sender was10.32.7.156:16325
Jun 26, 2007 2:05:49 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
I have also tried to use only one clusterGroupId but if i do so only one ftp-adapter is initiating my bpel-process. so why does this usecase does not work with using one clusterGroupId???
bpel.xml
<BPELSuitcase>
<BPELProcess id="Service_Barring_TAS" src="Service_Barring_TAS.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="ReadBarringFiles">
<property name="wsdlLocation">ReadBarringFiles.wsdl</property>
</partnerLinkBinding>
<partnerLinkBinding name="ReadUnbarringFiles">
<property name="wsdlLocation">ReadUnbarringFiles.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="ReadBarringFiles">
<property name="clusterGroupId">barring_group</property>
<property name="FileInputDirBarring" type="LogicalDirectory">/Mahnung/bar</property>
<property name="portType">Get_ptt</property>
</activationAgent>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="ReadUnbarringFiles">
<property name="clusterGroupId">unbarring_group</property>
<property name="FileInputDirUnbarring" type="LogicalDirectory">/Mahnung/unbar</property>
<property name="portType">Get_ptt</property>
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
Message was edited by:
harald.reinmueller

Hi,
I am also seeing the same warn messages. And on our production we got OutOfMemory exception. Is there any setup we need to change to get rid of this error message? did you get the solution?
11/09/08 10:12:25 Exception in thread "MERGE2.FindSubgroups thread" java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 11
11/09/08 10:12:25 at java.lang.Thread.startImpl(Native Method)
11/09/08 10:12:25 at java.lang.Thread.start(Thread.java:979)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.protocols.PingWaiter.start(PingWaiter.java:51)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.protocols.Discovery.down(Discovery.java:303)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.stack.Protocol.passDown(Protocol.java:551)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.protocols.MERGE2$FindSubgroups.findInitialMembers(MERGE2.java:305)
11/09/08 10:12:25 at org.collaxa.thirdparty.jgroups.protocols.MERGE2$FindSubgroups.run(MERGE2.java:263)
11/09/08 10:12:25 at java.lang.Thread.run(Thread.java:810)
11/09/08 10:13:35 java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 11
11/09/08 10:13:35 at java.lang.Thread.startImpl(Native Method)
11/09/08 10:13:35 at java.lang.Thread.start(Thread.java:979)
11/09/08 10:13:35 at com.evermind.util.ReleasableResourcePooledExecutor.addThread(ReleasableResourcePooledExecutor.java:236)
11/09/08 10:13:35 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:997)
11/09/08 10:13:35 at com.evermind.util.ThreadPool.launch(ThreadPool.java:283)
11/09/08 10:13:35 at com.evermind.server.rmi.RMIServerConnection.startConnection(RMIServerConnection.java:141)
11/09/08 10:13:35 at com.evermind.server.rmi.RMIServer.createRMIServerConnection(RMIServer.java:812)
11/09/08 10:13:35 at com.evermind.server.rmi.RMIServer.connect(RMIServer.java:805)
11/09/08 10:13:35 at com.evermind.serv

Similar Messages

Trying to throw fault from one BPEL process to another

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?

How to use multiple WSDL operations in One BPEL process Recieve Activity ?

Is there anyway to attach multiple WSDL operations with a Single BPEL process ? How ?

Thanks Melvin for your quick respond.
When I create a BPEL process, It asks me to give the XSD as an Input. When I import the XSD it asks me to select an operation not more than one. Let suppose I select addRequest and finish the wizard.
Now what I can see, It create Recieve activity with an Input msg of Add operation. Well what I understand from your statement is that, I remove the recieve activity and put the Pick activity.
Now my question is How to mention the other operations like update and delete ? And how to test them ?? The link provided by you is just tell me what Pick activity can do for me, But its not telling me how to use it ?? and how the give the operation to it. Where should I need to change in the BPEL ???

Implementing several web-methods in one BPEL process

Hi
We are trying to implement an integration system with help of BPEL PM, which must provide its interface for another system as a single web-service with different web-methods (operations).
By now we were able to provide only one operation per web-service, as default BPEL behavior.
How is it possible to make a single web service "entry point" to our different BPEL processes as a web-service with different methods?
WBR, Serg.

You must start the (async) process with a pick-activity (not the default receive), and check it to Create Instance.
I just made some test-processes (soon to be more like production), so my finding are not quite mature, but here they are:
You now need to add your flavour of operations (which I assume have to be async, I've not tested sync). The operations are simply added to the process wsdl-file, typically within the existing portType.
To start with I would suggest that you use the same portType and the same message name for all operations.
You soon discover the need for separate responses as well, again its designing it and code the wsdl-file.
When you get going you can try to differentiate the message, it's all about coding the wsdl-file.
Adding portTypes looks a bit more complex, but it seems to work (but does it do you any good?).
If you add portTypes, remember to add a plnk:partnerLinkType as well.
So: Multi-operation BPEL WS here we come!
CadB

Multiple BPEL Process Managers in one environment?

Hi,
I'm quite new to the Oracle SOA product line, so please be gentle when my question doesn't make sense.
I’m in the process of designing a new enterprise architecture based on service orientation. I’m looking at the Oracle SOA Suite software to get a better understanding of what things will look like when getting to the actual implementation.
Some internal projects are moving fast, so I’m trying to get an understanding on how things will work out in the future. One case has my current attention, related to the BPEL Process Manager.
A 3rd party vender is offering a specific solution which is using or based on the BPEL Process Manager. This solution can be purchased as a black-box. From the perspective of my new architecture I would like to purchase the SOA suite as a whole. New developments will most likely be using the BPEL Process Manager for orchestration. But when purchasing the black-box application, the environment will be extended with an extra BPEL Process Manager. My first thought is to try and incorporate the BPEL processes from the 3rd party vendor onto one single BPEL Process Manager. But I also think two BPEL Process Managers can have advantages.
I’m not sure how to go forward with this. How should I handle this? Is it common to have multiple BPEL Process Managers in one environment or should I pursue maximum integration and only go for one BPEL Process Manager?

Hi,
We have similar situation at my current client site and we are going with two seperate BPEL PM installs for various reasons. One of the main driver in our case is conflicting in timelines of two seperate projects.
But my suggestion is to go with single enterprise install if that's not breaking the 3rd-party vendor supporting contracts. This has obviously benefits of redecued infrastructure/administrative and other related costs. How many processes does the vendor has as part of their solution? If they are handful you know it doesn't justify having seperate environments.
On the otherhand having two seperate installs isn't bad either depending on how big or small your SOA service/process orchestration footprint is. We don't have complete handle on the performance/scalability aspects of BPEL PM based on number of processes deployed. But as you can see that may be one of drivers to have redundancy in BPEL PM servers.
End of the day there is no clear cut answer. If you have funding and resources, go with two seperate instances. But from architectural perspective better to have single install with clustering for better performance/scalability.
HTH
Regards,
Rajesh

PHP always invokes Two BPEL process Instances

Hello All:
I have a BPEL process that I want to invoke from a PHP form. The problem that I'm having is that every time that I invoke the BPEL process from PHP, two instances of that BPEL process get created and invoked in the BPEL manager.
Has anyone experienced this problem? I know that when I log into the BPEL console and initiate a test instance, I only get one, so my feeling is that it may be PHP. Here is a list of my environments:
BPEL Server Environment
OS Version - Microsoft Windows XP
Oracle SOA Suite v10.1.3.1.0
Oracle BPEL Console v10.1.3.1.0
Client Environment
Server Software - Apache/2.0.55 (Win32)
OS Version - Microsoft Windows XP
PHP Version - 5.1.4
Zend Engine Version - 2.1.0
Here is my PHP code for invoking the BPEL process:
<?php
$wsdl = 'http://localhost:8888/orabpel/default/ChangeCustomerName/1.0/ChangeCustomerName?wsdl';
try {
     $client = new SoapClient($wsdl);
     $return = $client->process(array("cust_account_id"=>167484,"new_cust_name"=>"TESTING>"));
     if ($return->return_code == 'E') {
     echo 'Error: '.$return->return_message;
     } else {
     echo 'Success!';
} catch (SOAPFault $e) {
var_dump($e);
?>
Again the problem is not that I can't invoke a BPEL process or that the BPEL process does not function properly, it is that when I do invoke it from PHP, I get two instances in BPEL.
Thanks,
Ben

If you are using a tool like: soapui.org (Opensource SOAP client tool), and create a soap request, do you get the same behavior. If so, there is an issue in BPEL, otherwise in your PHP environment.

1 bpel process invoking two osb proxies of same wsdl

Hello,
We have:
SCA composite with BPEL process (BPEL1)
1 WSDL with multiple operations (op1, op2) in OSB
OSB proxy services (PS1->based on wsdl op1, PS2 -> based on wsdl op2). Both of them are based on same WSDL.
Now I am trying to invoke PS1 and PS2 from BPEL1 by creating two partner links each referring to two different operations
(op1 and op2) of WSDL. But I am getting error when trying to invoke PS2 because even if I invoke PS2, it is calling
operation 1(op1).
So my question is, can we invoke multiple operations of same wsdl in one BPEL process instance?

maybe the selection algorithm on the proxy service isn't the correct one, so it can't dispatch to the correct operation
can you check the value setting of Operation Selection Configuration > Selection Algorithm on you proxy service on the osb
we mostly use SOAP Body Type

Integrate Multiple BPEL Process into one project

Hi,
Can anyone help for the following problem?
We created different BPEL process.One bpel process calls the another bpel process internally .
EX:
process1,process2 and process3.
In side process1, I will call process2 and process3.
I want to integrate all 3 process into one.
Can anyone help how can i do this.
Thanks in advance.
Thanks,
Bharath

Can't you create a new process, copy everything between the main-scopes of the other processes to the new process (skip some of the receives and callbacks so you have 1 receive and 1 callback left), copy all the variables, namespaces, xsl mappings, and try again.
it's more a bit of 'trial and error' and see what's left.
Hope you can use this a bit.

How to install Oracle BPEL Process Manager for OracleAS Middle Tier

hi,
i need to install BPEL process manager, so i download the following file from otn
1.soa_windows_x86_101310_disk1
2.soa_windows_x86_bpel_101310
here i read the document named b28980.pdf from bpel\doc\pc.1012 to install BPEL PM
so i start to complete the pre-installation task
1.installed Oracle database 10g
2.Run the Integration Repository Creation Assistant on the Database
3.Install Oracle Application Server 10g Release3 (10.1.3.1.0) and select either the J2EE Server installation type or the J2EE and Web Server installation type. selected J2EE and Web Server installation type
and installed according to the Oracle application server installation guide.
installed OracleAS in the path : D:\product\10.1.3.1\OracleAS_1
4.Install the current release of Oracle BPEL Process Manager for OracleAS Middle Tier
here they mention to select the J2EE and Web Server installation type because that type is selected in Oracle AS installed in Oracle Application Server
so i start to install the BPEL PM by selecting the setup.exe-->and shows the location source and destination
default destination is : D:\product\10.1.3.1\OraBPEL_1 selected next on the screen
the next screen is select installation type here there are two types named
1.BPEL process Manager for Developer (371MB)
2.BPEL process manager for Oracle AS Middle tier (107MB)
i selected 2.BPEL process manager for Oracle AS Middle tier (107MB) and click next
pop up window opens with title dependencies
error:
BPEL Process manager for oracle AS Middle tier will run on top of a supported Oracle Application Server 10.1.3.1.0 J2EE server and Web Server Or J2EE server instance. this location does not contain this instance. Please select new Oracle home that contains a supported instance.
so i changed the destination path to : D:\product\10.1.3.1\OracleAS_1\BIN then also i got the same error.
please any one mention the path for J2EE and Web Server instance for installing the BPEL PM for Oracle AS Middle Tier.
Thanks in Advance
Aswath Thaniga

If you choose the developer version you will be fine.
If you have installed J2EE and Web Server installation into D:\product\10.1.3.1\OracleAS_1 then this is the location you install your BPEL PM into, not D:\product\10.1.3.1\OraBPEL_1 or D:\product\10.1.3.1\OracleAS_1\BIN.
D:\product\10.1.3.1\OracleAS_1 is what we call the ORACLE_HOME, generally we create a new home for each install, but in this case there is a dependency on 10.1.3.1 OC4J container. So it needs to be installed into 10.1.3.1 oracle home.
The bin directory is just the executables for that home, its not the actual. home.
cheers
James

How to know BPEL process is running

Hi,
I have BPEL process which is triggerred by FileAdapter. File Adapter polls for every 120seconds and if any file exists, it reads and BPEL process is initiated.
As BPEL proccess is big and sometimes it executes more than 120seconds and it depends on environment with less load process faster and more load its takes more time.
Due to this is there a way to know BPEL process is running before fetching new file or before starting actual BPEL process.
JDev: 11.1.1.6.0
Thanks,
Bhaskar

Can a singleton bpel will resolve your problem ?
At a time only one bpel process will be running there wont be any parallel instances for that bpel. In that way there wont be any second instance created until the first instance has done with its job.
http://orasoa.blogspot.co.uk/2007/05/create-singleton-process.html
http://blogs.bpel-people.com/2009/04/writing-singleton-bpel-process.html
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.
Thanks,
Vijay

Error while checking the flow of bpel process in bpel console

Hi Experts
I have created one bpel process which invokes task manager for approving or rejecting the leave request. I ve successfully deployed the bpel process and also able to test approve or reject the leave request . But i am facing one error
when i am initiate a bpel process and started to check the flow of that bpel process in bpelconsole it gives me some error message in small pop up like
error : Internal/ bug ( #589 )
\u017E is not defined
i click Ok and after this no error and all working well.
Thanks.

A quick answer is:
1. make sure you defined the Application/Integration Server in your developer (user/pass you have - if not oc4jadmin then one the IT gave you).
2. Deploy your project to that server.
3. Choose the correct domain in the Console when deploying.
Is this what you wanted to know???

BPEL process state "Off"

Hi,
I had created one BPEL process which reads from FTP Remote server and writes to local file directory.
After reading from Remote FTP server I am deleting file from the server. In the remote server I had created on user to interact with FTP server with all permissions. When the BPEL process executed FTP Adapter is deleting the File successfully from remote location but BPEL state is changed to “Off”.
When I checked the logs, I found there is problem with Delete permission. Actually as mentioned above file is deleted successfully in the remote location.
OPMN logs:
<File Adapter::Outbound> Processing file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<File Adapter::Outbound> Sending message to Adapter Framework for posting to BPEL engine: {
file=/click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<2007-06-11 19:00:42,677> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sucessfully sent message : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt to Adapter Framework.
<2007-06-11 19:00:42,724> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt after processing.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host name is 'DT1521-localhost.com'.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Reading reply from DT1521-localhost.com
<2007-06-11 19:00:42,818> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: Write, partnerLink: <partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>null</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=Write, parnterLink=<partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::doShortCut> Parner Property optShortCut
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> ResourceAdapterMetaData Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Looking up Resource Adapter JDNI location 'eis/FileAdapter'
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Managed Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating Connection
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating FileInteraction
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> FileInteraction Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec with properties: {FileNamingConvention=spob230_%SEQ%.txt, OpaqueSchema=true, ElapsedTime=60, NumberMessages=1, PhysicalDirectory=c:\inbound_dir, FileSize=1024000}
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Invoking JCA outbound Interaction
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> File Adapter received an input Record
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Waiting outside sync object.....
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher created using staging : true with number of messages : 1
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Input Record: javax.xml.transform.dom.DOMSource@e5394c
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Translating....
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Outbound Translation done.
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Refreshed (staging/num Messages) file count : 1
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: USER orabpel
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Wrote to Control File
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batching staging File: staging0
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher sending to sender for output file writing
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sending File to output Dir
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FileAgent.putFile() puts spob230_17.txt in c:\inbound_dir begins ...
<2007-06-11 19:00:42,865> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done Writing to output file spob230_17.txt in dir c:\inbound_dir !!
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting staging File: staging0
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Interaction gets a ok response
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done with Input Record
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: USER, reply:
331 Password required for orabpel
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: PASS
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: PASS, reply:
230 Login OK
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: CWD /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: CWD, reply:
250 Directory successfully changed
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: DELE po_28.txt
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: DELE, reply:
200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): 200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <ERROR> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): Unable to delete file po_28.txt', reply code = 200
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Processer thread calling onFatalError with exception Error deleting file from FTP Server.
Unable to delete file from server.
Please ensure whether the remote file has delete permission.
<2007-06-11 19:00:43,709> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Get_ptt::Get(opaque)] - Resource Adapter requested Process shutdown!
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Get_ptt, operation=Get
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Endpoint De-activation called in adapter for endpoint : /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,725> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:44,037> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::onStateChanged State is changed for process 'bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/', state=OFF
<2007-06-11 19:00:44,037> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::updateRevision> Updated state for process FTPRetrieveTOFileWriteProcess (revision 1.0) to 1
Thanks,
Vidya

Hi SR,
You can do this by having a BPEL process with a java embedding containing below code.
* Input Variables
String processName   = (String)getVariableData("processName");
String revision      = (String)getVariableData("revision");
* Declare variables.
IBPELProcessHandle procHandle = null;
Locator loc = null;
BPELProcessMetaData bpelProcessMetadata = null;
try{
     * get Locator Instance
    loc = getLocator();
     * Lookup Process. Revision optional.
    if(revision == null || revision.trim().equals(""))
      procHandle = loc.lookupProcess( processName );
    else
      procHandle = loc.lookupProcess(processName, revision);
    if(procHandle == null)
      throw new Exception("Unable to find process: " + processName);
     * Get Metadata of the process.
    bpelProcessMetadata = procHandle.getMetaData();
     * Set Lifecycle to Retired.
     * Use setState(IBPELProcessConstants.STATE_OFF) to change process state to off.
    bpelProcessMetadata.setLifecycle(IBPELProcessConstants.LIFECYCLE_RETIRED);
     * Finally update the process with the modified metadata.
    procHandle.updateMetaData(bpelProcessMetadata);
}catch (Exception e)
addAuditTrailEntry(e);
}If you want you can schedule this process.
Regards
PavanKumar.M

Invoking BPEL process from ADF...

All,
I have deployed one BPEL process and invoking the same process from ADF test page. I created one Webservice Data Control for this process and did drag and drop to ADF page. It is working fine as expected.
When I created data control, I gave the web service URL as "http://<hostname>:<port>/orabpel/default/<processname>/.......<processname>.wsdl
My question is, if I want to deploy this BPEL process as well as this ADF page into another server, what will happen to this ADF data control ? since the hostname and port will not be similar for the new server. Do I need to change any params ?
Or when we create data control itself, are there any options to achieve this ?
Please let me know the details.
TIA,
-- prabaa !

Hi,
Check if your wsdl endpoint can accessed properly. If yes, check the soap-binding address is properly pointing to the server hosting the webservice.
Regards,
Harikiran.

Error shown in console while running BPEL process

We have built one BPEL process that creates AR invoices in Oracle Apps from a legacy system. While deploying the process it deploys without Error, but when viewing the process through BPEL Console by clicking the instance it throws Below ERROR -- "java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
java.lang.Exception: No Exception - originate from:"
We have increased <transaction-config timeout="90000"/> residing in Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\server.xml file. but still the Error remains same....
Any help will be appreciated.
Regards,
Suman

Have you created a connection pool with the JNDI specified while configuring adapter in Oracle Apps adapter on weblogic admin console. You should create it at Deployments --> OracleAppsAdapter --> Configuration--> Outbound Connection pools
Make sure to update the adapter after creating a connection pool so that changes can take effect.
Regards,
Anuj

Unable to call a BPEL Process from ESB

Has anyone worked on Oracle ESB ?
I've implemented an ESB Scenario where, based on some value, either it should call one BPEL process otherwise it should call another BPEL Process. But, Routing Service is unable to call either of the service.
Can anyone help me out?
Thanks in Advance.
Regards

I am able to call the bpel processes from the bpel console. I tried to use the TCP Packet Monitor but it shows waiting for connection and doesn't turn up. I checked the port number. The local server port is correct but I dont know how to check the listener port for it i.e. by default showing 1234.
I tried to test my esb through em as a webservice but it shows the following exception after input:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</faultcode><faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
     javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
     at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:83)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
     at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
I've setup the trackable fields also but trackable data showed me no data. When I checked the validate check box, it has shown me error in first stage i.e. in file adapter itself.
I don't know what's the problem?
Please help as I am struggling with this.
Thanks & Regards

Two FTPAdapters triggers one BPEL-Process in Cluster

Similar Messages

Maybe you are looking for