January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2396) ReturnValueRestriction passes null to evaluator

by Nick Heudecker (JIRA)

ReturnValueRestriction passes null to evaluator ----------------------------------------------- Key: JBRULES-2396 URL: https://jira.jboss.org/jira/browse/JBRULES-2396 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Environment: Drools 5.1.0-SNAPSHOT, JDK 1.6.0, OSX 10.6 Reporter: Nick Heudecker Assignee: Mark Proctor Attachments: null-date-eval.patch When attempting 'less than', 'greater than', 'less than equals to' and 'greater than equals to' operations on dates, the ReturnValueRestriction passes a null to the evaluator's InternalWorkingMemory param, causing an NPE when the evaluator attempts to get the date formats from the Working Memory. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7597) Support AgentX (RFC 2741) in snmp-adaptor

by James Livingston (JIRA)

Support AgentX (RFC 2741) in snmp-adaptor ----------------------------------------- Key: JBAS-7597 URL: https://jira.jboss.org/jira/browse/JBAS-7597 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: SNMP adapter Reporter: James Livingston Assignee: Dimitris Andreadis It would be good if the SNMP adaptor supported RFC 2741 (AgentX), so that it can act as a sub-agent for a master agent. Unfortunately JoeSNMP doesn't appear to support that although other Java implementations (e.g. SNMP4J do). -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2399) java regexp inline modifier in dsl causes java.lang.IndexOutOfBoundsException

by Lev Kochubeevsky (JIRA)

java regexp inline modifier in dsl causes java.lang.IndexOutOfBoundsException ----------------------------------------------------------------------------- Key: JBRULES-2399 URL: https://jira.jboss.org/jira/browse/JBRULES-2399 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Environment: Windows XP, Eclipse 3.4 with Drools 5.0.1 plugin Reporter: Lev Kochubeevsky Assignee: Mark Proctor Does Drools 5 support java regexp inline modifiers? I tested my pattern matching in java and it works fine: System.out.println ( Pattern.matches("(?i)update the message", "uPdAte the message")); // true I'm trying to use the same thing in DSL: [then](?i)update the message fact=update ( m ); DSLR: update the message fact and get: java.lang.IndexOutOfBoundsException: No group 3 at java.util.regex.Matcher.group(Matcher.java:470) at java.util.regex.Matcher.appendReplacement(Matcher.java:737) at java.util.regex.Matcher.replaceAll(Matcher.java:813) at org.drools.lang.dsl.DefaultExpander.expandRHS(DefaultExpander.java:305) at org.drools.lang.dsl.DefaultExpander.expandConstructions(DefaultExpander.java:145) at org.drools.lang.dsl.DefaultExpander.expand(DefaultExpander.java:116) at org.drools.compiler.DrlParser.parse(DrlParser.java:125) at org.drools.eclipse.DroolsEclipsePlugin.generateParsedResource(Unknown Source) at org.drools.eclipse.DroolsEclipsePlugin.generateParsedResource(Unknown Source) at org.drools.eclipse.DroolsEclipsePlugin.parseResource(Unknown Source) at org.drools.eclipse.view.rules.RulesView.updateResource(Unknown Source) at org.drools.eclipse.view.rules.RulesView.access$1(Unknown Source) at org.drools.eclipse.view.rules.RulesView$1.visit(Unknown Source) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48) at org.drools.eclipse.view.rules.RulesView.resourceChanged(Unknown Source) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:153) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-584) Add junit 4.8.1 to maven repository

by Paul Gier (JIRA)

Add junit 4.8.1 to maven repository ----------------------------------- Key: JBBUILD-584 URL: https://jira.jboss.org/jira/browse/JBBUILD-584 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build Support 2010 jpederse requested to add junit 4.8.1 to the maven2 repository -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1432) Queries Executed while Rules are Firing Causes Exceptions

by Steve Shabino (JIRA)

Queries Executed while Rules are Firing Causes Exceptions --------------------------------------------------------- Key: JBRULES-1432 URL: http://jira.jboss.com/jira/browse/JBRULES-1432 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.4 Environment: Sun 1.5.0_04 Windows Reporter: Steve Shabino We have a stateful WM into which we periodically (1) insert new facts and fire rules, and (2) execute queries. Drools fails when we allow query execution in another thread during fireAllRules(). Set-up: - Every 10 seconds, Thread A inserts some facts and calls fireAllRules(). fireAllRules() is never called concurrently with itself. - Thread B executes many getQueryResults() calls in series (no concurrency in query execution) Our rule base uses shadow facts for all facts and is set up this way: conf.setAssertBehaviour(RuleBaseConfiguration.AssertBehaviour.EQUALITY); conf.setRemoveIdentities(true); conf.setLogicalOverride(RuleBaseConfiguration.LogicalOverride.DISCARD); conf.setMaintainTms(true); conf.setShadowProxy(true); We are making some use of insertLogical(). Expected: - Queries are run against the last consistent truth state, even while fireAllRules() is running. Actual Behavior: We get this exception: Caused by: java.lang.RuntimeException: Unable to pop at org.drools.util.PrimitiveLongStack.pop(PrimitiveLongStack.java:63) at org.drools.common.AbstractFactHandleFactory.newFactHandle(AbstractFactHandleFactory.java:44) at org.drools.reteoo.ReteooWorkingMemory.getQueryResults(ReteooWorkingMemory.java:90) This bug occurs under 4.04 and 4.1 Trunk as of 1/22. Please let us know if we can provide additional information. -- 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

