January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1465) NullPointerException on transaction.rollback() in DbPersistenceService

by Martin Putz (JIRA)

NullPointerException on transaction.rollback() in DbPersistenceService ---------------------------------------------------------------------- Key: JBPM-1465 URL: https://jira.jboss.org/jira/browse/JBPM-1465 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jPDL 3.2.3, SOA 4.2 CP02 Reporter: Martin Putz Assignee: Alejandro Guizar We are having NullPointerException from DbPersistenceService when Hibernate throws Exception on close() method. The line is transaction.rollback(); in rollback() method. My two cents is this code should be embraced with "if ( isTransactionEnabled && (transaction != null) )" statement, because we are using external JDBC Connection provider, and the transaction reference never be set. All calls to the rollback() method in DbPersistenceService are already preceded by a check for if ( (isTransactionEnabled) && (transaction!=null) ) { except this one after an exception has happened during the Hibernate session.flush call: Exception flushException = flushSession(); if (flushException!=null) { rollback(); // missing check if there is a transaction closeSession(); closeConnection(); throw new JbpmPersistenceException("hibernate flush failed", flushException); } -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Closed: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ] Alejandro Guizar closed JBPM-1452. ---------------------------------- Closing issues that I resolved in already released versions. > JbpmConfiguration assumes the object factory has a jbpm.job.executor entry > -------------------------------------------------------------------------- > > Key: JBPM-1452 > URL: https://jira.jboss.org/jira/browse/JBPM-1452 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: 3.3 snapshot > Spring > Reporter: Alejandro Guizar > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.0 GA > > > The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR. > org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size] > at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76) > at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603) > at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51) > at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32) > at org.jbpm.svc.Services.getService(Services.java:156) > at org.jbpm.svc.Services.getCurrentService(Services.java:94) > at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328) > at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329) > at org.jbpm.graph.exe.Token.end(Token.java:301) > at org.jbpm.graph.exe.Token.end(Token.java:251) > at org.jbpm.graph.node.EndState.execute(EndState.java:59) > The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-1620) EntitySchedulerService fails with ObjectNotFoundException

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1620?page=com.atlassian.jira.plug... ] Alejandro Guizar closed JBPM-1620. ---------------------------------- Closing issues that I resolved in already released versions. > EntitySchedulerService fails with ObjectNotFoundException > --------------------------------------------------------- > > Key: JBPM-1620 > URL: https://jira.jboss.org/jira/browse/JBPM-1620 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jBPM 3.2.3 > Environment: jbpm-enterprise.ear with jbpm.cfg.xml: > <service name="scheduler" factory="org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory" /> > Reporter: Martin Putz > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.0 GA > > > When a process contains a timer definition, the EntitySchedulerService#createTimer function fails with the following stacktrace: > 2008-08-14 14:42:22,563 DEBUG [org.jbpm.scheduler.ejbtimer.EntitySchedulerService] creating timer timer(initialReminder,08-08-14 14:42:32,553,Token: 6999) > 2008-08-14 14:42:22,563 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0) > 2008-08-14 14:42:22,563 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection > 2008-08-14 14:42:22,563 DEBUG [org.hibernate.SQL] select nextval ('hibernate_sequence') > 2008-08-14 14:42:22,564 DEBUG [org.hibernate.id.SequenceGenerator] Sequence identifier generated: 7000 > 2008-08-14 14:42:22,564 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1) > 2008-08-14 14:42:22,564 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection > 2008-08-14 14:42:22,564 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)] > 2008-08-14 14:42:22,564 DEBUG [org.hibernate.event.def.AbstractSaveEventListener] generated identifier: 7000, using strategy: org.hibernate.id.SequenceGenerator > 2008-08-14 14:42:22,565 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.TimerEntityBean#findByPrimaryKey] Executing SQL: SELECT t0_TimerEntityBean.ID_ FROM jbpm_job t0_TimerEntityBean WHERE t0_TimerEntityBean.ID_=? > 2008-08-14 14:42:22,566 ERROR [org.jbpm.scheduler.ejbtimer.EntitySchedulerService] failed to retrieve entity for timer timer(initialReminder,08-08-14 14:42:32,553,Token: 6999) > javax.ejb.ObjectNotFoundException: No such entity! > at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:64) > at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:604) > at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:315) > at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:236) > at org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1099) > at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:676) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > ... > at $Proxy62.findByPrimaryKey(Unknown Source) > The new record has not been written to the JBPM_JOB table at the time the timerEntityHome.findByPrimaryKey(new Long(timer.getId())); call is made. I tried adding a Hibernate session.flush() before, which solved this problem. But as a consequence this workaround showed the symptoms of multiple 1-phase aware participants enlisting in the same transaction (http://wiki.jboss.org/wiki/Multiple1PC), so there must be a cleaner solution to it. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1694) move UserTransaction lookup to persistence service factory

by Alejandro Guizar (JIRA)

move UserTransaction lookup to persistence service factory ---------------------------------------------------------- Key: JBPM-1694 URL: https://jira.jboss.org/jira/browse/JBPM-1694 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jPDL 3.2.3 Reporter: Alejandro Guizar Fix For: JBossBPM-3.3.0.GA In jBPM 3.2.3 and earlier, the UserTransaction object is retrieved from JNDI every time a JTA persistence service is opened and no transaction is in progress. This works fine; however, the UserTransaction might as well be retrieved only once and cached in the JTA persistence service factory. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-1709) JtaDbPersistenceService cannot begin Tx

