December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3093) Drools Fusion broker example throws stacktraces in drools 5.2.0

by Geoffrey De Smet (JIRA)

Drools Fusion broker example throws stacktraces in drools 5.2.0 --------------------------------------------------------------- Key: JBRULES-3093 URL: https://issues.jboss.org/browse/JBRULES-3093 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Kris Verlaenen Fix For: 5.2.0 {code} ============================================================= Unexpected exception caught: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalAction@1eeba19 org.drools.RuntimeDroolsException: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalAction@1eeba19 at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:996) at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1059) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:733) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:699) at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218) at org.drools.examples.broker.Broker.receive(Broker.java:68) at org.drools.examples.broker.events.EventFeeder$FeedJob.execute(EventFeeder.java:85) at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:146) at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:124) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IllegalArgumentException: XOR split could not find at least one valid outgoing connection for split Take Action at org.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:98) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:122) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:185) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:150) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:162) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:143) at org.jbpm.workflow.instance.node.RuleSetNodeInstance.signalEvent(RuleSetNodeInstance.java:73) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:339) at org.jbpm.process.instance.event.DefaultSignalManager.internalSignalEvent(DefaultSignalManager.java:80) at org.jbpm.process.instance.event.DefaultSignalManager$SignalAction.execute(DefaultSignalManager.java:175) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:994) ... 15 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
11
0 / 0

[JBoss JIRA] (AS7-2838) ClusteredWebTestCase does not deploy application on the second node

by Radoslav Husar (Created) (JIRA)

ClusteredWebTestCase does not deploy application on the second node ------------------------------------------------------------------- Key: AS7-2838 URL: https://issues.jboss.org/browse/AS7-2838 Project: Application Server 7 Issue Type: Bug Components: Clustering, Test Suite Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Blocker The second deployment is not specified, thus the application is not clustered. I already have fix in my branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

7
7
0 / 0

[JBoss JIRA] (AS7-2916) Implement a failover test in ClusteredWebTestCase

by Radoslav Husar (Created) (JIRA)

Implement a failover test in ClusteredWebTestCase ------------------------------------------------- Key: AS7-2916 URL: https://issues.jboss.org/browse/AS7-2916 Project: Application Server 7 Issue Type: Sub-task Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3305) Use any JPA Provider

by Geoffrey De Smet (Commented) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3305: ------------------------------------------- Note: if we upgrade to JPA 2 that @CollectionOfElements can be replaced by JPA's @ElementCollection. > Use any JPA Provider > -------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2821) One-test run may not pass and cause configuration file corruption (due to starting with non appropriate xml configuration)

by Vladimir Rastseluev (Created) (JIRA)

One-test run may not pass and cause configuration file corruption (due to starting with non appropriate xml configuration) -------------------------------------------------------------------------------------------------------------------------- Key: AS7-2821 URL: https://issues.jboss.org/browse/AS7-2821 Project: Application Server 7 Issue Type: Bug Environment: ./integration-tests.sh install -Dtest=org.jboss.as.test.smoke.embedded.mgmt.datasource.DataSourceOperationsUnitTestCase.java Reporter: Vladimir Rastseluev Fix For: 7.1.0.CR1 After execution of this command (Environment) test fails and configuration file ~/testsuite/integration/smoke/target/jbossas-smoke/standalone/configuration/standalone-full.xml is changed (datasource MyNewDs is added). Problem is caused by starting test with non appropriate configuration in /testsuite/integration/smoke/pom.xml file(test starts twice with standalone-full.xml and standalone.xml configuration). This test needs another configuration file - standalone.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3305) Use any JPA Provider

