Debugging BPEL Process Timeouts...

I get a BPEL process timeout while invoking an external (outside the firewall) process with the following error (BPEL debugging output shown at the end of this message).
My BPELPM proxy server settings seem to be getting picked up ok because monitoring on the TCP Tunnel seems to show a proper response from the service almost immediately.
If the BPEL admin console is queried for the flow/audit, it merely shows up as:
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="summary">
<summary>null</summary>
</part>
</bindingFault>
How does one start debugging this?
Thanks and Regards.
<2005-12-19 12:22:44,603> <DEBUG> <default.collaxa.cube.engine.delivery> <Delive
ryHandler::initialRequestAnyType> started instance cce7adadf6056580:737371:10840
ef6dc9:-7fa8, localConvId=LocalGUID:cce7adadf6056580:737371:10840ef6dc9:-7fa7. W
aiting ...
<2005-12-19 12:22:44,603> <DEBUG> <default.collaxa.cube.engine.delivery> <Delive
ryService::getResult> waiting for localConvId: LocalGUID:cce7adadf6056580:737371
:10840ef6dc9:-7fa7 with timeout: 45000
<2005-12-19 12:23:29,597> <DEBUG> <default.collaxa.cube.engine.delivery> <Delive
ryHandler::initialRequestAnyType> com.oracle.bpel.client.delivery.ReceiveTimeOut
Exception: Waiting for response has timed out. The conversation id is cce7adadf6
056580:737371:10840ef6dc9:-7fa8. Please check the process instance for detail.
<2005-12-19 12:23:29,597> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::l
ogError> Error while invoking bean "delivery": Waiting for response has timed ou
t. The conversation id is cce7adadf6056580:737371:10840ef6dc9:-7fa8. Please chec
k the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response ha
s timed out. The conversation id is cce7adadf6056580:737371:10840ef6dc9:-7fa8. P
lease check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:112)
at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_Sta
telessSessionBeanWrapper22.java:288)
at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryServi
ce.java:101)
at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryServi
ce.java:65)
at ngDoInitiate.jspService(_ngDoInitiate.java:253)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:5
6)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:810)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequ
estDispatcher.java:121)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageCont
ext.java:267)
at displayProcess.jspService(_displayProcess.java:700)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:5
6)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:810)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:322)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequ
estDispatcher.java:220)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:649)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:322)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpReques
tHandler.java:798)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:278)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:120)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(Relea
sableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for
response has timed out. The conversation id is cce7adadf6056580:737371:10840ef6d
c9:-7fa8. Please check the process instance for detail.
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyTyp
e(DeliveryHandler.java:524)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(Deliv
eryHandler.java:426)
at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHand
ler.java:133)
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:97)
... 29 more
<2005-12-19 12:23:39,892> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispat
cher::insert> Received no-op message

So, you debug your processes via the BPEL Console. Plain and simple. You just design in JDeveloper.
Good Luck!
BradW

Similar Messages

Debugging BPEL process in 10.1.3.1

Hi,
Does anyone know more about debugging features in BPEL 10.1.3.1? If I try to run/debug a BPEL process, it asks for 'Default Run Target' and I do not know what this is - any help?
Thanks!

So, you debug your processes via the BPEL Console. Plain and simple. You just design in JDeveloper.
Good Luck!
BradW

How to debug a bpel process

I'm a new user in the jdeveloper community :)
i want to debug a bpel process ,for example the "AmazonFlow" sample project.
but it asking for a "default run target" path, what kind of a file it expect? i guess it's a kind of a file that consume input for the bpel process? is it always expect a default run target?
thanks

user573208;
It is not possible to use the normal Debug menus in JDeveloper, you have to do what Mark says, deploy the process to a BPEL (or SOA Suite) server, and do a test run of the process. You will find plenty of documentation on how to set up the server, and initiate a process.
When the server is up and running, the process is deployed, and a test instance has been started, debugging is actually very easy. In a development environment, you will use the server's BPEL Console to debug the process, instead of sensors (much easier). The default logging options give you full access to your data at any point of the process, it's out of the box and easily understood.
Generally, the visual Flow view gives you the best overview, and you have full access to the content of variables, the request and response data of web service calls, fault details, etc. (at any point in the process) by clicking the different elements (icons) of the process flow.
The other tabs (Audit, Debug) work the same way, but in a less visual manner.
-Rune

One way BPEL Process Retrying after 60 seconds

