Bug 777894 (SOA-422) - Document issues with jBPM
Summary: Document issues with jBPM
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-422
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 CR3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2 GA
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-13 12:58 UTC by Jiri Pechanec
Modified: 2014-10-19 23:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-27 21:02:03 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-422 0 None None None Never

Description Jiri Pechanec 2008-02-13 12:58:45 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-02-21 03:10:09
project_key: SOA

Document issues and limitations
- The jBPM can use only one executor
- The jBPM occasionally generates WARN or ERROR messages to log. These are only scary messages and do not affect jBPM functionality

Comment 1 Mark Little 2008-02-13 15:05:04 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]


Comment 2 Joshua Wulf 2008-02-21 08:10:09 UTC
Are there any other open JIRAs against these issues that I can refer to?

Is there a way for the user to distinguish between the spurious WARN and ERROR messages and important ones?

Comment 3 Joshua Wulf 2008-02-27 21:01:46 UTC
This is already release noted with respect to SOA-409 and SOA-410, which detail the messages:

5.6. Multiprocessor machines running jbpm_orchestration2 quickstart using HSQLDB

Various errors and warnings are logged when running the jbpm_orchestration2 quickstart on a machine with multiple CPUs using HSQLDB.

Further Information: http://jira.jboss.com/jira/browse/SOA-409 | http://jira.jboss.com/jira/browse/SOA-417 | http://jira.jboss.com/jira/browse/SOA-415 | http://jira.jboss.com/jira/browse/SOA-410 


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