September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3167) Null pointer exception with multithread enabled

by Pascal de Kloe (JIRA)

Null pointer exception with multithread enabled ----------------------------------------------- Key: JBRULES-3167 URL: https://issues.jboss.org/browse/JBRULES-3167 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.Final Reporter: Pascal de Kloe Assignee: Mark Proctor ******************************************************************************************************* Partition task manager caught an unexpected exception: null Drools is capturing the exception to avoid thread death. Please report stack trace to development team. java.lang.NullPointerException at org.drools.core.util.LeftTupleIndexHashTable.remove(LeftTupleIndexHashTable.java:285) at org.drools.reteoo.NotNode.assertObject(NotNode.java:144) at org.drools.reteoo.PartitionTaskManager$FactAssertAction.execute(PartitionTaskManager.java:272) at org.drools.reteoo.PartitionTaskManager$PartitionTask.run(PartitionTaskManager.java:116) at org.drools.concurrent.ExternalExecutorService$ObservableRunnable.run(ExternalExecutorService.java:443) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3194) Generate invoker classes with ASM

by Mario Fusco (JIRA)

Generate invoker classes with ASM --------------------------------- Key: JBRULES-3194 URL: https://issues.jboss.org/browse/JBRULES-3194 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Generate invoker classes with ASM -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3203) JMSTaskClientConnector doesn't dequeue received messages

by Frank23 Knoll23 (JIRA)

JMSTaskClientConnector doesn't dequeue received messages -------------------------------------------------------- Key: JBRULES-3203 URL: https://issues.jboss.org/browse/JBRULES-3203 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: apache-activemq-5.5.0 as a JMS provider Reporter: Frank23 Knoll23 Assignee: Mark Proctor Hi, org.jbpm.task.service.jms.JMSTaskClientConnector doesn't dequeue received messages from it's responseQueue. Cheers, Frank -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3222) Error unmarshalling knowledgeSession with Facts inserted in entry-points

by Stefan Wehner (JIRA)

Error unmarshalling knowledgeSession with Facts inserted in entry-points ------------------------------------------------------------------------ Key: JBRULES-3222 URL: https://issues.jboss.org/browse/JBRULES-3222 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1, 5.2.0.Final Reporter: Stefan Wehner Assignee: Mark Proctor When trying to marshall and then unmarshall a StatefulKnowledgeSession where a Fact has been inserted into an entry-point a NullPointerException is thrown: java.lang.NullPointerException at org.drools.reteoo.RuleTerminalNodeLeftTuple.<init>(RuleTerminalNodeLeftTuple.java:151) at org.drools.reteoo.RuleTerminalNode.createLeftTuple(RuleTerminalNode.java:608) at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarshaller.java:523) at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMarshaller.java:373) at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshaller.java:230) at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarshaller.java:92) at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarshaller.java:63) at com.sample.DroolsTest.main(DroolsTest.java:50) Provided is a testcase with two simple rules matching Fact objects directly and from the entry-point "facts". A fact is inserted directly into the knowledgeSession and then it is marshalled and unmarshalled - which works fine. Then a fact is inserted into a entry-point "facts" and the session is marshalled and unmarshalled - which throws the NPE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (SECURITY-617) PicketBoxSecurityVault should consider system property for Keystore URL

by Anil Saldhana (JIRA)

PicketBoxSecurityVault should consider system property for Keystore URL ----------------------------------------------------------------------- Key: SECURITY-617 URL: https://issues.jboss.org/browse/SECURITY-617 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v4_0_2 Reporter: Anil Saldhana Assignee: Anil Saldhana Currently only the enc dir can take in system prop. we need to that for the keystore url too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1971) Better base class for write-attribute handlers

by Brian Stansberry (JIRA)

Better base class for write-attribute handlers ---------------------------------------------- Key: AS7-1971 URL: https://issues.jboss.org/browse/AS7-1971 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 ServerWriteAttributeOperationHandler isn't a very nice base for a write-attribute handler. 1) It does stuff in Stage.MODEL (validateResolvedValue()) that should be in Stage.RUNTIME. 2) It forces subclasses to register a Stage.RUNTIME handler, instead of providing that for them. 3) It doesn't provide very good support for handling rollbacks of runtime changes. 4) It's in the server module instead of controller. I'm going to add a new AbstractWriteAttributeHandler in controller, deprecate ServerWriteAttributeOperationHandler, and convert all existing uses of it in the AS code base. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1554) Upgrade felix webconsole to remove dep 3.1.6.SP1

