April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3298) NPE in ExpireJobContextTimerOutputMarshaller.write

by Drools User (Created) (JIRA)

NPE in ExpireJobContextTimerOutputMarshaller.write -------------------------------------------------- Key: JBRULES-3298 URL: https://issues.jboss.org/browse/JBRULES-3298 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.3.0.Final Reporter: Drools User Assignee: Mark Proctor Priority: Blocker {code} Caused by: java.lang.NullPointerException at org.drools.reteoo.ObjectTypeNode$ExpireJobContextTimerOutputMarshaller.write(ObjectTypeNode.java:639) at org.drools.marshalling.impl.OutputMarshaller.writeTimers(OutputMarshaller.java:1105) at org.drools.marshalling.impl.OutputMarshaller.writeSession(OutputMarshaller.java:172) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:142) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:125) at org.drools.persistence.SessionMarshallingHelper.getSnapshot(SessionMarshallingHelper.java:72) at org.drools.persistence.info.SessionInfo.update(SessionInfo.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.ejb.event.BeanCallback.invoke(BeanCallback.java:23) at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:80) at org.hibernate.ejb.event.EntityCallbackHandler.preUpdate(EntityCallbackHandler.java:65) at org.hibernate.ejb.event.EJB3FlushEntityEventListener.invokeInterceptor(EJB3FlushEntityEventListener.java:41) at org.hibernate.event.def.DefaultFlushEntityEventListener.handleInterception(DefaultFlushEntityEventListener.java:330) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:270) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:151) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:219) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:99) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:49) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1028) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:366) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:137) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) ... 34 more {code} -- 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3411) Incorrect rule activation in flow

by James Nord (JIRA)

James Nord created JBRULES-3411: ----------------------------------- Summary: Incorrect rule activation in flow Key: JBRULES-3411 URL: https://issues.jboss.org/browse/JBRULES-3411 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.1.Final Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000) Maven home: c:\Java\maven-3.0.3\bin\.. Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: c:\java\jdk1.6.0_24\jre Default locale: en_GB, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" Reporter: James Nord Assignee: Mark Proctor Attachments: Drools_flow bug.zip In the attached project the flow should always be terminated by the raising of a signal. That is the following should be printed to stdout when run (jtn.test.flow.ProcessTest) {noformat} pre sub process Raising Failure Signal Signal received! main exiting {noformat} However if you change the signal_abort_test_group1.drl file to not activate the "say hello" rule by either commenting it out or changing the eval(true) to eval false then the signal is not raised - as can be seen by the stdout {noformat} pre sub process post sub process pre human task main exiting {noformat} (and the showing of the HumanTaskUI) As the "say hello" rule does not change any state of the working memory it should be completely irrelavent if it is activated or not as to the path the flow takes. (a copy of the rule file is shown below but is included in the sample project) {code:title=signal_abort_test_group1.drl} package org.jbpm.examples.request import org.drools.runtime.process.WorkflowProcessInstance // if the whole rule is commented out the "Cancellation of request" is never run. rule "say hello" ruleflow-group "abort" when // if this is set to false then the "Cancellation of request" is never run. eval(false) then System.out.println("I'm alive"); end rule "Cancellation of request" ruleflow-group "abort" when p: WorkflowProcessInstance() then System.out.println("Raising Failure Signal"); kcontext.getKnowledgeRuntime().signalEvent("Failure", null, p.getId()); end {code} -- 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

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3307) Event does not expire when temporal operators are used.

by Scott Embler (Created) (JIRA)

Event does not expire when temporal operators are used. ------------------------------------------------------- Key: JBRULES-3307 URL: https://issues.jboss.org/browse/JBRULES-3307 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Final Environment: OS: Windows XP Java: 1.6.0_29 Reporter: Scott Embler Assignee: Mark Proctor Expectations: When rules use temporal operators to relate two events in time, it is expected that those both events will be expired when the session clock advances far enough. In the unit tests I have provided you'll see that there are two event types A and B. Each rule tries to relate these two events using a different temporal operator. After the rules match, both A and B should be expired, and a String should be inserted into working memory to signal to the test that the rule worked. Observed behavior: When A and B are inserted into their respective entry points the rules do match, and the appropriate String is inserted into working memory. B is also retracted. However A remains in working memory forever, causing heap space exceptions if there are many A's to process. It can also be seen using JMX that the computed event expiration for B is 0, and for A is the maximum long value. -- 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3458) Java 7 support in Drools Eclipse plugin

by Jan Gaspar (JIRA)

Jan Gaspar created JBRULES-3458: ----------------------------------- Summary: Java 7 support in Drools Eclipse plugin Key: JBRULES-3458 URL: https://issues.jboss.org/browse/JBRULES-3458 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.3.0.Final Reporter: Jan Gaspar Assignee: Mark Proctor I created a Drools project in Eclipse (Indigo) configured to use JRE 1.7. But I get an error pointing to my .drl file: com/sample/DroolsTest$Message : Unsupported major.minor version 51.0 The com.sample.DroolsTest.Message class is imported by the .drl file. The Drools runtime was 5.2.1 (also tried with 5.3.0.Final). Apparently Drools eclipse plugin expects the fact classes to be compiled with JDK6. Is there any way to make the plugin working with JDK7 compiled classes? -- 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-4651) NPE in logmanager

