July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4347) Produce a snapshot on demand

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4347?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4347: --------------------------------------- Sprint: 2019 Week 29-31 > Produce a snapshot on demand > ---------------------------- > > Key: DROOLS-4347 > URL: https://issues.jboss.org/browse/DROOLS-4347 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-1849) WildFlyElytronSaslDigestProvider does not register necessary password factories

by Tristan Tarrant (Jira)

Tristan Tarrant created ELY-1849: ------------------------------------ Summary: WildFlyElytronSaslDigestProvider does not register necessary password factories Key: ELY-1849 URL: https://issues.jboss.org/browse/ELY-1849 Project: WildFly Elytron Issue Type: Bug Components: SASL Affects Versions: 1.10.0.CR3 Reporter: Tristan Tarrant Registering the DIGEST SASL mech with WildFlyElytronSaslDigestProvider does not register all the necessary password factories, causing the mech to fail with {{Caused by java.lang.IllegalStateException: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "digest-md5"}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4349) Use bootstrap and Drools for readinessProbe and livenessProbe

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4349: ------------------------------------------ Summary: Use bootstrap and Drools for readinessProbe and livenessProbe Key: DROOLS-4349 URL: https://issues.jboss.org/browse/DROOLS-4349 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1390) BlockingFailureCount not tracking IJ000655 errors in SemaphoreConcurrentLinkedDequeManagedConnectionPool

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/JBJCA-1390?page=com.atlassian.jira.plugin... ] Ivo Studensky reassigned JBJCA-1390: ------------------------------------ Assignee: Ivo Studensky > BlockingFailureCount not tracking IJ000655 errors in SemaphoreConcurrentLinkedDequeManagedConnectionPool > -------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1390 > URL: https://issues.jboss.org/browse/JBJCA-1390 > Project: IronJacamar > Issue Type: Bug > Environment: JBoss Enterprise Application Platform 7 > Reporter: TJ Cowhey > Assignee: Ivo Studensky > Priority: Major > > The timeout counter increment performed in the [array list version of the pool|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.15.F...] is omitted from the [linked dequeue based version|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.1...]. > This results in BlockingFailureCount not tracking IJ000655 errors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4335) Allow to define sequence mode in kmodule.xml

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4335?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-4335: ------------------------------------- Implemented by https://github.com/kiegroup/droolsjbpm-knowledge/commit/c1c804211908c160f... and https://github.com/kiegroup/drools/commit/e7269644b9bdddece0f928e640e76b3... > Allow to define sequence mode in kmodule.xml > -------------------------------------------- > > Key: DROOLS-4335 > URL: https://issues.jboss.org/browse/DROOLS-4335 > Project: Drools > Issue Type: Feature Request > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Fix For: 7.25.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Klara Kufova resolved DROOLS-4161. ---------------------------------- Resolution: Done > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu commented on DROOLS-4161: --------------------------------- Thanks [~aglass][~kkufova], I think this task could been set as resolved.:) > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1446) EJB thread pool keepalive not honored and is not reusing inactive threads

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFCORE-1446?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFCORE-1446: ------------------------------- Description: Copied description from BZ1255494 : Description of problem: It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java -I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem.- was: Copied description from BZ1255494 : Description of problem: It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java -I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem. - > EJB thread pool keepalive not honored and is not reusing inactive threads > ------------------------------------------------------------------------- > > Key: WFCORE-1446 > URL: https://issues.jboss.org/browse/WFCORE-1446 > Project: WildFly Core > Issue Type: Bug > Reporter: Brad Maxwell > Assignee: Cheng Fang > Priority: Major > > Copied description from BZ1255494 : > Description of problem: > It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. > ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java > -I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem.- -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1446) EJB thread pool keepalive not honored and is not reusing inactive threads

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFCORE-1446?page=com.atlassian.jira.plugi... ] Cheng Fang reassigned WFCORE-1446: ---------------------------------- Assignee: Cheng Fang (was: Panagiotis Sotiropoulos) > EJB thread pool keepalive not honored and is not reusing inactive threads > ------------------------------------------------------------------------- > > Key: WFCORE-1446 > URL: https://issues.jboss.org/browse/WFCORE-1446 > Project: WildFly Core > Issue Type: Bug > Reporter: Brad Maxwell > Assignee: Cheng Fang > Priority: Major > > Copied description from BZ1255494 : > Description of problem: > It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. > ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java > I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1446) EJB thread pool keepalive not honored and is not reusing inactive threads

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFCORE-1446?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFCORE-1446: ------------------------------- Description: Copied description from BZ1255494 : Description of problem: It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java -I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem. - was: Copied description from BZ1255494 : Description of problem: It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem. > EJB thread pool keepalive not honored and is not reusing inactive threads > ------------------------------------------------------------------------- > > Key: WFCORE-1446 > URL: https://issues.jboss.org/browse/WFCORE-1446 > Project: WildFly Core > Issue Type: Bug > Reporter: Brad Maxwell > Assignee: Cheng Fang > Priority: Major > > Copied description from BZ1255494 : > Description of problem: > It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there. The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core. > ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java > -I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem. > - -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019