15 years

3
11
0 / 0

[JBoss JIRA] Created: (JBRULES-1649) Queryresult.getFactHandles() returns bad handles

by Jaroslaw Kijanowski (JIRA)

Queryresult.getFactHandles() returns bad handles ------------------------------------------------ Key: JBRULES-1649 URL: http://jira.jboss.com/jira/browse/JBRULES-1649 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7, 5.0.0-M1 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor This is present in 4.0.7 and trunk (rev. 20565) I have following code: TestFact tf1 = new TestFact(); TestFact tf2 = new TestFact(); FactHandle factHandle1 = workingMemory.insert(tf1); FactHandle factHandle2 = workingMemory.insert(tf2); workingMemory.fireAllRules(); System.out.println("Expected:"); System.out.println(tf1); System.out.println(factHandle1); System.out.println(tf2); System.out.println(factHandle2); System.out.println("Received:"); QueryResults queryResults = workingMemory.getQueryResults("getTestFacts"); for ( Iterator it = queryResults.iterator(); it.hasNext(); ) { QueryResult result = ( QueryResult ) it.next(); System.out.println(result.get(0 )); System.out.println( result.getFactHandles()[0] ); } I would expect that result.getFactHandles() returns the same handle I got when I was inserting the fact into the workingmemory -- 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

15 years

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7593) Investigate org.jboss.test.spring.test.SpringClusterTestCase failure

by Brian Stansberry (JIRA)

Investigate org.jboss.test.spring.test.SpringClusterTestCase failure -------------------------------------------------------------------- Key: JBAS-7593 URL: https://jira.jboss.org/jira/browse/JBAS-7593 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Spring integration, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 Test fails because of this: Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [org.jboss.spring.cluster.CachePostProcessor] not found Offending resource: URL [vfszip:/home/bes/dev/jboss/trunk/testsuite/output/lib/spring-cluster-pojos.jar/META-INF/cluster-spring.xml] The class isn't found because it's not there; appears to have been dropped in the extraction of spring-int module. I'll check w/ Ales if he wants it. This test will eventually be removed, or perhaps repackaged to include POJO Cache in the deployment, as POJO Cache will not be included with AS 6 and the Infinispan we use with AS 6 will not include the kind of capabilities used by this CachePostProcessor class. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7596) Microcontainer does not always choose the right constructor when creating ModClusterService

by Paul Ferraro (JIRA)

Microcontainer does not always choose the right constructor when creating ModClusterService ------------------------------------------------------------------------------------------- Key: JBAS-7596 URL: https://jira.jboss.org/jira/browse/JBAS-7596 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: JBossAS-6.0.0.M2 A user encountered the following error when attempting to start EAP 5.0.0 w/mod_cluster 1.1.0.Beta1: 09:25:15,078 ERROR [AbstractKernelController] Error installing to Instantiated: name=ModClusterService state=Described mode=On Demand requiredState=Installed java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.modcluster.config.ModClusterConfig, org.jboss.modcluster.load.LoadBalanceFactorProviderFactory] actual=[org.jboss.modcluster.config.ha.HAModClusterConfig, org.jboss.modcluster.load.impl.DynamicLoadBalanceFactorProvider] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) The microcontainer is trying to instantiate ModClusterService using the wrong constructor. The mod_cluster-jboss-beans.xml should be updated to explicitly define the parameter types to remove this ambiguity. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-117) Unify Module Release Cycle

by Andrew Lee Rubinger (JIRA)

Unify Module Release Cycle -------------------------- Key: JBBOOT-117 URL: https://jira.jboss.org/jira/browse/JBBOOT-117 Project: JBoss Bootstrap Issue Type: Task Components: api, api-as, api-embedded, api-mc, build, impl-as, impl-base, impl-embedded, impl-mc, main, spi, spi-as, spi-mc Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Experiments in ShrinkWrap and EmbeddedAS have proven successful, so unify the jboss-bootstrap release cycle such that all modules share a version within the tree. As it currently stands, modules such as spi-test have outdated versions configured, and end up testing artifacts that are not the current SNAPSHOTs, leading to a false sense of security. -- 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

1
1
0 / 0

[JBoss JIRA] Updated: (GPD-376) candidate-groups info lost

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-376?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-376: -------------------------- Fix Version/s: jBPM jPDL Designer 4.4 (was: jBPM jPDL Designer 4.3) > candidate-groups info lost > -------------------------- > > Key: GPD-376 > URL: https://jira.jboss.org/jira/browse/GPD-376 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Joram Barrez > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.4 > > > When manually adding 'candidate-groups="administrator" ' to a task in the XML, this field is lost after having saved, gone back to the diagram and back to the xml. > Also the PNG is messed up. -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010