WLI : JTA Timeout at about 300 seconds ?

I've been fighting against WLI on that matter for the last two days.

In the beginning, when I saw that stacktrace :


<27 mars 2009 12 h 38 IRST> <Error> <WLW> <000000> <Exception processing myProcess
javax.transaction.TransactionRolledbackException: EJB Exception: : javax.transaction.TransactionRolledbackException: EJB Exception: :

 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds

        at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1600)
        at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1147)
        at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1882)
        at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1064)
        at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
        at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
        at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
        at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)


I thought to myself "This is pretty much annoying, but I guess I can handle that !".

And I started to change the JTA parameters in the console :




But it didn't change a thing ...

Eureka ! It's got to be something related to the EJB as said in the error message.

I then exploded (oh yeah) all my Event Generators (embodied by EJBs) and updated the weblogic DD such as :


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">

  <disable-warning>BEA-010001</disable-warning> <!-- EJB class loaded from system CL -->
  <disable-warning>BEA-010054</disable-warning> <!-- EJB class loaded from system CL (ejbc) -->
  <disable-warning>BEA-010200</disable-warning> <!-- EJB class contains static member -->
  <disable-warning>BEA-010202</disable-warning> <!-- Call-by-reference disabled -->


But it didn't change a thing ...

I was a bit disappointed and lost because, to me, I had done all that was in my power.

Thanks to Google (once again), I finally reached an interesting page saying :

"The default timeout period for a transaction is 300 seconds (5 minutes)."


Oh gush ! Exactly what I was trying to figure out for two days !!!

So, what am I to do to get rid of that exception ??? (thrill)


Well, it's no big deal, but this option is not easily findable :

Take your process project and locate the directory WEB-INF :




In that directory, you''ll find a wlw-config.xml file.

That's this file you'll have to modify to change the JTA timeout.

Example :


<wlw-config xmlns="http://www.bea.com/2003/03/wlw/config/">



And voilà ! But be sure you understand the use of wlw-config.xml and wlw-runtime-config.xml.

Quoting Oracle : Note that the values appearing in wlw-config.xml are hardcoded into the deployment EAR and cannot be overridden by other runtime configuration mechanisms.

For most cases you should use wlw-runtime-config.xml to configure the runtime information for your Workshop application.


Hope that helped !



Searching on forums.bea.com

Who hasn't faced one day a BEA search result leading to a page on forums.bea.com ?

Pretty easy answer : nobody.

Till a couple weeks ago, it was possible to use Google cache to get the desired posts.

But now the cache's expired, it's impossible.

Well, that's what lots of people think but they're mistaken !


Oracle has migrated the whole site onto forums.oracle.com.

Unfortunately, Google hasn't indexed those pages yet.

However, you still can perform a search directly on the site.


As I like to take care of my readers :) , I've looked for the most direct link, and here it is :



Click that link, enter some keywords, and voilà !


Mots clés Technorati : ,,,,


JAX-WS, OSB & BPEL Process Manager : a simple example

If you can't wait next summer to know what's going to happen with SOA Suite 11g,

here's a sample to manage your frustration :)


Presenting the context


The example I've chosen is a quite simple one. Indeed, it's no real case,

just a convenient way to illustrate how the complete chain works.

=> A user wants to go to the movies. He will send the movie title to a webservice

which will route him to the theater where there are the most available seats.

To do that example, I've installed :

  • => OSB 10gR3 / Workshop 10gR3
  • => SOA Suite 10g

In the end, I'll have three JVMs running :

  • => One for OSB
  • => One for WLS (hosting the webservices)
  • => One for BPEL Process Manager (OC4J)


Designing some webservices (JAX-WS)


We'll design three webservices, in order to have enough data to process.

Three webservices (one per theater) :

  • => UGB
  • => Gomon (GMN)
  • => MK3


Workshop Structure


They all have the same business contract : only the returned result differs from one to another.

You can have a detailed example on how to design a JAX-WS webservice on another blogpost :


Example : the Gomon Webservice


package fr.mbutton.blog;

import javax.jws.*;

public class CheckAvailability_GMN {

