September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3146) timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession.

by winton xu (JIRA)

timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession. ---------------------------------------------------------------------------------------------------------------- Key: JBRULES-3146 URL: https://issues.jboss.org/browse/JBRULES-3146 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: winton xu Assignee: Mark Proctor Priority: Critical we can reproduce it by following steps. 1. create a knowledge session. and call the method 'fireAllRules()' 2. reload knowledge session. 3. crate and build a timer rule. 4. fire the timer rule. [Actual Result] the timer rule cannot work fine. [Expected Result] the timer rule can work fine. (please check the attachement 'TimerAndCalendarTest.java.txt') -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3213) DisposeCommand closes down all data structures and then persits them

by Mark Proctor (JIRA)

DisposeCommand closes down all data structures and then persits them -------------------------------------------------------------------- Key: JBRULES-3213 URL: https://issues.jboss.org/browse/JBRULES-3213 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Disposing is only for closing down resources, not deleting state n the remote server. At the moment it's closing down things, like timer service, which has a list of state to persist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3207) Getting 5.2.x Working Again after various merges

by Mark Proctor (JIRA)

Getting 5.2.x Working Again after various merges ------------------------------------------------ Key: JBRULES-3207 URL: https://issues.jboss.org/browse/JBRULES-3207 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3212) Spring is closing EntityManager early

by Mark Proctor (JIRA)

Spring is closing EntityManager early ------------------------------------- Key: JBRULES-3212 URL: https://issues.jboss.org/browse/JBRULES-3212 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMETA-338) Fix WS ref parsing & merging process

by Richard Opalka (JIRA)

Fix WS ref parsing & merging process ------------------------------------ Key: JBMETA-338 URL: https://issues.jboss.org/browse/JBMETA-338 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Affects Versions: 7.0.0.Beta12 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.0.0.Beta13 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1900) Inconsistent class space with package from javaee.api

by Thomas Diesler (JIRA)

Inconsistent class space with package from javaee.api ------------------------------------------------------ Key: AS7-1900 URL: https://issues.jboss.org/browse/AS7-1900 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3210) NPE in Fusion's BrokerExample since 5.3

by Geoffrey De Smet (JIRA)

