March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ] Johnathon Lee updated JBJCA-1318: --------------------------------- Summary: list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker (was: property driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker) > list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker > ---------------------------------------------------------------------------- > > Key: JBJCA-1318 > URL: https://issues.jboss.org/browse/JBJCA-1318 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Reporter: Johnathon Lee > Assignee: Johnathon Lee > > Configuration/property defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker. > Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, .properties, etc or defined via a new structure in the standalone/domain configuration files. > Documentation updated to reflect suggested error codes for vendor based upon the current implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1318) property driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ] Johnathon Lee updated JBJCA-1318: --------------------------------- Summary: property driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker (was: property driven ExceptionSoter, StaleConnectionChecker & ValidConnectionChecker) > property driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker > -------------------------------------------------------------------------------- > > Key: JBJCA-1318 > URL: https://issues.jboss.org/browse/JBJCA-1318 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Reporter: Johnathon Lee > Assignee: Johnathon Lee > > Configuration/property defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker. > Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, .properties, etc or defined via a new structure in the standalone/domain configuration files. > Documentation updated to reflect suggested error codes for vendor based upon the current implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1318) property driven ExceptionSoter, StaleConnectionChecker & ValidConnectionChecker

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ] Jesper Pedersen reassigned JBJCA-1318: -------------------------------------- Assignee: Johnathon Lee (was: Jesper Pedersen) > property driven ExceptionSoter, StaleConnectionChecker & ValidConnectionChecker > ------------------------------------------------------------------------------- > > Key: JBJCA-1318 > URL: https://issues.jboss.org/browse/JBJCA-1318 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Reporter: Johnathon Lee > Assignee: Johnathon Lee > > Configuration/property defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker. > Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, .properties, etc or defined via a new structure in the standalone/domain configuration files. > Documentation updated to reflect suggested error codes for vendor based upon the current implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1318) property driven ExceptionSoter, StaleConnectionChecker & ValidConnectionChecker

by Johnathon Lee (JIRA)

Johnathon Lee created JBJCA-1318: ------------------------------------ Summary: property driven ExceptionSoter, StaleConnectionChecker & ValidConnectionChecker Key: JBJCA-1318 URL: https://issues.jboss.org/browse/JBJCA-1318 Project: IronJacamar Issue Type: Enhancement Components: JDBC Reporter: Johnathon Lee Assignee: Jesper Pedersen Configuration/property defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker. Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, .properties, etc or defined via a new structure in the standalone/domain configuration files. Documentation updated to reflect suggested error codes for vendor based upon the current implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1105) Publish kie-aries-blueprint and kie-spring XSDs to drools.org

by Petr Široký (JIRA)

Petr Široký created DROOLS-1105: ----------------------------------- Summary: Publish kie-aries-blueprint and kie-spring XSDs to drools.org Key: DROOLS-1105 URL: https://issues.jboss.org/browse/DROOLS-1105 Project: Drools Issue Type: Task Components: build Affects Versions: 6.4.0.CR2 Reporter: Petr Široký Assignee: Petr Široký {{kie-aries-blueprint}} and {{kie-spring}} XSDs should be published alongside the kie-module XSD at drools.org/xsd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1447) Patch with wrong upgrade name should not be accepted

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1447?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFCORE-1447: ------------------------------------------ Assignee: Bartosz Baranowski > Patch with wrong upgrade name should not be accepted > ---------------------------------------------------- > > Key: WFCORE-1447 > URL: https://issues.jboss.org/browse/WFCORE-1447 > Project: WildFly Core > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1104) Smoke tests need to use custom settings.xml to fetch the asset-mgmt jar

by Petr Široký (JIRA)

Petr Široký created DROOLS-1104: ----------------------------------- Summary: Smoke tests need to use custom settings.xml to fetch the asset-mgmt jar Key: DROOLS-1104 URL: https://issues.jboss.org/browse/DROOLS-1104 Project: Drools Issue Type: Enhancement Components: build Affects Versions: 6.4.0.CR2 Reporter: Petr Široký Assignee: Petr Široký Our kie-wb smoke tests (https://github.com/droolsjbpm/kie-wb-distributions/tree/master/kie-wb-smo...) need to use custom Maven settings.xml, which point to the KIE staging repositories. This is needed in order to fetch the asset-mgmt jar (avoiding tons of exceptions in the log). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1103) FireAllRules can trigger java.util.concurrent.RejectedExecutionException from the JDKTimerService

