September 2008 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: PostgeSQL runs take too long

by thomas.diesler＠jboss.com

There are still some dropSchema() calls scattered around in test cases. Removing them should speed up things as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176005#4176005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176005

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: PostgeSQL runs take too long

by thomas.diesler＠jboss.com

Did some refactoring and removed the dropSchema() call in tearDown(); [tdiesler@tdvaio core]$ mvn -o -Ddatabase=postgresql test ... Tests run: 982, Failures: 0, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9 minutes 37 seconds [INFO] Finished at: Fri Sep 12 01:10:25 CEST 2008 [INFO] Final Memory: 11M/42M [INFO] ------------------------------------------------------------------------ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176004#4176004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176004

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise

by kukeltje

Great, thanks Thomas. May I conclude that jBPM is now (un)officially not supported anymore on JDK 1.4 with the upcomming 3.3 release? Might be something specifically for the releasenotes View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175931#4175931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175931

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise

by alex.guizar＠jboss.com

I like the EJB3 profile proposal. Whether it should be in lieu of EJB2 is a question to be asked to the community. For now however, we should focus on getting 3.3.0.CR out :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175928#4175928 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175928

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise

by alex.guizar＠jboss.com

anonymous wrote : If I understand you correctly, you associated the DS for the TimerEntityBean with the JbpmDS to share the same DS with the rest of the engine and not have multiple 1PC resources enlisted. The DS for the TimerEntityBean must be the JbpmDS, otherwise the whole thing does not work :-) In JBPM-1708 I meant the DS for the EJB timer service itself, tough. When the EntitySchedulerService creates an EJB timer, the data source specified in ejb2-timer-service.xml (JBoss 5) or ejb-deployer.xml (JBoss 4) enters the scene. <mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database"> |  | <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=JbpmDS</depends> |  | <attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</attribute> |  | <attribute name="TimersTable">EJB_TIMER</attribute> | <depends>jboss.jdbc:datasource=JbpmDS,service=metadata</depends> | </mbean> If set to a data source other than JbpmDS, multiple 1PC problems happen. Another option is to enable multiple last resource enlistment in the transaction service. But that might result in inconsistent rollbacks, which would be very bad when coupled with optimistic locking exceptions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175926#4175926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175926

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: PostgeSQL runs take too long

by thomas.diesler＠jboss.com

I'd say we take the opposite approach and clear those lines and reinsert where actually needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175924#4175924 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175924

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: PostgeSQL runs take too long

by alex.guizar＠jboss.com

It ain't configuration, it is the AbstractDbTestCase code: http://anonsvn.jboss.org/repos/jbpm/jbpm3/trunk/modules/core/src/main/jav... public void setUp() throws Exception { | createSchema(); // HERE | createJbpmContext(); | initializeMembers(); | } | | public void tearDown() throws Exception { | resetMembers(); | closeJbpmContext(); | dropSchema(); // AND HERE | super.tearDown(); | } Note however that removing the above lines will be a challenge because many tests depend on an empty database. Perhaps we could simply clear the tables instead of dropping them? Of course that would imply caring about constraint violations. Not an easy way out either. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175887#4175887 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175887

15 years, 8 months

1
0
0 / 0

PostgeSQL runs take too long

by Thomas Diesler

Alejandro, this issue will slow down Hudson runs by >12h http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142201 Perhaps, you have an easy answer? cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler BPM Product Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Unifying jBPM project lifecycles

by thomas.diesler＠jboss.com

Folks, after internal discussions we came to the conclusion that it would simplify the development cycle of both jbpm3 and 4 a great deal if we would actually talk about these to development branches as such. In Jira, SVN, Maven we would have jbpm-3.3.x and jbpm-4.0.x releases. Both project branches would align their release cycle, so that consumers of these projects can rely on updates in the maven repository approximately every 8 weeks. The distinction between pvm, jpdl4 lifecycle is superfluous because for the foreseeablr future both projects evolve lock step anyway. For jBPM users it will also become easier, because in future you will only need to refer to jbpm-x.y.z without needing to make a distinction in project name based on component. The pvm release artefact in the maven repository will of course stay decoupled as is for folks that only want to consume the pvm base component. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175869#4175869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175869

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: PostgeSQL runs take too long

by thomas.diesler＠jboss.com

Where in the config would that be? http://anonsvn.jboss.org/repos/jbpm/jbpm3/trunk/modules/core/src/main/res... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175861#4175861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175861

15 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev September 2008