View Single Post
  #2 (permalink)  
Old September 14th, 2007, 18:24
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 863
Blog Entries: 7
Groans: 0
Groaned at 1 Time in 1 Post
Thanks: 55
Thanked 213 Times in 126 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Invalid state of package in BPEL

Jeff,

So far, for Client A, we've only had to update a single BPEL timeout value, which is the "transaction-config timeout" specified in the server.xml file. We set the value as follows:

server.xml
Code:
<transaction-config timeout="300000" />
For Client B, we had to change a two, as follows:

server.xml
Code:
<transaction-config timeout="300000" />
domain.xml
Code:
<property id="syncMaxWaitTime">
        <name>Delivery result receiver maximum wait time</name>
        <value>120</value>
We also had to increase the Java Heap (memory allocation) of the BPEL server to get it to process more efficiently and reduce transaction times. The minimum heap I would consider for your BPEL server is 1024MB.

Haven't had to adjust any of the other files that you referenced, but these may be due to the version of BPEL that you are using?

Thanks,
Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote