Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1075181

Summary: Unable to create deployment to Business-Central cluster via REST
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: Maciej Swiderski <mswiders>
Status: CLOSED NOTABUG QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.1CC: kverlaen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-13 13:22:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server log - node one
none
server log - node two none

Description Radovan Synek 2014-03-11 16:28:13 UTC 
Created attachment 873206 [details]
server log - node one

Having a Business-Central cluster with two EAP nodes in a domain, sometimes - but _NOT_ every time - the deployment via REST fails. Server log of the first node (which is the one communicating via REST with client) contains following exception:
ERROR [org.kie.services.remote.rest.async.AsyncDeploymentJobExecutor] (pool-22-thread-1) Unable to deploy [org.jboss.qa.bpms:clustering:1.0.0.Final]: java.lang.IllegalStateException: Unable to find transaction: java:comp/UserTransaction

See the attached server log for complete stacktrace.

How reproducible:
This issue does not raise every time

Steps to Reproduce:
1. configure a cluster with 2 EAP nodes
2. create an org. unit, clone a repository containing some project
3. POST http://localhost:8080/business-central/rest/deployment/${DEPLOYMENT_ID}/deploy
Comment 1 Radovan Synek 2014-03-11 16:30:09 UTC 
Created attachment 873207 [details]
server log - node two
Comment 2 Radovan Synek 2014-03-13 13:22:11 UTC 
The issue does not appear any more (tried several times) after another stabilization of test suite and cannot be reproduced locally. Probably just some problem in test environment.
If the issue appear again, I will re-open this BZ.