Open ThorbenLindhauer opened 3 years ago
This comment was imported from JIRA and written by user @tmetzke
Hi azNbxw7,
thanks for bringing this to our attention. This issue is not known so far and we will investigate what might be causing this behavior and why it has come up with 7.15.0 and WildFly 22.
We will come back with feedback as soon as we have further insights.
Best, Tobias
This comment was imported from JIRA and written by user @tmetzke
Hi azNbxw7,
We will not be able to investigate your request any time soon. Investigating this request requires more resources than we can currently expend.
If there are any additional details that you think can speed up the process of investigation, don't hesitate to add them. We will close this ticket in case there is no further activity within the next two weeks.
Thank you for your understanding.
Cheers, Tobias
This comment was imported from JIRA and written by user azNbxw7What 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 Tobias Metzke-Bernstein,
I attached a thread dump of the WildFly while it stucks, because of the (expected) error during the deployment.
Maybe this makes it easier for you.
This comment was imported from JIRA and written by user o0Y77aBWhat 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.
Hello @Tobias Metzke-Bernstein,
I come to this Jira just to know if there have been an update or advance regarding this issue.
Kind regards
María
This comment was imported from JIRA and written by user @tmetzke
Hi o0Y77aB,
we didn't have the resources to further look into this yet. We appreciate any further hints and insight on this.
Best, Tobias
This issue was imported from JIRA:
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.Environment:
Camunda/WildFly was downloaded here:
https://downloads.camunda.cloud/release/camunda-bpm/wildfly/7.15/
Description:
Given is a Singleton with automatic startup (@Startup annotation).
When an exception is thrown in the @PostConstruct handler, the WildFly rolls back the deployment. The @PreDestroy handler is called and the WildFly removes the content.
When adding a Camunda @ProcessApplication, the WildFly stucks in the deployment until a timeout happens. The WildFly is then broken and e.g. cannot be stopped anymore. The process has to be killed and the WildFly must be restarted.
Steps to reproduce / Observed Behavior:
Error case:
Working case:
When using WildFly 20 and Camunda 7.14.0 it works fine!
Expected behavior:
The deployment should fail and be rolled-back when an exception is thrown.
Hints:
I also tested with WildFly 23 and Camunda 7.16 (Alpha). Here the same problem as in WF 22 and Camunda 7.15 happens.
You can find the logs for the working case (without @ProcessApplication) and the problematic one in the attachment of this issue.
I created also a post in the forum:
https://forum.camunda.org/t/wildfly-deployment-cannot-be-rolled-back/30326
Links: