[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-5994:
------------------------------
Component/s: Server
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-5994:
---------------------------------
Assignee: Jason Greene (was: David Lloyd)
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: Jason Greene
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-5994:
------------------------------
Component/s: (was: Remoting)
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1025) NPE removing a rule that contains a subnetwork
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1025?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated DROOLS-1025:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1298579
Bugzilla Update: Perform
> NPE removing a rule that contains a subnetwork
> ----------------------------------------------
>
> Key: DROOLS-1025
> URL: https://issues.jboss.org/browse/DROOLS-1025
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Removing a rule containing a subnetwork causes the following NPE:
> {code}
> java.lang.NullPointerException
> at org.drools.core.phreak.AddRemoveRule.deletePeerLeftTuple(AddRemoveRule.java:777)
> at org.drools.core.phreak.AddRemoveRule.followPeer(AddRemoveRule.java:749)
> at org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:713)
> at org.drools.core.phreak.AddRemoveRule.flushStagedTuples(AddRemoveRule.java:281)
> at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:153)
> at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:173)
> at org.drools.core.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:163)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1635)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1626)
> at org.drools.core.impl.KnowledgeBaseImpl.internalRemoveRule(KnowledgeBaseImpl.java:1610)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1581)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5293) EJB3 method invocation statistics exposed incorrectly through JMX
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-5293:
----------------------------------------
The affects version in a Jira issue is generally used to indicate the version that was in use at the time an issue was discovered - for many bugs depending on how they were introduced it is always quite likely that a previous version may also have the exact same issue.
> EJB3 method invocation statistics exposed incorrectly through JMX
> -----------------------------------------------------------------
>
> Key: WFLY-5293
> URL: https://issues.jboss.org/browse/WFLY-5293
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 9.0.1.Final
> Reporter: Arto Huusko
> Assignee: Kabir Khan
>
> EJB3 method invocation statistics, that is the "methods" attribute in an EJB3 session JMX object is exposed as CompositeDataSupport object that has the expected keys ("execution-time", and so on), but
> - the values for the keys are always null
> - there is only a single CompositeDataSupport object even when the session has several methods
> - the method name is not available.
> Possibly the invocation statistics should be exposed as an array of CompositeDataSupport objects where one of the keys is the method name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda commented on WFLY-5994:
-----------------------------------------
FYI: reload the server and you have "XNIO007007: Thread is terminating" error too
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda commented on WFLY-5994:
-----------------------------------------
cat /etc/redhat-release
Fedora release 23 (Twenty Three)
java -version
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
free -h
total used free shared buff/cache available
Mem: 11G 3.3G 5.6G 795M 2.6G 7.3G
cat /proc/cpuinfo
...
model name : Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
We can see this on RHEL 7, RHEL 6, Solaris, Windows
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-5994?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-5994:
-----------------------------------
I am having a hard time duplicating this problem. Can you give more information about your OS, JVM, and the hardware you are testing on?
> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
> Key: WFLY-5994
> URL: https://issues.jboss.org/browse/WFLY-5994
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.0.0.CR5
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5293) EJB3 method invocation statistics exposed incorrectly through JMX
by Stefano Coletta (JIRA)
[ https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin.... ]
Stefano Coletta edited comment on WFLY-5293 at 1/14/16 7:08 AM:
----------------------------------------------------------------
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug affect also wildfly-8.2.0.Final?
I didn't understand the problem affect only the jconsole gui (where I don't see the ejb3 method statistics) or the jmx bean who reads from cli command the statistics value.
was (Author: stecolet):
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug affect also wildfly-8.2.0.Final?
Thanks.
> EJB3 method invocation statistics exposed incorrectly through JMX
> -----------------------------------------------------------------
>
> Key: WFLY-5293
> URL: https://issues.jboss.org/browse/WFLY-5293
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 9.0.1.Final
> Reporter: Arto Huusko
> Assignee: Kabir Khan
>
> EJB3 method invocation statistics, that is the "methods" attribute in an EJB3 session JMX object is exposed as CompositeDataSupport object that has the expected keys ("execution-time", and so on), but
> - the values for the keys are always null
> - there is only a single CompositeDataSupport object even when the session has several methods
> - the method name is not available.
> Possibly the invocation statistics should be exposed as an array of CompositeDataSupport objects where one of the keys is the method name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5293) EJB3 method invocation statistics exposed incorrectly through JMX
by Stefano Coletta (JIRA)
[ https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin.... ]
Stefano Coletta edited comment on WFLY-5293 at 1/14/16 7:08 AM:
----------------------------------------------------------------
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug affect also wildfly-8.2.0.Final?
I didn't understand the problem affect only the jconsole gui (where I don't see the ejb3 method statistics) or the jmx bean (who reads from cli command the statistics value).
was (Author: stecolet):
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug affect also wildfly-8.2.0.Final?
I didn't understand the problem affect only the jconsole gui (where I don't see the ejb3 method statistics) or the jmx bean who reads from cli command the statistics value.
> EJB3 method invocation statistics exposed incorrectly through JMX
> -----------------------------------------------------------------
>
> Key: WFLY-5293
> URL: https://issues.jboss.org/browse/WFLY-5293
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 9.0.1.Final
> Reporter: Arto Huusko
> Assignee: Kabir Khan
>
> EJB3 method invocation statistics, that is the "methods" attribute in an EJB3 session JMX object is exposed as CompositeDataSupport object that has the expected keys ("execution-time", and so on), but
> - the values for the keys are always null
> - there is only a single CompositeDataSupport object even when the session has several methods
> - the method name is not available.
> Possibly the invocation statistics should be exposed as an array of CompositeDataSupport objects where one of the keys is the method name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months