June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-909) java.lang.ClassCastException: org.drools.rule.AbstractCompositeConstraint$MultiFieldOrConstraintContextEntry

by Dirk Bergstrom (JIRA)

java.lang.ClassCastException: org.drools.rule.AbstractCompositeConstraint$MultiFieldOrConstraintContextEntry ------------------------------------------------------------------------------------------------------------ Key: JBRULES-909 URL: http://jira.jboss.com/jira/browse/JBRULES-909 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.0.MR3 Reporter: Dirk Bergstrom Assigned To: Mark Proctor When asserting User objects into the a WM that has already had rules fired, I get this exception: java.lang.ClassCastException: org.drools.rule.AbstractCompositeConstraint$MultiFieldOrConstraintContextEntry at org.drools.rule.VariableRestriction.isAllowedCachedLeft(VariableRestriction.java:72) at org.drools.rule.VariableConstraint.isAllowedCachedLeft(VariableConstraint.java:72) at org.drools.rule.OrConstraint.isAllowedCachedLeft(OrConstraint.java:64) at org.drools.common.DoubleBetaConstraints.isAllowedCachedLeft(DoubleBetaConstraints.java:140) at org.drools.reteoo.CollectNode.assertTuple(CollectNode.java:137) at org.drools.reteoo.CompositeTupleSinkAdapter.propagateAssertTuple(CompositeTupleSinkAdapter.java:30) at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:155) at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:317) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:183) at org.drools.reteoo.Rete.assertObject(Rete.java:121) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201) at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:70) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:766) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:578) at net.juniper.dash.data.DataSource.reconcileAssertedRecords(DataSource.java:265) at net.juniper.dash.data.UserSource.populateRecords(UserSource.java:234) at net.juniper.dash.Updater$DataSourceProcessor.work(Updater.java:177) at net.juniper.dash.Refresher.run(Refresher.java:69) I assert a bunch of Users (and a bunch of other objects), then fire the rules, then attempt to assert more Users, and I get this on the *second* User I assert. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBRULES-904) ArrayIndexOutOfBoundsException in org.drools.util.TupleIndexHashTable.toArray

by Dirk Bergstrom (JIRA)

ArrayIndexOutOfBoundsException in org.drools.util.TupleIndexHashTable.toArray ----------------------------------------------------------------------------- Key: JBRULES-904 URL: http://jira.jboss.com/jira/browse/JBRULES-904 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: Java 1.5 Reporter: Dirk Bergstrom Assigned To: Mark Proctor When asserting a particular object type, I get the following stacktrace: java.lang.ArrayIndexOutOfBoundsException: 26 at org.drools.util.TupleIndexHashTable.toArray(TupleIndexHashTable.java:178) at org.drools.reteoo.CollectNode.assertObject(CollectNode.java:212) at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:317) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:183) at org.drools.reteoo.Rete.assertObject(Rete.java:121) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201) at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:70) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:766) at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:578) at net.juniper.dash.data.DataSource.reconcileAssertedRecords(DataSource.java:250) at net.juniper.dash.data.DataSource.populateRecords(DataSource.java:193) at net.juniper.dash.Updater$DataSourceProcessor.work(Updater.java:177) at net.juniper.dash.Refresher.run(Refresher.java:69) I added some println() statements, and it's not an off-by-one error, it's something more serious. I changed the allocated size of the array to (this.size * 10), and it *still* tried to overfill the array. The hashtable had 26 entries, but it tried to add 261, and counting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

4
19
0 / 0

[JBoss JIRA] Created: (JBPM-1007) jBPM console search error

by Troy Kelley (JIRA)

jBPM console search error ------------------------- Key: JBPM-1007 URL: http://jira.jboss.com/jira/browse/JBPM-1007 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2 Environment: Windows XP, Java 5, jbpm-jpdl-3.2.GA download from sourceforge with no mods. Reporter: Troy Kelley Assigned To: Tom Baeyens Typing anything in any of the search fields on any of the search screens and you get an error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1116) Refactor out the use of UnversionedNode.getCHildrenMapDirect() due to inherent inefficiencies

by Manik Surtani (JIRA)

Refactor out the use of UnversionedNode.getCHildrenMapDirect() due to inherent inefficiencies --------------------------------------------------------------------------------------------- Key: JBCACHE-1116 URL: http://jira.jboss.com/jira/browse/JBCACHE-1116 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1117) CacheLoader.getChildrenNames() returns a Set<String>. Should be Set<Object>

by Manik Surtani (JIRA)

CacheLoader.getChildrenNames() returns a Set<String>. Should be Set<Object> ---------------------------------------------------------------------------- Key: JBCACHE-1117 URL: http://jira.jboss.com/jira/browse/JBCACHE-1117 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR3 Cache loader implementations may choose to restrict Fqn types acceptable for a particular cache loader - some cache loaders such as FileCacheLoader and JdbcCacheLoader can only accept Fqn<String> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4509) Remoting BisocketClientInvoker should guard against scheduling on an expired Timer

by Fernando Nasser (JIRA)

Remoting BisocketClientInvoker should guard against scheduling on an expired Timer ---------------------------------------------------------------------------------- Key: JBAS-4509 URL: http://jira.jboss.com/jira/browse/JBAS-4509 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Reporter: Fernando Nasser Please switch build-thirdpart.xml to use https://svn.jboss.org/repos/repository.jboss.org/jboss/remoting/2.2.0.SP4... Which contains the JBoss Remoting with the appropriate fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-540) Multiplexer: ordering issue

by Bela Ban (JIRA)

Multiplexer: ordering issue --------------------------- Key: JGRP-540 URL: http://jira.jboss.com/jira/browse/JGRP-540 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.5 Sometimes messages from the same sender are not delivered in the correct order, the test that shows this (happens infrequently) is MultiplexerTest.testOrdering(). When disabling the Multiplexer thread pool (-Djgroups.mux.enabled=false), everything works fine, so I suspect this is a thread pool issue in the Multiplexer (FIFOMessageQueue). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1005) Redlivery delay does not kick in on local delivery

by Tim Fox (JIRA)

Redlivery delay does not kick in on local delivery -------------------------------------------------- Key: JBMESSAGING-1005 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1005 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Currently if a tx is rolled back, then redelivery delay does not kick in because, redelivery occurs locally (this is what the JMS spec does). 1) So we can either store the scheduled deliveries on the client side (I don't like this) 2) Cancel them to the server on rollback if there is a redelivery delay 3) Always cancel back to the server on rollback -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1007) Add old message id header to message before bridging

by Tim Fox (JIRA)

Add old message id header to message before bridging ---------------------------------------------------- Key: JBMESSAGING-1007 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1007 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.4.0.CR1 Add a header Message.HEADER_JBM_OLD_MESSAGE_ID to message before bridging if bridge attribute addOldMessageIDAsHeader is true This allows responses to be correlated on the sender. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-168) Message tests derive from MessageTestBase

by Sergey Koshcheyev (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-168?page=comments#action_12... ] Sergey Koshcheyev commented on JBMESSAGING-168: ----------------------------------------------- JMSTest and MessageTest use almost the same setup, they could be merged or one could derive from the other. > Message tests derive from MessageTestBase > ----------------------------------------- > > Key: JBMESSAGING-168 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-168 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The jms message tests, e.g. JMSExpirationHeaderTest inherit from MessageTest. > Therefore all the tests in MessageTest are being re-run for each of the subtypes. > The hierarchchy of tests is overly complex and confusing. > We have messagetest, messagetestbase, jmstest, messagingtestcase...... (!) > The structure should be flattened and simplified to aid comprehension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
0
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 June 2007