[JBoss JIRA] Created: (JBRULES-3150) NPE in ObjectTypeConfigurationRegistry when accumulate returns null (and "quick hack for 5.2")
by Wolfgang Laun (JIRA)
NPE in ObjectTypeConfigurationRegistry when accumulate returns null (and "quick hack for 5.2")
----------------------------------------------------------------------------------------------
Key: JBRULES-3150
URL: https://issues.jboss.org/browse/JBRULES-3150
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.1.Final
rule foo # the problem is usually better "hidden"
when
Object() from accumulate( Object(),
init( Object res = null; )
action( res = null; )
result( res ) )
then
end
causes the exception as shown below, or similar.
A runtime diagnostic should tell the user (at least) that
an accumulate result is null.
ALSO, PLEASE NOTE THIS COMMENT in AccumulateNode.java:642!
// this is a quick hack for the 5.2 release
Exception in thread "main" java.lang.NullPointerException
at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:58)
at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:646)
at org.drools.reteoo.AccumulateNode.assertLeftTuple(AccumulateNode.java:183)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:197)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.createAndPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:146)
at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:154)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:204)
at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:191)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:332)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:293)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:864)
at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:255)
at match.Main.makeFacts(Main.java:120)
at match.Main.execute(Main.java:98)
at match.Main.main(Main.java:126)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1054) The CallbackHandler is called multiple times on the client side with Remoting / Managent Interface
by Darran Lofthouse (JIRA)
The CallbackHandler is called multiple times on the client side with Remoting / Managent Interface
--------------------------------------------------------------------------------------------------
Key: AS7-1054
URL: https://issues.jboss.org/browse/AS7-1054
Project: Application Server 7
Issue Type: Bug
Components: Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Alpha1
This may be a side effect of the current problems where Remoting is looped to establish the connection but it means that we need to cache the users username and password from the first attempt so we don't keep prompting them - the problem then is we do not know if the subsequent call is because their values were invalid or just because of the retries.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1374) Domain Management - Ensure we keep Native connections alive where appropriate
by Darran Lofthouse (JIRA)
Domain Management - Ensure we keep Native connections alive where appropriate
-----------------------------------------------------------------------------
Key: AS7-1374
URL: https://issues.jboss.org/browse/AS7-1374
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
Establishing a connection can generally also involve negotiating the security before the connection is first used, this has the potential to become a major performance drain especially if the management load is high (management can be everything from updating the model to querying metrics).
This task is to ensure we keep the connections alive where it makes sense.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1102) Create PKCS#11 Compitable Cryptographic Services for Domain Management
by Darran Lofthouse (JIRA)
Create PKCS#11 Compitable Cryptographic Services for Domain Management
----------------------------------------------------------------------
Key: AS7-1102
URL: https://issues.jboss.org/browse/AS7-1102
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Fix For: 7.1.0.Beta1
Within domain management there are occasions where passwords need to be stored or keystores accessed either for encryption / decryption of password or to load the keys used for SSL exchanges.
Commonly a password within code is used for password based encryption of other passwords, this obfuscates the password but does not over complicate the process of recovering the password, alternatively a local keystore can be used for the encryption but again everything is available on the local disk to recover the password.
PKCS#11 will allow the cryptographic to be delegated to hardware which contains it's own protection against keys being made available.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-2005) Setting recursive="true" in management/outbound-connections/ldap results in Unexpected attribute 'recursive' encountered
by Darran Lofthouse (Created) (JIRA)
Setting recursive="true" in management/outbound-connections/ldap results in Unexpected attribute 'recursive' encountered
------------------------------------------------------------------------------------------------------------------------
Key: AS7-2005
URL: https://issues.jboss.org/browse/AS7-2005
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Security
Affects Versions: 7.0.2.Final
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
I noticed that setting recursive="true" in management/outbound-connections/ldap should be possible after jboss-as-config_1_0.xsd but on startup JBoss throws a parser exception:
22:45:47,704 ERROR [stderr] Exception in thread "Controller Boot Thread" java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
22:45:47,705 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:89)
22:45:47,705 ERROR [stderr] at java.lang.Thread.run(Thread.java:619)
22:45:47,705 ERROR [stderr] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
22:45:47,706 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:115)
22:45:47,706 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:104)
22:45:47,706 ERROR [stderr] at org.jboss.as.server.ServerService.boot(ServerService.java:195)
22:45:47,706 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83)
22:45:47,707 ERROR [stderr] ... 1 more
22:45:47,707 ERROR [stderr] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[69,4]
22:45:47,707 ERROR [stderr] Message: Unexpected attribute 'recursive' encountered
22:45:47,707 ERROR [stderr] at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:84)
22:45:47,707 ERROR [stderr] at org.jboss.as.controller.parsing.CommonXml.parseLdapConnection(CommonXml.java:501)
22:45:47,708 ERROR [stderr] at org.jboss.as.controller.parsing.CommonXml.parseConnections(CommonXml.java:448)
22:45:47,708 ERROR [stderr] at org.jboss.as.controller.parsing.CommonXml.parseManagement(CommonXml.java:413)
22:45:47,708 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:158)
22:45:47,708 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:91)
22:45:47,709 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:79)
22:45:47,709 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
22:45:47,709 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
22:45:47,709 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:107)
22:45:47,709 ERROR [stderr] ... 4 more
--
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
12 years, 6 months