[JBoss JIRA] (WFCORE-2998) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2998?page=com.atlassian.jira.plugi... ]
James Perkins resolved WFCORE-2998.
-----------------------------------
Resolution: Done
Thanks for catching this. The documentation was definitely wrong and is now fixed.
> levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-2998
> URL: https://issues.jboss.org/browse/WFCORE-2998
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.2.1.Final
> Reporter: Gregor Rosenauer
> Assignee: James Perkins
> Labels: check, configuration, logging, startup
>
> Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Oracle JDK 8 build 1.8.0_131-b11
> running in a docker container using Docker 1.12.6, build 78d1802
> Trying to configure e.g. a console-appender with a logging filter as described in
> [Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Config...]
> The server will startup and happily parse the configuration, but then exit without any error:
> {{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
> 2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
> The culprit is the *order* of the levels in the range expression, which is the wrong way around.
> The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2992) Can't restart domain master host with slave attached
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2992?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2992:
-------------------------------------
Fix Version/s: 3.0.0.Beta27
Priority: Blocker (was: Major)
I've made this a Blocker with Fix Version 3.0.0.Beta27 but really it's a Blocker for CR1. I doubt it will be fixed for Beta27 and that's ok. But I want it scheduled for the current version so it's more visible.
> Can't restart domain master host with slave attached
> ----------------------------------------------------
>
> Key: WFCORE-2992
> URL: https://issues.jboss.org/browse/WFCORE-2992
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Beta11
> Reporter: Matthew Casperson
> Assignee: Ken Wills
> Priority: Blocker
> Fix For: 3.0.0.Beta27
>
> Attachments: wildflydclogs.zip
>
>
> With a domain controller (whose management interface is configured with HTTPS) started on a host called master and no slaves attached, I can restart the host master with the command
> *./jboss-cli.ps1 --controller=remote+https://localhost:9993 -c --command="/host=master:shutdown(restart=true)"*
> over and over with no issues.
> Once a domain slave is attached, I often will not be able to restart the host master with the same command. It will shutdown, but not restart. The host master does seem to occasionally restart as expected, but not always.
> The output from the domain controller is this:
> {code:java}
> Registered remote slave host "desktop-p010d77", JBoss WildFly Full 11.0.0.Alpha1 (WildFly 3.0.0.Beta11)
> [Host Controller] 14:14:19,294 INFO [org.jboss.as.host.controller] (management-handler-thread - 1) WFLYHC0180: Shutting
> down in response to management operation 'shutdown'
> 14:14:19,300 INFO [org.jboss.as.process] (Thread-15) WFLYPC0017: Shutting down process controller
> 14:14:19,301 INFO [org.jboss.as.process.Host Controller.status] (Thread-15) WFLYPC0019: Stopping process 'Host Controll
> er'
> [Host Controller] 14:14:19,317 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 40) WFLYHC0024: S
> topping server server-one
> [Host Controller] 14:14:19,320 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 40) WFLYHC0024: S
> topping server server-two
> 14:14:19,320 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 4) WFLYPC0019: Stopping
> process 'Server:server-one'
> 14:14:19,321 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 4) WFLYPC0019: Stopping
> process 'Server:server-two'
> [Server:server-one] 14:14:19,322 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut
> down; shutting down
> [Server:server-two] 14:14:19,324 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut
> down; shutting down
> [Server:server-one] 14:14:19,343 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0
> 010: Unbound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 14:14:19,351 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ000
> 6: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> [Server:server-one] 14:14:19,354 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host defaul
> t-host stopping
> [Server:server-one] 14:14:19,357 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0011: Unbound
> JCA ConnectionFactory [java:/JmsXA]
> [Server:server-two] 14:14:19,362 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0
> 010: Unbound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 14:14:19,358 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HT
> TPS listener https suspending
> [Server:server-one] 14:14:19,360 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HT
> TPS listener https stopped, was bound to 127.0.0.1:8443
> [Server:server-two] 14:14:19,367 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ000
> 6: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> [Server:server-one] 14:14:19,364 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLY
> MSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> [Server:server-two] 14:14:19,370 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0011: Unbound
> JCA ConnectionFactory [java:/JmsXA]
> [Server:server-two] 14:14:19,371 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HT
> TPS listener https suspending
> [Server:server-two] 14:14:19,372 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HT
> TPS listener https stopped, was bound to 127.0.0.1:8593
> [Server:server-two] 14:14:19,374 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 35) WFLY
> MSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory
> [Server:server-one] 14:14:19,392 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Sto
> pped Driver service with driver-name = h2
> [Server:server-two] 14:14:19,407 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host defaul
> t-host stopping
> [Server:server-two] 14:14:19,414 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0019: Sto
> pped Driver service with driver-name = h2
> [Server:server-one] 14:14:19,426 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 74) AMQ151003: res
> ource adaptor stopped
> [Server:server-two] 14:14:19,437 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 73) AMQ151003: res
> ource adaptor stopped
> [Server:server-one] 14:14:19,475 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ22
> 1002: Apache ActiveMQ Artemis Message Broker version 1.5.3.jbossorg-003 [3d9fbbfb-5620-11e7-9672-9cb6d0de7033] stopped,
> uptime 3 minutes
> [Server:server-one] 14:14:19,475 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HT
> TP listener default suspending
> [Server:server-one] 14:14:19,476 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HT
> TP listener default stopped, was bound to 127.0.0.1:8080
> [Server:server-one] 14:14:19,478 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.
> 4.11.Final stopping
> [Host Controller] 14:14:19,488 INFO [org.jboss.as.host.controller] (management task-3) WFLYHC0027: Unregistering server
> server-one
> [Server:server-two] 14:14:19,491 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ22
> 1002: Apache ActiveMQ Artemis Message Broker version 1.5.3.jbossorg-003 [3da40166-5620-11e7-9b85-9cb6d0de7033] stopped,
> uptime 3 minutes
> [Server:server-two] 14:14:19,493 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HT
> TP listener default suspending
> [Server:server-two] 14:14:19,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HT
> TP listener default stopped, was bound to 127.0.0.1:8230
> [Server:server-two] 14:14:19,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Undertow 1.
> 4.11.Final stopping
> [Host Controller] 14:14:19,507 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0027: Unregistering server
> server-two
> [Server:server-one] 14:14:19,510 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 11.0.0.Alpha1 (
> WildFly Core 3.0.0.Beta11) stopped in 174ms
> [Server:server-two] 14:14:19,518 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 11.0.0.Alpha1 (
> WildFly Core 3.0.0.Beta11) stopped in 159ms
> 14:14:19,883 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'S
> erver:server-one' finished with an exit status of 0
> [Host Controller] 14:14:19,884 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027:
> Unregistering server server-one
> 14:14:19,903 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'S
> erver:server-two' finished with an exit status of 0
> [Host Controller] 14:14:19,904 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027:
> Unregistering server server-two
> [Host Controller] 14:14:19,906 WARN [org.jboss.as.domain.controller] (MSC service thread 1-1) WFLYHC0030: Connection to
> remote host "desktop-p010d77" closed unexpectedly
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2998) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2998?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-2998:
----------------------------------------
Assignee: James Perkins (was: Thomas Diesler)
> levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-2998
> URL: https://issues.jboss.org/browse/WFCORE-2998
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.2.1.Final
> Reporter: Gregor Rosenauer
> Assignee: James Perkins
> Labels: check, configuration, logging, startup
>
> Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Oracle JDK 8 build 1.8.0_131-b11
> running in a docker container using Docker 1.12.6, build 78d1802
> Trying to configure e.g. a console-appender with a logging filter as described in
> [Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Config...]
> The server will startup and happily parse the configuration, but then exit without any error:
> {{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
> 2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
> The culprit is the *order* of the levels in the range expression, which is the wrong way around.
> The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2998) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2998?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-8989 to WFCORE-2998:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2998 (was: WFLY-8989)
Component/s: Logging
(was: ConfigAdmin)
Affects Version/s: (was: 10.1.0.Final)
> levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-2998
> URL: https://issues.jboss.org/browse/WFCORE-2998
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Gregor Rosenauer
> Assignee: Thomas Diesler
> Labels: check, configuration, logging, startup
>
> Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Oracle JDK 8 build 1.8.0_131-b11
> running in a docker container using Docker 1.12.6, build 78d1802
> Trying to configure e.g. a console-appender with a logging filter as described in
> [Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Config...]
> The server will startup and happily parse the configuration, but then exit without any error:
> {{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
> 2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
> The culprit is the *order* of the levels in the range expression, which is the wrong way around.
> The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2998) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2998?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2998:
-------------------------------------
Affects Version/s: 2.2.1.Final
> levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-2998
> URL: https://issues.jboss.org/browse/WFCORE-2998
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.2.1.Final
> Reporter: Gregor Rosenauer
> Assignee: Thomas Diesler
> Labels: check, configuration, logging, startup
>
> Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Oracle JDK 8 build 1.8.0_131-b11
> running in a docker container using Docker 1.12.6, build 78d1802
> Trying to configure e.g. a console-appender with a logging filter as described in
> [Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Config...]
> The server will startup and happily parse the configuration, but then exit without any error:
> {{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
> 2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
> The culprit is the *order* of the levels in the range expression, which is the wrong way around.
> The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8989) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
by Gregor Rosenauer (JIRA)
Gregor Rosenauer created WFLY-8989:
--------------------------------------
Summary: levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
Key: WFLY-8989
URL: https://issues.jboss.org/browse/WFLY-8989
Project: WildFly
Issue Type: Bug
Components: ConfigAdmin
Affects Versions: 10.1.0.Final
Reporter: Gregor Rosenauer
Assignee: Thomas Diesler
Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Oracle JDK 8 build 1.8.0_131-b11
running in a docker container using Docker 1.12.6, build 78d1802
Trying to configure e.g. a console-appender with a logging filter as described in
[Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Config...]
The server will startup and happily parse the configuration, but then exit without any error:
{{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
The culprit is the *order* of the levels in the range expression, which is the wrong way around.
The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months