Bug 1231070 - [GSS](6.4.z) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor
Summary: [GSS](6.4.z) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Petr Jurak
QA Contact: Radim Hatlapatka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-12 06:34 UTC by Eiichi Nagai
Modified: 2019-07-11 09:22 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-27 16:38:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-6511 0 Minor Pull Request Sent ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor 2017-08-08 08:08:28 UTC
Red Hat Issue Tracker WFCORE-773 0 Major Resolved ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor 2017-08-08 08:08:28 UTC

Description Eiichi Nagai 2015-06-12 06:34:12 UTC
Description of problem:
ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor.

Exception in thread "testTP-threads - 1" java.lang.ArrayIndexOutOfBoundsException: 0
	at org.jboss.threads.ArrayQueue.poll(ArrayQueue.java:118)
	at org.jboss.threads.QueueExecutor.takeTask(QueueExecutor.java:713)
	at org.jboss.threads.QueueExecutor.access$400(QueueExecutor.java:45)
	at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:842)
	at java.lang.Thread.run(Thread.java:745)
	at org.jboss.threads.JBossThread.run(JBossThread.java:122)


Version-Release number of selected component (if applicable):
EAP 6.4.1

Steps to Reproduce:
1. Set the thread pool executor.
~~~
[standalone@localhost:9999 /] /subsystem=threads/bounded-queue-thread-pool=testTP:add(max-threads=10, queue-length=0)
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=web/connector=http:write-attribute(name=executor,value=testTP)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone@localhost:9999 /] reload
~~~

2. Execute "http://localhost:8080/" in your browser.

3. You can confirm the ArrayIndexOutOfBoundsException in your server log.

Comment 1 Petr Jurak 2016-10-19 13:31:08 UTC
PR https://github.com/jbossas/jboss-eap/pull/2863

Comment 2 JBoss JIRA Server 2016-10-19 13:48:12 UTC
Petr Jurak <pjurak> updated the status of jira WFCORE-773 to Coding In Progress

Comment 6 Petr Jurak 2016-10-21 06:00:14 UTC
Due to my repo clean up I had to create a new PR:
https://github.com/jbossas/jboss-eap/pull/2865

Comment 11 Peter Palaga 2016-10-27 16:38:31 UTC
Closing as WONTFIX because Brian sees the proposed fix as changing the described management API of the jca and threads subsystems, which makes it not a good candidate for a CP.


Note You need to log in before you can comment on or make changes to this bug.