NPE in Fusion's BrokerExample since 5.3 --------------------------------------- Key: JBRULES-3210 URL: https://issues.jboss.org/browse/JBRULES-3210 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Beta1 Reporter: Geoffrey De Smet Assignee: Edson Tirelli Priority: Critical Fix For: 5.3.0.CR1 {code} org.drools.runtime.rule.ConsequenceException: rule: Update stock price at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1100) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1029) at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1250) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:733) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:699) at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218) at org.drools.examples.broker.Broker.receive(Broker.java:71) at org.drools.examples.broker.events.EventFeeder$FeedJob.execute(EventFeeder.java:85) at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:151) at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:126) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@1ba4159 at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:996) at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:473) at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:365) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:298) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:306) at org.drools.base.ModifyInterceptor.doAfter(ModifyInterceptor.java:59) at org.mvel2.ast.InterceptorWrapper.getReducedValueAccelerated(InterceptorWrapper.java:38) at org.mvel2.MVELRuntime.execute(MVELRuntime.java:89) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:125) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:118) at org.mvel2.MVEL.executeExpression(MVEL.java:928) at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:105) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1090) ... 16 more Caused by: java.lang.NullPointerException at org.drools.core.util.RightTupleIndexHashTable.removeAdd(RightTupleIndexHashTable.java:321) at org.drools.reteoo.JoinNode.modifyRightTuple(JoinNode.java:229) at org.drools.reteoo.BetaNode.modifyObject(BetaNode.java:431) at org.drools.reteoo.JoinNode.modifyObject(JoinNode.java:463) at org.drools.reteoo.SingleObjectSinkAdapter.propagateModifyObject(SingleObjectSinkAdapter.java:68) at org.drools.reteoo.PropagationQueuingNode$ModifyAction.execute(PropagationQueuingNode.java:391) at org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:225) at org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:438) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:994) ... 28 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Updated: (AS7-1816) DC down, domain.sh with --cached-dc option doesn't start on slave node

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/AS7-1816?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated AS7-1816: ----------------------------------- Issue Type: Bug (was: Feature Request) Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha1) > DC down, domain.sh with --cached-dc option doesn't start on slave node > ---------------------------------------------------------------------- > > Key: AS7-1816 > URL: https://issues.jboss.org/browse/AS7-1816 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.0.1.Final > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Critical > Fix For: 7.1.0.Beta1 > > > I have local copy of the domain configuration (using -backup), file domain.cached-remote.xml exists. > Can't start domain.sh (with --cached-dc) when DC is down, script ends with could not connect to remote server error. > *Details:* > (Master instance = MI, slave instance = SI, both on the same machine, EAP6 instances copied into different directories) > MI> just start bin/domain.sh > SI: remove all domain/configuration/domain* (optional) > SI: change name attribute of host element in domain/configuration/host.xml > SI: change interfaces definition to public IP address in domain/configuration/host.xml > SI: change domain-controller definition to use remote domain controller (127.0.0.1 in my case) in domain/configuration/host.xml > SI: run bin/domain.sh --backup > MI> shutdown EAP6 instance > SI: shutdown EAP6 instance > SI: make sure file domain/configuration/domain.cached-remote.xml > SI: run bin/domain.sh --cached-dc > SI: there is error, DC couldn't be contacted > log: > {code} > [Host Controller] 09:01:06,861 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3 > [Host Controller] 09:01:11,980 WARN [org.jboss.as.domain.controller] (Controller Boot Thread) Could not connect to remote domain controller 127.0.0.1:9999 > [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) Exception in thread "Controller Boot Thread" java.lang.IllegalStateException: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms > [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:238) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:159) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:291) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:662) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) Caused by: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:144) > [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:221) > [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) ... 4 more > {code} > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1816) DC down, domain.sh with --cached-dc option doesn't start on slave node

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/AS7-1816?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated AS7-1816: ----------------------------------- Summary: DC down, domain.sh with --cached-dc option doesn't start on slave node (was: CLONE - DC down, domain.sh with --cached-dc option doesn't start on slave node) > DC down, domain.sh with --cached-dc option doesn't start on slave node > ---------------------------------------------------------------------- > > Key: AS7-1816 > URL: https://issues.jboss.org/browse/AS7-1816 > Project: Application Server 7 > Issue Type: Feature Request > Components: Scripts > Affects Versions: 7.0.1.Final > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Critical > Fix For: 7.1.0.Alpha1 > > > I have local copy of the domain configuration (using -backup), file domain.cached-remote.xml exists. > Can't start domain.sh (with --cached-dc) when DC is down, script ends with could not connect to remote server error. > *Details:* > (Master instance = MI, slave instance = SI, both on the same machine, EAP6 instances copied into different directories) > MI> just start bin/domain.sh > SI: remove all domain/configuration/domain* (optional) > SI: change name attribute of host element in domain/configuration/host.xml > SI: change interfaces definition to public IP address in domain/configuration/host.xml > SI: change domain-controller definition to use remote domain controller (127.0.0.1 in my case) in domain/configuration/host.xml > SI: run bin/domain.sh --backup > MI> shutdown EAP6 instance > SI: shutdown EAP6 instance > SI: make sure file domain/configuration/domain.cached-remote.xml > SI: run bin/domain.sh --cached-dc > SI: there is error, DC couldn't be contacted > log: > {code} > [Host Controller] 09:01:06,861 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3 > [Host Controller] 09:01:11,980 WARN [org.jboss.as.domain.controller] (Controller Boot Thread) Could not connect to remote domain controller 127.0.0.1:9999 > [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) Exception in thread "Controller Boot Thread" java.lang.IllegalStateException: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms > [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:238) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:159) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:291) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:662) > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) Caused by: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms > [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:144) > [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:221) > [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) ... 4 more > {code} > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-621) Update JASPI dependency to org.jboss.spec.javax.security.auth.message.jboss-jaspi-api_1.0_spec

by Stefan Guilhen (JIRA)

Update JASPI dependency to org.jboss.spec.javax.security.auth.message.jboss-jaspi-api_1.0_spec ---------------------------------------------------------------------------------------------- Key: SECURITY-621 URL: https://issues.jboss.org/browse/SECURITY-621 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: PicketBox_v4_0_2 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: PicketBox_v4_0_3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
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 September 2011