Bug 975878 - Exception in response when starting task via REST
Summary: Exception in response when starting task via REST
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER2
: 6.0.0
Assignee: Maciej Swiderski
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 14:06 UTC by Radovan Synek
Modified: 2014-08-06 20:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kmodule jar (3.18 KB, application/x-java-archive)
2013-06-19 14:06 UTC, Radovan Synek
no flags Details
REST response (19.33 KB, text/plain)
2013-06-19 14:07 UTC, Radovan Synek
no flags Details
server log (105.91 KB, text/x-log)
2013-07-15 15:28 UTC, Radovan Synek
no flags Details

Description Radovan Synek 2013-06-19 14:06:55 UTC
Created attachment 762968 [details]
kmodule jar

Exception raises when starting a user task via REST API saying that transaction is not active. See the attached response.txt for more details. Business-central is in the default configuration - with H2 datasource.


Version-Release number of selected component (if applicable):
DR5

Steps to Reproduce:
1. deploy attached k-module (proj1-1.0.jar) to business-central
2. start a new process by REST: 
POST http://localhost:8080/business-central/rest/runtime/org.jboss.qa:proj1:1.0/process/proj1.src.main.resources.default.testproc/start

3. try to start the first task
POST http://localhost:8080/business-central/rest/task/1/start

4. see the response msg.

Strange thing is that when I repeat the second step - just POSTing it again, it works and the task is properly started.

Comment 1 Radovan Synek 2013-06-19 14:07:26 UTC
Created attachment 762969 [details]
REST response

Comment 2 Mauricio Salatino 2013-07-11 08:14:56 UTC
I've noticed that this BZ is going back and forth between marco and myself. 
Marco can you give me some input about what is the current status of this? 
If this is rest I was assuming that you will take a look on it.

Cheers

Comment 3 Maciej Swiderski 2013-07-13 16:19:53 UTC
just a quick comment as I tried to reproduce it with latest (after beta5) build of kie-wb and could not see any error as described here.
I deployed the kjar attached (worth noticing is that kbase and ksession name must be given as they are defined in kmodule.xml and not marked as default)

On completely new instance of EAP 6.1 first attempt to start the task succeeds and no error is thrown. Considering this issue was opened like a month ago it could already be fixed so I would like to suggest to retest that on beta 5 as it might be resolved.

Comment 4 Mauricio Salatino 2013-07-15 08:37:45 UTC
This issues could be related with the integration with the Dashbuilder. 
I Notice serveral issues saying that the inbox was failing all of them mention the dashbuilder. I guess that we will not be able to reproduce this issues without having dashbuilder deployed in the same AS/EAP.

Comment 5 Radovan Synek 2013-07-15 15:27:07 UTC
Hi Maciej and Mauricio,

I have tried on beta 5 with clean EAP 6.1 and it's true I got response 200 OK, but the behaviour is the same - the first attempt to start a task will fail and I can see that error in the server log (attaching), the second attempt succeeds and the task is in progress.

And second notice - I do not think this is connected with dashbuilder, I can see this error having deployed business-central only. Probably bug 983421 is the same issue - I can reach the error through GUI as well.

Comment 6 Radovan Synek 2013-07-15 15:28:34 UTC
Created attachment 773816 [details]
server log

Comment 7 Radovan Synek 2013-07-16 08:29:09 UTC
Verified that the issue no more exists on actual snapshot - after beta 5 (tested with EAP 6.1 bundle from nexus: /org/kie/kie-wb-distribution-wars/6.0.0-SNAPSHOT/kie-wb-distribution-wars-6.0.0-20130716.005046-463-eap-6.1.war md5 6c3cfd171340a94f17f0a424092f8393)

Will retest on the next production build.

Comment 8 Maciej Swiderski 2013-07-16 08:59:16 UTC
based on the above comment and discussion with Radek I mark this as modified to be retested with new production build and assign to me in case of further work.

Comment 9 Marek Baluch 2013-07-18 06:32:13 UTC
Blocks test execution as this feature is counted into the basic feature set.

Comment 11 Radovan Synek 2013-09-04 11:56:25 UTC
Verified on BPMS 6.0.0.ER2


Note You need to log in before you can comment on or make changes to this bug.