[JBoss JIRA] (WFLY-7281) IllegalStateException: DummyTransaction is not in a valid state to be invoking cache operations on
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7281?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-7281:
------------------------------------
I don't think there are any plans for a 10.2 release. 11.0 is scheduled to be released very soon.
> IllegalStateException: DummyTransaction is not in a valid state to be invoking cache operations on
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-7281
> URL: https://issues.jboss.org/browse/WFLY-7281
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> Occured on server during scenario eap-7x-failover-http-granular-shutdown-repl-sync.
> Server log stacktrace:
> {code}
> 23:04:41,857 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-97) ISPN000136: Error executing command GetKeyValueCommand, writing keys []: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=19027}, status=1} is not in a valid state to be invoking cache operations on.
> [JBossINF] at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:395)
> [JBossINF] at org.infinispan.interceptors.TxInterceptor.enlistIfNeeded(TxInterceptor.java:351)
> [JBossINF] at org.infinispan.interceptors.TxInterceptor.enlistReadAndInvokeNext(TxInterceptor.java:345)
> [JBossINF] at org.infinispan.interceptors.TxInterceptor.visitGetKeyValueCommand(TxInterceptor.java:331)
> [JBossINF] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
> [JBossINF] at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:85)
> [JBossINF] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> [JBossINF] at org.infinispan.statetransfer.StateTransferInterceptor.visitReadCommand(StateTransferInterceptor.java:177)
> [JBossINF] at org.infinispan.statetransfer.StateTransferInterceptor.visitGetKeyValueCommand(StateTransferInterceptor.java:154)
> [JBossINF] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> [JBossINF] at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:114)
> [JBossINF] at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:83)
> [JBossINF] at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:85)
> [JBossINF] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> [JBossINF] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
> [JBossINF] at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:85)
> [JBossINF] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:43)
> [JBossINF] at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:335)
> [JBossINF] at org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:411)
> [JBossINF] at org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:403)
> [JBossINF] at org.infinispan.cache.impl.AbstractDelegatingCache.get(AbstractDelegatingCache.java:286)
> [JBossINF] at org.wildfly.clustering.web.infinispan.session.fine.FineImmutableSessionAttributes.getAttribute(FineImmutableSessionAttributes.java:59)
> [JBossINF] at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.lambda$findListeners$13(InfinispanSessionManager.java:406)
> [JBossINF] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> [JBossINF] at java.util.concurrent.ConcurrentHashMap$KeySpliterator.forEachRemaining(ConcurrentHashMap.java:3527)
> [JBossINF] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> [JBossINF] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> [JBossINF] at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> [JBossINF] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> [JBossINF] at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> [JBossINF] at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.findListeners(InfinispanSessionManager.java:406)
> [JBossINF] at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.triggerPrePassivationEvents(InfinispanSessionManager.java:389)
> [JBossINF] at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.close(InfinispanSessionManager.java:457)
> [JBossINF] at org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:80)
> [JBossINF] at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:814)
> [JBossINF] at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:572)
> [JBossINF] at io.undertow.servlet.spec.HttpServletResponseImpl.doErrorDispatch(HttpServletResponseImpl.java:171)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:327)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> [JBossINF] at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> [JBossINF] at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> [JBossINF] at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> [JBossINF] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668)
> [JBossINF] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668)
> [JBossINF] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668)
> [JBossINF] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> [JBossINF] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> [JBossINF] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207)
> [JBossINF] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:810)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> {code}
> Link to server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
> WARN occured on client at the same time:
> {code}
> 2016/09/21 23:04:41:857 EDT [WARN ][Runner - 1402] HOST dev220.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Link to client log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8635) Monitoring SessionTimeout of Specific SFSB
by Yogesh Vedpathak (JIRA)
[ https://issues.jboss.org/browse/WFLY-8635?page=com.atlassian.jira.plugin.... ]
Yogesh Vedpathak deleted WFLY-8635:
-----------------------------------
> Monitoring SessionTimeout of Specific SFSB
> ------------------------------------------
>
> Key: WFLY-8635
> URL: https://issues.jboss.org/browse/WFLY-8635
> Project: WildFly
> Issue Type: Feature Request
> Environment: JBoss EAP 7. WildFly 10
> Reporter: Yogesh Vedpathak
> Assignee: Stuart Douglas
> Priority: Optional
>
> Requirement is to monitor the SessionTimeout set for a Stateful Session Bean. Jboss gives a default timeout for session beans which can be monitored through CLI. SessionTimeout set for a specific bean, will either be in the bean code with annotaion or in the config files. This can not be monitored through JBoss.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1078) Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/ELY-1078?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated ELY-1078:
----------------------------
Fix Version/s: 1.1.0.Beta37
> Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException
> --------------------------------------------------------------------------
>
> Key: ELY-1078
> URL: https://issues.jboss.org/browse/ELY-1078
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta36
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.1.0.Beta37
>
>
> In case when implementation of {{asString(StringBuilder b)}} for MatchRule does not change length of passed parameter (which is 0) then 'java.lang.StringIndexOutOfBoundsException: String index out of range: -1' is thrown for calling {{MatchRule.toString()}} due to calling {{StringBuilder.setLength(-1)}}.
> e.g. MatchRule {{ALL}} in implementation {{asString(StringBuilder b)}} just returns passed parameter, which results to mentioned exception.
> Thrown exception:
> {code}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java:180)
> at java.lang.StringBuilder.setLength(StringBuilder.java:76)
> at org.wildfly.security.auth.client.MatchRule.toString(MatchRule.java:581)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8642) rewrite handler handles references to contextual values incorrect
by Markus Stier (JIRA)
Markus Stier created WFLY-8642:
----------------------------------
Summary: rewrite handler handles references to contextual values incorrect
Key: WFLY-8642
URL: https://issues.jboss.org/browse/WFLY-8642
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.1.0.Final
Environment: * Windows 10
* Wildfly 10.1.0 Final
Reporter: Markus Stier
Assignee: Stuart Douglas
Context:
A URL in the form of "http://somehost.org/path/a/b" should be rewritten to "http://somehost.org/newpath?param1=a¶m2=b"
The following filter should perform this rewrite:
{code}
<expression-filter name="rewrite-path" expression="regex('^/path/([^/]+)/(.*)/?$') -> rewrite('/newpath'); set(attribute='%{QUERY_STRING}', value='param1=$1&param2=$2'); done()"/>
{code}
Problem:
The output is (according to access-log);
{code}
somehost.org "GET /newpath?param1=b
{code}
* param1 is assigned to the value of $2
* param2 is dropped completly
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1537:
-------------------------------------
What you're doing wrong in your test case is unmarshalling the ksession against a kbase that is different from the one you used for marshalling. This is not allowed and if you need incremental compilation you should use the KieScanner.
I'm pasting below a simplified version of your test case. I tried it against master and it works as expected.
{code}
public static KieSession marshallAndUnmarshall(KieBase kbase, KieSession ksession, KieSessionConfiguration sessionConfig) {
// Serialize and Deserialize
try {
Marshaller marshaller = KieServices.Factory.get().getMarshallers().newMarshaller(kbase);
ByteArrayOutputStream baos = new ByteArrayOutputStream();
marshaller.marshall(baos, ksession);
marshaller = MarshallerFactory.newMarshaller( kbase );
ByteArrayInputStream bais = new ByteArrayInputStream(baos.toByteArray());
baos.close();
ksession = marshaller.unmarshall(bais, sessionConfig, null);
bais.close();
} catch (Exception e) {
e.printStackTrace();
fail("unexpected exception :" + e.getMessage());
}
return ksession;
}
@Test
public void testSnapshotRecoveryScheduledRulesPlain() throws Exception {
// DROOLS-1537
String drl = "package com.drools.restore.reproducer\n" +
"global java.util.List list;\n" +
"global java.util.List list2;\n" +
"rule R1\n" +
" timer (int: 20s)\n" +
" when\n" +
" $m : String( this == \"Hello World1\" )\n" +
" then\n" +
" list.add( $m );\n" +
" retract( $m );\n" +
"end\n" +
"rule R2\n" +
" timer (int: 30s)\n" +
" when\n" +
" $m : String( this == \"Hello World2\" )\n" +
" then\n" +
" list2.add( $m );\n" +
" retract( $m );\n" +
"end\n";
KieSessionConfiguration ksconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration();
ksconf.setOption( ClockTypeOption.get( ClockType.PSEUDO_CLOCK.getId() ) );
ksconf.setOption( TimedRuleExecutionOption.YES );
ksconf.setOption(TimerJobFactoryOption.get("trackable"));
ksconf.setOption(ClockTypeOption.get("pseudo"));
KieHelper helper = new KieHelper();
helper.addContent( drl, ResourceType.DRL );
KieBase kbase = helper.build( EventProcessingOption.STREAM );
KieSession ksession = kbase.newKieSession( ksconf, null );
PseudoClockScheduler timeService = (PseudoClockScheduler) ksession.<SessionClock> getSessionClock();
List list = new ArrayList();
ksession.setGlobal("list", list);
List list2 = new ArrayList();
ksession.setGlobal("list2", list2);
ksession.insert("Hello World1");
ksession.insert("Hello World2");
ksession.fireAllRules();
timeService.advanceTime(10500, TimeUnit.MILLISECONDS);
ksession = marshallAndUnmarshall( kbase, ksession, ksconf );
ksession.fireAllRules();
long accumulatedSleepTime = 0;
for (int i = 0; i < 6; i++) {
timeService.advanceTime(5050, TimeUnit.MILLISECONDS);
accumulatedSleepTime += 5050;
assertEquals( i < 1 ? 0 : 1, list.size() );
assertEquals( i < 3 ? 0 : 1, list2.size() );
}
}
{code}
However I've found a bug also in this. In fact if after deserialization I retake the pseudo clock instance from the deserialized ksession
{code}
PseudoClockScheduler timeService2 = (PseudoClockScheduler) ksession.<SessionClock> getSessionClock();
{code}
and then in the for loop I do the advance on this second instance I get an Exception like the one I'm pasting below. I'll investigate this further problem immediately.
{code}
11:08:41.029 [main] WARN o.d.c.t.impl.DefaultTimerJobInstance.call:81 - Unable to execute timer job!
org.kie.api.runtime.rule.ConsequenceException: Exception executing consequence for rule "R1" in com.drools.restore.reproducer: java.lang.NullPointerException
at org.drools.core.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) ~[classes/:na]
at org.drools.core.common.DefaultAgenda.handleException(DefaultAgenda.java:1256) ~[classes/:na]
at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:440) ~[classes/:na]
at org.drools.core.phreak.RuleExecutor.fireActivation(RuleExecutor.java:382) ~[classes/:na]
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:136) ~[classes/:na]
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:93) ~[classes/:na]
at org.drools.core.phreak.PhreakTimerNode$TimerAction.evaluateAndFireRule(PhreakTimerNode.java:441) ~[classes/:na]
at org.drools.core.phreak.PhreakTimerNode$TimerAction.execute(PhreakTimerNode.java:433) ~[classes/:na]
at org.drools.core.phreak.SynchronizedPropagationList$1.execute(SynchronizedPropagationList.java:51) ~[classes/:na]
at org.drools.core.common.DefaultAgenda.executeTask(DefaultAgenda.java:1169) ~[classes/:na]
at org.drools.core.phreak.SynchronizedPropagationList.addEntry(SynchronizedPropagationList.java:47) ~[classes/:na]
at org.drools.core.common.DefaultAgenda.addPropagation(DefaultAgenda.java:1268) ~[classes/:na]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.addPropagation(StatefulKnowledgeSessionImpl.java:2057) ~[classes/:na]
at org.drools.core.phreak.PhreakTimerNode$TimerNodeJob.execute(PhreakTimerNode.java:372) ~[classes/:na]
at org.drools.core.time.SelfRemovalJob.execute(SelfRemovalJob.java:34) ~[classes/:na]
at org.drools.core.time.impl.DefaultTimerJobInstance.call(DefaultTimerJobInstance.java:69) [classes/:na]
at org.drools.core.time.impl.DefaultTimerJobInstance.call(DefaultTimerJobInstance.java:30) [classes/:na]
at org.drools.core.time.impl.PseudoClockScheduler.runCallBacksAndIncreaseTimer(PseudoClockScheduler.java:208) [classes/:na]
at org.drools.core.time.impl.PseudoClockScheduler.advanceTime(PseudoClockScheduler.java:160) [classes/:na]
at org.drools.compiler.integrationtests.marshalling.MarshallingTest.testSnapshotRecoveryScheduledRulesPlain(MarshallingTest.java:2939) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_92]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_92]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_92]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_92]
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) [junit-4.12.jar:4.12]
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12]
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) [junit-4.12.jar:4.12]
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) [junit-4.12.jar:4.12]
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) [junit-4.12.jar:4.12]
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
at org.junit.runner.JUnitCore.run(JUnitCore.java:137) [junit-4.12.jar:4.12]
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) [junit-rt.jar:na]
at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:51) [junit-rt.jar:na]
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:237) [junit-rt.jar:na]
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) [junit-rt.jar:na]
Caused by: java.lang.NullPointerException: null
at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:427) ~[classes/:na]
... 39 common frames omitted
{code}
> Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-1537
> URL: https://issues.jboss.org/browse/DROOLS-1537
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.5.0.Final
> Reporter: Kay J
> Assignee: Mario Fusco
> Attachments: RestoreReproducer.java
>
>
> Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78
> Hello Drools users,
> I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic.
> I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1538) Work Item Definition: Validation does not reveal missing import
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-1538:
-----------------------------------
Summary: Work Item Definition: Validation does not reveal missing import
Key: DROOLS-1538
URL: https://issues.jboss.org/browse/DROOLS-1538
Project: Drools
Issue Type: Bug
Affects Versions: 7.0.0.CR2
Reporter: Jozef Marko
Assignee: Jozef Marko
Attachments: missingImportWorkItemDefinition.wid
The validation of work item definition is successful, even if the validated file misses import. As result of this, the Service Tasks are not loaded in the jbpm-designer. The problem is that user of jbpm-designer can hardly detect the root cause of the problem, because the validation of work item definition file was successful.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2724) Attribute protocol in authentication-configuration of Elytron subsystem is not used
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2724?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2724:
---------------------------------
Description:
When authentication-configuration in Elytron subsystem uses attribute {{protocol}} then value of this attribute is not used for outgoing connection. Attributes {{host}} and {{port}} are used correctly.
Following authentication-configuration of Elytron subsystem should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{protocol}} is not used:
{code}
<authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990">
<credential-reference clear-text="pass@123"/>
</authentication-configuration>
{code}
was:
When authentication-configuration in Elytron subsystem uses attribute {{protocol}} then value of this attribute is not used for outgoing connection. Attributes {{host}} and {{port}} are used correctly.
Following authentication-configuration of Elytron subsystem should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{protocol}} is not used:
{code}
<authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990">
<credential-reference clear-text="pass@123"/>
</authentication-configuration>
{code}
We request blocker because this issue blocks feature for RFE EAP7-568. Due to issue incorrect protocol can be unexpectedly used for outgoing connection, e.g. http can be used instead of https.
This issue is blocker for GA, not for testing.
> Attribute protocol in authentication-configuration of Elytron subsystem is not used
> -----------------------------------------------------------------------------------
>
> Key: WFCORE-2724
> URL: https://issues.jboss.org/browse/WFCORE-2724
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When authentication-configuration in Elytron subsystem uses attribute {{protocol}} then value of this attribute is not used for outgoing connection. Attributes {{host}} and {{port}} are used correctly.
> Following authentication-configuration of Elytron subsystem should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{protocol}} is not used:
> {code}
> <authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990">
> <credential-reference clear-text="pass@123"/>
> </authentication-configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2724) Attribute protocol in authentication-configuration of Elytron subsystem is not used
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2724?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2724:
---------------------------------
Affects Version/s: 3.0.0.Beta13
> Attribute protocol in authentication-configuration of Elytron subsystem is not used
> -----------------------------------------------------------------------------------
>
> Key: WFCORE-2724
> URL: https://issues.jboss.org/browse/WFCORE-2724
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When authentication-configuration in Elytron subsystem uses attribute {{protocol}} then value of this attribute is not used for outgoing connection. Attributes {{host}} and {{port}} are used correctly.
> Following authentication-configuration of Elytron subsystem should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{protocol}} is not used:
> {code}
> <authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990">
> <credential-reference clear-text="pass@123"/>
> </authentication-configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years