[JBoss JIRA] Commented: (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 commented on JBPM-1452:
----------------------------------------
I cannot reproduce. All objects defined in default.jbpm.cfg.xml get created in any JbpmConfiguration. A custom jbpm.cfg.xml file overrides default objects of the same name.
Adding the following line to the configuration file effectively removes the job executor from the configuration. Nonetheless, the jbpm.job.executor entry still exists.
<null name="jbpm.job.executor" />
The above line appears in the jBPM enterprise configuration, which does not employ the job executor. It should resolve this issue without any code modification.
> 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)
> Affects Versions: JBossBPM-3.3.0
> Environment: 3.3 snapshot
> Spring
> Reporter: Alejandro Guizar
> Assignee: Alejandro Guizar
> Fix For: JBossBPM-3.3.0
>
>
> 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
15 years, 10 months
[JBoss JIRA] Resolved: (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 resolved JBPM-1620.
------------------------------------
Fix Version/s: JBossBPM-3.3.0
Resolution: Partially Completed
Added session flush after saving timer. Marking as partially completed to revisit the issue in case the explicit flush proves problematic operational environments.
> 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: jPDL 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: JBossBPM-3.3.0
>
>
> 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
15 years, 10 months
[JBoss JIRA] Commented: (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 commented on JBPM-1446:
----------------------------------------
On the contrary, it was great input. Thanks, Ronald.
I'm inclined to settle this issue on showing times in the server time zone. It may not be a global solution, but creating a page which allows the user to set the session time zone may be a waste considering the new GWT-based console is underway. I don't see any votes for this issue either.
Unless I hear otherwise I will resolve this issue in favor of the server time zone.
> display non GMT+0 time zones
> ----------------------------
>
> Key: JBPM-1446
> URL: https://jira.jboss.org/jira/browse/JBPM-1446
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Engine
> Reporter: Jiri Pechanec
> Assignee: Alejandro Guizar
> Fix For: SOA 4.2 CP03, SOA 4.3
>
> 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
[JBoss JIRA] Commented: (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 commented on JBPM-1620:
----------------------------------------
I wonder how the entity scheduler service manages to work without the flush in the web console. Flushing is the technique employed by the old session scheduler service and the PVM enterprise timer session, and works well in both cases. The multiple last resources problem manifests itself whenever the EJB timer service participates in the transaction, not just when flushing; hence I don't regard flushing as a dirty solution. Nonetheless, flushing the entire session just to get a single record inserted is not cost effective.
One alternative to flushing the session is to insert the timer record through an EJB creation method. It might be worth to explore this option to avoid a potentially expensive flush in the middle of a transaction.
> 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: jPDL 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
>
> 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
15 years, 10 months
[JBoss JIRA] Work started: (JBPM-1620) EntitySchedulerService fails with ObjectNotFoundException
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1620?page=com.atlassian.jira.plug... ]
Work on JBPM-1620 started by Alejandro Guizar.
> 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: jPDL 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
>
> 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
15 years, 10 months
[JBoss JIRA] Commented: (JBPM-1619) Wrong JNDI lookup to java:comp/env space in non-EJB enterprise components
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1619?page=com.atlassian.jira.plug... ]
Alejandro Guizar commented on JBPM-1619:
----------------------------------------
I reviewed the patch and applied the fixes for JBPM-960.
Conversely, I don't think that reverting to global JNDI names after switching to local environment references in 3.2.3 is a good idea. See the arguments in JBPM-960 and JBPM-1046. Please keep me informed on any issue you encounter while deploying the application to the EAP.
> Wrong JNDI lookup to java:comp/env space in non-EJB enterprise components
> -------------------------------------------------------------------------
>
> Key: JBPM-1619
> URL: https://jira.jboss.org/jira/browse/JBPM-1619
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Engine
> Affects Versions: jPDL 3.2.3
> Reporter: Martin Putz
> Assignee: Alejandro Guizar
> Attachments: JBPM-1619.patch
>
>
> The following components of the enterprise archive attempt to make a lookup from their local JNDI environment at java:comp/env:
> - org.jbpm.msg.jms.JmsMessageServiceFactoryImpl
> - org.jbpm.scheduler.ejbtimer.EjbSchedulerServiceFactory
> - org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory
> As these components are no EJB's, they have no local JNDI environment. The lookup should use the In-VM space by default (eg. java:/JmsXA), and it should be possible to override the lookup locations through jbpm.cfg.xml (see JBPM-960).
--
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