June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4244) Test Scenario: test tool dock is not automatically opened when click on header

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4244: ------------------------------------- Summary: Test Scenario: test tool dock is not automatically opened when click on header Key: DROOLS-4244 URL: https://issues.jboss.org/browse/DROOLS-4244 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Yeser Amer When user click on header cell, test tool dock should be opened and focused -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4243) Test Scenario: rule scenarios with maps are failing

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4243: ------------------------------------- Summary: Test Scenario: rule scenarios with maps are failing Key: DROOLS-4243 URL: https://issues.jboss.org/browse/DROOLS-4243 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12236) Log spam in category org.apache.activemq.audit.base

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12236?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12236: --------------------------------- Workaround Description: Configure the logging subsystem to limit the offending category to WARN or higher severity: {code} <logger category="org.apache.activemq.audit.base"> <level name="WARN"/> </logger> {code} CLI examples for both the {{org.apache.activemq.audit.base}} and {{org.apache.activemq.audit.message}} categories. {code} /subsystem=logging/logger=org.apache.activemq.audit.base:add(level=WARN) /subsystem=logging/logger=org.apache.activemq.audit.message:add(level=WARN) {code} was: Configure the logging subsystem to limit the offending category to WARN or higher severity: {code} <logger category="org.apache.activemq.audit.base"> <level name="WARN"/> </logger> {code} > Log spam in category org.apache.activemq.audit.base > --------------------------------------------------- > > Key: WFLY-12236 > URL: https://issues.jboss.org/browse/WFLY-12236 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Final > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 18.0.0.Beta1 > > > Artemis is spamming the logs with what look like low-level messages, but recorded at INFO level: > {code} > 14:43:29,427 INFO [org.apache.activemq.audit.base] (Thread-40 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@39c78b17)) AMQ601265: User 4dd3d543-be6a-4a9a-b5d2-5cac9efe8f0f is creating a core consumer on target resource ServerSessionI mpl(jms-session=*N/A*) [with parameters: [175, jms.queue.DCS_DEV.processDcsIntegrationQueue, null, 0, false, true, null]] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12236) Log spam in category org.apache.activemq.audit.base

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12236?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-12236: -------------------------------------- We probably also want to do the same config change for {{org.apache.activemq.audit.message}} which is part of the same audit logger. > Log spam in category org.apache.activemq.audit.base > --------------------------------------------------- > > Key: WFLY-12236 > URL: https://issues.jboss.org/browse/WFLY-12236 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Final > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 18.0.0.Beta1 > > > Artemis is spamming the logs with what look like low-level messages, but recorded at INFO level: > {code} > 14:43:29,427 INFO [org.apache.activemq.audit.base] (Thread-40 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@39c78b17)) AMQ601265: User 4dd3d543-be6a-4a9a-b5d2-5cac9efe8f0f is creating a core consumer on target resource ServerSessionI mpl(jms-session=*N/A*) [with parameters: [175, jms.queue.DCS_DEV.processDcsIntegrationQueue, null, 0, false, true, null]] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11255: ----------------------------------- Component/s: (was: EE) > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11255: ----------------------------------- Component/s: Concurrency Utilities > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Components: Concurrency Utilities > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins reassigned WFLY-11255: -------------------------------------- Assignee: Eduardo Martins > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3515) [DMN Designer] Validation: Validate button should compile the DMN file and report issues

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3515?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-3515: ---------------------------------- Writer: Stetson Robinson > [DMN Designer] Validation: Validate button should compile the DMN file and report issues > ---------------------------------------------------------------------------------------- > > Key: DROOLS-3515 > URL: https://issues.jboss.org/browse/DROOLS-3515 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Thomas Mantegazzi > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-01-14-09-24-07-415.png, image-2019-01-14-09-25-01-777.png, image-2019-01-14-09-25-16-907.png > > > The "validate" button at the top does nit seem to be validating feel expressions: > !image-2019-01-14-09-24-07-415.png|thumbnail! > The input of this Decision is a "person" object: > !image-2019-01-14-09-25-01-777.png|thumbnail! > and this is the DRG: > !image-2019-01-14-09-25-16-907.png|thumbnail! > The validation should say that this literal expression is not valid. > h2. Acceptance test > Validation button should report > - Non existing variable name (/) > - Existing variable name, but not connected (/) > - Invalid operator (+++, &&, ..) (/) > - Unknown keyword (switch) (/) > - Multiple diagrams opened (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-204) JAX-RS FactoryFinder failing resolution using ServiceLoader with secMgr enabled

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/JBEE-204?page=com.atlassian.jira.plugin.s... ] Alessio Soldano resolved JBEE-204. ---------------------------------- Fix Version/s: jboss-jaxrs-api-2.1_1.0.3.Final Resolution: Done > JAX-RS FactoryFinder failing resolution using ServiceLoader with secMgr enabled > ------------------------------------------------------------------------------- > > Key: JBEE-204 > URL: https://issues.jboss.org/browse/JBEE-204 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: jboss-jaxrs-api-2.1_1.0.3.Final > > > From JBEAP-17069: > When the security manager is enabled the resteasy client initialization fails with the following exception: > {noformat} > ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /resteasy/SampleServlet: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" version 1.0.1.Final-redhat-00001 from local module loader @69d9c55 (finder: local module finder @13a57a3b (roots: /opt/jboss/jboss-eap-7.2/modules,/opt/jboss/jboss-eap-7.2/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.1.CP,/opt/jboss/jboss-eap-7.2/modules/system/layers/base))] > at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:132) > at com.redhat.sample.SampleServlet.processRequest(SampleServlet.java:29) > at com.redhat.sample.SampleServlet.doGet(SampleServlet.java:48) > ... > Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" version 1.0.1.Final-redhat-00001 from local module loader @69d9c55 (finder: local module finder @13a57a3b (roots: /opt/jboss/jboss-eap-7.2/modules,/opt/jboss/jboss-eap-7.2/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.1.CP,/opt/jboss/jboss-eap-7.2/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:120) > at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:227) > at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:96) > ... 52 more > {noformat} > It seems that the issue is that the internal resteasy class is not found and the default {{org.glassfish.jersey.client.JerseyClientBuilder}} is tried but fails. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4242) NPE in Kogito Quickstart: broken codegen

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4242: -------------------------------------- Summary: NPE in Kogito Quickstart: broken codegen Key: DROOLS-4242 URL: https://issues.jboss.org/browse/DROOLS-4242 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Fix For: 8.0.0.Final kogito-codegen erroneously expects a field to be injected but the class is instantiated explicitly. Should either inject the parent class or instantiate the missing field explicitly -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 June 2019