October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12708) Upgrade saaj api to 1.0.1.Final

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/WFLY-12708?page=com.atlassian.jira.plugin... ] Jim Ma updated WFLY-12708: -------------------------- Description: This upgrade mainly fix this issue: when jboss module class in classpath and there is no jboss modules exists , it is unable to load jboss module 'org.jboss.ws.saaj-impl' and stops trying to load SAAJFactory from flat classpath. > Upgrade saaj api to 1.0.1.Final > ------------------------------- > > Key: WFLY-12708 > URL: https://issues.jboss.org/browse/WFLY-12708 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Affects Versions: 18.0.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 19.0.0.Beta1 > > > This upgrade mainly fix this issue: > when jboss module class in classpath and there is no jboss modules exists , it is unable to load jboss module 'org.jboss.ws.saaj-impl' and stops trying to load SAAJFactory from flat classpath. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-422) Timer based rules don't fire and facts can't expire after session restore

by Maksim Drobyshev (Jira)

[ https://issues.jboss.org/browse/DROOLS-422?page=com.atlassian.jira.plugin... ] Maksim Drobyshev edited comment on DROOLS-422 at 10/28/19 12:07 AM: -------------------------------------------------------------------- Do you have any news about this bug? We have the same issue with KieSession deserialization. [~mark.proctor] can you help me? was (Author: d.max): Do you have any news about this bug? We have the same issue with KieSession deserialization. > Timer based rules don't fire and facts can't expire after session restore > ------------------------------------------------------------------------- > > Key: DROOLS-422 > URL: https://issues.jboss.org/browse/DROOLS-422 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > JBoss AS 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Priority: Major > Attachments: drools-mongodb-persistence.zip > > > I have implemented a custom persistence engine for Drools sessions in MongoDB. When session is built for first time, everything works like a charm. I am having some problems when Drools sessions are restored from MongoDB collection. Firstly, interval based rules (for example timer(int: 10s 10s)) don't fire. Some facts that should expire, they just don't expire and remain forever in WM. I attached the source code. When session is built for first time, I use code like this: > KnowledgeBase kbase = createKBase(getKnowledgeBuilder(rulePackagePath), > config); > if (hasKnowledgeAgent) { > > createKnowledgeAgent(kbase, correlatorId); > > wm = (ReteooStatefulSession) ((KnowledgeBaseImpl) kagent > .getKnowledgeBase()).ruleBase.newStatefulSession( > (SessionConfiguration) ksconf, env); > ksession = new StatefulKnowledgeSessionImpl(wm, kagent > .getKnowledgeBase()); > > stateOutputMarshaller = StateMarshallerFactory.newOutputMarshaller(this, ksession, ksconf); > stateOutputMarshaller.init(); > ((InternalKnowledgeRuntime) ksession).setEndOperationListener(this); > } > Then, after every action I update the session in MongoDB collection. > public void endOperation(InternalKnowledgeRuntime ikr) { > > stateOutputMarshaller.marshall(); > } > For session restoring, after AS restart I use this code: > KnowledgeBase kbase = createKBase( getKnowledgeBuilder(rulePackagePath), getKBaseConfig() ); > stateInputMarshaller = StateMarshallerFactory.newInputMarshaller( this, kbase, getSessionConf() ); > ksession = stateInputMarshaller.unmarshall(correlatorId); > stateOutputMarshaller = StateMarshallerFactory.newOutputMarshaller( this, ksession, getSessionConf() ); > > ((InternalKnowledgeRuntime)ksession).setEndOperationListener(this); > > protected static KnowledgeBaseConfiguration getKBaseConfig() { > KnowledgeBaseConfiguration config = KnowledgeBaseFactory > .newKnowledgeBaseConfiguration(); > config.setOption(EventProcessingOption.STREAM); > return config; > } > protected static KnowledgeSessionConfiguration getSessionConf() { > KnowledgeSessionConfiguration ksconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ksconf.setOption(ClockTypeOption.get("realtime")); > return ksconf; > } > Any help is appreciated. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-422) Timer based rules don't fire and facts can't expire after session restore

by Maksim Drobyshev (Jira)

[ https://issues.jboss.org/browse/DROOLS-422?page=com.atlassian.jira.plugin... ] Maksim Drobyshev commented on DROOLS-422: ----------------------------------------- Do you have any news about this bug? We have the same issue with KieSession deserialization. > Timer based rules don't fire and facts can't expire after session restore > ------------------------------------------------------------------------- > > Key: DROOLS-422 > URL: https://issues.jboss.org/browse/DROOLS-422 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > JBoss AS 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Priority: Major > Attachments: drools-mongodb-persistence.zip > > > I have implemented a custom persistence engine for Drools sessions in MongoDB. When session is built for first time, everything works like a charm. I am having some problems when Drools sessions are restored from MongoDB collection. Firstly, interval based rules (for example timer(int: 10s 10s)) don't fire. Some facts that should expire, they just don't expire and remain forever in WM. I attached the source code. When session is built for first time, I use code like this: > KnowledgeBase kbase = createKBase(getKnowledgeBuilder(rulePackagePath), > config); > if (hasKnowledgeAgent) { > > createKnowledgeAgent(kbase, correlatorId); > > wm = (ReteooStatefulSession) ((KnowledgeBaseImpl) kagent > .getKnowledgeBase()).ruleBase.newStatefulSession( > (SessionConfiguration) ksconf, env); > ksession = new StatefulKnowledgeSessionImpl(wm, kagent > .getKnowledgeBase()); > > stateOutputMarshaller = StateMarshallerFactory.newOutputMarshaller(this, ksession, ksconf); > stateOutputMarshaller.init(); > ((InternalKnowledgeRuntime) ksession).setEndOperationListener(this); > } > Then, after every action I update the session in MongoDB collection. > public void endOperation(InternalKnowledgeRuntime ikr) { > > stateOutputMarshaller.marshall(); > } > For session restoring, after AS restart I use this code: > KnowledgeBase kbase = createKBase( getKnowledgeBuilder(rulePackagePath), getKBaseConfig() ); > stateInputMarshaller = StateMarshallerFactory.newInputMarshaller( this, kbase, getSessionConf() ); > ksession = stateInputMarshaller.unmarshall(correlatorId); > stateOutputMarshaller = StateMarshallerFactory.newOutputMarshaller( this, ksession, getSessionConf() ); > > ((InternalKnowledgeRuntime)ksession).setEndOperationListener(this); > > protected static KnowledgeBaseConfiguration getKBaseConfig() { > KnowledgeBaseConfiguration config = KnowledgeBaseFactory > .newKnowledgeBaseConfiguration(); > config.setOption(EventProcessingOption.STREAM); > return config; > } > protected static KnowledgeSessionConfiguration getSessionConf() { > KnowledgeSessionConfiguration ksconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ksconf.setOption(ClockTypeOption.get("realtime")); > return ksconf; > } > Any help is appreciated. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-132) Add a ConnectionValidator with timeout.

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-132?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-132. ---------------------------- > Add a ConnectionValidator with timeout. > --------------------------------------- > > Key: AG-132 > URL: https://issues.jboss.org/browse/AG-132 > Project: Agroal > Issue Type: Feature Request > Components: api > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > > Provide a method to create a Connectionvalidator with a timeout, as currently a connection could become stuck in validation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-130) Add new callback for 'info' messages.

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-130?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-130. ---------------------------- > Add new callback for 'info' messages. > ------------------------------------- > > Key: AG-130 > URL: https://issues.jboss.org/browse/AG-130 > Project: Agroal > Issue Type: Bug > Components: api, pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > > Some warning messages can create unjustified concerns on users. For that case create a new 'info' method on the listener interface. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-129) Fix JDBC leak report

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-129?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-129. ---------------------------- > Fix JDBC leak report > -------------------- > > Key: AG-129 > URL: https://issues.jboss.org/browse/AG-129 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-133) Fix initialization info messages

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-133?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-133. ---------------------------- > Fix initialization info messages > -------------------------------- > > Key: AG-133 > URL: https://issues.jboss.org/browse/AG-133 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-133) Fix initialization info messages

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-133?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-133. ------------------------------ Resolution: Done > Fix initialization info messages > -------------------------------- > > Key: AG-133 > URL: https://issues.jboss.org/browse/AG-133 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-133) Fix initialization info messages

by Luis Barreiro (Jira)

Luis Barreiro created AG-133: -------------------------------- Summary: Fix initialization info messages Key: AG-133 URL: https://issues.jboss.org/browse/AG-133 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 1.6 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.7 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-132) Add a ConnectionValidator with timeout.

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-132?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-132. ------------------------------ Resolution: Done > Add a ConnectionValidator with timeout. > --------------------------------------- > > Key: AG-132 > URL: https://issues.jboss.org/browse/AG-132 > Project: Agroal > Issue Type: Feature Request > Components: api > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > > Provide a method to create a Connectionvalidator with a timeout, as currently a connection could become stuck in validation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 October 2019