[JBoss JIRA] (WFCORE-2992) Can't restart domain master host with slave attached
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2992?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-2992:
-------------------------------
Fix Version/s: 3.0.0.Beta29
(was: 3.0.0.Beta28)
> 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.Beta29
>
> 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-2968) Servers in a domain won't boot if local auth is disabled on the host controller
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2968?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-2968:
-------------------------------
Fix Version/s: 3.0.0.Beta29
(was: 3.0.0.Beta28)
> Servers in a domain won't boot if local auth is disabled on the host controller
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2968
> URL: https://issues.jboss.org/browse/WFCORE-2968
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: James Perkins
> Assignee: Ken Wills
> Priority: Blocker
> Fix For: 3.0.0.Beta29
>
>
> If local authentication has been disabled on the host controller servers cannot communicate with the host controller and fail to start.
> {code}
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] ... 4 more
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:188)
> [Server:server-one] at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> [Server:server-one] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
> [Server:server-one] ... 3 more
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,243 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> [Server:server-one] 15:10:51,254 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 3.0.0.Beta27-SNAPSHOT "Kenny" stopped in 6ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1645) Wildcard in packages does not work in Spring Boot jar
by Jacek Hola (JIRA)
Jacek Hola created DROOLS-1645:
----------------------------------
Summary: Wildcard in packages does not work in Spring Boot jar
Key: DROOLS-1645
URL: https://issues.jboss.org/browse/DROOLS-1645
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.0.0.Final
Reporter: Jacek Hola
Assignee: Mario Fusco
In applications built with Spring Boot the resources under {{src/main/resources/}} are packed into jar in {{BOOT-INF/classes/}}. That's why when in {{kmodule.xml}} someone specifies
{code:xml}
<kbase name="base" default="true" packages="com.company.*">
...
</kbase>
{code}
then for example resource {{src/main/resources/com/company/rule.drl}} will not be picked up, because the path in jar(zip) is {{BOOT-INF/classes/com/company/rule.drl}}.
>From my investigation it seems the logic in org.drools.compiler.kie.builder.impl.KieBuilderImpl#isFileInKieBase does not recognize these files as it compares the packages for equality or if one starts with the other.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1225) Elytron - Write SASL mechanism implementing class into trace log
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1225?page=com.atlassian.jira.plugin.s... ]
Jan Kalina edited comment on ELY-1225 at 7/3/17 5:00 AM:
---------------------------------------------------------
PR 1: trace into mechs factories
PR 2: toString of delegating objects
was (Author: honza889):
Second PR: toString of delegating objects
> Elytron - Write SASL mechanism implementing class into trace log
> ----------------------------------------------------------------
>
> Key: ELY-1225
> URL: https://issues.jboss.org/browse/ELY-1225
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.1.0.Beta50
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 1.1.0.Beta51
>
>
> It's very hard to debug issues when a wrong SASL mechanism implementation is used (e.g. JDK provided one instead Elytron one). The class name implementing the mechanism should be logged by Elytron.
> One place to cover this could be {{org.wildfly.security.auth.client.AuthenticationConfiguration.createSaslClient()}} method, but there are probably more places to look into.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1225) Elytron - Write SASL mechanism implementing class into trace log
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1225?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1225:
---------------------------------
Second PR: toString of delegating objects
> Elytron - Write SASL mechanism implementing class into trace log
> ----------------------------------------------------------------
>
> Key: ELY-1225
> URL: https://issues.jboss.org/browse/ELY-1225
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.1.0.Beta50
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 1.1.0.Beta51
>
>
> It's very hard to debug issues when a wrong SASL mechanism implementation is used (e.g. JDK provided one instead Elytron one). The class name implementing the mechanism should be logged by Elytron.
> One place to cover this could be {{org.wildfly.security.auth.client.AuthenticationConfiguration.createSaslClient()}} method, but there are probably more places to look into.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months