You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2009/02/06 11:17:59 UTC
[jira] Created: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
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
Fix For: 1.3
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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672083#action_12672083 ]
Sean Ahn commented on ODE-511:
------------------------------
Rafal,
Can you help me understand how the problem happens here?
You said that terminate() (and corresponding getBpelRuntimeContext().cancel(_pickResponseChannel), which unregisters route) is not executed at all in Error Scenario. Do you know in which path the control flows when that happens?
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, 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671385#action_12671385 ]
Sean Ahn commented on ODE-511:
------------------------------
Rafal,
Are you using the same correlation id for the two requests?
A partner link, an operation and a correlation id determines a process instance uniquely. So, you cannot have multiple process instances with the same correlation id within the same process.
To a certain degree, ODE supports multiple instances with the same correlation id. But, inherently, there's limit on how far it can go. Furthermore, there's no guarantee that all requests will be idempotent when a process becomes a complex chain of web service calls.
By using the 'unique' attribute, you can make sure that you always get an error on the client when you have multiple process instances with the same correlation id.
https://issues.apache.org/jira/browse/ODE-262?focusedCommentId=12658182#action_12658182
Let me know if your problem is different from what I explained about and if you have more questions.
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, 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.
[jira] Updated: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-511:
----------------------------
Attachment: OnEventCorrelation.bpel
Attached process with commented out working while alternative
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672043#action_12672043 ]
Rafal Rusin commented on ODE-511:
---------------------------------
I rerun all tests and they passed. So it's safe to apply.
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675950#action_12675950 ]
Rafal Rusin commented on ODE-511:
---------------------------------
Thanks for copy-pasting procedure. It's very helpful.
I noticed that one needs additionally to set environment to use proper settings.
In this particular case, one needs to do:
buildr -e hib-derby clean test:BpelActivityTest
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-511:
----------------------------
Attachment: jbi-sa.zip
error-hib.txt
axis.zip
> 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
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672487#action_12672487 ]
Sean Ahn commented on ODE-511:
------------------------------
Rafal,
I noticed that by putting an empty activity just before the <wait>, the process does not throw the error. The channel gets released property through a EH_EVENT.WAIT.stop().
> 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.
[jira] Updated: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-511:
-----------------------------
Fix Version/s: (was: 1.3.1)
1.3.2
> 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.1
> Environment: axis2, jbi
> Reporter: Rafal Rusin
> Assignee: Sean Ahn
> Fix For: 1.3.2
>
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675962#action_12675962 ]
Rafal Rusin commented on ODE-511:
---------------------------------
>Rafal,
>I noticed that by putting an empty activity just before the <wait>, the process does not throw the error. The channel gets released properly through a EH_EVENT.WAIT.stop().
I can't confirm that. I put empty before wait and still got an error. I did following:
Index: OnEventCorrelation.bpel
===================================================================
--- OnEventCorrelation.bpel (revision 747015)
+++ OnEventCorrelation.bpel (working copy)
@@ -49,9 +49,12 @@
</bpws:scope>
</bpws:onEvent>
</bpws:eventHandlers>
- <bpws:wait>
- <bpws:for><![CDATA['PT4S']]></bpws:for>
- </bpws:wait>
+ <bpws:sequence>
+ <bpws:empty/>
+ <bpws:wait>
+ <bpws:for><![CDATA['PT4S']]></bpws:for>
+ </bpws:wait>
+ </bpws:sequence>
</bpws:scope>
</bpws:scope>
<bpws:receive operation="initiate" partnerLink="client"
Note that bpws:sequence is required here.
> 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.
[jira] Assigned: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert reassigned ODE-511:
---------------------------------
Assignee: Sean Ahn
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671401#action_12671401 ]
Rafal Rusin commented on ODE-511:
---------------------------------
Actually, I'm ready to start fixing this issue. But first, I'd like to make sure it's really a bug, and maybe get some clues on how to resolve 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, 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688301#action_12688301 ]
Rafal Rusin commented on ODE-511:
---------------------------------
I found a workaround for this.
You can set initiate=join in correlation set inside event handler. Then this problem won't happen.
I think we can close this bug.
> 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.
[jira] Issue Comment Edited: (ODE-511) Hibernate DAO + OnEvent +
Correlation error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672386#action_12672386 ]
seanahn edited comment on ODE-511 at 2/10/09 8:16 PM:
-------------------------------------------------------
Rafal,
thanks for helping me understanding the problem.
I added a test case under axis2-war. As you said, the real problem seems to be the channel not being cleaned up when an event handler throws a fault and later when the same correlation is being used for a receive.
r743081 | seanahn | 2009-02-10 12:08:37 -0800 (Tue, 10 Feb 2009) | 1 line
Changed paths:
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/java/org/apache/ode/axis2/BpelActivityTest.java
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/deploy.xml
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test1.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test2.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.bpel
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest2.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest3.soap
ODE-511, Hibernate DAO + OnEvent + Correlation error
Note that the test is commented out in the class file, not to break the build currently. I should yet to work out what the best way is. I prefer using the channel listeners since it's like a pattern that we use everywhere. Let me know if you can help me.
In case you want to use the test case, I cut-and-pasted the procedure to run an axis2-war test using a different database other than the default embedded derby one.
1.Copy settings.rb.example that's checked in to the root directory of the ODE project root to your home directory's .buildr directory. Rename the copied one to settings.rb.
2.In the file, change the line that has REQUIRES:
REQUIRES = [MYSQL]
3. Check the settings for local_hib_mysql. Change the jdbc url to what you want. The database should already exist. Buildr will drop any ODE aware tables and recreate them before running your test.
4. Go to the bottom of the file and comment out all lines except the hib-mysql one. Save the file.
5. Go to the ODE root directory and do clean:
buildr clean
6.Under axis2-war directory, run your test using buildr:
buildr test:MyUnitTest
Thanks
was (Author: seanahn):
Rafal,
thanks for helping me understanding the problem.
I added a test case under axis2-war. As you said, the real problem seems to be the channel not being cleaned up when an event handler throws a fault and later when the same correlation is being used for a receive.
r743081 | seanahn | 2009-02-10 12:08:37 -0800 (Tue, 10 Feb 2009) | 1 line
Changed paths:
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/java/org/apache/ode/axis2/BpelActivityTest.java
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/deploy.xml
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test1.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test2.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.bpel
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest2.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest3.soap
ODE-511, Hibernate DAO + OnEvent + Correlation error
Note that the test is commented out in the class file, not to break the build currently. I should yet to work out what the best way is. I prefer using the channel listeners since it's like a pattern that we use everywhere. Let me know if you can help me.
In case you want to use the test case, I cut-and-pasted the procedure to run an axis2-war test using a different database other than the default embedded derby one.
1.Copy settings.rb.example that's checked in to the root directory of the ODE project root to your home directory's .buildr directory. Rename the copied one to settings.rb.
2.In the file, change the line that has REQUIRES:
REQUIRES = [MYSQL]
3. Check the settings for local_hib_mysql. Change the jdbc url to what you want. The database should already exist. Buildr will drop any ODE aware tables and recreate them before running your test.
4. Go to the bottom of the file and comment out all lines except the hib-derby one. Save the file.
5. Go to the ODE root directory and do clean:
buildr clean
6.Under axis2-war directory, run your test using buildr:
buildr test:MyUnitTest
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, 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.
[jira] Issue Comment Edited: (ODE-511) Hibernate DAO + OnEvent +
Correlation error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710536#action_12710536 ]
Sean Ahn edited comment on ODE-511 at 5/18/09 10:17 PM:
--------------------------------------------------------
Added cleaning up of the route group in the ParentScopeChannelListener.complete(), in EH_EVENT.
When a fault is thrown, the event handler that throws the fault gets terminated through the parent scope channel.
The termination channel is used only when you have multiple event handlers set up. The event handler that throws a fault is always terminated through the parent scope channel and only the rest of handlers will be terminated through the termination channel.
Thanks Rafal and sorry for the late reply.
was (Author: seanahn):
Added cleaning up of the route group in the ParentScopeChannelListener.complete(), in EH_EVENT.
When a fault thrown, the event handler that threw the fault gets terminated through the parent scope channel.
The termination channel is used only when you have multiple event handlers set up. The event handler that throws a fault is always terminated through the parent scope channel and the rest of handlers will be terminated through the termination channel.
Thanks Rafal and sorry for the late reply.
> 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.2
> Environment: axis2, jbi
> Reporter: Rafal Rusin
> Assignee: Sean Ahn
> Fix For: 1.3.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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672386#action_12672386 ]
Sean Ahn commented on ODE-511:
------------------------------
Rafal,
thanks for helping me understanding the problem.
I added a test case under axis2-war. As you said, the real problem seems to be the channel not being cleaned up when an event handler throws a fault and later when the same correlation is being used for a receive.
r743081 | seanahn | 2009-02-10 12:08:37 -0800 (Tue, 10 Feb 2009) | 1 line
Changed paths:
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/java/org/apache/ode/axis2/BpelActivityTest.java
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/deploy.xml
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test1.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test2.properties
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.bpel
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4-process.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/test4.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest2.soap
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch/testRequest3.soap
ODE-511, Hibernate DAO + OnEvent + Correlation error
Note that the test is commented out in the class file, not to break the build currently. I should yet to work out what the best way is. I prefer using the channel listeners since it's like a pattern that we use everywhere. Let me know if you can help me.
In case you want to use the test case, I cut-and-pasted the procedure to run an axis2-war test using a different database other than the default embedded derby one.
1.Copy settings.rb.example that's checked in to the root directory of the ODE project root to your home directory's .buildr directory. Rename the copied one to settings.rb.
2.In the file, change the line that has REQUIRES:
REQUIRES = [MYSQL]
3. Check the settings for local_hib_mysql. Change the jdbc url to what you want. The database should already exist. Buildr will drop any ODE aware tables and recreate them before running your test.
4. Go to the bottom of the file and comment out all lines except the hib-derby one. Save the file.
5. Go to the ODE root directory and do clean:
buildr clean
6.Under axis2-war directory, run your test using buildr:
buildr test:MyUnitTest
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, 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.
[jira] Updated: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-511:
----------------------------
Attachment: event-handler-correlation.diff
OK, I found a solution. I'm attaching a patch.
I added getBpelRuntimeContext().cancel(_pickResponseChannel) toParentScopeChannelListener.completed().
This was just a cleanup issue.
> 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672418#action_12672418 ]
Sean Ahn commented on ODE-511:
------------------------------
Checked in Rafal's test case as it is:
r743120 | seanahn | 2009-02-10 13:57:39 -0800 (Tue, 10 Feb 2009) | 1 line
Changed paths:
M /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/java/org/apache/ode/axis2/BpelActivityTest.java
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/OnEventCorrelation.bpel
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/OnEventCorrelation.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/OnEventCorrelation.xsd
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/OnEventCorrelationArtifacts.wsdl
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/deploy.xml
A /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEvent/testRequest.soap
D /ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestThrowOnEventNoCatch
ODE-511, Hibernate DAO + OnEvent + Correlation error
> 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.
[jira] Updated: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-511:
----------------------------
Attachment: testRequest.soap
OnEventCorrelation-soapui-project.xml
> 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
> 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.
[jira] Issue Comment Edited: (ODE-511) Hibernate DAO + OnEvent +
Correlation error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672487#action_12672487 ]
seanahn edited comment on ODE-511 at 2/10/09 8:17 PM:
-------------------------------------------------------
Rafal,
I noticed that by putting an empty activity just before the <wait>, the process does not throw the error. The channel gets released properly through a EH_EVENT.WAIT.stop().
was (Author: seanahn):
Rafal,
I noticed that by putting an empty activity just before the <wait>, the process does not throw the error. The channel gets released property through a EH_EVENT.WAIT.stop().
> 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.
[jira] Resolved: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn resolved ODE-511.
--------------------------
Resolution: Fixed
Added cleaning up of the route group in the ParentScopeChannelListener.complete(), in EH_EVENT.
When a fault thrown, the event handler that threw the fault gets terminated through the parent scope channel.
The termination channel is used only when you have multiple event handlers set up. The event handler that throws a fault is always terminated through the parent scope channel and the rest of handlers will be terminated through the termination channel.
Thanks Rafal and sorry for the late reply.
> 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.2
> Environment: axis2, jbi
> Reporter: Rafal Rusin
> Assignee: Sean Ahn
> Fix For: 1.3.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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ODE-511) Hibernate DAO + OnEvent + Correlation
error
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672798#action_12672798 ]
Rafal Rusin commented on ODE-511:
---------------------------------
That's very interesting.
I looks like maybe some channels are lost during concurrent processing of BpelRuntimeContext by Jacob. I'll do some more investigations.
> 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.