[JBoss JIRA] Created: (JBPM-1764) JobExecutorDbTest does not work on Sybase
by Alejandro Guizar (JIRA)
JobExecutorDbTest does not work on Sybase
-----------------------------------------
Key: JBPM-1764
URL: https://jira.jboss.org/jira/browse/JBPM-1764
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.3.0 CR1
Environment: Linux
Sybase ASE 12.5
jTDS 1.2.2
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.3.0 GA
While running org.jbpm.job.executor.JobExecutorDbTest, the following error prevents job execution threads from completing jobs within the predefined threshold of 1 minute.
2008-09-29 19:03:41,078 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1205, SQLState: S1000
2008-09-29 19:03:41,078 ERROR [org.hibernate.util.JDBCExceptionReporter] Your server command (family id #0, process id #77) encountered a deadlock situation. Please re-run your command.
The test will be excluded until this issue is resolved. The hibernate.order_updates property might help solve the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBPM-1814) make jbpm installation in jboss optional
by Tom Baeyens (JIRA)
make jbpm installation in jboss optional
----------------------------------------
Key: JBPM-1814
URL: https://jira.jboss.org/jira/browse/JBPM-1814
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Installer
Affects Versions: jBPM 3.3.0 GA
Reporter: Tom Baeyens
Fix For: jBPM 3.3.1 GA
currently, the jbpm installation into jboss is mandatory. you have to point the installer to an empty directory if you don't want to install it in jboss.
installation of jbpm into jboss should be optional.
When fixing this, also make sure that the docs are updated: currently there is a section like this in chapter "Getting Started":
"
If you don't want to install jBPM in JBoss, then you'll have to point the installer to an empty temporary directory where it can put those files anyway. This limitation will be removed in the next version.
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBPM-1811) JmsMessageTest fails intermitently on HSQLDB
by Thomas Diesler (JIRA)
JmsMessageTest fails intermitently on HSQLDB
--------------------------------------------
Key: JBPM-1811
URL: https://jira.jboss.org/jira/browse/JBPM-1811
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Fix For: jBPM 3.3.1 GA
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at org.jbpm.msg.jms.JmsMessageTest.testAsyncFork(JmsMessageTest.java:193)
EventCallback.waitForEvent(Event.EVENTTYPE_PROCESS_END);
assertTrue("Process has ended", hasProcessEnded(processId));
It seems that hasProcessEnded() can return false although the exent had already been sent.
This sould be a race condition
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBPM-1880) Release API 1.0.0.Alpha1
by Thomas Diesler (JIRA)
Release API 1.0.0.Alpha1
------------------------
Key: JBPM-1880
URL: https://jira.jboss.org/jira/browse/JBPM-1880
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: API
Reporter: Thomas Diesler
Fix For: API 1.0.0 Alpha1
Inclusion of the following API concepts:
* Configuration
* ProcessEngine
* ProcessDefinitionService
* ProcessBuilder
* ProcessInstance or Process
* Execution or Token
* StartEvent with no Trigger
* EndEvent with no Result
* WaitState
* Exclusive Gateway
* Sequence Flow
Inclusion of the following process constructs
* processe (<process/>)
* start event (<start/>)
* state == wait tasks (<state/>)
* exclusive gateway (<exclusive/>)
* sequence flow (<flow/>
<process>
<start name='A'>
<flow to='B'/>
</start>
<exclusive name='B' [expr='outcome']>
<flow to='C' [expr='expr1'] [name='accept']/>
<flow to='E' [expr='expr2'] [name='reject']/>
<flow to='D' [default='true'] [name='unknown']/>
</exclusive>
<state name='C'>
<flow to='E'/>
</state>
<exclusive name='D'>
<handler class='foo.bar'>
<config>
any
</config>
</handler>
</exclusive>
<end name='E'/>
</process>
The GPD will support the BPMN notation for these concepts
and they will be documented as such in the documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months