April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4910) Log WARN if JBoss Logging Handler gets removed

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4910?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4910: ---------------------------------- Description: Spring Boot when add-logging-api-dependencies=false and jul-to-slf4j.jar is packaged in the app, that it will remove all handlers from the root logger, which includes JBoss Logging's Handler resulting in logging to stop. {code} 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.slf4j.bridge.SLF4JBridgeHandler.removeHandlersForRootLogger(SLF4JBridgeHandler.java:-1) 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.removeJdkLoggingBridgeHandler(Slf4JLoggingSystem.java:78) 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.configureJdkLoggingBridgeHandler(Slf4JLoggingSystem.java:61) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.beforeInitialize(Slf4JLoggingSystem.java:41) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.log4j2.Log4J2LoggingSystem.beforeInitialize(Log4J2LoggingSystem.java:136) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:231) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:210) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:122) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:69) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:48) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.SpringApplication.run(SpringApplication.java:292) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:156) 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:136) 20:37:01,191 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91) 20:37:01,191 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169) {code} > Log WARN if JBoss Logging Handler gets removed > ----------------------------------------------- > > Key: WFCORE-4910 > URL: https://issues.redhat.com/browse/WFCORE-4910 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: James Perkins > Priority: Major > > Spring Boot when add-logging-api-dependencies=false and jul-to-slf4j.jar is packaged in the app, that it will remove all handlers from the root logger, which includes JBoss Logging's Handler resulting in logging to stop. > {code} > 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.slf4j.bridge.SLF4JBridgeHandler.removeHandlersForRootLogger(SLF4JBridgeHandler.java:-1) > 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.removeJdkLoggingBridgeHandler(Slf4JLoggingSystem.java:78) > 20:37:01,188 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.configureJdkLoggingBridgeHandler(Slf4JLoggingSystem.java:61) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.Slf4JLoggingSystem.beforeInitialize(Slf4JLoggingSystem.java:41) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.log4j2.Log4J2LoggingSystem.beforeInitialize(Log4J2LoggingSystem.java:136) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:231) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:210) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) > 20:37:01,189 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:122) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:69) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:48) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.SpringApplication.run(SpringApplication.java:292) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:156) > 20:37:01,190 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:136) > 20:37:01,191 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91) > 20:37:01,191 INFO [stdout] (ServerService Thread Pool -- 79) org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1408) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Ilia Vassilev (Jira)

Ilia Vassilev created JBJCA-1408: ------------------------------------ Summary: Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown Key: JBJCA-1408 URL: https://issues.redhat.com/browse/JBJCA-1408 Project: IronJacamar Issue Type: Bug Reporter: Ilia Vassilev Assignee: Flavia Rainone By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 There is a constant error in server shutdown {code:xml} 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4908: ------------------------------------- Component/s: CLI [~jdenise] I put the CLI component on this as I think the odds are high that any problem is in the CLI. I'd be surprised if anything on the server side is manipulating the 'name' attribute of the operation ModelNode once it hits the server. > The write-attribute operation does not work on a hosts JVM resource > ------------------------------------------------------------------- > > Key: WFCORE-4908 > URL: https://issues.redhat.com/browse/WFCORE-4908 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management > Reporter: James Perkins > Assignee: Jeff Mesnil > Priority: Major > Labels: domain-mode > > Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected. > {code} > [domain@embedded /] /host=master/server-config=server-one/jvm=default:add > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"]) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource > { > "outcome" => "success", > "result" => { > "agent-lib" => undefined, > "agent-path" => undefined, > "debug-enabled" => undefined, > "debug-options" => undefined, > "env-classpath-ignored" => undefined, > "environment-variables" => undefined, > "heap-size" => undefined, > "java-agent" => undefined, > "java-home" => undefined, > "jvm-options" => undefined, > "launch-command" => undefined, > "max-heap-size" => undefined, > "max-permgen-size" => undefined, > "permgen-size" => undefined, > "stack-size" => undefined, > "type" => undefined > } > } > {code} > As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4746: ------------------------------------------- [~karreiro][~danielezonca] [~tirelli] I posted a draft wireframe: https://marvelapp.com/7208d3a This uses either the right click contextual menu, or the toolbar button, to access a right panel/dock when the user may add input values. I can look into additional methods as an iteration, just wanted to get your feedback on this first pass. Thanks! > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: decision-logic-2-2.png, decision-logic-3-2.png > > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4910) Log WARN if JBoss Logging Handler gets removed

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4910?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4910: ------------------------------------------ This needs a description to provide some context. :) I'd assume that either the handler isn't referenced in which case why WARN, or it is referenced in which case removing it should fail. So I figure there's some situation here where the WARN is appropriate. > Log WARN if JBoss Logging Handler gets removed > ----------------------------------------------- > > Key: WFCORE-4910 > URL: https://issues.redhat.com/browse/WFCORE-4910 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: James Perkins > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4906) Exclude commons-codec dep from httpclient.

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4906?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4906: -------------------------------- Fix Version/s: 12.0.0.Beta2 (was: 12.0.0.Beta1) > Exclude commons-codec dep from httpclient. > ------------------------------------------ > > Key: WFCORE-4906 > URL: https://issues.redhat.com/browse/WFCORE-4906 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 12.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12834) CVE-2019-14887 The 'enabled-protocols' value in legacy security is not respected if OpenSSL security provider is in use

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-12834?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-12834: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13152, https://github.com/wildfly/wildfly/pull/13190 (was: https://github.com/wildfly/wildfly/pull/13152) > CVE-2019-14887 The 'enabled-protocols' value in legacy security is not respected if OpenSSL security provider is in use > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12834 > URL: https://issues.redhat.com/browse/WFLY-12834 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Kunjan Rathod > Assignee: Farah Juma > Priority: Major > Fix For: 20.0.0.Beta1 > > > Security Issue > Do not make this issue public. > The 'enabled-protocols' attribute in legacy security seems not to be working if 'openssl.TLS' provider is in use. If regular JSSE provider with 'TLS' value is in use, it is working just fine, although not in case 'openssl.TLS'. See more info in reproduction steps. > NOTE as described in WFCORE-4737 comment, this is a possible security issue as an attacker can simply persuade server to communicate with him via lower TLS version than which is specified in server configuration! This is currently also a reason why this is marked as blocker now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4878) Upgrade WildFly OpenSSL to 1.0.10.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4878?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-4878: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4098, https://github.com/wildfly/wildfly-core/pull/4138 (was: https://github.com/wildfly/wildfly-core/pull/4098) > Upgrade WildFly OpenSSL to 1.0.10.Final > --------------------------------------- > > Key: WFCORE-4878 > URL: https://issues.redhat.com/browse/WFCORE-4878 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 12.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13349) Upgrade WildFly Core 12.0.0.Beta1

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13349?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13349: ------------------------------- Component/s: Management > Upgrade WildFly Core 12.0.0.Beta1 > --------------------------------- > > Key: WFLY-13349 > URL: https://issues.redhat.com/browse/WFLY-13349 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13349) Upgrade WildFly Core 12.0.0.Beta1

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13349: ---------------------------------- Summary: Upgrade WildFly Core 12.0.0.Beta1 Key: WFLY-13349 URL: https://issues.redhat.com/browse/WFLY-13349 Project: WildFly Issue Type: Component Upgrade Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020