måndag, april 07, 2008

Calling Asynchronous BPEL Process Results in ORABPEL-02118

If you try to invoke an asynchronous BPEL process that is deployed to Oracle BPEL Process Manager or later you may end up with an ORABPEL-02118 error. Also, this problem was not seen in earlier versions of Oracle BPEL Process Manager.

This problem occurs due to that the default behaviour regarding variables for completed instances has changed between these versions. In pre release the default behaviour were to keep global variable information along with the instance information for completed BPEL processes. In 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.

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

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

4 kommentarer:

  1. Blogs are so informative where we get lots of information on any topic. Nice job keep it up!!

    Dissertation Editing

  2. This post includes all information that I have always required. Although on internet we find a lot of information but the practical information is limited which you have originated in this post.

    Dissertation Samples

  3. Your blog is really helps for my search and i really like it.. Thanks a lot..:)

    Dissertation Editing Services

  4. This is my Good luck that I found your post which is according to my search and topic, I think you are a great blogger, thanks for helping me outta my problem..
    Dissertation Wtiting help