Hibernate DAO + OnEvent + Correlation error

[Rafal Rusin <ra...@gmail.com>]

I run ode1x with hibernate DAO, created a process with receive,
onevent, receive, all correlated.
I sent testRequest.soap from attachment twice.
I had an error
ERROR 23505: The statement was aborted because it would have caused a
duplicate key value in a unique or primary key constraint or unique
index identified by 'SQL090129030544101' defined on 'BPEL_SELECTORS'.

Could you reproduce this? So I'll add it to jira.

Note that I didn't have this on OpenJPA DB.

-- 
Rafał Rusin
www.mimuw.edu.pl/~rrusin

Re: Hibernate DAO + OnEvent + Correlation error

[Rafal Rusin <ra...@gmail.com>]

I forgot to add that in attached process, there is a commented out
similar statement, using flow and receive. This exception didn't
appear while it was used, so I think it's related to correlated
OnEvent statement and its cleanup. When a process goes out of it and
enters any correlated receive or another correlated OnEvent, this
exception occurs.

2009/2/5 Rafal Rusin <ra...@gmail.com>:
> I run ode1x with hibernate DAO, created a process with receive,
> onevent, receive, all correlated.
> I sent testRequest.soap from attachment twice.
> I had an error
> ERROR 23505: The statement was aborted because it would have caused a
> duplicate key value in a unique or primary key constraint or unique
> index identified by 'SQL090129030544101' defined on 'BPEL_SELECTORS'.
>
> Could you reproduce this? So I'll add it to jira.
>
> Note that I didn't have this on OpenJPA DB.
>
> --
> Rafał Rusin
> www.mimuw.edu.pl/~rrusin
>



-- 
Rafał Rusin
www.mimuw.edu.pl/~rrusin

Re: Hibernate DAO + OnEvent + Correlation error

[Matthieu Riou <ma...@gmail.com>]

2009/2/18 Milinda Pathirage <mi...@gmail.com>

> Hi Matthieu,
>
> As I remember Karthick fix this bug by introducing new attribute to receive
> activity(I don't remember what it is.). But he has mentioned that this can't
> be fixed in 1.X branch due to differences in process model.
>

Unless I'm mixing issues, this one was fixed by Sean and was the result of
the wrong isolation level being used. I believe we now force the correct
isolation level.

Cheers,
Matthieu


>
> Thanks,
> Milinda
>
> 2009/2/5 Matthieu Riou <ma...@gmail.com>
>
>> On Thu, Feb 5, 2009 at 4:22 AM, Rafal Rusin <ra...@gmail.com>
>> wrote:
>>
>> > I run ode1x with hibernate DAO, created a process with receive,
>> > onevent, receive, all correlated.
>> > I sent testRequest.soap from attachment twice.
>> > I had an error
>> > ERROR 23505: The statement was aborted because it would have caused a
>> > duplicate key value in a unique or primary key constraint or unique
>> > index identified by 'SQL090129030544101' defined on 'BPEL_SELECTORS'.
>> >
>> > Could you reproduce this? So I'll add it to jira.
>> >
>>
>> I think you can create a bug no matter what, we shouldn't have such an
>> exception. The puzzling thing is that it's attempting to create a new
>> route
>> (BPEL_SELECTORS) in a message exchange cleanup stage. Smells like a bug.
>>
>> Sean, could you have a look as you know the cleanup code best?
>>
>> Thanks,
>> Matthieu
>>
>>
>> >
>> > Note that I didn't have this on OpenJPA DB.
>> >
>> > --
>> > Rafał Rusin
>> > www.mimuw.edu.pl/~rrusin <http://www.mimuw.edu.pl/%7Errusin> <
>> http://www.mimuw.edu.pl/%7Errusin>
>> >
>>
>
>
>
> --
> http://mpathirage.com
> http://wso2.org "Oxygen for Web Service Developers"
> http://wsaxc.blogspot.com "Web Services With Axis2/C"
>

Re: Hibernate DAO + OnEvent + Correlation error

[Milinda Pathirage <mi...@gmail.com>]

Hi Matthieu,

As I remember Karthick fix this bug by introducing new attribute to receive
activity(I don't remember what it is.). But he has mentioned that this can't
be fixed in 1.X branch due to differences in process model.

Thanks,
Milinda

2009/2/5 Matthieu Riou <ma...@gmail.com>

> On Thu, Feb 5, 2009 at 4:22 AM, Rafal Rusin <ra...@gmail.com> wrote:
>
> > I run ode1x with hibernate DAO, created a process with receive,
> > onevent, receive, all correlated.
> > I sent testRequest.soap from attachment twice.
> > I had an error
> > ERROR 23505: The statement was aborted because it would have caused a
> > duplicate key value in a unique or primary key constraint or unique
> > index identified by 'SQL090129030544101' defined on 'BPEL_SELECTORS'.
> >
> > Could you reproduce this? So I'll add it to jira.
> >
>
> I think you can create a bug no matter what, we shouldn't have such an
> exception. The puzzling thing is that it's attempting to create a new route
> (BPEL_SELECTORS) in a message exchange cleanup stage. Smells like a bug.
>
> Sean, could you have a look as you know the cleanup code best?
>
> Thanks,
> Matthieu
>
>
> >
> > Note that I didn't have this on OpenJPA DB.
> >
> > --
> > Rafał Rusin
> > www.mimuw.edu.pl/~rrusin <http://www.mimuw.edu.pl/%7Errusin> <
> http://www.mimuw.edu.pl/%7Errusin>
> >
>



-- 
http://mpathirage.com
http://wso2.org "Oxygen for Web Service Developers"
http://wsaxc.blogspot.com "Web Services With Axis2/C"

Re: Hibernate DAO + OnEvent + Correlation error

[Matthieu Riou <ma...@gmail.com>]

On Thu, Feb 5, 2009 at 4:22 AM, Rafal Rusin <ra...@gmail.com> wrote:

> I run ode1x with hibernate DAO, created a process with receive,
> onevent, receive, all correlated.
> I sent testRequest.soap from attachment twice.
> I had an error
> ERROR 23505: The statement was aborted because it would have caused a
> duplicate key value in a unique or primary key constraint or unique
> index identified by 'SQL090129030544101' defined on 'BPEL_SELECTORS'.
>
> Could you reproduce this? So I'll add it to jira.
>

I think you can create a bug no matter what, we shouldn't have such an
exception. The puzzling thing is that it's attempting to create a new route
(BPEL_SELECTORS) in a message exchange cleanup stage. Smells like a bug.

Sean, could you have a look as you know the cleanup code best?

Thanks,
Matthieu


>
> Note that I didn't have this on OpenJPA DB.
>
> --
> Rafał Rusin
> www.mimuw.edu.pl/~rrusin <http://www.mimuw.edu.pl/%7Errusin>
>