ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vito <testfor...@163.com>
Subject Re:Re:Re: Management API function be blocked until all the instances run to the end
Date Thu, 27 Mar 2014 08:26:08 GMT
Hi all,

These days I tried to invoke listInstancesSummary functions of Management API after invoke
many instances, but the functions were all blocked until all the instances ran to the end.
I thought of abandoning the bitronix transaction manager, and it works. The functions are
not blocked any more. Do you know why bitronix block my functions, and can I do some modification
to the bitronix configuration in ODE?


At 2014-03-25 19:54:51,Vito <testforvln@163.com> wrote:
>Hi Sathwik,
>Actually I did not solve the problem of combining openjpa and postgresql, and the two
communities also did not give me much information of the problem. What I do is to use hibernate
DAO to combine ODE and postgresql, and it's working just fine.
>The listInstancesSummary function is already in the Management API. I just invoked it
and found it blocked sometimes when I had many instances running. After looking into the ODE
source code, I find that the function listAllInstances() actually have little difference from
listInstancesSummary(), while the former function have few filters than the latter.
>Have you met with the problem that the Management API be blocked? I think it may be caused
by some transaction problems.
>At 2014-03-25 17:02:24,"Sathwik B P" <sathwik.bp@gmail.com> wrote:
>>Good to know you could solve the issue with Postgresql. It would be great
>>if you could help the community know about the changes you did to make it
>>work :)
>>You might have a look at listAllInstances which will list all the instances.
>>What is the query that used in listInstancesSummary?
>>On Tue, Mar 25, 2014 at 11:33 AM, Vito <testforvln@163.com> wrote:
>>> Hi all,
>>> Thank you for your kindly help these days. I just make ODE up and running
>>> with mysql and postgresql finally! But when I try some experiments, other
>>> problems seem to come up. Actually, it may not be called an error because
>>> there is no error or exception.
>>> The problem came out when I ran multiple instances. It met no problem
>>> until I try to list instances summary from ODE Management API to get the
>>> instance number in the engine. The list function returned no results until
>>> all the instances ran to the end. I think it may be blocked by the
>>> transactions of running instances.
>>> Do you think the transactions really block the management api function? If
>>> this really happens, how can I get the number of instance number of the
>>> current engine?
>>> Best,
>>> Vito
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message