[JBoss JIRA] (AS7-6802) acceptor and poller threads not destroyed when reloading
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/AS7-6802?page=com.atlassian.jira.plugin.s... ]
Jean-Frederic Clere commented on AS7-6802:
------------------------------------------
it seems there are too many http-/127.0.0.1:8080-* threads in the thread-dump
> acceptor and poller threads not destroyed when reloading
> --------------------------------------------------------
>
> Key: AS7-6802
> URL: https://issues.jboss.org/browse/AS7-6802
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Fedora 18
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Alexey Loubyansky
> Assignee: Remy Maucherat
> Attachments: server_thread_dump.txt
>
>
> I'm testing the reload operation. At some point the server becomes unresponsive. One of the reasons is
> 14:39:17,452 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 240ms - Started 144 of 181 services (55 services are lazy, passive or on-demand)
> 14:39:17,452 ERROR [stderr] (Controller Boot Thread) Controller Boot Thread releasing lock on 565478949
> 14:39:17,713 ERROR [org.xnio.listener] (Remoting "fedorka:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_13]
> at java.lang.Thread.start(Thread.java:691) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_13]
> at org.xnio.XnioWorker.execute(XnioWorker.java:724) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:218) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:518)
> And if look at the thread dump of the server process, I see lots of acceptor and poller threads. See the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6802) acceptor and poller threads not destroyed when reloading
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6802?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated AS7-6802:
-----------------------------
Assignee: Remy Maucherat (was: David Lloyd)
Component/s: Web
(was: Remoting)
Sorry, my mistake.
> acceptor and poller threads not destroyed when reloading
> --------------------------------------------------------
>
> Key: AS7-6802
> URL: https://issues.jboss.org/browse/AS7-6802
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Fedora 18
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Alexey Loubyansky
> Assignee: Remy Maucherat
> Attachments: server_thread_dump.txt
>
>
> I'm testing the reload operation. At some point the server becomes unresponsive. One of the reasons is
> 14:39:17,452 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 240ms - Started 144 of 181 services (55 services are lazy, passive or on-demand)
> 14:39:17,452 ERROR [stderr] (Controller Boot Thread) Controller Boot Thread releasing lock on 565478949
> 14:39:17,713 ERROR [org.xnio.listener] (Remoting "fedorka:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_13]
> at java.lang.Thread.start(Thread.java:691) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_13]
> at org.xnio.XnioWorker.execute(XnioWorker.java:724) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:218) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:518)
> And if look at the thread dump of the server process, I see lots of acceptor and poller threads. See the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (DROOLS-86) DSL string is having semi-colon added to //
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-86?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-86.
-------------------------------
Fix Version/s: 5.6
6.0.0.Alpha1
Resolution: Done
The problem wasn't caused by the dsl expander, indeed I could reproduce it even with a plain DRL.
It was caused by the expression delimiter when creating the mvel consequence and I fixed it.
> DSL string is having semi-colon added to //
> -------------------------------------------
>
> Key: DROOLS-86
> URL: https://issues.jboss.org/browse/DROOLS-86
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Environment: linux
> Reporter: Richard Ambridge
> Assignee: Mario Fusco
> Labels: dsl
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> If the DSL has a statement like:
> "[then]setout {val}=String me=\"http://onefineday.{val}\";System.out.println(me)\n ";
> and a rule has: setout 123
> the result is http:;//onefineday.123
> notice the http:; <- semi colon added by drools
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6803) NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
by Michael Musgrove (JIRA)
Michael Musgrove created AS7-6803:
-------------------------------------
Summary: NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
Key: AS7-6803
URL: https://issues.jboss.org/browse/AS7-6803
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 8.0.0.Alpha1
Reporter: Michael Musgrove
Assignee: Ondrej Zizka
This test fails when we run the test suite with the following IPv6 options:
{noformat}
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1]
{noformat}
It appears that the test is expecting an array containing one nic address but instead gets two (IPv4 and IPv6) addresses. The linked JBTM jira is where we initially reported the issue. Test output is:
{noformat}
Failed tests:
testBasic(org.jboss.as.controller.interfaces.NicInterfaceCriteriaUnitTestCase): expected:<[/0:0:0:0:0:0:0:1%1]> but was:<[/0:0:0:0:0:0:0:1%1, /127.0.0.1]>
testMultipleCriteria(org.jboss.as.controller.interfaces.NotInterfaceCriteriaUnitTestCase): expected:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
testMultipleCriteria(org.jboss.as.controller.interfaces.AnyInterfaceCriteriaUnitTestCase): expected:<{name:lo (lo)=[/0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:lo (lo)=[/127.0.0.1, /0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6802) acceptor and poller threads not destroyed when reloading
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6802?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated AS7-6802:
-----------------------------
Assignee: David Lloyd (was: Remy Maucherat)
Component/s: Remoting
(was: Web)
> acceptor and poller threads not destroyed when reloading
> --------------------------------------------------------
>
> Key: AS7-6802
> URL: https://issues.jboss.org/browse/AS7-6802
> Project: Application Server 7
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Fedora 18
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Alexey Loubyansky
> Assignee: David Lloyd
> Attachments: server_thread_dump.txt
>
>
> I'm testing the reload operation. At some point the server becomes unresponsive. One of the reasons is
> 14:39:17,452 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 240ms - Started 144 of 181 services (55 services are lazy, passive or on-demand)
> 14:39:17,452 ERROR [stderr] (Controller Boot Thread) Controller Boot Thread releasing lock on 565478949
> 14:39:17,713 ERROR [org.xnio.listener] (Remoting "fedorka:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_13]
> at java.lang.Thread.start(Thread.java:691) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_13]
> at org.xnio.XnioWorker.execute(XnioWorker.java:724) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:218) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:518)
> And if look at the thread dump of the server process, I see lots of acceptor and poller threads. See the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6802) acceptor and poller threads not destroyed when reloading
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-6802?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky updated AS7-6802:
-----------------------------------
Attachment: server_thread_dump.txt
> acceptor and poller threads not destroyed when reloading
> --------------------------------------------------------
>
> Key: AS7-6802
> URL: https://issues.jboss.org/browse/AS7-6802
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Fedora 18
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Alexey Loubyansky
> Assignee: Remy Maucherat
> Attachments: server_thread_dump.txt
>
>
> I'm testing the reload operation. At some point the server becomes unresponsive. One of the reasons is
> 14:39:17,452 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 240ms - Started 144 of 181 services (55 services are lazy, passive or on-demand)
> 14:39:17,452 ERROR [stderr] (Controller Boot Thread) Controller Boot Thread releasing lock on 565478949
> 14:39:17,713 ERROR [org.xnio.listener] (Remoting "fedorka:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_13]
> at java.lang.Thread.start(Thread.java:691) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_13]
> at org.xnio.XnioWorker.execute(XnioWorker.java:724) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:218) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:518)
> And if look at the thread dump of the server process, I see lots of acceptor and poller threads. See the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6802) acceptor and poller threads not destroyed when reloading
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created AS7-6802:
--------------------------------------
Summary: acceptor and poller threads not destroyed when reloading
Key: AS7-6802
URL: https://issues.jboss.org/browse/AS7-6802
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.3.Final (EAP)
Environment: Fedora 18
java version "1.7.0_13"
Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Reporter: Alexey Loubyansky
Assignee: Remy Maucherat
I'm testing the reload operation. At some point the server becomes unresponsive. One of the reasons is
14:39:17,452 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 240ms - Started 144 of 181 services (55 services are lazy, passive or on-demand)
14:39:17,452 ERROR [stderr] (Controller Boot Thread) Controller Boot Thread releasing lock on 565478949
14:39:17,713 ERROR [org.xnio.listener] (Remoting "fedorka:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_13]
at java.lang.Thread.start(Thread.java:691) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_13]
at org.xnio.XnioWorker.execute(XnioWorker.java:724) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:218) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting-3.2.15.GA.jar:3.2.15.GA]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.Beta9.jar:3.1.0.Beta9]
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:518)
And if look at the thread dump of the server process, I see lots of acceptor and poller threads. See the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6779) AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-6779?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber commented on AS7-6779:
------------------------------------------
I assume you are also seeing something like this in the client?
{noformat}
"management-client-thread 1-2" prio=10 tid=0x00007f21a4016000 nid=0x226c in Object.wait() [0x00007f21ffefd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007d7386690> (a org.jboss.remoting3.remote.OutboundMessage)
at java.lang.Object.wait(Object.java:503)
at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:91)
- locked <0x00000007d7386690> (a org.jboss.remoting3.remote.OutboundMessage)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:125)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:113)
at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:77)
at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:95)
- locked <0x00000007d73866c8> (a org.xnio.streams.BufferPipeOutputStream)
at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:176)
at java.io.DataOutputStream.write(DataOutputStream.java:107)
- locked <0x00000007d7388760> (a java.io.DataOutputStream)
at java.io.FilterOutputStream.write(FilterOutputStream.java:97)
at org.jboss.as.protocol.mgmt.FlushableDataOutputImpl.write(FlushableDataOutputImpl.java:118)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:208)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:483)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{noformat}
> AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
> ---------------------------------------------------------------------
>
> Key: AS7-6779
> URL: https://issues.jboss.org/browse/AS7-6779
> Project: Application Server 7
> Issue Type: Bug
> Components: Remoting
> Reporter: Rob Stryker
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Attachments: out.zip
>
>
> Somewhere along the line recently, EAP6.1 / AS 7.2 has a regression in remoting or xnio somehow, and this is causing blocking problems for tools.
> Recall:
> 1) JBossTools bundles a set of jars capable of communicating with a running application server
> 2) This single set of jars must be capable of communicating with all servers in the 7.x stream
> 3) Bundling a second set of jars is not easily accomplished, but could be possible
> And:
> 4) Using the as7.1.0 jars against eap6.1 in a specific unit test causes eclipse to hang
> The basic code of our test case (once we get rid of the jbt stuff wrapped around it) is basically as follows:
> {code}
> this.client = ModelControllerClient.Factory.create(details.getHost(), details.getManagementPort(),
> getCallbackHandler());
> this.manager = ServerDeploymentManager.Factory.create(client);
> DeploymentPlanBuilder builder = manager.newDeploymentPlan().replace(name, file);
> try {
> DeploymentAction action = builder.getLastAction();
> Future<ServerDeploymentPlanResult> planResult = manager.execute(builder.build());
> // FREEZE HERE
> // This is "DeploymentOperationResult.getStatus() in the stack trace
> ServerDeploymentActionResult actionResult = planResult.get().getDeploymentActionResult(action.getId());
> IStatus status = createStatus(action.getDeploymentUnitUniqueName(), action.getType().name(), actionResult);
> } catch (Exception e) {
> throw new JBoss7ManangerException(e);
> }
> {code}
> The actual stack trace is:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=461)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=462)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 363
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 317
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerIntegrationTest.canReplaceWar() line: 129
> {code}
> The list of jars we are using to communicate with the server are:
> {code}
> jboss-as-controller-client-7.1.0.Final.jar
> jboss-as-protocol-7.1.0.Final.jar
> jboss-dmr-1.1.1.Final.jar
> jboss-logging-3.1.0.GA.jar
> jboss-marshalling-1.3.9.GA.jar
> jboss-remoting-3.2.7.GA.jar
> jboss-sasl-1.0.0.Final.jar
> jboss-threads-2.0.0.GA.jar
> xnio-api-3.0.3.GA.jar
> xnio-nio-3.0.3.GA.jar
> {code}
> It was suggested in irc by ctomc that we simply replace the following jars with new jars from jboss-as 7.2 / eap6.1:
> {code}
> jboss-remoting-3.2.7.GA.jar -> 3.2.15.GA
> xnio-api-3.0.3.GA.jar -> 3.0.7
> xnio-nio-3.0.3.GA.jar -> 3.0.7
> {code}
> This approach also failed, with the following stack trace:
> {code}
> java.lang.NoClassDefFoundError: org/xnio/Cancellable
> (sic)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:59)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:211)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:173)
> {code}
> So it is obvious that jboss-as-controller jar from as-7.1 requires classes that are no longer present in xnio. If this is the case, it would indicate that xnio has REMOVED classes from its jar during an incremental version from 3.0.3 to 3.0.7, which would constitute an API breakage.
> So clearly for us, updating only remoting and xnio does not work. The next possible solution would be to update ALL jars, however, this led to a similar situation when using AS7.2 / Eap 6.1 jars to communicate with an AS 7.0.0 server. Again, similar to what was mentioned above, all tests passed EXCEPT the test above. The test above failed with an almost identical stack trace:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=160)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=161)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture(AbstractDelegatingAsyncFuture<T>).get() line: 100
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerTestUtils.quietlyUndeploy(String, AS71Manager) line: 76
> AS7ManagerIntegrationTest.canReplaceWar() line: 135
> {code}
> No matter how you look at it, the contract has been broken. JBossTools now is looking for a specific set of jars which care capable of communicating with AS7.0, 7.1, 7.2, eap6.0, 6.1, jpp6.0, etc. Without a set of jars that can communicate with all of these servers, our tools will need to implement drastic workarounds or bundle several versions of the app server's jars within it.
> It's interesting to me that the as7.1 jars work against everything except eap6.1, and yet, the eap6.1 jars work against everything except as7.0.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month