by Thomas Diesler (JIRA)

Upgrade felix webconsole to remove dep 3.1.6.SP1 ------------------------------------------------ Key: AS7-1554 URL: https://issues.jboss.org/browse/AS7-1554 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.CR1 > There is no version 3.1.6.SP1 of webconsole in SCM Its here https://github.com/tdiesler/org.apache.felix.webconsole/commits/3.1.6.SP1/ > And should we switch to 3.1.8 which appears to be the latest version? Not unless AS7 pulls in that version. A prerequisite would be that my patches made it upstream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1709) Client JNDI support for AS7

by Carlo de Wolf (JIRA)

Client JNDI support for AS7 --------------------------- Key: AS7-1709 URL: https://issues.jboss.org/browse/AS7-1709 Project: Application Server 7 Issue Type: Task Components: Naming Reporter: Carlo de Wolf Assignee: John Bailey Priority: Critical Fix For: 7.1.0.CR1 The following use case are applicable both to a remote/client VM and within AS7 itself. The configuration of the initial context is not specified in here, it'll be a resultant of this task and outlined in some documentation. Note that any {code}InitialContext ctx = new InitialContext();{code} might need {code}InitialContext ctx = new InitialContext(props);{code} where the actual contents of {{props}} is currently unspecified. h3. Calling AS7 It *must* be possible for a client to call AS7 via the following code: {code} InitialContext ctx = new InitialContext(); MyRemote bean = ctx.lookup("java:myserver1/myapp/myjar/myBean#MyRemote"); {code} h3. Calling different AS7 instances It *should* be possible for a client to call two different AS7 instances via the following code: {code} InitialContext ctx = new InitialContext(); MyRemote bean = ctx.lookup("java:myserver1/myapp/myJar/OtherBean#MyRemote"); OtherRemote bean2 = ctx.lookup("java:myserver2/otherapp/otherjar/OtherBean2#OtherRemote"); {code} Whether security and transaction propagation between the servers is available or possible is left beyond scope. h3. Calling different type/version of servers It *may* be possible for a client to call two different EAP versions via the following code: {code} InitialContext ctx = new InitialContext(); MyRemote bean = ctx.lookup("java:myEAP6/myapp/myJar/OtherBean#MyRemote"); OtherRemote bean2 = ctx.lookup("java:myEAP5/otherapp/otherjar/OtherBean2#OtherRemote"); {code} The last one would require a context to be associated with a certain module to load the proper client classes. See also http://wolf-71.blogspot.com/2010/02/et-phone-home.html Whether security and transaction propagation between the servers is available or possible is left beyond scope. Also the propagation of the current established tx/sec context might not be available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1923) Rule order counts when adding inheriting rules

by Toni Rikkola (JIRA)

Rule order counts when adding inheriting rules ---------------------------------------------- Key: JBRULES-1923 URL: https://jira.jboss.org/jira/browse/JBRULES-1923 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: FUTURE Reporter: Toni Rikkola Assignee: Mark Proctor When inheriting rules, the order they are written to DRL counts. dward noticed this when using Guvnor. There is no way to control the order of the rules in Guvnor, so because of this inheritance doesn't always work. This works: rule A when ... then end rule B extends A when ... then end This doesn't work: rule B extends A when ... then end rule A when ... then end -- 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

13 years

5
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener

by Justin Bertram (JIRA)

Failed fail-over doesn't trigger client's ExceptionListener ----------------------------------------------------------- Key: JBMESSAGING-1855 URL: https://issues.jboss.org/browse/JBMESSAGING-1855 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP09 Reporter: Justin Bertram Assignee: Yong Hao Gao If the cluster node to which a client is connected is dropped gracefully and the cluster is using FailoverOnNodeLeave = false then the client's connection will die and its exception listener will not be triggered so it may manually reconnect to another node of the cluster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011