[JBoss JIRA] (DROOLS-5638) Majority vote operator does not work in mining model
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5638?page=com.atlassian.jira.plug... ]
Gabriele Cardosi closed DROOLS-5638.
------------------------------------
> Majority vote operator does not work in mining model
> ----------------------------------------------------
>
> Key: DROOLS-5638
> URL: https://issues.redhat.com/browse/DROOLS-5638
> Project: Drools
> Issue Type: Bug
> Components: PMML
> Affects Versions: 7.44.0.Final
> Reporter: Jiri Petrlik
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Majority vote operator does not work in new PMML implementation. Evaluation fails with the following exception:
> java.lang.NullPointerException
> at org.drools.core.rule.constraint.MvelConstraint.equals(MvelConstraint.java:675)
> at org.drools.core.reteoo.AlphaNode.equals(AlphaNode.java:198)
> at java.base/java.util.HashMap.getNode(HashMap.java:567)
> at java.base/java.util.HashMap.get(HashMap.java:552)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.getMatchingNode(CompositeObjectSinkAdapter.java:523)
> at org.drools.core.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:117)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months
[JBoss JIRA] (WFLY-13919) (7.3.z) "Contains non-LDH ASCII" characters during remote EJB SSL call in IPV6 network
by Ivo Studensky (Jira)
Ivo Studensky created WFLY-13919:
------------------------------------
Summary: (7.3.z) "Contains non-LDH ASCII" characters during remote EJB SSL call in IPV6 network
Key: WFLY-13919
URL: https://issues.redhat.com/browse/WFLY-13919
Project: WildFly
Issue Type: Bug
Components: EJB, Web (Undertow)
Affects Versions: 19.1.0.Final
Reporter: Ivo Studensky
Assignee: Flavia Rainone
*Summary*: " Contains non-LDH ASCII characters " during any remote EJB SSL call in IPV6 network on Kubernetes
*Problem Description*
We are doing EJB call SSL from client container A to EJB located in container B. I reproduced this issue with two different remote EJB SLL call.
Unfortunately, this is only happening on some of our servers. It's difficult to reproduce since we need Kubernetes/IPV6 stack only - and I don't have a test case for it locally.
The wildfly context use to get the ejb (javax.naming.InitialContext) in our app is using this url
java.naming.provider.url=[https://my-server:8443/wildfly-services]
as you can see the hostname is my-server. my-server does not have illegal characters and SNIHostName does not throw an exception when using it in a small unit test.
My assumption is at some point in undertow wildfly code converts the hostname into a IPV6 adress.
*Other notes:*
• The issue is seen on the client side. The client is a java standalone client. The issue is seen under kubernetes.
• The issue is seen with the 19.0.1.Final wildfly-client-all jar. It is also seen with 18.0.0.Final wildfly-client-all jar. It looks to me like an issue in SNIHostName(destinationURI.getHost()) in UndertowXnioSsl.
• I can reproduce this issue with OpenJDK class SNIHostaneme with a local Junit using a IPV6 dummy adress [65:765]
{code:java}
public void testSNIHostName_Case_IPV6()
{
String hostname = "[65:765]";
SNIHostName sniHostname = new SNIHostName(hostname);
}
{code}
{noformat}
java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at java.net.IDN.toASCIIInternal(IDN.java:296)
at java.net.IDN.toASCII(IDN.java:122)
at javax.net.ssl.SNIHostName.<init>(SNIHostName.java:99){noformat}
*Logs*
What we see in the log file of the client:
{{2020-07-31 08:46:47,731 INFO [org.wildfly.naming] [RegistrationStateChangeNotification-pool-27-thread-1] WildFly Naming version 1.0.12.Final
2020-07-31 08:46:47,786 INFO [org.wildfly.security] [RegistrationStateChangeNotification-pool-27-thread-1] ELY00001: WildFly Elytron version 1.11.4.Final
2020-07-31 08:46:47,826 INFO [org.xnio] [RegistrationStateChangeNotification-pool-27-thread-1] XNIO version 3.7.7.Final
2020-07-31 08:46:47,837 INFO [org.xnio.nio] [RegistrationStateChangeNotification-pool-27-thread-1] XNIO NIO Implementation Version 3.7.7.Final
2020-07-31 08:46:47,868 INFO [org.jboss.threads] [RegistrationStateChangeNotification-pool-27-thread-1] JBoss Threads version 2.3.3.Final
2020-07-31 08:46:48,004 INFO [org.jboss.remoting] [RegistrationStateChangeNotification-pool-27-thread-1] JBoss Remoting version 5.0.17.Final
2020-07-31 08:46:48,045 INFO [org.jboss.ejb.client] [RegistrationStateChangeNotification-pool-27-thread-1] JBoss EJB Client version 4.0.30.Final
2020-07-31 08:46:48,206 ERROR [com.application.lifecycle.internal.dataservice.ServiceImpl] [RegistrationStateChangeNotification-pool-27-thread-1] RemoteException while accessing ServiceRemote on cluster: Error; nested exception is:
java.io.IOException: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
java.rmi.RemoteException: Error; nested exception is:
java.io.IOException: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:219)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:125)
at com.sun.proxy.$Proxy12.register(Unknown Source)
at com.application.lifecycle.internal.dataservice.ServiceImpl$1.exec(ServiceImpl.java:41)
at com.application.lifecycle.internal.dataservice.ServiceImpl$1.exec(ServiceImpl.java:38)
at com.service.remoteservice.AbstractStatelessRemoteServiceProxy.exec(AbstractStatelessRemoteServiceProxy.java:128)
at com.application.lifecycle.internal.dataservice.ServiceImpl.register(ServiceImpl.java:38)
at com.application.lifecycle.internal.model.BusinessTierClusterModelImpl.register(BusinessTierClusterModelImpl.java:94)
at com.application.lifecycle.internal.action.RegisterAction.execute(RegisterAction.java:51)
at com.af.app.action.DefaultActionManager.executeRequest(DefaultActionManager.java:176)
at com.service.message.DelegatingMessageReceiver.delegate(DelegatingMessageReceiver.java:68)
at com.service.message.DelegatingMessageReceiver.receive(DelegatingMessageReceiver.java:50)
at com.af.app.message.DefaultMessageReceiver.execute(DefaultMessageReceiver.java:65)
at com.af.app.action.DefaultActionManager.executeRequest(DefaultActionManager.java:176)
at com.af.app.message.DefaultMessageReceiver.onMessage(DefaultMessageReceiver.java:154)
at com.af.app.impl.LocalMessageSenderImpl$SenderRunnable.run(LocalMessageSenderImpl.java:189)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:450)
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:416)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:333)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
Caused by: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at java.net.IDN.toASCIIInternal(IDN.java:296)
at java.net.IDN.toASCII(IDN.java:122)
at javax.net.ssl.SNIHostName.<init>(SNIHostName.java:99)
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:434)
.. 4 more
2020-07-31 08:46:48,208 WARN [com.application.lifecycle.internal.action.RegisterAction] [RegistrationStateChangeNotification-pool-27-thread-1] Failed to register with business tier. Retrying in 10 seconds.
com.Exception: RemoteException while accessing ServiceRemote on cluster
at com.service.remoteservice.AbstractStatelessRemoteServiceProxy.handleRemoteException(AbstractStatelessRemoteServiceProxy.java:112)
at com.service.remoteservice.AbstractStatelessRemoteServiceProxy.exec(AbstractStatelessRemoteServiceProxy.java:130)
at com.application.lifecycle.internal.dataservice.ServiceImpl.register(ServiceImpl.java:38)
at com.application.lifecycle.internal.model.BusinessTierClusterModelImpl.register(BusinessTierClusterModelImpl.java:94)
at com.application.lifecycle.internal.action.RegisterAction.execute(RegisterAction.java:51)
at com.af.app.action.DefaultActionManager.executeRequest(DefaultActionManager.java:176)
at com.service.message.DelegatingMessageReceiver.delegate(DelegatingMessageReceiver.java:68)
at com.service.message.DelegatingMessageReceiver.receive(DelegatingMessageReceiver.java:50)
at com.af.app.message.DefaultMessageReceiver.execute(DefaultMessageReceiver.java:65)
at com.af.app.action.DefaultActionManager.executeRequest(DefaultActionManager.java:176)
at com.af.app.message.DefaultMessageReceiver.onMessage(DefaultMessageReceiver.java:154)
at com.af.app.impl.LocalMessageSenderImpl$SenderRunnable.run(LocalMessageSenderImpl.java:189)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.rmi.RemoteException: Error; nested exception is:
java.io.IOException: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:219)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:125)
at com.sun.proxy.$Proxy12.register(Unknown Source)
at com.application.lifecycle.internal.dataservice.ServiceImpl$1.exec(ServiceImpl.java:41)
at com.application.lifecycle.internal.dataservice.ServiceImpl$1.exec(ServiceImpl.java:38)
at com.service.remoteservice.AbstractStatelessRemoteServiceProxy.exec(AbstractStatelessRemoteServiceProxy.java:128)
.. 13 more
Caused by: java.io.IOException: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:450)
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:416)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:333)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
Caused by: java.lang.IllegalArgumentException: Contains non-LDH ASCII characters
at java.net.IDN.toASCIIInternal(IDN.java:296)
at java.net.IDN.toASCII(IDN.java:122)
at javax.net.ssl.SNIHostName.<init>(SNIHostName.java:99)
at io.undertow.protocols.ssl.UndertowXnioSsl$StreamConnectionChannelListener.handleEvent(UndertowXnioSsl.java:434)
.. 4 more}}
*Other information:*
Java version:
$ java -version
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)
Java arguments:
-Djava.net.preferIPv4Stack=false
tested also with this java arguments :
-Djava.net.preferIPv6Addresses=true
Wildfly server version:
WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final)
my-server corresponds to a kubernetes service which redirects to pod my-pod-hostname
In our environment we verified that we can curl between client pod and wildfly pod
>podA
curl -6 -k https://1234:ef7:.......:rt5:8443
curl -6 -k https://my-pod-hostname:8443
Welcome to wildfly
As far as we know the Kubernetes and pods are well configured in IPV6.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months
[JBoss JIRA] (WFCORE-2592) wildfly-service.exe and jbosspass wrong with # inside
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFCORE-2592?page=com.atlassian.jira.plug... ]
Lukas Vydra commented on WFCORE-2592:
-------------------------------------
Characters ; and # as part of the procrun syntax can be escaped by putting them into single quotes, so my'#'pass should by working. We could also add character escaping into service.bat
> wildfly-service.exe and jbosspass wrong with # inside
> -----------------------------------------------------
>
> Key: WFCORE-2592
> URL: https://issues.redhat.com/browse/WFCORE-2592
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 8.0.0.Beta5
> Reporter: Seb Dk
> Assignee: Lukas Vydra
> Priority: Major
>
> Hi there,
>
> I am installing wildfy 10.1.0 as service on a win 20012 server.
> It is working but I cannot stop the service.
> I figured out where the problem is coming from.
>
> When I installe Wildly as a service, I run the following command:
> E:\Products\wildfly-10.1.0.Final\bin\service>service.bat install /serviceuser .\JBoss /servicepass my#pass /controller localhost:9991 /jbossuser myuser /jbosspass *my#pass*
>
> But I can see whe I am trying to stop the service, the command running is:
> E:\Products\wildfly-10.1.0.Final\bin\jboss-cli.bat --controller=localhost:9991 --connect --user=myuser --password=*my" "pass* --command=:shutdown
>
> Any workaround?
>
> Thanks,
>
> S.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months
[JBoss JIRA] (WFCORE-5146) WFLYPRT0057 message handling improvement
by Katarína Hermanová (Jira)
[ https://issues.redhat.com/browse/WFCORE-5146?page=com.atlassian.jira.plug... ]
Katarína Hermanová updated WFCORE-5146:
---------------------------------------
Description:
WFLYPRT0057 message may or may not be output.
This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_).
{code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java}
126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable {
--- snip ---
135 @Override
136 public Cancellable cancel() {
137 if (cancellable && cancelled.compareAndSet(false, true)) {
138 final Thread thread = this.thread;
139 if(thread != null) {
140 thread.interrupt();
141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread);
142 }
143 }
144 return this;
145 }
--- snip ---
152 @Override
153 public void run() {
154 if (cancellable && cancelled.get()) {
155 Thread.currentThread().interrupt();
156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName());
157 }
158 this.thread = Thread.currentThread();
159 try {
160 doExecute();
161 } finally {
162 this.thread = null;
163 }
164 }
{code}
The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_).
This is just a timing, we cannot determine the need for this message.
{noformat}
- Thread dump
"management task-2" #139 prio=5 os_prio=0 tid=0x0000562c38351800 nid=0x3626 at breakpoint[0x00007facf3098000]
java.lang.Thread.State: RUNNABLE
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.cancel(ManagementRequestContextImpl.java:141)
at org.jboss.as.protocol.mgmt.ActiveOperationImpl.asyncCancel(ActiveOperationImpl.java:150)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.cancelAllActiveOperations(AbstractMessageHandler.java:441)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.shutdownNow(AbstractMessageHandler.java:150)
at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:181)
at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:178)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:150)
at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:129)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:273)
at org.jboss.remoting3.remote.RemoteConnectionChannel$$Lambda$737/243506564.run(Unknown Source)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor$$Lambda$720/801134859.run(Unknown Source)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
"management-handler-thread - 3" #145 prio=5 os_prio=0 tid=0x0000562c38d5b000 nid=0x3b80 at breakpoint[0x00007facf416f000]
java.lang.Thread.State: RUNNABLE
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:162)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
- log
09:45:24,686 INFO [org.jboss.as.protocol] (management task-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 3,5,management-handler-thread]{noformat}
was:
WFLYPRT0057 message may or may not be output.
This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_).
{code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java}
126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable {
--- snip ---
135 @Override
136 public Cancellable cancel() {
137 if (cancellable && cancelled.compareAndSet(false, true)) {
138 final Thread thread = this.thread;
139 if(thread != null) {
140 thread.interrupt();
141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread);
142 }
143 }
144 return this;
145 }
--- snip ---
152 @Override
153 public void run() {
154 if (cancellable && cancelled.get()) {
155 Thread.currentThread().interrupt();
156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName());
157 }
158 this.thread = Thread.currentThread();
159 try {
160 doExecute();
161 } finally {
162 this.thread = null;
163 }
164 }
{code}
The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_).
This is just a timing, we cannot determine the need for this message.
> WFLYPRT0057 message handling improvement
> ----------------------------------------
>
> Key: WFCORE-5146
> URL: https://issues.redhat.com/browse/WFCORE-5146
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI, Management, Remoting
> Reporter: Katarína Hermanová
> Assignee: Katarína Hermanová
> Priority: Major
>
> WFLYPRT0057 message may or may not be output.
> This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_).
> {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java}
> 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable {
> --- snip ---
> 135 @Override
> 136 public Cancellable cancel() {
> 137 if (cancellable && cancelled.compareAndSet(false, true)) {
> 138 final Thread thread = this.thread;
> 139 if(thread != null) {
> 140 thread.interrupt();
> 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread);
> 142 }
> 143 }
> 144 return this;
> 145 }
> --- snip ---
> 152 @Override
> 153 public void run() {
> 154 if (cancellable && cancelled.get()) {
> 155 Thread.currentThread().interrupt();
> 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName());
> 157 }
> 158 this.thread = Thread.currentThread();
> 159 try {
> 160 doExecute();
> 161 } finally {
> 162 this.thread = null;
> 163 }
> 164 }
> {code}
> The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_).
> This is just a timing, we cannot determine the need for this message.
> {noformat}
> - Thread dump
> "management task-2" #139 prio=5 os_prio=0 tid=0x0000562c38351800 nid=0x3626 at breakpoint[0x00007facf3098000]
> java.lang.Thread.State: RUNNABLE
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.cancel(ManagementRequestContextImpl.java:141)
> at org.jboss.as.protocol.mgmt.ActiveOperationImpl.asyncCancel(ActiveOperationImpl.java:150)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.cancelAllActiveOperations(AbstractMessageHandler.java:441)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.shutdownNow(AbstractMessageHandler.java:150)
> at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:181)
> at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:178)
> at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:150)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:129)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:273)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$$Lambda$737/243506564.run(Unknown Source)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$$Lambda$720/801134859.run(Unknown Source)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> "management-handler-thread - 3" #145 prio=5 os_prio=0 tid=0x0000562c38d5b000 nid=0x3b80 at breakpoint[0x00007facf416f000]
> java.lang.Thread.State: RUNNABLE
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:162)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> - log
> 09:45:24,686 INFO [org.jboss.as.protocol] (management task-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 3,5,management-handler-thread]{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months