[JBoss JIRA] Created: (JBPM-2078) JSF Console doesn't deploy
by Heiko Braun (JIRA)
JSF Console doesn't deploy
--------------------------
Key: JBPM-2078
URL: https://jira.jboss.org/jira/browse/JBPM-2078
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Heiko Braun
Priority: Blocker
Fix For: jBPM 3.2.6 GA
Caused by: org.hibernate.PropertyNotFoundException: field [id] not found on org.jbpm.identity.User
at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:122)
at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:114)
at org.hibernate.property.DirectPropertyAccessor.getGetter(DirectPropertyAccessor.java:137)
at org.hibernate.util.ReflectHelper.getter(ReflectHelper.java:83)
at org.hibernate.util.ReflectHelper.reflectedPropertyClass(ReflectHelper.java:71)
at org.hibernate.mapping.SimpleValue.setTypeUsingReflection(SimpleValue.java:276)
at org.hibernate.cfg.HbmBinder.bindSimpleId(HbmBinder.java:401)
at org.hibernate.cfg.HbmBinder.bindRootPersistentClassCommonValues(HbmBinder.java:334)
at org.hibernate.cfg.HbmBinder.bindRootClass(HbmBinder.java:273)
at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:144)
at org.hibernate.cfg.Configuration.add(Configuration.java:669)
at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:504)
at org.hibernate.cfg.Configuration.addResource(Configuration.java:566)
--
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] Created: (JBPM-2042) Add possibility to query failed Jobs
by Bernd Ruecker (JIRA)
Add possibility to query failed Jobs
------------------------------------
Key: JBPM-2042
URL: https://jira.jboss.org/jira/browse/JBPM-2042
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Bernd Ruecker
Assignee: Bernd Ruecker
Priority: Minor
Fix For: jBPM 3.2.6 GA
The JobExecutor decrements the number of retries every time an exception is thrown during execution of jobs. The exception stacktrace is saved in the Jobs.
In the API (JobSession) I now add a method to query all failed jobs (where retries==0 and excpetion!=null) which will not be executed again by the JobExecutor.
I added the method "findFailedJobs", the hibernate named query "JobSession.findFailedJobs" and a test case for 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-455) NullPointerException when subprocess starts or ends
by s p (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-455?page=com.atlassian.jira.plugi... ]
s p commented on JBPM-455:
--------------------------
Fix for this bug creates a new problem described here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214128#4214128
> NullPointerException when subprocess starts or ends
> ---------------------------------------------------
>
> Key: JBPM-455
> URL: https://jira.jboss.org/jira/browse/JBPM-455
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Reporter: Eduardo Jimenez
> Assignee: Tom Baeyens
>
> Imagine a scenario where process A calls process B. Process A provides "in" parameters for process B through "read" access variables, and "out" parameters through "write" access variables.
> Now imagine one of the "out" parameters is optional, say a failure code for instance (say documentation submitted with an application was imcomplete, the code indicates what part of the application was unacceptable). It might be set by process B or it might not be set.
> When jBPM notifies process A that process B is done, it tries to copy the "out" variable value from process B to process A. If the variable was never set in process B, hence its value is NULL, jBPM throws a RuntimeException because the variable cannot be created in process A with a null value.
> The same thing happens if an "in" parameter ("read" access variable) is passed to a subprocess and the variable has not been set.
> In either case, an exception should not be thrown, the variable should just not be created on the subprocess for in variables, or copied to the parent process for out variables.
--
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] Created: (JBPM-2074) Fix intermittent problem with JbpmConfigurationTest.testDomainModelConfigsWithoutJbpmContext
by Thomas Diesler (JIRA)
Fix intermittent problem with JbpmConfigurationTest.testDomainModelConfigsWithoutJbpmContext
--------------------------------------------------------------------------------------------
Key: JBPM-2074
URL: https://jira.jboss.org/jira/browse/JBPM-2074
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Fix For: jBPM 3.2.6 GA
It seems that some asynchronous process creates a JbpmContext
2009-02-28 19:53:53,895 DEBUG [org.jbpm.AbstractJbpmTestCase] ### START org.jbpm.JbpmConfigurationTest.testDomainModelConfigsWithoutJbpmContext ####################################################
2009-02-28 19:53:53,895 DEBUG [org.jbpm.configuration.ObjectFactoryImpl] adding object info 'jbpmConfiguration'
2009-02-28 19:53:53,895 DEBUG [org.jbpm.persistence.db.StaleObjectLogConfigurer] stale object exceptions are already hidden from logging
2009-02-28 19:53:53,896 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[message, tx, scheduler, authentication, persistence, logging]'
2009-02-28 19:53:53,896 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@1a7abed
2009-02-28 19:53:53,896 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@1a7abed
2009-02-28 19:53:53,896 INFO [org.hibernate.connection.DriverManagerConnectionProvider] cleaning up connection pool: jdbc:hsqldb:mem:jbpm
2009-02-28 19:53:53,897 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[message, tx, scheduler, authentication, persistence, logging]'
2009-02-28 19:53:53,897 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@1bfe151
2009-02-28 19:53:53,898 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@1bfe151
2009-02-28 19:53:53,898 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[message, tx, scheduler, authentication, persistence, logging]'
2009-02-28 19:53:53,898 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@10994db
2009-02-28 19:53:53,898 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@10994db
2009-02-28 19:53:53,899 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[]'
2009-02-28 19:53:53,899 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@1945b7a
2009-02-28 19:53:53,899 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@1945b7a
2009-02-28 19:53:53,901 DEBUG [org.jbpm.AbstractJbpmTestCase] ### END org.jbpm.JbpmConfigurationTest.testDomainModelConfigsWithoutJbpmContext ######################################################
--
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