[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by Krisztian Kocsis (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
Krisztian Kocsis commented on WFLY-7275:
----------------------------------------
Note that I 2 months ago I was able to produce h2load -n 1000000 -c 20000 without any errors to a Vert.X (Netty) server on the same machine.
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by Krisztian Kocsis (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
Krisztian Kocsis commented on WFLY-7275:
----------------------------------------
So, I run a test with *h2load -n 5000 -c 1000 https://...*. After that even -c 10 does not work (10 concurrent conn.). I'v attached the screenshots of htop after the load test + two stack traces directly after the hang and after 1min (unable to recover without restart). SSL config: TLS 1.2 only, (ciphers only: AES128GCM, ECDHE+RSA). Note that actually the scheduled EJB task is properly executed in every 2 minutes (checked the log files), only the web interface is dead, but it is totally.
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by Krisztian Kocsis (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
Krisztian Kocsis updated WFLY-7275:
-----------------------------------
Attachment: Screen Shot 2016-10-07 at 20.18.31.png
Screen Shot 2016-10-07 at 20.18.27.png
wildfly-after-hang+1min.txt
wildfly-after-hang.txt
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by Krisztian Kocsis (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
Krisztian Kocsis commented on WFLY-7275:
----------------------------------------
@David: I try to reproduce the issue, it takes some time. The main thread was show and 10108 in htop as using 100% but I think there was an other thread too (I don't remember correctly).
@James: Yes, I run a periodic (every 2 minutes) EJB task that imports data from one datasource to an other datasource.
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-7275:
-------------------------------------
Are you using a scheduled job with the {{ManagedScheduledExecutorService}}? I didn't look in detail on the thread-dump, but noticed some parked EE concurrency threads. They don't look unusual, just trying to get an idea of what your application might be doing.
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-7275:
-----------------------------------
What thread? You can find out by using "ps" or "top" to display the PID of the thread, and then convert that value to hexadecimal and search for that value in the output of jstack.
> Wildfly eats the CPU up to 100% and does not respond
> ----------------------------------------------------
>
> Key: WFLY-7275
> URL: https://issues.jboss.org/browse/WFLY-7275
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
> Reporter: Krisztian Kocsis
> Assignee: Jason Greene
> Attachments: wildfly-hang.txt
>
>
> Hi!
>
> I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
> It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
>
> I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
> Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond
by Krisztian Kocsis (JIRA)
Krisztian Kocsis created WFLY-7275:
--------------------------------------
Summary: Wildfly eats the CPU up to 100% and does not respond
Key: WFLY-7275
URL: https://issues.jboss.org/browse/WFLY-7275
Project: WildFly
Issue Type: Bug
Affects Versions: 10.1.0.Final
Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit
Reporter: Krisztian Kocsis
Assignee: Jason Greene
Attachments: wildfly-hang.txt
Hi!
I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.
I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
Please help me, I can provide more information if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-258) Redesign mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated WFLY-258:
--------------------------------
Affects Version/s: JBoss AS7 7.1.1.Final
> Redesign mod_cluster subsystem
> ------------------------------
>
> Key: WFLY-258
> URL: https://issues.jboss.org/browse/WFLY-258
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Affects Versions: JBoss AS7 7.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Changes to the schema
> * simplified names and sync in line with scheme recommendations
> * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem
> * fix load factor enum: no pool metric supported
> * make load-balancers configurable via socket-outbuound-group mechanism
> * add missing load-balancer properties to <proxies/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-258) Redesign mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated WFLY-258:
--------------------------------
Summary: Redesign mod_cluster subsystem (was: mod_cluster schema 2.0)
> Redesign mod_cluster subsystem
> ------------------------------
>
> Key: WFLY-258
> URL: https://issues.jboss.org/browse/WFLY-258
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Changes to the schema
> * simplified names and sync in line with scheme recommendations
> * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem
> * fix load factor enum: no pool metric supported
> * make load-balancers configurable via socket-outbuound-group mechanism
> * add missing load-balancer properties to <proxies/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months