February 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2072) ConnectionManager deadlock running XA transaction on AS 4

by Heiko Braun (JIRA)

ConnectionManager deadlock running XA transaction on AS 4 --------------------------------------------------------- Key: JBPM-2072 URL: https://jira.jboss.org/jira/browse/JBPM-2072 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0 Alpha2 10:15:41,408 ERROR [LogInterceptor] RuntimeException in method: public abstract java.lang.Object org.jbpm.enterprise.internal.ejb.LocalCommandExecutor.execute(org.jbpm.cmd.Command): java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:125) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1137) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:431) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.unlock(BaseWrapperManagedConnection.java:278) at org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:180) at org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper.end(JcaXAResourceWrapper.java:58) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endSuspendedRMs(TransactionImple.java:1529) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:235) at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501) -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-1446) display non GMT+0 time zones

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1446?page=com.atlassian.jira.plug... ] Alejandro Guizar resolved JBPM-1446. ------------------------------------ Resolution: Done Added timeZone attribute to every f:convertDateTime tag. > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-1446 > URL: https://jira.jboss.org/jira/browse/JBPM-1446 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Engine > Affects Versions: jBPM 3.2.3 > Reporter: Jiri Pechanec > Assignee: Alejandro Guizar > Fix For: jBPM 3.2.6 GA > > Attachments: Screenshot.jpg, SolutionShot.png > > > I spotted it today so I am creating the link to project JIRA. It is really inconvenient for user to have UTC time displayed in browser. See JBPM-987 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-2057: --------------------------------- Fix Version/s: jBPM 3.2.6 GA > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2064) re-introduce schema sql scripts in distro

by Tom Baeyens (JIRA)

re-introduce schema sql scripts in distro ----------------------------------------- Key: JBPM-2064 URL: https://jira.jboss.org/jira/browse/JBPM-2064 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBPM-304) Transient variables are not available in scripts

by Simon Gibbs (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-304?page=com.atlassian.jira.plugi... ] Simon Gibbs commented on JBPM-304: ---------------------------------- This issue is still present as of version 3.2. I'd like to expose the services of Spring beans by injecting a list of named beans into the transient variables of individual process instances before signalling them. e.g. in beanshell I'd like this to work: persistentVariable = transientSpringBean.findData(arg); I've tried wrapping VariableResolver but this only affects EL, and is not a suitable alternative. > Transient variables are not available in scripts > ------------------------------------------------ > > Key: JBPM-304 > URL: https://jira.jboss.org/jira/browse/JBPM-304 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.0 > Reporter: Daniel Serodio > Assignee: Tom Baeyens > Priority: Minor > > The jBPM documentation, section 7.4.5. Script, says: > "... By default, all process variables are available as script-variables and no script-variables will be written to the process variables." > But the transient variables are not available to <script>s, just to <action>s. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1210) spring configuration support

by Andries Inze (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1210?page=com.atlassian.jira.plug... ] Andries Inze updated JBPM-1210: ------------------------------- Attachment: spring-jbpm-24022009-patch.zip Added new svn patch (24022009) Allows for the following process definitions: <?xml version="1.0" encoding="UTF-8"?> <process name="Spring"> <start> <transition to="test" /> </start> <spring name="test"> <bean>testBean</bean> <method>testMethod</method> <transition to="testWithParameters" /> </spring> <spring name="testWithParameters"> <bean>testBean</bean> <method>testMethodWithParameters</method> <parameters> <string value="a good test" /> </parameters> <transition to="exclusive spring test" /> </spring> <exclusive name="exclusive spring test" handler-ref="testBean"> <transition name="no" to="wait" /> <transition name="yes" to="wait" /> </exclusive> <state name="wait" /> </process> The handler-ref refers to a spring bean. > spring configuration support > ---------------------------- > > Key: JBPM-1210 > URL: https://jira.jboss.org/jira/browse/JBPM-1210 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > Assignee: Mauricio Salatino > Priority: Minor > Fix For: jBPM 4.0.x > > Attachments: spring-jbpm-24022009-patch.zip, spring-jbpm-v1.7z, spring-jbpm-v1.zip > > > The first goal is to create an EnvironmentFactory implementation that is based on spring configuration. > The class to complete is org.jbpm.pvm.internal.env.SpringEnvironmentFactory > The SpringEnvironmentFactory should relate to a spring ApplicationContext, I believe. The first thing to do is create a test that shows how a spring configuration can be used to create hibernate sessions. > Something like this: > static EnvironmentFactory environmentFactory = SpringEnvironmentFactory.parseResource("org/jbpm/pvm/spring/springbeans.xml"); > Environment environment = environmentFactory.openEnvironment(); > try { > Session hibernateSession = environment.get(Session.class); > assertNotNull(hibernateSession); > } finally { > environment.close(); > } -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2060) Investigate requirement on ALTER TABLE privileges

by Thomas Diesler (JIRA)

Investigate requirement on ALTER TABLE privileges ------------------------------------------------- Key: JBPM-2060 URL: https://jira.jboss.org/jira/browse/JBPM-2060 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.2.x -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-2043) Add jBPM performance test coverage

by Pavel Macik (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2043?page=com.atlassian.jira.plug... ] Pavel Macik commented on JBPM-2043: ----------------------------------- Now the jobs are configured to take bits from svn tags: https://svn.jboss.org/repos/jbpm/jbpm3/tags/jpdl-3.2.2-SOA-4.2.0.CP03/ https://svn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.5.SP1/ > Add jBPM performance test coverage > ---------------------------------- > > Key: JBPM-2043 > URL: https://jira.jboss.org/jira/browse/JBPM-2043 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Productization > Affects Versions: jBPM 3.2.5 GA > Environment: SOA 4.3.0 CP01 CR2 > Reporter: Pavel Macik > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA > > > Performance of jBPM has dropped significantly according to > http://hudson.qa.jboss.com/hudson/view/SOA-Performance/job/SOA-Platform-P... > Other performance has not changed much so the performance drop is isolated to jBPM. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-2057) Do not truncate long messages/exceptions

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-2057. ---------------------------------- Resolution: Done jbpm-3.2.5.SP2 contains this fix for sybase only. < create table JBPM_JOB (... EXCEPTION_ varchar(4000) null, ...) > create table JBPM_JOB (... EXCEPTION_ text null, ...) < create table JBPM_LOG (... EXCEPTION_ varchar(4000) null, ...) > create table JBPM_LOG (... EXCEPTION_ text null, ...) Additional mappings to "text" properties need to be decided > Do not truncate long messages/exceptions > ---------------------------------------- > > Key: JBPM-2057 > URL: https://jira.jboss.org/jira/browse/JBPM-2057 > Project: JBoss jBPM > Issue Type: Bug > Components: Productization > Environment: Sybase/DB2 > Reporter: Ryan Campbell > Assignee: Thomas Diesler > Fix For: jBPM-3.2.5.SP2 > > > For sybase, a "text" column should be used instead of the current varchar(4000) > This will prevent the truncation of stack traces. > Do to data migration issues we cannot change the mapping of existing db columns. Instead the issue should be resolved by adding additional "text" columns. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2056) REstore strictly compatible jbpm322 schema

by Thomas Diesler (JIRA)

REstore strictly compatible jbpm322 schema ------------------------------------------ Key: JBPM-2056 URL: https://jira.jboss.org/jira/browse/JBPM-2056 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM-3.2.5.SP2 -- 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, 10 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2009