[ 
https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672227#action_12672227
 ] 

Rafal Rusin commented on ODE-511:
---------------------------------

Well, yes, I know that path. 
After sending second request in Error Scenario, I got (in EH_EVENT):

-------------
PickResponseChannelListener().onRequestRcvd()
SELECT::run()
WAITING::run()
WAITING::ParentScopeChannelListener::failure() -> 
ParentScopeChannelListener::completed()
--------------

And there was no WAITING::TerminationChannelListener::terminate() nor 
WAITING::EventHandlerControlChannelListener::stop(). 
It might be better to use one of them. I think it needs then investigation in 
SCOPE class. 
If you want, I can do it. 
However this patch I attached, which watches for ParentScope completion or 
failure and cancels pickResponseChannel when it happens, is a good solution too.

I've got also a question. I'd like to add a test case for it. It would need 
adding assertion to 
./bpel-runtime/src/main/java/org/apache/ode/bpel/memdao/CorrelatorDaoImpl.java 
addRoute() method, 
so it won't accept ambigous routes. What do you think about it?


> 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, event-handler-correlation.diff, 
> 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.

Reply via email to