ORABPEL-02182

Problem:
ORABPEL-02182

JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "4260005-BpInv5-BpTry7.13-1". Please consult your administrator regarding this error.

Some Thoughts:
You can encounter this error if response time of adapter is greater than the predefined waiting time for a BPEL instance.As a result process does not get dehydrated on time and fails by throwing this error.

Solution:
A better solution for above problem should be to increase the transaction-timeout values in order to make the BPEL instance to wait more time until a response returns from the adapter.

Following are the steps you should follow to acheive the result:

1) Stop SOA Server

1) Goto SOA_Home\j2ee\config\transaction-manager.xml, serach for transaction-timeout and set transaction-timeout for e.g. to 7200 or more (default value is 30).

2) Goto SOA_Home\j2ee\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml and set all transaction-timeout to 3600 or more. The value passed here should be always less than the value which is mentioned in step 2.

3) Goto SOA_Home\bpel\domains\config\domain.xml and set syncMaxWaitTime to 240 or more. The value passed here should be always less than the value which is mentioned in step 3. (Default value is 45)

4) Start SOA server and run the process again. Process should work fine.

ORABPEL-04077

Problem:
ORABPEL-04077
Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "jdbc/BPELServerDataSource". The exception reported is: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: Timed out

Thoughts:
Sometimes deploying a bpel project of bigger size using JDeveloper throws exception: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: Timed out. This is due to the fact that JDeveloper takes too much time and fails to deploy the project.

Solution:
To solve the issue we need to change values of some configuration files of SOA Server. Follow the below mentioned steps:

1) Stop the SOA Server

2) Open the transaction-manager.xml file present under location:-
<SOA_HOME>\j2ee\oc4j_soa\config\transaction-manager.xml

3) Change the transaction-timeout attribute value to some higher value, viz. transaction-timeout="7200"

4) Now open the orion-ejb-jar.xml file present under location:-
<SOA_HOME>\j2ee\oc4j_soa\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml

5) Change the transaction-timeout attribute to some higher value, viz. transaction-timeout="3600"

6)There will be 6 entries of transaction-timeout attributes in the file. You have to change all the 6 attributes.

7) Save the files.

8) Restart the SOA Server.

9) Now try to deploy the BPEL project using JDeveloper. It should work.

ORABPEL-10903

Problem:
ORABPEL-10903: "failed to read wsdl" when deploying BPEL process

Solution:
Check your schema file which you are using. There might be a possibility that the schema file name contains spaces. Rename the schema file(with no spaces).

Note that if you are importing that schema in your wsdl file then dont forget to change the name there too.

Redeploy the project and the error will be gone.

ORABPEL-05244

Problem:
ORABPEL-05244 error sometimes occurs in the opmn log shortly after deploying the BPEL process. Furthermore, it may cause the BPEL domain to hang.
The error looks like:
<2009-06-27 11:14:27,752> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError>
Error while invoking bean "process manager": Timed out waiting for process load lock.
Failed to obtain load lock for process "HelloWorld-1.0"; timed out after 120,000 seconds.

Timed out waiting for process load lock.
Failed to obtain load lock for process "HelloWorld-1.0"; timed out after 120,000 seconds.

Solution:
There is no direct solution to solve this problem.
To overcome this there are some suggestion by which you can get rid of such errors. The following suggestions are:
1) Undeploy the existing project.
2) Bounce the SOA Server.

BPEL : ORABPEL-11622

Problem:
A "javax.transaction.RollbackException" is thrown when BPEL PM is under heavy load.

Error:
Caused by: ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor
(i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-23005]
(Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)):
oracle.toplink.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: Transaction has been marked for rollback

Solution:
A step by step solution for this error is shown as under:
a. Goto SOA_HOME/bpel/domains//config

