[JBoss JIRA] Created: (JBPM-2827) Run gwt-console on JBoss AS 4.x and 5.x
by Kris Verlaenen (JIRA)
Run gwt-console on JBoss AS 4.x and 5.x
---------------------------------------
Key: JBPM-2827
URL: https://jira.jboss.org/jira/browse/JBPM-2827
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Kris Verlaenen
How can we support deployment on both JBoss AS 4.x and 5.x? Because for 4.x I need to exclude a lot of jars because they otherwise conflict with the ones by default on the server classpath (hibernate, jta, jpa, javassist). Having an issue with javassist in this case as well, as the version you are bundling in the gwt-console-server-drools.war conflicts with the javassist + hibernate on server classpath. Is there any chance this could be marked as provided? These jars don't seem to be there in AS 5.x by default, so in that case the war should contain all jars?
--
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
13 years, 11 months
[JBoss JIRA] Created: (JBPM-2965) jBPM4 Alpha start.demo ant task fails
by eric schabell (JIRA)
jBPM4 Alpha start.demo ant task fails
--------------------------------------
Key: JBPM-2965
URL: https://jira.jboss.org/browse/JBPM-2965
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 5.0 Alpha
Environment: intel x08_64, fedora 13, sun jdk 1.6_16
Reporter: eric schabell
Fix For: jBPM 5.0 Alpha
After running ant install.demo (which takes fooooooreeeeevvvvveerrrrrrr !) I try to run a simple 'ant start.demo' and get first a pop-up from eclipse:
JVM terminated. Exit code=13
/usr/bin/java
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-os linux
-ws gtk
-arch x86
-showsplash
-launcher /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse/eclipse
-name Eclipse
--launcher.library /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.1.R36x_v20100810/eclipse_1309.so
-startup /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-exitdata 8c0005
-data .//workspace
-plugincustomization ./eclipse.preferences.ini
-vm /usr/bin/java
-vmargs
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
Then at the start.humantask I get:
start.human.task:
[java] Failed to instantiate SLF4J LoggerFactory
[java] Reported exception:
[java] java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
[java] at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
[java] at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
[java] at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
[java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
[java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
[java] at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:151)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:107)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
[java] at org.jbpm.DemoTaskService.main(Unknown Source)
[java] Exception in thread "main" java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder
[java] at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
[java] at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
[java] at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
[java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
[java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
[java] at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:151)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:107)
[java] at java.lang.Class.initializeClass(libgcj.so.10)
[java] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
[java] at org.jbpm.DemoTaskService.main(Unknown Source)
[java] Java Result: 1
start.demo:
BUILD SUCCESSFUL
Total time: 30 seconds
This is all done with the latest build (yesterday, 20 Oct 2010) installer from hudson.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBPM-2985) Make jBPM 4 build compatible with Maven 3
by Alejandro Guizar (JIRA)
Make jBPM 4 build compatible with Maven 3
-----------------------------------------
Key: JBPM-2985
URL: https://issues.jboss.org/browse/JBPM-2985
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
The current continuous integration scripts rely on a profiles.xml file, incompatible with Maven 3. There are some other loose ends like the absence of explicit plugin version declarations. All of these tidbits need to be ironed out to leverage Maven 3 to its fullest.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBPM-2986) Reorganize jBPM 4 modules and continuous integration
by Alejandro Guizar (JIRA)
Reorganize jBPM 4 modules and continuous integration
----------------------------------------------------
Key: JBPM-2986
URL: https://issues.jboss.org/browse/JBPM-2986
Project: jBPM
Issue Type: Quality Risk
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Priority: Minor
Fix For: jBPM 3.2.10
The current layout places the project modules in a "modules" directory which is not standard practice and prevents certain desirable functionality such as m2eclipse "hide folders of physically nested modules" check box.
On a separate topic, the "hudson" directory and its subdirectories could use shorter, better names.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBPM-2919) Memory leak because of org.jbpm.JbpmConfiguration.jbpmConfigurationStacks not released
by Mauro Molinari (JIRA)
Memory leak because of org.jbpm.JbpmConfiguration.jbpmConfigurationStacks not released
--------------------------------------------------------------------------------------
Key: JBPM-2919
URL: https://jira.jboss.org/browse/JBPM-2919
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.7
Reporter: Mauro Molinari
When class org.jbpm.JbpmConfiguration gets initialized by the class loader, a static variable named jbpmConfigurationStacks gets initialized. This is a ThreadLocal, and so it gets registered in the java.lang.Thread.threadLocals map of the calling thread.
However, if jBPM is embedded into a web application, this means that that variable is registered on one of the HTTP threads of the application server. When the web application shuts down, the mapping is not removed, because there's no code in jBPM that takes care of this task.
Fortunately, the value of this thread local is of type ArrayList, which is a class which is surely loaded by the root class loader, so no references to the webapp class loader are retained. However, Tomcat 6.0.28 still says the following:
SEVERE: The web application [/webappname] created a ThreadLocal with key of type [org.jbpm.JbpmConfiguration.StackThreadLocal] (value [org.jbpm.JbpmConfiguration$StackThreadLocal@26fe26cc]) and a value of type [java.util.ArrayList] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
A fix could be to do a remove() on that ThreadLocal when a call to org.jbpm.JbpmConfiguration.popJbpmConfiguration() causes the list to become empty.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBPM-2133) Error handling in CommandServiceBean.execute
by Volker Börchers (JIRA)
Error handling in CommandServiceBean.execute
--------------------------------------------
Key: JBPM-2133
URL: https://jira.jboss.org/jira/browse/JBPM-2133
Project: JBoss jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.6.SP1
Environment: irrelevant
Reporter: Volker Börchers
Priority: Minor
regards CommndServiceBean.execute(Command command):
public Object execute(Command command)
{
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try
{
log.debug("executing " + command);
return command.execute(jbpmContext);
}
catch (RuntimeException e)
{
sessionContext.setRollbackOnly();
throw e;
}
catch (Exception e)
{
sessionContext.setRollbackOnly();
throw new JbpmException("failed to execute " + command, e);
}
finally
{
jbpmContext.close();
}
}
If an exception occurres in Command.excute() it's important that this exception is propagated to the client to allow for proper exception handling to differentiate e.g. between a concurrency issue ("job is locked by...") and a database error.
These exceptions are not propagated to the client if the jbpmContext.close() in the finally block throws an exceptions. This might very well happen since it performs non-trivial operations, e.g. access the database. (Actually it it seems to me as if the failure of jbpmContext.close() always happen, maybe since after the setRollbackOnly() no new connections are possible.)
The following change will fix the problem:
public Object execute(Command command)
{
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
boolean exceptionThrown = false;
try
{
log.debug("executing " + command);
return command.execute(jbpmContext);
}
catch (RuntimeException e)
{
sessionContext.setRollbackOnly();
exceptionThrown = true;
throw e;
}
catch (Exception e)
{
sessionContext.setRollbackOnly();
exceptionThrown = true;
throw new JbpmException("failed to execute " + command, e);
}
finally
{
try
{
jbpmContext.close();
}
catch (Exception e2) {
if (exceptionThrown)
{
// JIRA XX: do not hide thrown exception
log.error("exception on context close", e2);
}
else
{
throw e2;
}
}
}
}
--
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
14 years
[JBoss JIRA] Created: (JBPM-2142) No save of processInstance in TaskInstanceEndCommand
by Joram Barrez (JIRA)
No save of processInstance in TaskInstanceEndCommand
-----------------------------------------------------
Key: JBPM-2142
URL: https://jira.jboss.org/jira/browse/JBPM-2142
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.3.1 GA, jBPM 3.2.7 GA
Reporter: Joram Barrez
Priority: Minor
The TaskInstanceEndCommand does not save the processInstance.
This means (among others) that the process logs will not be persisted to the database, since they are only stored upon a call to the save() method on the jBPM Context.
The solution is simple, add
jbpmContext.save(taskInstance.getProcessInstance());
to the command.
I haven't checked the other commands, but the bug can occur in other commands.
--
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
14 years
[JBoss JIRA] Created: (JBPM-2031) Some bidirectional associations do not use inverse="true"
by Tomasz Wysocki (JIRA)
Some bidirectional associations do not use inverse="true"
---------------------------------------------------------
Key: JBPM-2031
URL: https://jira.jboss.org/jira/browse/JBPM-2031
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.3.1 GA
Environment: Tested with MySQL with query log enabled in JUnit.
Reporter: Tomasz Wysocki
Priority: Minor
Currently couple of bidirectional associations do not use inverse="true" on one-to-many side (collection)
The examples are
- ProcessInstance.instances
- CompositeLog.children
I'm sure there are more of them.
Lack of inverse="true" results in additional "UPDATE" statement being issued by hibernate to create a relationship from a one-to-many side.
This is not necessary when java code is updating both ends of an association.
Some use-cases where lots of new processes are being created would see a performance improvement.
CompositeLog logging overhead will decrease (only INSERT will be issued - no UPDATE)
Please consider reviewing all of your bidirectional associations with respect to this optimization.
--
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
14 years