Bug 1007895 - Inilializing process instance provoke an error in the log
Summary: Inilializing process instance provoke an error in the log
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-13 14:09 UTC by Michael
Modified: 2013-09-25 11:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-25 11:16:43 UTC
Type: Bug
Embargoed:
kverlaen: needinfo+


Attachments (Terms of Use)

Description Michael 2013-09-13 14:09:10 UTC
Description of problem:
When initializing a process instance in JBoss AS 7 [kie-wb-6.0.0-SNAPSHOT-as-7.war deployed] this error is thrown:

https://gist.github.com/mbiarnes/6551171



Version-Release number of selected component (if applicable):
kie-wb-6.0.0-SNAPSHOT-as-7.war in JBoss AS 7

How reproducible:


Steps to Reproduce:
1. Create a project, process, datamodel and forms
2. Initialize a process instance


Actual results:
Error message appears in the log:
https://gist.github.com/mbiarnes/6551171

Comment 2 Kris Verlaenen 2013-09-16 13:41:36 UTC
Michael,

Do you have any more information about this issue?  As it doesn't just happen for every process you try to execute, so having issues reproducing this one.  Is this on as 7.1.1 only, or also on EAP 6.1?

Comment 3 Michael 2013-09-16 14:11:57 UTC
Kris,
No I don't have more information about this.
This only occurred when initiating an instance of a process (not one of the existing ones,  a new one, created to do smoke tests).
As I repeated the smoke tests in EAP 6.1 and AS 7.1.1 I assume that this happens only to AS 7.1.1 since this is not reported for EAP 6.1

Comment 4 Kris Verlaenen 2013-09-24 13:40:56 UTC
Unable to reproduce this for now


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