July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4852) (XNIO-2 I/O-1) XNIO001007 java.util.concurrent.RejectedExecutionException error shown intermittently during server shutdown

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-4852?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka updated WFLY-4852: ----------------------------------- Attachment: JPAProxyCrashRecoveryTestCase_haltConnectionAfterDbCommits_jta_server.log server.log with the error shown > (XNIO-2 I/O-1) XNIO001007 java.util.concurrent.RejectedExecutionException error shown intermittently during server shutdown > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4852 > URL: https://issues.jboss.org/browse/WFLY-4852 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Ondřej Chaloupka > Assignee: Jason Greene > Attachments: JPAProxyCrashRecoveryTestCase_haltConnectionAfterDbCommits_jta_server.log > > > Exception > {code} > ERROR [org.xnio.listener] (XNIO-2 I/O-1) XNIO001007: A channel event listener threw an exception: java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteReadListener$1$1@2d696007 rejected from org.xnio.XnioWorker$TaskPool@74a153ee[Shutting down, pool size = 9, active threads = 0, queued tasks = 0, completed tasks = 50] > {code}, details at [1] > could be hit when stopping server. This happens intermediately. > I run transaction integration tests on WildFly/EAP7 DR builds. My tests works in way of doing some settings via CLI, deploy application, do the test, undeploy application, stop the server. > During the stopping the server this exception is shown in log. > Adding server log from my test for possible more details. > [1] > {code} > INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = module_ojdbc7.jar > INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2 > INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: Host default-host stopping > ERROR [org.xnio.listener] (XNIO-2 I/O-1) XNIO001007: A channel event listener threw an exception: java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteReadListener$1$1@2d696007 rejected from org.xnio.XnioWorker$TaskPool@74a153ee[Shutting down, pool size = 9, active threads = 0, queued tasks = 0, completed tasks = 50] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1364) > at org.xnio.XnioWorker.execute(XnioWorker.java:741) > at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:54) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) > at org.xnio.IoUtils.safeClose(IoUtils.java:134) > at org.xnio.channels.TranslatingSuspendableChannel$3.handleEvent(TranslatingSuspendableChannel.java:133) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.StreamConnection.invokeCloseListener(StreamConnection.java:80) > at org.xnio.Connection.writeClosed(Connection.java:117) > at org.xnio.nio.AbstractNioStreamConnection.writeClosed(AbstractNioStreamConnection.java:47) > at org.xnio.nio.NioSocketConduit.terminateWrites(NioSocketConduit.java:181) > at org.xnio.nio.NioSocketConduit.truncateWrites(NioSocketConduit.java:191) > at org.xnio.conduits.ConduitStreamSinkChannel.close(ConduitStreamSinkChannel.java:186) > at org.xnio.IoUtils.safeClose(IoUtils.java:134) > at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.forceTermination(WriteReadyHandler.java:57) > at org.xnio.nio.NioSocketConduit.forceTermination(NioSocketConduit.java:107) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:490) > INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 71) AMQ151003: resource adaptor stopped > INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.0.0 [8e39e2e6-1fc3-11e5-b5ab-adb038d9447d] stopped > INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP listener default suspending > INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032018: Destroying TransactionManagerService > INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032014: Stopping transaction recovery manager > DEBUG [com.arjuna.ats.arjuna] (Listener:4712) Recovery listener existing com.arjuna.ats.internal.arjuna.recovery.WorkerService > DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-3) PeriodicRecovery: Mode <== TERMINATED > DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-3) PeriodicRecovery: shutdown scan wait complete > DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread exiting > INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to localhost/127.0.0.1:8080 > INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0004: Undertow 1.3.0.Beta2 stopping > INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.Alpha5) stopped in 237ms > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4851) Cannot read and list log files in sub-directory of jboss.server.log.dir

by Nikoleta Žiaková (JIRA)

