[JBoss JIRA] Created: (JBAS-8595) Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always.
by Nishant Parikh (JIRA)
Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always.
-------------------------------------------------------------------------------------------------------
Key: JBAS-8595
URL: https://jira.jboss.org/browse/JBAS-8595
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.1.GA
Environment: Windows/Linux, JDK1.5, RAM 2GB, Processor 3GHz, Intel Core Due CPU
Reporter: Nishant Parikh
Assignee: Darran Lofthouse
Priority: Critical
When we fire concurrent request more than 200, let's say 200+x (With maxThreads specified 1000 from jmx/web console), Everything works fine but after few seconds x NUMBER OF THREADS GETS BUSY and they never get free. On server log we are getting below ArrayIndexOutOfBoundsException.
Exception in thread "http-192.168.1.166-8080-4" java.lang.ArrayIndexOutOfBoundsException: 200
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769)
at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457)
at java.lang.Thread.run(Thread.java:662)
Exception in thread "http-192.168.1.166-8080-16" java.lang.ArrayIndexOutOfBoundsException: 201
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769)
at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457)
at java.lang.Thread.run(Thread.java:662)
Exception in thread "http-192.168.1.166-8080-91" java.lang.ArrayIndexOutOfBoundsException: 202
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769)
at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457)
at java.lang.Thread.run(Thread.java:662)
Exception in thread "http-192.168.1.166-8080-98" java.lang.ArrayIndexOutOfBoundsException: 203
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769)
at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457)
at java.lang.Thread.run(Thread.java:662)
17:08:49,515 ERROR [JIoEndpoint] Error allocating socket processor
java.lang.ArrayIndexOutOfBoundsException: 203
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778)
at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661)
at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702)
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313)
at java.lang.Thread.run(Thread.java:662)
17:08:49,530 ERROR [JIoEndpoint] Error allocating socket processor
java.lang.ArrayIndexOutOfBoundsException: 202
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778)
at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661)
at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702)
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313)
at java.lang.Thread.run(Thread.java:662)
17:08:49,546 ERROR [JIoEndpoint] Error allocating socket processor
java.lang.ArrayIndexOutOfBoundsException: 201
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778)
at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661)
at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702)
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313)
at java.lang.Thread.run(Thread.java:662)
17:08:49,548 ERROR [JIoEndpoint] Error allocating socket processor
java.lang.ArrayIndexOutOfBoundsException: 200
at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778)
at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661)
at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702)
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry resolved AS7-3847.
-----------------------------------
Resolution: Done
I believe this is done; please re-open if not.
> Non-standard format of IPv6 address(-es) in LOG files
> -----------------------------------------------------
>
> Key: AS7-3847
> URL: https://issues.jboss.org/browse/AS7-3847
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Bartosz Baranowski
> Fix For: 7.1.2.Final-redhat1
>
>
> There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default).
> I think in enterprise product we should not violate this RFC.
> I'm mentioning about LOG messages like:
> {code}
> 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999
> 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447
> {code}
> In both lines IPv6 address should be stretched to "::1" string.
> The second related issue (JBossWeb part) is tracked as AS7-3851.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years