[
https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671398#action_12671398
]
Rafal Rusin commented on ODE-511:
---------------------------------
I' m using the same correlation id for two requests. So the second one goes to
the same (only one) instance in my example. I agree that multiple instances
with the same correlations are better to avoid.
In attached process, there is a commented out
similar statement, using flow, receive and throw. The hibernate error didn't
appear while it was used, so I think the exception is related to correlated
OnEvent statement and its cleanup.
When a process goes out of OnEvent statement and enters any correlated
receive or another correlated OnEvent after, this error occurs.
> 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, 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.
