April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2772) Drools Grid Impl2 remoting features (socket)

by Mauricio Salatino (JIRA)

Drools Grid Impl2 remoting features (socket) -------------------------------------------- Key: JBRULES-2772 URL: https://jira.jboss.org/browse/JBRULES-2772 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino Implement the Remoting Clients and Providers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2746) Drools Grid Impl2

by Mauricio Salatino (JIRA)

Drools Grid Impl2 ----------------- Key: JBRULES-2746 URL: https://jira.jboss.org/browse/JBRULES-2746 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino New APIs for Drools Grid -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2775) Drools Grid Impl 2 Spring Support for remote execution nodes

by Mauricio Salatino (JIRA)

Drools Grid Impl 2 Spring Support for remote execution nodes ------------------------------------------------------------ Key: JBRULES-2775 URL: https://jira.jboss.org/browse/JBRULES-2775 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mauricio Salatino We need to add support for the new APIs inside drools-container/drools-spring. To support grid nodes configurations using spring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBRULES-46) Prolog Style Query Based Backward Chaining

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-46?page=com.atlassian.jira.plugin... ] Michael Anstis commented on JBRULES-46: --------------------------------------- Won't this achieve what you need:- rule "UpdateCounter" salience 10000 when $c : Counter( .... , $value : value) $o : BusinessObject( $something : something, .... ) then $o.setValue($something + $value); update($o); end rule "CheckCounter" when $o : BusinessObject(value > 1234) then Alerts.addNew(...); end > Prolog Style Query Based Backward Chaining > ------------------------------------------ > > Key: JBRULES-46 > URL: https://issues.jboss.org/browse/JBRULES-46 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > > Forward Chaining means that facts are asserted and propgated forward throughout the network, during forward propagation matching takes place which results in rules being fired - the rules are event based, in that they are fired in response to changed in the working memory. > Backward chaining is query based. Rules attempt to fire first but do not have the necessary matched facts, so facts are pulled in from an external source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-46) Prolog Style Query Based Backward Chaining

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/JBRULES-46?page=com.atlassian.jira.plugin... ] Mark Proctor commented on JBRULES-46: ------------------------------------- "Other vendors has a sequential mode in which facts updates in first rules are taken in account for rules triggered after (BlazeAdvisor does this, not sure about JRules). Anyway, it could be an interresting feature. Drools sequential mode collects all t-uples, then apply rules. This prevents 'first' rules to do some updates that could change one t-uple value or even trigger (or not trigger) other rules that comes after in the rule sequence." Currently our sequential mode works as single pass, but it has no inference as rete join memory is turned off. So it produces all the conflict set more efficiently, and then it uses rule order for the execution order of the conflict set. However changes in the current rule are not recognised by the later rules. That is planned though by "partinioning" the sequential engine around the modify statements. The advantage to this is we keep a single algorithm that is just configured slightly to provide different behaviours. Rather than two competely different engines. > Prolog Style Query Based Backward Chaining > ------------------------------------------ > > Key: JBRULES-46 > URL: https://issues.jboss.org/browse/JBRULES-46 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > > Forward Chaining means that facts are asserted and propgated forward throughout the network, during forward propagation matching takes place which results in rules being fired - the rules are event based, in that they are fired in response to changed in the working memory. > Backward chaining is query based. Rules attempt to fire first but do not have the necessary matched facts, so facts are pulled in from an external source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9324) Fix race condition between Infinispan channel creation and JGroups ChannelFactory availability

by Paul Ferraro (JIRA)

Fix race condition between Infinispan channel creation and JGroups ChannelFactory availability ---------------------------------------------------------------------------------------------- Key: JBAS-9324 URL: https://issues.jboss.org/browse/JBAS-9324 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.0.Beta3 Currently, the EmbeddedCacheManagerService depends on the ChannelFactoryRegistry. Consequently, the referenced ChannelFactory may not yet exist when the cache manager starts. Instead, the dependency should be on the specific ChannelFactory, although the ChannelFactoryRegistry dependency may need to persist, to obtain the default stack if none was specified. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8856) Saxon 9.3 HE implementation

by Nicolai Jorgensen (JIRA)

Saxon 9.3 HE implementation --------------------------- Key: JBAS-8856 URL: https://issues.jboss.org/browse/JBAS-8856 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: 6.1.0 Reporter: Nicolai Jorgensen Fix For: 6.1.0 Is it possible to implement saxon 9.3 HE in order to obtain support for xslt 2.0 functionality in Jboss 6.1.0. It seems that Xalan stopped it's development in 2007 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9042) Smoke tests hang in management request handling code

by Brian Stansberry (JIRA)

Smoke tests hang in management request handling code ---------------------------------------------------- Key: JBAS-9042 URL: https://issues.jboss.org/browse/JBAS-9042 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker I'm seeing hangs in the smoke tests where threads are all blocking in the management request handling code. Thread dump attached. One thing that stands out is the large number of threads in this state: "pool-1-thread-7" prio=5 tid=102be5800 nid=0x10f377000 in Object.wait() [10f376000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <7f5235be8> (a java.lang.Object) at java.lang.Object.wait(Object.java:485) at org.jboss.as.protocol.Pipe$1.read(Pipe.java:75) - locked <7f5235be8> (a java.lang.Object) at org.jboss.as.protocol.ConnectionImpl$MessageInputStream.close(ConnectionImpl.java:302) at org.jboss.as.protocol.StreamUtils.safeClose(StreamUtils.java:294) at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:65) at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:254) at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:213) 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:680) I don't see how there would be that many concurrent requests going on; what I *suspect* is happening is those threads are handling requests from different test cases and are hanging. Eventually the pool is exhausted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-9337) transactional entity manager should close persistence context when invoked outside of a transaction (when component invocation completes)

by Scott Marlow (JIRA)

transactional entity manager should close persistence context when invoked outside of a transaction (when component invocation completes) ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9337 URL: https://issues.jboss.org/browse/JBAS-9337 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9236) Resource injection ends up searching for wrong target method when a resource type is specified

by jaikiran pai (JIRA)

Resource injection ends up searching for wrong target method when a resource type is specified ---------------------------------------------------------------------------------------------- Key: JBAS-9236 URL: https://issues.jboss.org/browse/JBAS-9236 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EE Affects Versions: 7.0.0.Beta2 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.0.Beta3 Consider either of the following examples: {code} @Resource (type=ChildClass.class) public void setSomeValue(ParentClass b); {code} @EJB (beanInterface=SpecificBeanClassImpl.class) public void setSomeEjb(ParentClass b); {code} The resource injection framework ends up searching for an (incorrect) method whose paramtype is ChildClass/SpecificBeanImplClass and doesn't find such a method. As a result, the deployment fails with exception like: {code} Caused by: java.lang.IllegalArgumentException: Invalid injection - Method void setSomeEjb(SpecificBeanImplClass) not found on class blah.blah.SomeClass at org.jboss.as.ee.component.ResourceInjection$Factory.create(ResourceInjection.java:88) at org.jboss.as.ee.component.JndiInjectionPointStore.applyInjections(JndiInjectionPointStore.java:98) at org.jboss.as.ee.component.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:206) at org.jboss.as.ee.component.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:67) ... 5 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
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 April 2011