ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milinda Pathirage <milinda.pathir...@gmail.com>
Subject Re: Problem with database - A lock could not be obtained due to a deadlock
Date Fri, 11 Mar 2011 10:13:20 GMT
Hi Rafal,

Embedded Derby database can't handle concurrent requests to ODE. Best thing
is to use external database server if you are going to production with ODE
or if you are doing any load tests. According to your log it cannot be a
issue in DB. Can you tell us the ODE version you are using.


On Thu, Feb 24, 2011 at 3:21 PM, Rafal Perkowski <rafal.p123@gmail.com>wrote:

> Hi,
> I have two processes:
> GenericInvoke - this process invoke AddTask method from external
> webservice and waiting for response (invoke method GetResult from
> external webservice every 15 s until receive response). I set endpoint
> from url in input variable.
> MainProcess - invoke 10 times (sometimes 2 parallels invoke in flow)
> GenericInvoke.
> If I start one instance it always finish sucessfull.
> If I start 10 instances with embedded databse it finsh sucessfull, but
> It takes a lot of time and I get a lot of errors "A lock could not be
> obtained due to a deadlock" (errors in attachment).
> If I start 10 instances with external databse (SQL Server) 5-6 finish
> succesfull and 4-5 instances stuck with state active (errors in
> attachment).
> I think that apache dosn't support deadlock for Sql Server.
> I have to use SQL Server. Can you advise how can I fix this problem?
> Thanks,
> Rafal

Milinda Pathirage
Technical Lead & Product Manager WSO2 BPS; http://wso2.org/bps
WSO2 Inc.; http://wso2.com
E-mail: milinda@wso2.com, milinda.pathirage@gmail.com
Web: http://mpathirage.com
Blog: http://blog.mpathirage.com

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message