[JBoss JIRA] Created: (JBPM-2093) Stabilize EjbSchedulerTest.testScheduleFork under MySQL
by Alejandro Guizar (JIRA)
Stabilize EjbSchedulerTest.testScheduleFork under MySQL
-------------------------------------------------------
Key: JBPM-2093
URL: https://jira.jboss.org/jira/browse/JBPM-2093
Project: JBoss jBPM
Issue Type: Quality Risk
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.6 GA , jBPM-3.2.5.SP3
Environment: JBoss 5.0.0.GA
MySQL 5.0.67
Sun JDK 1.5.0.16
Reporter: Alejandro Guizar
testScheduleFork fails with:
org.jbpm.JbpmException: event 'process-end' did not occur within 300000 ms
at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:125)
at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:106)
at org.jbpm.enterprise.ejbtimer.EjbSchedulerTest.testScheduleFork(EjbSchedulerTest.java:265)
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2119) Work around the need for an extra column to persist field Join.parentLockMode
by Alejandro Guizar (JIRA)
Work around the need for an extra column to persist field Join.parentLockMode
-----------------------------------------------------------------------------
Key: JBPM-2119
URL: https://jira.jboss.org/jira/browse/JBPM-2119
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM-3.2.5.SP4
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Priority: Blocker
Fix For: jBPM 3.2.7 GA
In JBPM-1755, a new column PARENTLOCKMODE_ was added to table JBPM_NODE for persisting field Join.parentLockMode. Turns out the schema change is a barrier for our customers to upgrade to newer versions.
The proposed solution is to provide two different mappings for the Join class, with and without the column. The provided Hibernate configuration will include the mapping without the column by default. Interested parties may inclde the version with the column in their own Hibernate configuration.
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2202) jBPM might be re-loading classes when not strictly necessary
by Alejandro Guizar (JIRA)
jBPM might be re-loading classes when not strictly necessary
------------------------------------------------------------
Key: JBPM-2202
URL: https://jira.jboss.org/jira/browse/JBPM-2202
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.5.SP5
Environment: 39 unique processes
243 entries in jbpm.jbpm_processdefinition
ach process has ~6 versions deployed, of which only the most recent version is in daily usage
ehcache is configured as the hibernate cache.
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
jBPM creates new Java classes out of binary process definition data stored in the database. This is needed for different versions of the process. It appears a special classloader is used for this. In SUN hotspot-class JVMs, parts of these load classes would be stored in perm gen rather than heap, which is not typically collected until absolutely necessary, potentially causing high cpu gc thrashing issues. If this was normal objects we were dealing with, the parallel scavenges or CMS fulls should collect them without problems. It appears this is not the case.
I believe the issue is that jBPM might be re-loading classes when not strictly necessary.
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2360) fix deletion of deployments in cluster
by Tom Baeyens (JIRA)
fix deletion of deployments in cluster
--------------------------------------
Key: JBPM-2360
URL: https://jira.jboss.org/jira/browse/JBPM-2360
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Fix For: jBPM 4.0
when a deployment gets deleted, the request arrives in one node of the cluster. that node can remove the deployment and its process definition from the repository cache immediately.
but how will the other nodes in the cluster know ?
some check with db access has to be added every time an object (process definition) is fetched from the repository cache. alternatively this can also be enforced at those locations where suspended must be checked: in the commands for starting a new execution, signalling and so on.
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2230) jBPM failed the build with Maven 2.1.0 though there is no problem with Maven 2.0.9 or 2.0.10
by ryan zhang (JIRA)
jBPM failed the build with Maven 2.1.0 though there is no problem with Maven 2.0.9 or 2.0.10
--------------------------------------------------------------------------------------------
Key: JBPM-2230
URL: https://jira.jboss.org/jira/browse/JBPM-2230
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 3.2.5.SP5
Environment: mvn version
Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800)
Java version: 1.5.0_18
Java home: /home/ryan/software/jdk1.5.0_18/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.27.5-117.fc10.i686" arch: "i386" Family: "unix"
Reporter: ryan zhang
Run "mvn -Pdistro clean install" at jBPM check out folder.(version 3.2.5), the build will failed.
Error log attached and some part of information followed either:
[INFO] Building JBoss jBPM3 - Distribution
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /home/ryan/workspace/soa-work/jbpm/checkout/modules/distribution/target
[INFO] [assembly:directory-single {execution: make-assembly}]
[INFO] Reading assembly descriptor: scripts/assembly-deploy-artifacts.xml
[INFO] Processing DependencySet (output=lib)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[INFO] Processing DependencySet (output=lib)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[INFO] Processing DependencySet (output=lib)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[INFO] Processing DependencySet (output=resources/jbpm-jpdl-config)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[INFO] Processing DependencySet (output=resources/jbpm-enterprise-config)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[INFO] Processing DependencySet (output=src)
[WARNING] Cannot include project artifact: org.jbpm.jbpm3:jbpm-distribution:pom:3.2.5.SP5; it doesn't have an associated file or directory.
[WARNING] The following patterns were never triggered in this artifact inclusion filter:
o 'org.jboss.jbpm:*:jar:sources'
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] : org.apache.maven.plugin.assembly.model.Assembly@11aed03
Assembly is incorrectly configured: deploy-artifacts
Assembly: deploy-artifacts is not configured correctly: One or more filters had unmatched criteria. Check debug log for more information.
--
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
15 years, 5 months