-
1. Re: CPU load at 99% with WildFly 8 CR1
halohalo Jan 22, 2014 5:22 AM (in response to froed)I asume you are using https connections, we had the same problem and for my opinion it's this bug: https://issues.jboss.org/browse/XNIO-215
As a workaround (until the issue is fixed) we go back to http and so the problem is gone.
-
2. Re: CPU load at 99% with WildFly 8 CR1
froed Jan 22, 2014 7:16 AM (in response to halohalo)Yes, right we are using HTTPS and for us it's not an option to use HTTP instead.
There seems to be another bug issue referencing this problem: [WFLY-2778] CPU load at 99% with WildFly 8 CR1 - JBoss Issue Tracker
-
3. Re: CPU load at 99% with WildFly 8 CR1
halohalo Jan 24, 2014 6:40 AM (in response to froed)They have fixed something at [XNIO-215] Infinite Loops after connection establishment failure for HttpUpgrade with SSL - JBoss Issue Tracker and I build a patch version of the XNIO jars. With that, HTTPS is working for me, without problems.
-
4. Re: CPU load at 99% with WildFly 8 CR1
samma Jan 27, 2014 5:15 AM (in response to halohalo)Just out of curiosity, on what kind of server did you have those issues, Matthias? Was it some kind of cloud environment?
-
5. Re: CPU load at 99% with WildFly 8 CR1
ctomc Jan 27, 2014 5:30 AM (in response to samma)Guys,
we manged to reproduce and hopefully fix this problem.
Fix was part of Xnio 3.2.0.Final which is now already part of WildFly upstream.
Just some background, problem only occurred on windows, which was the reason we didn't noticed it before.
Could you guys try with latest nightly builds any verify that fix is valid?
-
6. Re: CPU load at 99% with WildFly 8 CR1
froed Jan 27, 2014 5:49 AM (in response to ctomc)OK, we will check that, but our our environments are all linux boxes.
-
7. Re: CPU load at 99% with WildFly 8 CR1
halohalo Jan 27, 2014 11:50 AM (in response to froed)I checked it with the latest nightly on my Windows 7 and I think the issue is fixed.
But I have a new issue with a JSF error page wich I declare in web.xml
<error-page>
<error-code>404</error-code>
<location>/index.html</location>
</error-page>
For each page not found a new thread hangs