[ https://issues.jboss.org/browse/WFLY-4851?page=com.atlassian.jira.plugin.... ] Nikoleta Žiaková updated WFLY-4851: ----------------------------------- Affects Version/s: 10.0.0.Alpha4 > Cannot read and list log files in sub-directory of jboss.server.log.dir > ----------------------------------------------------------------------- > > Key: WFLY-4851 > URL: https://issues.jboss.org/browse/WFLY-4851 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 10.0.0.Alpha4 > Reporter: Nikoleta Žiaková > Assignee: James Perkins > > Listing and reading log files using CLI or Web Console works only for log files placed in jboss.server.log.dir directly. It should be enabled to log files in sub-directories of jboss.server.log.dir, too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4851) Cannot read and list log files in sub-directory of jboss.server.log.dir

by Nikoleta Žiaková (JIRA)

Nikoleta Žiaková created WFLY-4851: -------------------------------------- Summary: Cannot read and list log files in sub-directory of jboss.server.log.dir Key: WFLY-4851 URL: https://issues.jboss.org/browse/WFLY-4851 Project: WildFly Issue Type: Bug Components: Logging Reporter: Nikoleta Žiaková Assignee: James Perkins Listing and reading log files using CLI or Web Console works only for log files placed in jboss.server.log.dir directly. It should be enabled to log files in sub-directories of jboss.server.log.dir, too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka edited comment on WFLY-4850 at 7/1/15 6:20 AM: ---------------------------------------------------------------- I see. What to add to catch block {{AssertionError}} (as ActiveOperationSupport behaves in such way)? The place where I catch this is extended clustering test {{ClusterPassivationTestCase}}. Running like {code} ./integration-tests.sh clean install -Dts.noSmoke -Dts.clust -Dintegration.module -DextendedTests -Dtest=ClusterPassivationTestCase {code} Nevertheless in any test in testsuite where server is managed manually, where the check for {{isServerInRunningState}} is used and server is stopped at that time will occur that assertion exception instead of {{false}} is returned. was (Author: ochaloup): I see. Then what to add to catch block the AssertionError (as ActiveOperationSupport behaves in such way) The place where I catch this is extended clustering test {{ClusterPassivationTestCase}}. Running like {code} ./integration-tests.sh clean install -Dts.noSmoke -Dts.clust -Dintegration.module -DextendedTests -Dtest=ClusterPassivationTestCase {code} Nevertheless in any test in testsuite where server is managed manually, where the check for {{isServerInRunningState}} is used and server is stopped at that time will occur that assertion exception instead of {{false}} is returned. > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: Tomaz Cerar > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on WFLY-4850: ---------------------------------------- I see. Then what to add to catch block the AssertionError (as ActiveOperationSupport behaves in such way) The place where I catch this is extended clustering test {{ClusterPassivationTestCase}}. Running like {code} ./integration-tests.sh clean install -Dts.noSmoke -Dts.clust -Dintegration.module -DextendedTests -Dtest=ClusterPassivationTestCase {code} Nevertheless in any test in testsuite where server is managed manually, where the check for {{isServerInRunningState}} is used and server is stopped at that time will occur that assertion exception instead of {{false}} is returned. > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: Tomaz Cerar > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4850: ----------------------------------- Current change was done to fix WFLY-2140 What kind of exception is thrown in your scenario? What we could do is to catch runtime exception and propagate that, but for all other kind of exceptions we would return false. Just not sure if this would solve your problem. > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: Tomaz Cerar > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4850: --------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: Tomaz Cerar > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4850: ------------------------------ Component/s: Test Suite > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: Jason Greene > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-786) Remove temporary code to make compatible with WF core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-786?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-786: ------------------------------ Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha4) > Remove temporary code to make compatible with WF core > ----------------------------------------------------- > > Key: WFCORE-786 > URL: https://issues.jboss.org/browse/WFCORE-786 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha6 > > > Some temporary code is needed in core to preserve compatibility with Wildfly following the work done on WFCORE-401. This should be removed and WildFly should be adjusted once this is all in a core release. > The changes are > * org.jboss.as.controller.resource.SocketBindingGroupResourceDefinition should be removed (This was meant to be done for WFCORE-726 but somehow missed) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-786) Remove temporary code to make compatible with WF core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-786?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-786: ------------------------------ Description: Some temporary code is needed in core to preserve compatibility with Wildfly following the work done on WFCORE-401. This should be removed and WildFly should be adjusted once this is all in a core release. The changes are * org.jboss.as.controller.resource.SocketBindingGroupResourceDefinition should be removed (This was meant to be done for WFCORE-726 but somehow missed) was: Some temporary code is needed in core to preserve compatibility with Wildfly following the work done on WFCORE-401. This should be removed and WildFly should be adjusted once this is all in a core release. The changes are * Common.xml's default constructor should be removed * org.jboss.as.controller.resource.SocketBindingGroupResourceDefinition should be removed > Remove temporary code to make compatible with WF core > ----------------------------------------------------- > > Key: WFCORE-786 > URL: https://issues.jboss.org/browse/WFCORE-786 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha4 > > > Some temporary code is needed in core to preserve compatibility with Wildfly following the work done on WFCORE-401. This should be removed and WildFly should be adjusted once this is all in a core release. > The changes are > * org.jboss.as.controller.resource.SocketBindingGroupResourceDefinition should be removed (This was meant to be done for WFCORE-726 but somehow missed) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2015