Hi,
We have a one way BPEL Process that is getting errored after 60 seconds and retrying for 2 times. We check the JTA Timeout and it is set to 1800 sec.
Any transaction that gets completed in 60 seconds is not rolling
We also verified the EJB Timeout properties and it is set to 600 sec. Your help is highly appreciated, since we are having this issue in production.
<The execution of this instance XXX for process XXXXX is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" >
<Nov 17, 2014 7:44:43 PM PST> <Error> <oracle.soa.bpel.system> <BEA-000000> <Error while invoking bean "cube delivery": JTA transaction is not in active state.
bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id is XXX.
The reason was The execution of this instance XXXXXXXX for process XXXXXXXXx is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.
ORABPEL-02183
JTA transaction is not in active state.
bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id isXX.
The reason was The execution of this instance XXXXXXXXX for process XXXXXXXXX is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK" .
Consult the system administrator regarding this error.

Hi,
have you already checked this thread : oracle.fabric.common.FabricInvocationException while invoking external service from bpel 11g
You should check following parameters:
1. JTA Transaction timeout. (which you have already done)
2. BPEL EJB Timeout settings (which you have already done)
3. SyncMaxWaitTime setting. ( I can recoomend you this link to understand this parameter SyncMaxWaitTime in Oracle BPEL.. | Vikrant Bhardwaj's SOA Blog)
4. DB Tuning. (Specially the DISTRIBUTED_LOCK_TIMEOUT)
best regards, Nicolas

RequestTimeoutException error while invoking a BPEL process using RMI

Hi,
I am getting RequestTimeoutException error while invoking a BPEL process using this code:
Locator locator = LocatorFactory.createLocator(jndiProps);
String compositeDN = "default/"+processName+"!1.0";
Composite composite = locator.lookupComposite(compositeDN);
String serviceName = "client";
Service deliveryService = composite.getService(serviceName);
NormalizedMessage nm = new NormalizedMessageImpl();
nm.getPayload().put("payload", requestXml);
NormalizedMessage res = deliveryService.request("process", nm);
responseMap = res.getPayload();
The error stack trace is
weblogic.rmi.extensions.RequestTimeoutException: RJVM response from 'weblogic.rjvm.RJVMImpl@604f2d14 - id: '-361032376059206
2776S:10.67.232.164:[8001,-1,-1,-1,-1,-1,-1]:emaar_domain:soa_server1' connect time: 'Mon Jan 18 11:34:41 GST 2010'' for 'executeServiceMethod
(Loracle.soa.management.CompositeDN;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;) 'timed out after: 60000ms.
oracle.fabric.common.FabricInvocationException: weblogic.rmi.extensions.RequestTimeoutException: RJVM response from 'weblogic.rjvm.RJVMImpl@60
4f2d14 - id: '-3610323760592062776S:10.67.232.164:[8001,-1,-1,-1,-1,-1,-1]:emaar_domain:soa_server1' connect time: 'Mon Jan 18 11:34:41 GST 20
10'' for 'executeServiceMethod(Loracle.soa.management.CompositeDN;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;) 'timed out after: 6
0000ms.
        at oracle.soa.management.internal.facade.ServiceImpl.request(ServiceImpl.java:135)
        at com.gss.common.bo.BpelUtil.invokeBPELProcess(BpelUtil.java:81)
To add to it the BPEL process is executing successfuly and RMI call timeout is happening.
Can I know how to increase the related timeout value?

Have got the same problem. Scenario at my end is little different though.
I am trying to invoke a BPEL process from an ESB Service.
I am trying to look into it..
However, would be grateful, if someone can give some insight into this since many are running into this issue without being able to fix.
Ashish.

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

Migrating BPEL process from 10g to 11g

Hi All,
I am trying to migrate 10.1.3.4 BPEL process to 11g. When I try to migrate the process in 11g Jdeveloper it gives me the below error in the logs and the migration is unsuccessful.
Oct 5, 2009 6:01:13 PM oracle.viewgen.plugin.workflow.WorkflowBPELProcessUpgrader debug
INFO: No more than one .task file in the upgrade source directory and hence not upgrading the bpel src
Oct 5, 2009 6:01:13 PM oracle.viewgen.componentType.bpel.BpelDDUtil checkAndUpdateBPELDD
INFO: UPGBPEL-02041: Retrieving wsdl for partnerLink "SyncItemListAgileReqABCS" from "http://localhost:7857/orabpel/default/SyncItemListAgileReqABCS/SyncItemListAgileReqABCS?wsdl". This wsdl location can be used later for any manual setup of composite reference binding, if the upgrade plan includes using 1013x endpoints for the interim.
Oct 5, 2009 6:01:19 PM oracle.viewgen.ViewGenerator main
SEVERE: Upgrade failed. Check the logs for any exceptions. Ensure that appropriate servers are reachable and valid 10.1.3.x code source is used for upgrade. Before re-attempting upgrade, restore the original code src from the backup directory.
java.lang.NullPointerException
     at oracle.viewgen.plugin.bpel.BPELPlugin.createComponentType(BPELPlugin.java:172)
     at oracle.viewgen.ViewGenerator.main(ViewGenerator.java:212)
Caused by: java.lang.NullPointerException
     at java.util.Hashtable.put(Hashtable.java:394)
     at oracle.viewgen.componentType.bpel.BpelDDUtil.processDefinition(BpelDDUtil.java:576)
     at oracle.viewgen.componentType.bpel.BpelDDUtil.checkAndUpdateBPELDD(BpelDDUtil.java:473)
     at oracle.viewgen.plugin.bpel.BPELPlugin.createComponentType(BPELPlugin.java:107)
     ... 1 more
The BPEL Process which I am trying to migrate has an invoke activity which calls another BPEL process.Should the other BPEL process be migrated and deployed before ?
Thanks in advance.
Regards,
Kaavya

There is an issue with the process, it is trying to connect to the service, I don't believe it needs to be the new 11g version but the WSDL should be accessible.
http://localhost:7857/orabpel/default/SyncItemListAgileReqABCS/SyncItemListAgileReqABCS?wsdl". This wsdl location can be used later for any manual setup of composite reference binding, if the upgrade plan includes using 1013x endpoints for the interim.
Oct 5, 2009 6:01:19 PM oracle.viewgen.ViewGenerator main
SEVERE: Upgrade failed. Check the logs for any exceptions. Ensure that appropriate servers are reachable and valid 10.1.3.x code source is used for upgrade. Before re-attempting upgrade, restore the original code src from the backup directory.
cheers
James

Using Java Embedding Unzip Code and a Trigger File in a BPEL Process

Hello,
Thanks in advance to anyone that contributes with any insight. It is much appreciated. Having said that I will get to the crux of my problem.
I am currently using Oracle 11g. I have created a SOA composite application that incorporates BPEL and Java. I have the code needed to unzip and extract compressed folders. However, when this was first built out using BPEL it automatically created a web service in the "exposed service" lane and not a file adapter which I believe is needed in order to trigger the process via a start.txt file for example. Based on what I know ... this web service automatically connecting to the BPEL process was simply due to the order of operations, etc. So by creating a 'read' file adapter first and then creating the BPEL process and selecting the template "Define Service Later", it does not automatcially connect the web service to the BPEL process and it will allow me to connect a file adapter to this BPEL process instead ... great. When opening up the BPEL file I then connect a recieve component to this file adapter and configure appropriately.
Essentially, my objective in setting up a trigger to start this unzip process is due to the BPEL process before that outputs or writes the .zip folder to the same directory that I want to poll and/or trigger via a start.txt file. I can get this process to work with a webservice connecting to the BPEL process and by using a Java Embedded in BPEL file, which in turns calls the package/ class that has the java code needed to unzip.
For some reason whenever I try to use a file adapter instead of the native web service that gets created (as mentioned above) it doesn't work. It seems to build or compile just fine however, I am getting errors when I try to deploy.
Note: The Java code contains all the paths where the zip file is to be taken from and extracted to. So because this is in the code I don't need the file adapter to handle this. I just want to use the file adapter so that I can trigger the process via start.txt or something of that nature.
Thanks to anyone that has any suggestions.
Kind Regards,
Kevin
Errors when attempting to deploy are as follows:
[04:12:54 PM] Error deploying archive sca_Job2_UnZip_rev1.0.jar to partition "default" on server soa_server1 [http://WN017A.homedepot.com:8001]
[04:12:54 PM] HTTP error code returned [500]
[04:12:54 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Error occurred during deployment of component: BPELProcess1 to service engine: implementation.bpel, for composite: Job2_UnZip: ORABPEL-05250
Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "H:\Oracle\Middleware\user_projects\domains\Dev_Acorde\servers\soa_server1\dc\soa_d78eb301-314c-422a-a748-bcfe7d0906e8"; the exception reported is: java.lang.RuntimeException: failed to compile execlets of BPELProcess1
This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).
[04:12:54 PM] Check server log for more details.
[04:12:54 PM] Error deploying archive sca_Job2_UnZip_rev1.0.jar to partition "default" on server soa_server1 [http://WN017A.homedepot.com:8001]
[04:12:54 PM] #### Deployment incomplete. ####
[04:12:54 PM] Error deploying archive file:/C:/JDeveloper/mywork/Job2_UnZip/Job2_UnZip/deploy/sca_Job2_UnZip_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

Just wanted to provide a screenshot of the BPEL file as supporting documentation to better illustrate my issue.
Thanks so much,
Kevin

How to catch exception always in BPEL without Hanging BPEL Processes

Hi,
I am facing a freequent problem with stucking BPEL instances. Some time it stucks at a partner link level, some times at adapter level, some times at embeded java save point. Obviously we know that if there is any issue at some point in the BPEL process, then the instance will rollback upto the last persistance stage and the instance status shows like still its running. Is there a way where we can through the error always and catch and show with an error appearence in the console?
The QA team wants to see plain success or throwing error always in the BPEL console. Showing like a running process state is some misleading look in the BPEL console. How to achieve this?
--Khaleel

Hi,
I have seen some other instances which are in the same state, but its happening even after getting the reply from the invoked partner link.
To explain this in details... Say I have the process A which calls the webservice B. if the process B has a database adapter to insert some data and then the process B will send the status back to the calling process A.
However if the process B takes some more time because of any unknown reasons of database (say its very slow some time due to heavy load on db). So the db adapter may take some time after that it may get SQL error if the transaction is failed, or the successfully comes out if the transaction is success.
In both the above cases the process B sends the results back (either error message or the success message) back to the calling process A.
Now the issues is the process shows the status like its waiting for the process response. but when I go to Audit and see the process then the process B is actually already returned status back but took some extra time than usual.
Now in the process A I am expecting timeout error so that I can catch in catchall, or the success so that it come to an end successfully. But neither is happening.. the process shows like its waiting for the response.
Any explanation is appreciated.
I am looking at the following logs files.. some places I see like process already completed.. I didn't get what exact reason behind this.
/oracle/product/10.1.3/soa/bpel/domains/Website/logs/ == domain.log
/oracle/product/10.1.3/soa/bpel/system/logs/ == orabpel.log
/oracle/product/10.1.3/soa/opmn/logs/ == OC4J~oc4j_soa~default_group~1.log
/oracle/product/10.1.3/soa/j2ee/logs/ == oc4j_soa_default_group_1.xml
--Khaleel

TNS:Operation Timed Out error while trying to invoke BPEL Process from sql

Hi,
I am trying to invoke a BPEL Process from PL/sql code. When i try to invoke the process, I am getting the following error message
ORA-29273 HTTP Request Failed
ORA:06512: at SYS.UTH_HTTP at line 1029
ORA:12535: TNS:Operation Timed Out
ORA:06512: at line 18
I have the SOA suite installed on my local machine...and the BPEL process that i am trying to invoke is deployed their.
Any idea what could be wrong..following is the code piece
soap_request:='<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header/>
<soap:Body xmlns:ns1="http://xmlns.oracle.com/Test">
<ns1:TesProcessRequest><ns1:input>is1_1land</ns1:input></ns1:TesProcessRequest>
</soap:Body>
</soap:Envelope>';
dbms_output.put_line('soap_request: '||soap_request);
utl_http.set_proxy('3.209.30.25:80', '3.209.32.149:8888');
http_req:= utl_http.begin_request('http://3.209.32.149:8888/orabpel/default/Tes/1.0 '
,'POST'
,'HTTP/1.1');
dbms_output.put_line('after Begin Request' );
utl_http.set_header(http_req, 'Content-Type', 'text/xml') ;
Please advise

you are right the file adapter doesnt invoke any bpel
process, instead it is polling the file from
directory location?If it is polling for new files, shouldn't it create a new instance of the BPEL process automatically the moment it finds a new file? In other words, should a new file trigger an instance of the BPEL process rather than being started from PL/SQL?
Can this file adapter not be invoked as bpel process
in that case?The file adapter is part of a BPEL process. The BPEL process can be invoked from e.g. PL/SQL.
In this case this file adapeter return to an RECEIVE
activity...I think this receive cannot be invoked as
a BPEL process rite?Can you explain what you mean with this?
Also , will all synchronous request return "TIMEOUT"
error, if tried to invoke from pl/sql?Only if the synchronous process instance takes more time to complete (and thus to return) than the value specified for a time-out to occur. If the instance completes in for example 10 ms and the time-out time is specified as 30 seconds, no time-out will occur.
Regards, Ronald

New problem calling PL/SQL based WS from BPEL process

I have created a webservice based on a PL/SQL package based function with JDeveloper and deployed the web service on the BPEL OC4J server.
Calling the web service endpoint directly from internet explorer works fine.
I have also created and deployed a BPEL process to call this web service. When i run the process it completes normally but returns an Oracle error in the out-variable: "Ora-06502 Numerical value error".
Through my PL/SQL logging i can see that the input-variable to the PL/SQL function is empty (so when i try to use this value it gives me the Ora-06502 error).
When i check the audit trail of the BPEL process instance i find that the assignment of the input variable is ok. This input variable is used in the invokation of the web service (and at this point still has the proper value).
What can be wrong? (the only part i cannot trace is the working of the Java stub created by JDeveloper).
Any ideas?
thanks, Bart

This is the complete stack trace:
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: CataLog
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> inputContainer: {InputParameters=<CATLOG xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/EBILLING/CATALOG/"><ID_AZIENDA>134</ID_AZIENDA><ID_PROGETTO>134</ID_PROGETTO><CAPTURE_DATETIME>1959</CAPTURE_DATETIME><FULLNAME>lkjh</FULLNAME><PATHNAME>kjsf</PATHNAME><FILENAME>kjsf</FILENAME><DESTINATION_PATH>kjsf</DESTINATION_PATH><MOVE_DATETIME>1959</MOVE_DATETIME><SIZE_BYTES>134</SIZE_BYTES><LAST_WRITE>1959</LAST_WRITE><ID_THOR>2345234</ID_THOR><SNAPSHOT_PATH>kjsf</SNAPSHOT_PATH></CATLOG>}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> callProps: {is-initial-call=true, parentId=5602, process-id=StoredProcedure, rootId=5602, conversationId=bpel://localhost/default/StoredProcedure~1.0/5602-BpInv0-BpSeq0.3-3, location=null, priority=0, work-item-key=5602-BpInv0-BpSeq0.3-3, domain-id=default, revision-tag=1.0}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl
<2004-12-01 10:48:52,014> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=CataLogportTypeQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_pttserviceQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[{http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_ptt]: Locating jndiAdapterInstance eis/CatapultDBLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,016> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,234> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,235> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,294> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Invoking JCA outbound Interaction
<2004-12-01 10:48:52,296> <DEBUG> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
<2004-12-01 10:48:52,297> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
<2004-12-01 10:48:52,299> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
<2004-12-01 10:48:52,300> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happenned
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
<2004-12-01 10:48:52,302> <DEBUG> <default.collaxa.cube.ws> <BPELInvokeWMP::__invoke> Caught RemoteException
orabpel.apache.wsif.WSIFException: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA@788a7bhttp://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] : Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
; nested exception is:
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:464)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
... 25 more
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more

Invoking BPEL process from Java servlet with org.w3c.dom.Element as payload

Hello,
I'm trying to initiate a BPEL process from my servlet running under Tomcat. When I create the NormalizedMessage passing the XML as a String everything works fine. But if I use an org.w3c.domElement the BPEL server doesn't react at all (even on DEBUG log level there are no outputs).
This works:
NormalizedMessage message = new NormalizedMessage();
message.addPart("payload", "<foo></foo>");
This doesn't work:
org.w3c.dom.Element elem;
oracle.xml.parser.v2.XMLDocument xmlDocument;
NormalizedMessage message = new NormalizedMessage();
Element elem = xmlDocument.createElement("foo");
message.addPart("payload", elem);
Is there a known problem with payloads using Element or did I get something completely wrong? Thanks in advance,
Hans.

Hello,
I'm trying to initiate a BPEL process from my servlet running under Tomcat. When I create the NormalizedMessage passing the XML as a String everything works fine. But if I use an org.w3c.domElement the BPEL server doesn't react at all (even on DEBUG log level there are no outputs).
This works:
NormalizedMessage message = new NormalizedMessage();
message.addPart("payload", "<foo></foo>");
This doesn't work:
org.w3c.dom.Element elem;
oracle.xml.parser.v2.XMLDocument xmlDocument;
NormalizedMessage message = new NormalizedMessage();
Element elem = xmlDocument.createElement("foo");
message.addPart("payload", elem);
Is there a known problem with payloads using Element or did I get something completely wrong? Thanks in advance,
Hans.

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 deploy a BPEL process with rules

Hi All
I created a very simple BPEL process and defined a business Rule in composite, that I call from within my BPEL process.
I am however not able to deploy the project completely successfully.
I am using JDEV 11g to build/deploy my projects on a SOA_Suite_11g. Note that I can deploy a project successfully if it does not have a business rule.
This is what I see in the 'Deployment Log' tab:
[01:49:17 PM] Deploying profile...
[01:49:17 PM] Wrote SAR file to /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Deploying sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
[01:49:17 PM] Processing sar=/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Adding sar file - /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Preparing to send HTTP request for deployment
[01:49:17 PM] Creating HTTP connection to host:redunca.pvo.groundhog.com.au, port:8001
[01:49:17 PM] Sending internal deployment descriptor
[01:49:17 PM] Sending archive - sca_FLThree_rev1.0.jar
[01:49:19 PM] Received HTTP response from the server, response code=500
[01:49:19 PM] Error deploying archive sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
[01:49:19 PM] HTTP error code returned [500]
[01:49:19 PM] Error message from server:
Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
Process Generation Failed.
failure to generate the BPEL process file "".
Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
Ensure that the file "" is a valid file to be generated.
: Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
Process Generation Failed.
failure to generate the BPEL process file "".
Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
Ensure that the file "" is a valid file to be generated.
[01:49:19 PM] Check server log for more details.
[01:49:19 PM] #### Deployment incomplete. ####
[01:49:19 PM] Error deploying archive file:/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Any ideas..
Thanks

"Too many open files" issue is most likely because of a (few) Sun JDK6 bug(s). These bugs may not even get fixed in JDK6. It could hit at runtime or compile time depending on the number of jar files getting used and/or a few other variations around the use of file descriptors at a time by the JDK/JRE. One can use "lsof -p <pid>" command on Linux and see how the File Descriptors are growing when this issue is seen. E.g. use the pid of junit java process and not the main Ant java process if you want to debug at runtime. For compile time, grep on the compiler process.
Increasing the limit of file descriptors is used as a workaround.
How to increase per-process per-user file descriptor limit on your Linux hosted box:
Using "limit" (csh) or "ulimit" (bash) command find out what is the value of "descriptors". As a root user (use sudo) edit /etc/security/limits.conf file.
Close your x term and re-open (or re-connect your NX client) for this change to take effect. System re-start should not be required. If you are not able to increase the limit for some reason using these steps, try a few other things like re-starting your VNC server (or something similar), re-start your Linux box.

Executed and failed alternatively while testing a bpel process

I have created a bpel process such that the response from the bpel is posted to a Queue.
I have deployed the bpel and esb process successfully.
While testing the bpel process,it is completely executed for the first time.(no error in esb and bpel console)
While testing for the second time,it is failed(bpel is completely executed but in esb console i am getting error)
I dont know what is the problem.
The error message in esb console is:
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/Onsite_ESB_Topic/RMS_Topic.wsdl [ Produce_Message_ptt::Produce_Message(SynBPELProjectProcessResponse) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. esb:///ESB_Projects/Onsite_ESB_Topic/RMS_Topic.wsdl [ Produce_Message_ptt::Produce_Message(SynBPELProjectProcessResponse) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12133 ERRJMS_JMS_EXCEP. Unable to create JMS connection due to JMS exception. Please examine the log file to determine the problem. [Caused by: JMSServer[dgda21b:12652]: failed to authenticate "oc4jadmin/welcome1" via "[JAZNUserAdaptor: user=oc4jadmin]".] ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. esb:///ESB_Projects/Onsite_ESB_Topic/RMS_Topic.wsdl [ Produce_Message_ptt::Produce_Message(SynBPELProjectProcessResponse) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12133 ERRJMS_JMS_EXCEP. Unable to create JMS connection due to JMS exception. Please examine the log file to determine the problem. [Caused by: JMSServer[dgda21b:12652]: failed to authenticate "oc4jadmin/welcome1" via "[JAZNUserAdaptor: user=oc4jadmin]".] Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:633) at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:736) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:497) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:430) at oracle.tip.esb.server.common.wsif.WSIFInvo
Can anyone help me in solving this issue?
Thanks in Advance.

Hi,
I could see the userID/password is wrong in the adapter,
you can chnage that one by following:
em/-->
Cluster topology-->home 0c4j - >Applications ->stand alone Resource adapter (in View of the Drop down combo)
choose the adapter ->JMS Adapter ->connection factories -->eis/Jms/QueueConnectionFactory-change the password to your password(SOA)
and try the same....

Debugging BPEL Process Timeouts...

Similar Messages

Maybe you are looking for