by Geoffrey De Smet (Issue Comment Edited) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Geoffrey De Smet edited comment on JBRULES-3305 at 12/5/11 9:15 AM: -------------------------------------------------------------------- Moved from Guvnor's jira: Guvnor itself doesn't have any hibernate specific annotations. It does depend on hibernate-validator (but that's unrelated to hibernate persistence and/or JPA) and even then it only uses the bean validation JSR annotations. Drools does depend on hibernate-core, annotations and entitymanager, but it doesn't use any hibernate specific annotations. JBPM does use hibernate specific annotations: {code} Targets String 'import org.hibernate' Found usages (5 usages) Production (5 usages) jbpm-bam (4 usages) org.jbpm.process.audit (4 usages) HibernateUtil.java (2 usages) (19: 1) import org.hibernate.SessionFactory; (20: 1) import org.hibernate.cfg.Configuration; ProcessInstanceDbLog.java (1 usage) (21: 1) import org.hibernate.Session; WorkingMemoryDbLogger.java (1 usage) (28: 1) import org.hibernate.Session; jbpm-persistence-jpa (1 usage) org.jbpm.persistence.processinstance (1 usage) ProcessInstanceInfo.java (1 usage) (35: 1) import org.hibernate.annotations.CollectionOfElements; {code} What does the customer want? - Is removing that one @CollectionOfElements in jBPM enough? - Or do all the org.hibernate imports in jBPM have to be removed? - Or do all the hibernate-* dependencies be set to scope runtime (which might not be feasible)? was (Author: ge0ffrey): Moved from Guvnor's jira: Guvnor itself doesn't have any hibernate specific annotations. It does depend on hibernate-validator (but that's unrelated to hibernate persistence and/or JPA) and even then it only uses the bean validation JSR annotations. Drools does depend on hibernate-core, annotations and entitymanager, but it doesn't use any hibernate specific annotations. JBPM does use hibernate specific annotations: {code} Targets String 'import org.hibernate' Found usages (5 usages) Production (5 usages) jbpm-bam (4 usages) org.jbpm.process.audit (4 usages) HibernateUtil.java (2 usages) (19: 1) import org.hibernate.SessionFactory; (20: 1) import org.hibernate.cfg.Configuration; ProcessInstanceDbLog.java (1 usage) (21: 1) import org.hibernate.Session; WorkingMemoryDbLogger.java (1 usage) (28: 1) import org.hibernate.Session; jbpm-persistence-jpa (1 usage) org.jbpm.persistence.processinstance (1 usage) ProcessInstanceInfo.java (1 usage) (35: 1) import org.hibernate.annotations.CollectionOfElements; {code} What does the customer want? > Use any JPA Provider > -------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3305) Use any JPA Provider

by Geoffrey De Smet (Commented) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3305: ------------------------------------------- Moved from Guvnor's jira: Guvnor itself doesn't have any hibernate specific annotations. It does depend on hibernate-validator (but that's unrelated to hibernate persistence and/or JPA) and even then it only uses the bean validation JSR annotations. Drools does depend on hibernate-core, annotations and entitymanager, but it doesn't use any hibernate specific annotations. JBPM does use hibernate specific annotations: {code} Targets String 'import org.hibernate' Found usages (5 usages) Production (5 usages) jbpm-bam (4 usages) org.jbpm.process.audit (4 usages) HibernateUtil.java (2 usages) (19: 1) import org.hibernate.SessionFactory; (20: 1) import org.hibernate.cfg.Configuration; ProcessInstanceDbLog.java (1 usage) (21: 1) import org.hibernate.Session; WorkingMemoryDbLogger.java (1 usage) (28: 1) import org.hibernate.Session; jbpm-persistence-jpa (1 usage) org.jbpm.persistence.processinstance (1 usage) ProcessInstanceInfo.java (1 usage) (35: 1) import org.hibernate.annotations.CollectionOfElements; {code} What does the customer want? > Use any JPA Provider > -------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3305) Use any JPA Provider

by Geoffrey De Smet (Moved) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Geoffrey De Smet moved GUVNOR-1768 to JBRULES-3305: --------------------------------------------------- Project: Drools (was: Guvnor) Key: JBRULES-3305 (was: GUVNOR-1768) Affects Version/s: 5.3.0.Final (was: drools-5.2.0.Final) Fix Version/s: (was: drools-5.4.0.Beta1) > Use any JPA Provider > -------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1207) test for not persisted (xa)datasource properties

by Stefano Maestri (JIRA)

test for not persisted (xa)datasource properties ------------------------------------------------ Key: AS7-1207 URL: https://issues.jboss.org/browse/AS7-1207 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] (AS7-2720) tests for parsing particular datasources in standalone mode

by Vladimir Rastseluev (Created) (JIRA)

tests for parsing particular datasources in standalone mode ----------------------------------------------------------- Key: AS7-2720 URL: https://issues.jboss.org/browse/AS7-2720 Project: Application Server 7 Issue Type: Sub-task Components: JCA Reporter: Vladimir Rastseluev Assignee: Vladimir Rastseluev Fix For: 7.1.0.CR1 Trying to add datasources (non-XA and XA) with different properties (according to XSD) to the model in standalone mode using DRM API, in order to verify correct parsing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011