ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Fonden (JIRA)" <j...@apache.org>
Subject [jira] Created: (ODE-633) Deployment Error in JPA When deploying empty synchronous process
Date Wed, 01 Jul 2009 08:24:47 GMT
Deployment Error in JPA When deploying empty synchronous process

                 Key: ODE-633
                 URL: https://issues.apache.org/jira/browse/ODE-633
             Project: ODE
          Issue Type: Bug
          Components: Deployment
    Affects Versions: 2.0
         Environment: Debian/Linux, Tomcat 5.5, ODE Trunk Rev. 787195
            Reporter: Christian Fonden
             Fix For: 2.0
         Attachments: emptyprocess.zip, jpa_error.txt

When an empty, synchronous process is deployed, the deployment engine crashes with a duplicate
key exception in the JPA hibernate API. 

The process is structured as follows: 
- receive, receiving an empty message as part=payload
- reply, replying with a non-initialized output var
- both placed in a sequence container named main
I have attached to complete WSDL/BPEL Files to this bug to be able to reproduce it easily.

For testing, I have decided to add a BPEL:empty Empty Activity between the receive and the
reply activity, and - guess what - it worked!

This bug is really annoying because I'd like to test the execution speed of an empty process
and compare it to the performance of other processes. Measuring an empty process would have
been a good possibility to measure the time that is required to load a process from the persistance
api, instanciating it and doing the necessary Axis2 work. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message