Bug 813758 - NullPointerException when create simple task in jbpm console
Summary: NullPointerException when create simple task in jbpm console
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM Console
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-18 11:29 UTC by Ryan Zhang
Modified: 2022-01-05 05:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
screenshot.png (309.23 KB, image/png)
2012-04-18 11:31 UTC, Ryan Zhang
no flags Details
server.log (171.17 KB, text/x-log)
2012-04-18 11:32 UTC, Ryan Zhang
no flags Details

Description Ryan Zhang 2012-04-18 11:29:15 UTC
Description of problem:
When create task for sample process Evaluation, NPE was threw.

Version-Release number of selected component (if applicable):
ER6 development version (not entering QE test circle yet)
Download url: http://jawa05.englab.brq.redhat.com/miscellaneous/brms-5.3-ER6/brms-p-5.3.0.BRMS-ER6-standalone-20120418-14-39.zip

How reproducible:


Steps to Reproduce:
1. Install jbpm_example_repository.xml in jboss brms console and compile the default package in the console
2. Open jbpm console and check process overview, "Evaluation" process should be present
3. Click start to start a instance and fill in "Administrator" as user name. The error can be seen.
Error snapshot and server.log are attached.
  
Actual results:
NPE exception

Expected results:
Process instance should be created

Additional info:

Comment 1 Ryan Zhang 2012-04-18 11:31:46 UTC
Created attachment 578322 [details]
screenshot.png

Comment 2 Ryan Zhang 2012-04-18 11:32:52 UTC
Created attachment 578323 [details]
server.log

Comment 3 Ryan Zhang 2012-04-18 11:36:17 UTC
This is block issue for BRMS 5.3 ER6 release.

Comment 4 Marco Rietveld 2012-04-19 02:59:33 UTC
The reason that this issue has never shown up in the tests is that there was a typo in the JtaTransactionManager in drools-persistence-jpa which mean that the TransactionSynchronizationRegistry was never registered when using Bitronix (which is used during tests). 

Once I corrected that, this issue showed up in all of the tests in jbpm-gwt/jbpm-gwt-core.

Comment 5 Ryan Zhang 2012-04-23 07:36:46 UTC
Update status to ON_QA. Please verify them against ER6.


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