[JIRA] Resolved: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

  • From: "amyk (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Resolved: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread
  • Date: Thu, 20 Feb 2014 03:08:49 +0000 (UTC)
  • Auto-submitted: auto-generated


     [ 
https://java.net/jira/browse/MQ-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

amyk resolved MQ-349.
---------------------

    Fix Version/s: 5.0.1 (RI-Bug-Fix)
       Resolution: Fixed

Fixed in 5.0.1 build5

> dedicated mode may not release reader thread to RUN_READY state to thread 
> pool if unable to obtain a writer thread
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: MQ-349
>                 URL: https://java.net/jira/browse/MQ-349
>             Project: mq
>          Issue Type: Bug
>          Components: broker-core
>    Affects Versions: 4.1, 4.2, 4.3, 4.4, 4.4u1, 4.4u2, 4.5, 4.5.1, 4.5.2, 
> 5.0-RI (JMS2.0)
>            Reporter: amyk
>            Assignee: amyk
>             Fix For: 5.0.1 (RI-Bug-Fix)
>
>
> The problem can potentially be triggered when broker readPacket throws 
> IllegalArgumentException (or some other RuntimeException), with right 
> timing it may lead to a situation that the connection service, unpon 
> accepting a incoming socket connection, is only able to get a reader thread 
> but no more available thread for a writer thread.  The following warning 
> log messages will shown in broker log file for the connection service, e.g. 
> 'admin' service, as shown in the following broker log with a simulated 
> fault injection test,
> -----------------
> {noformat}
> [#|2014-02-19T18:02:51.025-0800|INFO|5.0.1|imq.log.Logger|_ThreadID=21;_ThreadName=Thread-admin[0];|[B1066]:
>    Closing: ???@127.0.0.1:0->admin:0 because 
> "java.lang.IllegalArgumentException: Bad packet version number: 38. 
> Expecting: 103 or 200 or 301". Count: service=1 broker=1
> |#]
> .....
> [#|2014-02-19T18:02:52.029-0800|WARNING|5.0.1|imq.log.Logger|_ThreadID=16;_ThreadName=admin_ACCEPT;|WARNING
>  [B3004]: No threads are available to process a new connection on service 
> admin. 2 threads out of a maximum of 2 threads are already in use by other 
> connections. A minimum of 2 threads must be available to process the 
> connection. Please either limit the # of connections or increase the 
> imq.<service>.max_threads property. Closing the new connection. 
> |#]
> .....
> [#|2014-02-19T18:02:54.044-0800|INFO|5.0.1|imq.log.Logger|_ThreadID=16;_ThreadName=admin_ACCEPT;|[B1066]:
>    Closing: ???@127.0.0.1:0->admin:0 because "[B3004]: No threads are 
> available to process a new connection on service admin. 1 threads out of a 
> maximum of 2 threads are already in use by other connections. A minimum of 
> 2 threads must be available to process the connection. Please either limit 
> the # of connections or increase the imq.<service>.max_threads property. 
> Closing the new connection. ". Count: service=0 broker=0
> |#]
> .....
> {noformat}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Created: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

amyk (JIRA) 02/20/2014

[JIRA] Updated: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

amyk (JIRA) 02/20/2014

[JIRA] Updated: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

amyk (JIRA) 02/20/2014

[JIRA] Updated: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

amyk (JIRA) 02/20/2014

[JIRA] Resolved: (MQ-349) dedicated mode may not release reader thread to RUN_READY state to thread pool if unable to obtain a writer thread

amyk (JIRA) 02/20/2014
Terms of Use; Privacy Policy; Copyright ©2013-2014 (revision 20140418.2d69abc)
 
 
Close
loading
Please Confirm
Close