Bug 1180490
| Summary: | EJB: synchronization between EJB and REST in BC is unreliable. | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marek Baluch <mbaluch> |
| Component: | Documentation | Assignee: | brms-docs <brms-docs> |
| Status: | CLOSED EOL | QA Contact: | Marek Baluch <mbaluch> |
| Severity: | high | Docs Contact: | Dawn Eisner <deisner> |
| Priority: | high | ||
| Version: | 6.1.0 | CC: | brms-docs, kverlaen, mbaluch |
| Target Milestone: | CR2 | ||
| Target Release: | One-off release | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 19:43:55 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: | |||
| Deadline: | 2015-05-07 | ||
Marek, this is most likely because of delay that might get in the way for deployment synchronization. It is a background job that runs every 3 seconds and can be altered by setting system property org.jbpm.deploy.sync.int to a valid integer value that will represent number of seconds how often it should attempt to synchronize. Can you either set additional delay after it was successfully deployed to workbench or modify the interval how often it synchronizes? Thanks Maciej - I made the updates and tests are running - Will let you know asap. Any results of these tests? My apologies - I was on PTO and a training right after that. The test results are fine. Changing the sync. interval helped to solve the issue. Vikram, could we add a warning/info message to the EJB guide that the synchronization service must first do it's job otherwise EJB will not see changes done via REST? (In reply to Marek Baluch from comment #5) > Vikram, could we add a warning/info message to the EJB guide that the > synchronization service must first do it's job otherwise EJB will not see > changes done via REST? Hi Marek, I have added a note at the bottom of this section [1]. Moving this to ON_QA. [1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Development_Guide/index.html#EJB_Interface_Methods Verified using links in comment #7. |
*** Description of problem If I use "maven install" operation in REST to install a project then this project may not be seen by EJB. *** Steps to reproduce I'm doing the following: 1/ A request to "${serverUrl}/rest/repositories/${repo}/projects/${project}/maven/install" is sent. 2/ Wait until the state of the deployment is equal to "DEPLOYED". This is done using REST and "${serverUrl}/rest/deployment/${deploymentId}" 3/ Start of a process belonging to the deployment with ${deploymentId} is performed using remote EJB. *** Additional info Sample output: [2015-01-09 10:47:27,325] INFO - Waiting for deployment 'org.jboss:integration:2.0.0-SNAPSHOT' to be in state 'DEPLOYED' ... [2015-01-09 10:47:28,062] INFO - Response entity: [<?xml version="1.0" encoding="UTF-8" standalone="yes"?><deployment-unit><groupId>org.jboss</groupId><artifactId>integration</artifactId><version>2.0.0-SNAPSHOT</version><kbaseName></kbaseName><ksessionName></ksessionName><strategy>SINGLETON</strategy><status>DEPLOYED</status></deployment-unit>] [2015-01-09 10:47:29,315] INFO - OK [2015-01-09 10:47:30,182] INFO - Cleaning up ... [2015-01-09 10:47:30,182] INFO - Found '0' active instances. Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.912 sec <<< FAILURE! - in org.jboss.qa.bpms.jbpm.integration.ejb.task.ETaskOperationTest testCompleteWorkItem(org.jboss.qa.bpms.jbpm.integration.ejb.task.ETaskOperationTest) Time elapsed: 2.911 sec <<< ERROR! javax.ejb.EJBException: org.jbpm.services.api.DeploymentNotFoundException: No deployments available for org.jboss:integration:2.0.0-SNAPSHOT at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:189) ...