b. Open domain.xml and change syncMaxWaitTime to 1800.
(If the existing value is more than this don't make any changes here)

c. Goto SOA_HOME/j2ee/OC4J_SOA/application-deployments/orabpel/ejb_ob_engine

d. Open orion-ejb-jar.xml and change all the transaction-timeout values to 3600. (If the existing value is more than this don't make any changes here).

e. Goto SOA_HOME/j2ee/OC4J_SOA/config

f. Open transaction-manager.xml and change transaction-timeout value to 7200. (This value you could use as high as 60000, if needed).

ORABPEL-02118

Problem:
This ORABPEL error will drive you crazy. This error occurs when you try to invoke an asynchronous BPEL process that is deployed to Oracle BPEL Process Manager 10.1.3.3 or later.

Solution:
I got the solution for this error over Internet & thought of sharing this with my blog readers.
In pre 10.1.3.3 release the default behaviour were to keep global variable information along with the instance information for completed BPEL processes.
In 10.1.3.3 or later, this behaviour changed for performance reasons so that the default behaviour is now, not to keep any global variables for a BPEL process once the BPEL process has completed.

You can configure this behaviour on a process level basis by using the parameter keepGlobalVariables in the bpel.xml file for the specific process:

<BPELSuitcase>
<BPELProcess src=".........." id="...........">
<configurations>
<property name="keepGlobalVariables">true</property>
</configurations>
</BPELProcess>
</BPELSuitcase>

ORABPEL-13080

During working on MQ Adapter for one of the clients project, I faced this problem so thought of posting it in my blog.

Error Summary:
org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/Jdev-Abhishek_ESP200011/ESP_PLF_JLE_JLN_IncomingMQAdapter.wsdl [
Enqueue_ptt::Enqueue(schedule) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: Error.
"[MessageProducer] Error while putting message in PORTAL.PUBLISHER.ERRORS "
; nested exception is:
ORABPEL-13080
Error.
"[MessageProducer] Error while putting message in PORTAL.PUBLISHER.ERRORS "
Contact oracle support if error is not fixable.

Solution:
ORABPEL-13080 error is associated with the MQ Adapter. I have identified two possible cause for this error:

1) Queue is full.
2) Queue not accessible.

So to get rid of this error, either check your MQ Adapter connection details and priviledge or Clear the unwanted messages from the Queue.

Thats it...Keep Learning...

BPEL : ORABPEL-09903

I am back with ORABPEL error topic again. This time I will show you how to get rid of the error ORABPEL-09903.

Problem:
Error shown below is reported sometimes when you deploy a BPEL project:

C:\jdevstudio10133\jdev\test\testApps\build.xml:79: A problem occured while connecting to server using port "7777":
bpel_testApps_1.0.jar failed to deploy.
Exception message is: ORABPEL-09903
Could not initialize activation agent.

Solution:
This type of error happens when the JNDI entry is not proper or you have insufficient priviledges.
Check for the following things to get rid of this error:

1) Check the JNDI names, as they may be pointing to a different location. Test it.

2) Test that the user connecting to the queue has enough priviledges.

In my case, I was not having proper priviledges for accessing the queue.


Now compile and try to deploy your process.

Happy Learning...

BPEL : Exception ORA-01691

Exception looks like:

<2008-04-15 16:05:59,168>

Error while invoking bean "delivery": Cannot update lob column.
The process domain was unable to update the lob column "7" in the datastore.
The exception reported is: ORA-01691: unable to extend lob segment ORABPEL.SYS_
LOB0000069158C00007$$ by 128 in tablespace ORABPEL

Solution:

For overcoming this exception, you can do either of the things mentioned below:

** Clean up the dehydration store

or

** Increase orabpel tablespace size by running a script similar to the following mentioned below:


alter tablespace orabpel add datafile
'/oracle/product/oradata/orcl/orabpel02.dbf'
size 1024M
autoextend on
next 512M
maxsize 12040M;


Note:- This script is already included in the default IRCA tool of Oracle
BPEL Process Manager for 10.1.3.

BPEL: Exception ORABPEL-05002

This post is in continuation to my post dated 27th september 07 on exception ORABPEL-05002. I have found some real good points to deal with such exceptions.

The exception looks like this,
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out.

Solution:
You need to follow the steps mentioned below:

1.) Goto $Oracle_Home\j2ee\home\config\transaction-manager.xml:
change the transaction-timeout parameter, say 'x'

2.) Goto $Oracle_Home\j2ee\home\application-deployments\orabpel\ ejb_ob_engine\orion-ejb-jar.xml:
change the transaction-timeout parameter, say 'y' (i.e. y < x)

3.) Goto BPELConsole:
Change the syncMaxWaitTime in all domains, where you need a bigger timeout

4.) Restart the application server (SOA Server)

While setting the parameter values, be careful because by doing so you will block threads by using long-running synchronous invokes. So as a result, it can affect the performance of BPEL engine.

BPEL : ORABPEL-05002

Question: Error ORABPEL-05002 in domain log??

Failed to handle dispatch message ... exception ORABPEL-05002Message handle error.An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage";the exception is: Transaction was rolled back: timed out;nested exception is: java.rmi.RemoteException:No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is: java.lang.Exception: No Exception - originate from:

Answer: The root cause of this problem is poor performance of the dehydration store database. If you are using Oracle Lite as dehydration store, switch to use Oracle 9i or 10g.( Better use 10g above version 10.2.0.1)

Following set ups you need to perform for overcoming such problem:

1. Increase the maxConnection number of the BPELServerDataSource. OC4J has too few available connections to the dehydration database.
Location: /j2ee/home/config/data-sources.xml

2. Size of message is too big. Two ways to deal with this problem:

a. Increase the transaction timeout
Location :/j2ee/home/config/server.xml

b. Decrease the auditLevel from BPELConsole. It will reduce the amount of data saved to the dehydration store.
Location: BPEL Console -> Manage BPEL Domain -> Configurations tab.