Bug 988770 - Exception when creating/starting new task in task list
Summary: Exception when creating/starting new task in task list
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.0.0
Assignee: Mauricio Salatino
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 10:29 UTC by Jan Hrcek
Modified: 2013-07-26 11:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-26 11:19:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server log with errors - deployed with H2 database (132.29 KB, text/x-log)
2013-07-26 10:33 UTC, Jan Hrcek
no flags Details
server log with errors - deployed with MySQL database (56.91 KB, text/x-log)
2013-07-26 10:33 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2013-07-26 10:29:58 UTC
Description of problem:

The problem described here (https://bugzilla.redhat.com/show_bug.cgi?id=983421#c8   ->  item 2) is still present in kie-workbench CR1 build.
--> When new task is created in kie-wb Task List, exception is thrown. (see stacktrace in attachments)


Version-Release number of selected component (if applicable):
kie-wb CR1 deployed on EAP 6.1

(downloaded from nexus  repository.jboss.org : /org/kie/kie-wb-distribution-wars/6.0.0.CR1/kie-wb-distribution-wars-6.0.0.CR1-eap-6_1.war)


How reproducible:
Reproduced problem with both default H2 in-memory datasource and with local MySQL 5.5 datasource.
The issue is reproduced in 100% of cases of automated selenium test runs - however the problem is not in the test automation (using simple selenium click() method of WebElement class - it works in hundreds of other tests in our test suite without problems).


Steps to Reproduce:
1. login to kie workbench with admin user (roles kie-user + admin)
2. navigate to Tasks > Tasks list
3. click "New Task", fill in task name and click "Create"

Actual results:
The "Create" button becomes disabled, but the "New task" dialog doesn't disappear and remains present. There are exception in app server log.

Expected results:
Task is created and started without exception.

Additional info:
Previously the problem manifested itself only after the task was started. Since then modifications were done to the code, that change the task state to INPROGRESS immediately after it is created. The starting of the task seems to be what is causing the exception (see *** Message delivery failure *** in the attached stack traces).

I cannot tell the cause for sure, but from analyzing stack trace it seems I suspect strongly, that there occurs some duplicate request from the UI side (see this highlights from the stacktrace --> All caused by attempts to start task)

1) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry 'admin' for key 'PRIMARY'
2) Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff7f000001:-8cfde30:51f233c7:8a status: ActionStatus.ABORT_ONLY >
3) Unique index or primary key violation: "PRIMARY_KEY_C6 ON PUBLIC.ORGANIZATIONALENTITY(ID)"; SQL statement: insert into OrganizationalEntity (DTYPE, id) values ('UserImpl', ?)

I'm almost sure you won't be able to reproduce the problem manually. However I'd still like to ask you to inspect the sources involved for a bug and try to investigate the root cause of this issue, as it blocks test automation - without the ability to start task from selenium tests, the main body of functionality is not testable.

Comment 1 Jan Hrcek 2013-07-26 10:33:13 UTC
Created attachment 778734 [details]
server log with errors - deployed with H2 database

Comment 2 Jan Hrcek 2013-07-26 10:33:50 UTC
Created attachment 778735 [details]
server log with errors - deployed with MySQL database

Comment 3 Jan Hrcek 2013-07-26 11:19:42 UTC
Got info from engineering: the problem is caused by using 'admin' as a user to login to EAP. Reason: The username admin is clashing with the business administrator, which is like a reserved word in the application. A separate bugzilla will be opened for this issue. This one will be closed, as the problem is no longer there, when different username is used.


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