    public boolean isMovieStillPlaying(String movieTitle) {
        return true;
    public int getAvailableSeatsForMovie (String movieTitle) {
        return 124;


And here's a sample build.xml for this webservice :


<project name="GMN" basedir="." default="build-webservice">

    <taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask" />
    <property name="dest.dir" value="D:\BEA_ROOT\user_projects\workspaces\osb_bpel\Theaters\EarContent" />

    <target name="build-webservice">
        <jwsc srcdir="src" destdir="${dest.dir}">
            <jws file="fr/mbutton/blog/CheckAvailability_GMN.java" type="JAXWS" />



The execution of the ANT build.xml will create one WAR per webservice.

Then, just deploy the three WARs to your WLS domain and make sure they're all reachable.

To do so, click on each of them :


Webservices Deployments


And then, once you've clicked on the webservice you want to test, you should see a "Testing" tab.


WSDL & Test Client


You can choose either to show the WSDL or launch a test client. Either way, you'll be sure it's up & running.


Setting up an OSB configuration

Here's a very simple definition. No extra processing : the proxy service will directly route to the

business service, with no additional computing.

Note : If you're working with two separate domains at the same time, I'll advise you to read that article :


A little remark : if you take a closer look to the generated webservice, and especially to their WSDLs, you'll see

that the XML schema is imported :


<xsd:import namespace=http://fr.mbutton.blog/gomon
     schemaLocation="" />


In OSB, you'll have to import those schemas separately and then link them to the corresponding webservice.


OSB Schemas


Then create as explained above, one business service per webservice exposed, and one proxy service per business service, like :


GMN Proxy Service


Once everything is correctly set up, test your configuration by trying to reach the proxy services.

To do so, click on a proxy service, it will lead you to this screen :


Review PS configuration


To test it, take your server URL (for example : http://myserver:7001), add the endpoint URI + "?WSDL" and check it you've got something :)

No need to tell that if you don't, it's not normal, right ?


Orchestrating webservice calls thanks to BPEL PM


Here we go ! Now, we've got three webservices up and running and we applied the mediator pattern thanks to an ESB.

What we need now is to call the webservices, store the results and return a computed result.

Exactly what BPEL was designed for.

Note : former BEA clients used WLI (WebLogic Integration) for the same kind of matter.

First thing, open JDeveloper and create a new Application (similar to an Eclipse workspace).


Application creation


Once created, add a synchronous BPEL Process Project.


BPEL process project type


Next step :


BPEL Process creation


In the application pane, an empty BPEL project is created :


BPEL Structure


In the graphical view, you'll only see two steps (receiveInput & replyOutput) and a partnerLink (client).


BPEL basic process


First of all, let's modify the name of the BPEL process variables.

To do so, open the associated XSD in Integration Content > Schemas and change element names (in blue) :

<schema attributeFormDefault="unqualified"
    <element name="BlogSampleProcessRequest">
                <element name="movieTitle" type="string"/>
    <element name="BlogSampleProcessResponse">
                <element name="theaterName" type="string"/>


As we will call three webservices at the same time, we'll need a "Flow" activity.

(Note : BPEL PM does spawn a thread for each branch. Whereas WLI has a flow-like activity, it's not parallel but sequential)

Drag and drop it to the node between the receive and the reply.




Open the branches. We'll need three branches and in each, a call to a webservice will be performed.

Add an "Invoke" activity in the first branch.



Flow & invoke


We'll have to link that Invoke activity to one of the webservice.

What you have to know is that any external part to the BPEL process

is called a "Partner Link" or "Adapter".

  • PartnerLink (client, webservice)

  • Adapter (file, JMS message and so on)

So to create a reference to the webservice, let's create a partnerLink.

Drag and drop a partnerLink service to the right side of the BPEL process. (it's a good practice to keep BPEL process callers

on the left and BPEL process called partners on the right).


image image



Once the item is dropped, a popup will show up.




Enter the URL of your webservice and click refresh (circle made of the two blue arrows).




Accept the proposal.

Draw a line between the invoke action and the partnerLink (you can bind these items differently)


Linking invoke & partnerLink


Choose the operation to invoke and create local variables.


PartnerLink Creation


For now, the wiring has been made, but we need to assign the bpel input variable to the webservice input variable.

Just add a Assign activity




and copy the value such as :


Copy operation


In order to see if our bpel process is working, we'll add another Assign activity which will assign the returned value

to the client.


Copy operation


Of course, this copy isn't right : the returned result represents a number of seats and the client expects a theater name ...

But it's just for some testing matters.


To build and deploy your BPEL process, edit the build.properties and make sure all the information match your configuration.

(port/user/password ...)

Right-click the application, chose "Make". Then right-click on the build.xml file and choose "Run Ant Target" > "Deploy".


Log in to your BPEL console (for me, it's http://localhost:8888/BPELConsole).

Select your BPEL Process and run the test console. Enter a movie title and notice the result.

It should be something like :


BPEL Flow 


Our BPEL process works perfectly.

I won't go deeper in the process and explain how to compare and assign values; you can figure out what to do next

by yourself and if not, you will find some good references on the Net.

If you want to learn more, contact Oracle University :)


Exposing the BPEL process through OSB


Last but not least, our BPEL process has to be exposed as a webservice. But as we started to use the mediator pattern,

no way a client can call the BPEL process directly. It has to be called through the ESB.

To do so, create a business service based on the BPEL process WSDL.

To get the WSDL, click on the corresponding tab :


WSDL & Enpoint URI


And in the bus, create a Business Service based on this WSDL.

Note : You'll have to create a schema first.

Import your schema from the URL (for me it's : http://mbutton01:8888/orabpel/default/BlogSample/1.0/BlogSample.xsd)

Once your WSDL is successfully created, map a business service on it and choose "BPEL 10g" as the transport :




For the endpoint URI, use the URL given on the WSDL page, but replace protocol "http" by "opmn".

On the next screen, chose "Synchronous Client".

Review and accept the configuration.


Creating the business service for the bpel process


Create a proxy service based on the newly created business service :


Creating the BPEL Proxy Service


Test your proxy service and you should have your BPEL process correctly exposed.


BPEL WSDL exposed


Mots clés Technorati : ,,,,,,