-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
Environment (Required on creation):
Camunda Platfrom 7.16, Websphere 8 or 9 / Weblogic 12R2, shared engine scenario
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
When deploying a CDI-based WAR the aforementioned application servers with a process containing a Timer Start Event with an expression-based definition that contains a bean defined in the WAR, the deployment of the WAR fails with the attached exception.
Steps to reproduce (Required on creation):
- Start the application server
- Deploy a WAR comparable to this integration test [1]
Observed Behavior (Required on creation):
- On Websphere, an exception is thrown:
CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getName". Exception data: javax.ejb.IllegalLoopbackException: Cannot call a method on a singleton session bean while constructing the bean instance : test#test.war#DefaultEjbProcessApplication
- On Weblogic, the test times out
Expected behavior (Required on creation):
The deployment succeeds.
Root Cause (Required on prioritization):
Solution Ideas (Optional):
Hints (Optional):
This is the controller panel for Smart Panels app
[CAM-13727] On Websphere and Weblogic, CDI-based WAR cannot be deployed when Timer Start Event resolves bean
Description |
Original:
h4. Environment (Required on creation):
h4. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): h4. Steps to reproduce (Required on creation): h4. Observed Behavior (Required on creation): h4. Expected behavior (Required on creation): h4. Root Cause (Required on prioritization): h4. Solution Ideas (Optional): h4. Hints (Optional): |
New:
h4. Environment (Required on creation):
Camunda Platfrom 7.16, Websphere 8 or 9, shared engine scenario h4. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deploying a CDI-based WAR to Tomcat with a process containing a Timer Start Event with an expression-based definition that contains a bean defined in the WAR, the deployment of the WAR fails with the attached exception. h4. Steps to reproduce (Required on creation): * Start Websphere * Deploy a WAR comparable to this integration test [1] h4. Observed Behavior (Required on creation): An exception is thrown: {code} CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getName". Exception data: javax.ejb.IllegalLoopbackException: Cannot call a method on a singleton session bean while constructing the bean instance : test#test.war#DefaultEjbProcessApplication {code} h4. Expected behavior (Required on creation): The deployment succeeds. h4. Root Cause (Required on prioritization): h4. Solution Ideas (Optional): h4. Hints (Optional): [1] https://github.com/camunda/camunda-bpm-platform/blob/master/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanResolutionOnDeploymentTest.java |
Mentioned Roles |
Mentioned Groups |
Attachment | New: was-error.txt [ 44375 ] |
Description |
Original:
h4. Environment (Required on creation):
Camunda Platfrom 7.16, Websphere 8 or 9, shared engine scenario h4. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deploying a CDI-based WAR to Tomcat with a process containing a Timer Start Event with an expression-based definition that contains a bean defined in the WAR, the deployment of the WAR fails with the attached exception. h4. Steps to reproduce (Required on creation): * Start Websphere * Deploy a WAR comparable to this integration test [1] h4. Observed Behavior (Required on creation): An exception is thrown: {code} CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getName". Exception data: javax.ejb.IllegalLoopbackException: Cannot call a method on a singleton session bean while constructing the bean instance : test#test.war#DefaultEjbProcessApplication {code} h4. Expected behavior (Required on creation): The deployment succeeds. h4. Root Cause (Required on prioritization): h4. Solution Ideas (Optional): h4. Hints (Optional): [1] https://github.com/camunda/camunda-bpm-platform/blob/master/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanResolutionOnDeploymentTest.java |
New:
h4. Environment (Required on creation):
Camunda Platfrom 7.16, Websphere 8 or 9 / Weblogic 12R2, shared engine scenario h4. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When deploying a CDI-based WAR the aforementioned application servers with a process containing a Timer Start Event with an expression-based definition that contains a bean defined in the WAR, the deployment of the WAR fails with the attached exception. h4. Steps to reproduce (Required on creation): * Start the application server * Deploy a WAR comparable to this integration test [1] h4. Observed Behavior (Required on creation): * On Websphere, an exception is thrown: {code:java} CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getName". Exception data: javax.ejb.IllegalLoopbackException: Cannot call a method on a singleton session bean while constructing the bean instance : test#test.war#DefaultEjbProcessApplication {code} * On Weblogic, the test times out h4. Expected behavior (Required on creation): The deployment succeeds. h4. Root Cause (Required on prioritization): h4. Solution Ideas (Optional): h4. Hints (Optional): [1] [https://github.com/camunda/camunda-bpm-platform/blob/master/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanResolutionOnDeploymentTest.java] |
Mentioned Roles |
Mentioned Groups |
Summary | Original: On Websphere, IllegalLoopbackException on deployment is thrown | New: On Websphere and Weblogic, CDI-based WAR cannot be deployed when Timer Start Event resolves bean |