by Thomas Diesler (JIRA)

JtaDbPersistenceService cannot begin Tx --------------------------------------- Key: JBPM-1709 URL: https://jira.jboss.org/jira/browse/JBPM-1709 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.0 org.jbpm.JbpmException: couldn't start JTA transaction at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:74) at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:47) at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:63) at org.jbpm.svc.Services.getService(Services.java:156) at org.jbpm.svc.Services.getPersistenceService(Services.java:195) at org.jbpm.persistence.jta.JtaDbPersistenceTest.isTxCreatedByService(JtaDbPersistenceTest.java:194) at org.jbpm.persistence.jta.JtaDbPersistenceTest.deployProcess(JtaDbPersistenceTest.java:79) at org.jbpm.persistence.jta.JtaDbPersistenceTest.testServiceTx(JtaDbPersistenceTest.java:59) at org.jbpm.persistence.jta.JtaDbPersistenceTest.testUserTx(JtaDbPersistenceTest.java:50) Caused by: javax.transaction.NotSupportedException at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:79) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:77) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:124) at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:72) -- 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, 3 months

3
19
0 / 0

[JBoss JIRA] Created: (JBPM-1717) web console: disable job executor launcher and resolve ejb and destination references

by Alejandro Guizar (JIRA)

web console: disable job executor launcher and resolve ejb and destination references ------------------------------------------------------------------------------------- Key: JBPM-1717 URL: https://jira.jboss.org/jira/browse/JBPM-1717 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Alejandro Guizar Priority: Blocker Fix For: jBPM 3.3.0 CR1 After much scratching my head over why the enterprise tests simply do not work despite they already worked in 3.2.3, I realized the job executor was running, which interferes with the enterprise scheduler and message services. The job executor launcher has to be disabled and the commented out ejb and destination references must be uncommented and resolved against the EJBs. The forum link discusses ear vs sar packaging, which influences how the ejb and destination references will be resolved. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1754) StaleObjectLog verbosity control code should be added to flushSession()

by Alejandro Guizar (JIRA)

StaleObjectLog verbosity control code should be added to flushSession() ----------------------------------------------------------------------- Key: JBPM-1754 URL: https://jira.jboss.org/jira/browse/JBPM-1754 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Fix For: jBPM 3.3.0 GA DbPersistenceService.flushSession line #272 Since a StaleObjectStateExcetion occures in flushSession() rather than commit(), StaleObjectLog verbosity control code should be added to flushSession() method as the same manner as commit(). See the following code snippet. An external transaction manager is being used and indeed DbPersistenceService.commit() does nothing. Exception flushSession() { if (mustSessionBeFlushed) { try { log.debug("flushing hibernate session " + session.toString()); session.flush(); // >>>>>>> begin } catch (StaleObjectStateException e) { log.info("optimistic locking failed"); StaleObjectLogConfigurer.staleObjectExceptionsLog.error("optimistic locking failed", e); return e; // <<<<<<< end } catch (Exception e) { log.error("hibernate flush failed", e); return e; } } return null; } -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1724) Fix or Remove SeamPageFlowTest

by Thomas Diesler (JIRA)

Fix or Remove SeamPageFlowTest ------------------------------ Key: JBPM-1724 URL: https://jira.jboss.org/jira/browse/JBPM-1724 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Caused by: java.lang.NullPointerException at org.jbpm.graph.def.Action.execute(Action.java:122) at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:256) -- 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, 3 months

3
15
0 / 0

[JBoss JIRA] Created: (JBPM-1726) JMS destinations service

by Alejandro Guizar (JIRA)

JMS destinations service ------------------------ Key: JBPM-1726 URL: https://jira.jboss.org/jira/browse/JBPM-1726 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine, Installer Reporter: Alejandro Guizar Fix For: jBPM 3.3.0 CR1 JBoss 5.0 does not create missing* JMS destinations automatically as JBoss 4.2 does. In any case JBoss 4.2 issues a warning which may be uncomfortable for users. Hence a default jBPM destinations descriptor must be provided and offered as an option in the installer. (*) that is, referenced in jboss.xml or jboss-web.xml but not bound to JNDI -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Closed: (JBPM-1024) Serializable variables are not being deserialized when retrieved from process

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1024?page=com.atlassian.jira.plug... ] Alejandro Guizar closed JBPM-1024. ---------------------------------- Closing issues that I resolved in already released versions. > Serializable variables are not being deserialized when retrieved from process > ----------------------------------------------------------------------------- > > Key: JBPM-1024 > URL: https://jira.jboss.org/jira/browse/JBPM-1024 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4, jBPM 3.2.2 > Reporter: thilker > Assignee: Alejandro Guizar > Fix For: jBPM 3.2.3 > > > Storing an serializable object in a process should write an "R" in the column "converter" in table JBPM_VARIABLEINSTANCE. > But the value of the field is "null". > The cause: > The converter ID is retrieved in class org.jbpm.db.hibernate.Converter at line 63. > For the case of the SerializableToByteArrayConverter the ID is "null". > Regards, > Thorsten -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009