by Juan Carlos Garcia (JIRA)

Juan Carlos Garcia created DROOLS-1103: ------------------------------------------ Summary: FireAllRules can trigger java.util.concurrent.RejectedExecutionException from the JDKTimerService Key: DROOLS-1103 URL: https://issues.jboss.org/browse/DROOLS-1103 Project: Drools Issue Type: Bug Affects Versions: 6.3.0.Final Reporter: Juan Carlos Garcia Assignee: Mark Proctor Under very rare circumstance we have found the following exception *java.util.concurrent.RejectedExecutionException* in our production log. Our guess is that the Drools Session is on its way to be dispose, while a new incoming request is in the middle of a fireAllRules operation (race condition). I will try to provide a reproducible testcase for this. {code} Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3e896443 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@71cc2f4c[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326) at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:549) at org.drools.core.time.impl.JDKTimerService.internalSchedule(JDKTimerService.java:118) at org.drools.core.time.impl.JDKTimerService.scheduleJob(JDKTimerService.java:101) at org.drools.core.phreak.PhreakTimerNode.scheduleTimer(PhreakTimerNode.java:304) at org.drools.core.phreak.PhreakTimerNode.scheduleLeftTuple(PhreakTimerNode.java:233) at org.drools.core.phreak.PhreakTimerNode.doLeftUpdates(PhreakTimerNode.java:131) at org.drools.core.phreak.PhreakTimerNode.doNode(PhreakTimerNode.java:65) at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:357) at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:67) at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:935) at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1200) at org.drools.core.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:957) at org.drools.core.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:936) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:260) at XXXXXX.XXXXX.XXXXX.processEventDrools(EventProcessorImpl.java:128) at XXXXXX.XXXXX.XXXXX.processEvent(EventProcessorImpl.java:101) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.... ] Richard Opalka commented on WFLY-6375: -------------------------------------- >From Jigsaw ML: --- This link didn't work for me yesterday but it does now. The six modules that you have listed here are the EE modules that are in Java SE. If you compare the output of the following commands: java -limitmods java.se -listmods vs. java -limitmods java.se.ee -listmods then you'll see the same six. In all cases then the way to override/upgrade these to the EE version is to deploy the EE version of the module on the upgrade module path. In recent years then the need for app servers to upgrade JAXB and JAX-WS has diminished significantly so you might not need to upgrade both of those. -Alan --- > Identify colliding JBoss modules WRT JEP 200, section 6 > ------------------------------------------------------- > > Key: WFLY-6375 > URL: https://issues.jboss.org/browse/WFLY-6375 > Project: WildFly > Issue Type: Sub-task > Affects Versions: 10.0.0.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > > JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.... ] Richard Opalka edited comment on WFLY-6375 at 3/23/16 7:20 AM: --------------------------------------------------------------- >From Jigsaw ML: --- The six modules that you have listed here are the EE modules that are in Java SE. If you compare the output of the following commands: java -limitmods java.se -listmods vs. java -limitmods java.se.ee -listmods then you'll see the same six. In all cases then the way to override/upgrade these to the EE version is to deploy the EE version of the module on the upgrade module path. In recent years then the need for app servers to upgrade JAXB and JAX-WS has diminished significantly so you might not need to upgrade both of those. -Alan --- was (Author: ropalka): >From Jigsaw ML: --- This link didn't work for me yesterday but it does now. The six modules that you have listed here are the EE modules that are in Java SE. If you compare the output of the following commands: java -limitmods java.se -listmods vs. java -limitmods java.se.ee -listmods then you'll see the same six. In all cases then the way to override/upgrade these to the EE version is to deploy the EE version of the module on the upgrade module path. In recent years then the need for app servers to upgrade JAXB and JAX-WS has diminished significantly so you might not need to upgrade both of those. -Alan --- > Identify colliding JBoss modules WRT JEP 200, section 6 > ------------------------------------------------------- > > Key: WFLY-6375 > URL: https://issues.jboss.org/browse/WFLY-6375 > Project: WildFly > Issue Type: Sub-task > Affects Versions: 10.0.0.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > > JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016