Calling subsequent message catch events fails about camunda-bpm-platform

[ThorbenLindhauer]

This comment was imported from JIRA and written by user wmpZ2ng

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi Philipp,

Thanks for your Bugreport.

Are you able to provide a failing testcase which reproduces the error?

Cheers
Robert

[ThorbenLindhauer]

This comment was imported from JIRA and written by user OJgkWq1

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi Robert,

you will find a test-project with an Arquillian test here: http://goo.gl/YJH21n
The link will expire soon, please attach the file to this task as I have no rights to do so.

Cheers,
Philipp

[ThorbenLindhauer]

This comment was imported from JIRA and written by user wmpZ2ng

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

great thanks for that

[ThorbenLindhauer]

This comment was imported from JIRA and written by user wmpZ2ng

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

we also fixed the user rights, so that you now should be able to attach and link yourself, sorry for that

[ThorbenLindhauer]

This comment was imported from JIRA and written by user zZ6Eda

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi Phillip,

Are both throwing message evnts executed in the same transaction? In that case the message subscription for the second event "Proben erhalten" is not yet flushed to the database and the database query cannot find it.

This is not easily fixable. If we want to fix it, we need to check the session cache for message subscriptions which also match the query.

It should work if you place a transaction boundary (for example asynchronous continuation) in the "lower" process between the first and second throwing message event.

Regards,
Daniel

[ThorbenLindhauer]

This comment was imported from JIRA and written by user OJgkWq1

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi Daniel,

yes, all is running from within the same thread and I understand the cause and implications for this.
In my production code, the manual tasks were dummies anyway, so I can come out of this situation easily.

I thought I should file this as a bug, since it is a valid model which the engine fails to work with.
Should I really add workarounds to my model to keep the engine happy?

Cheers,
Philipp

[ThorbenLindhauer]

This comment was imported from JIRA and written by user OJgkWq1

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

An updated, simpler screenshot taken from the test

[ThorbenLindhauer]

This comment was imported from JIRA and written by user zZ6Eda

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi Philipp,

of course it is a bug and thank you for reporting it. Users reporting bugs helps us improve our software.

I proposed the solution with the transaction boundary for you as a workaround until the bug is fixed.

Daniel