by Shane Bryzak (JIRA)

Shane Bryzak created AS7-4651: --------------------------------- Summary: NPE in logmanager Key: AS7-4651 URL: https://issues.jboss.org/browse/AS7-4651 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.1.Final Reporter: Shane Bryzak Assignee: James Perkins The logmanager is throwing a NPE when a null message is logged. The following line from com.sun.faces.facelets.impl.DefaultFaceletFactory seems to be the cause: log.log(Level.SEVERE, null, ex); Here's the stack trace: 07:59:57,339 ERROR [stderr] (http--127.0.0.1-8080-2) java.util.logging.ErrorManager: 5: Formatting error 07:59:57,340 ERROR [stderr] (http--127.0.0.1-8080-2) java.lang.NullPointerException 07:59:57,340 ERROR [stderr] (http--127.0.0.1-8080-2) at java.util.PropertyResourceBundle.handleGetObject(PropertyResourceBundle.java:136) 07:59:57,341 ERROR [stderr] (http--127.0.0.1-8080-2) at java.util.ResourceBundle.getObject(ResourceBundle.java:368) 07:59:57,341 ERROR [stderr] (http--127.0.0.1-8080-2) at java.util.ResourceBundle.getString(ResourceBundle.java:334) 07:59:57,341 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:366) 07:59:57,342 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:344) 07:59:57,342 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:357) 07:59:57,342 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:148) 07:59:57,343 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) 07:59:57,343 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) 07:59:57,344 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) 07:59:57,344 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:64) 07:59:57,344 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:283) 07:59:57,345 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,345 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,346 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,346 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,346 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,347 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,355 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) 07:59:57,358 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.Logger.logRaw(Logger.java:649) 07:59:57,358 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.logmanager.Logger.log(Logger.java:467) 07:59:57,359 ERROR [stderr] (http--127.0.0.1-8080-2) at com.sun.faces.facelets.impl.DefaultFaceletFactory.<init>(DefaultFaceletFactory.java:176) 07:59:57,359 ERROR [stderr] (http--127.0.0.1-8080-2) at com.sun.faces.facelets.impl.DefaultFaceletFactory.<init>(DefaultFaceletFactory.java:119) 07:59:57,361 ERROR [stderr] (http--127.0.0.1-8080-2) at org.jboss.seam.debug.jsf2.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:55) -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (LOGTOOL-47) Add custom stringifier option

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-47: ---------------------------------- Summary: Add custom stringifier option Key: LOGTOOL-47 URL: https://issues.jboss.org/browse/LOGTOOL-47 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 1.1.0.Beta1 Sometimes the default toString is no good for formatting an argument. We could introduce an interface into jboss-logging: {code} public interface Stringifier { String toString(Object object); } {code} Then we could introduce the following annotation: {code} @Retention(SOURCE) @Target(PARAMETER) public @interface FormatWith { Class<? extends Stringifier> value(); } {code} Parameters so annotated will be formatted using an instance (singleton, pre-instantiated with the logger instance) of the stringifier. Because of the method call overhead, such methods would require an explicit level check in the generated code. -- 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

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] (AS7-4646) Management Console needs to support FORM authentication

by Jess Sightler (JIRA)

Jess Sightler created AS7-4646: ---------------------------------- Summary: Management Console needs to support FORM authentication Key: AS7-4646 URL: https://issues.jboss.org/browse/AS7-4646 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Jess Sightler Assignee: Jason Greene Original code is: String referrer = responseHeaders.getFirst("Referrer"); But the HTTP Referer header is actually spelled "Referer". Pull request with fix is here: https://github.com/jbossas/jboss-as/pull/2139 -- 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

14 years, 3 months

3
20
0 / 0

[JBoss JIRA] (AS7-4666) Add support for versioning of serialization format of replicated data

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4666: --------------------------------- Summary: Add support for versioning of serialization format of replicated data Key: AS7-4666 URL: https://issues.jboss.org/browse/AS7-4666 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.2.Final-redhat1 -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-4457) API for registration and invocation of Resource transformers

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4457: ------------------------------------- Summary: API for registration and invocation of Resource transformers Key: AS7-4457 URL: https://issues.jboss.org/browse/AS7-4457 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 7.1.2.Final-redhat1 API extensions will use for registering their Resource transformation implementations. Registry for that information. API for accessing those resource transformers and doing the resource transformation during the host registraton process (e.g. from ReadMasterDomainModelHandler) -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3486) Planner Benchmarker: warmUp should also use parallelBenchmarkCount to run them on multiple threads

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3486: ----------------------------------------- Summary: Planner Benchmarker: warmUp should also use parallelBenchmarkCount to run them on multiple threads Key: JBRULES-3486 URL: https://issues.jboss.org/browse/JBRULES-3486 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Something that wasn't done for JBRULES-3393 -- 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

14 years, 3 months

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 April 2012