[
https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671955#action_12671955
]
Sean Ahn commented on ODE-511:
------------------------------
Rafal,
so, the problem is that within one instance, you send a request for a receive,
then you send another request for an event. And, you get the database unique
key problem?
And, do you mean, with the newly attached process, by using a flow instead, it
works?
Thanks
> Hibernate DAO + OnEvent + Correlation error
> -------------------------------------------
>
> Key: ODE-511
> URL: https://issues.apache.org/jira/browse/ODE-511
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3
> Environment: axis2, jbi
> Reporter: Rafal Rusin
> Assignee: Sean Ahn
> Fix For: 1.3
>
> Attachments: axis.zip, error-hib.txt, jbi-sa.zip,
> OnEventCorrelation-soapui-project.xml, OnEventCorrelation.bpel,
> testRequest.soap
>
>
> 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'.
> Note that I didn't have this on OpenJPA DB.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
