Bug 1112032 - "ChannelBusyException: Too many open outbound writes" when using concurrent JMX connections
Summary: "ChannelBusyException: Too many open outbound writes" when using concurrent J...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Darran Lofthouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-22 22:38 UTC by James Livingston
Modified: 2019-08-19 12:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:48:33 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)
reproducer (1.71 KB, text/x-java)
2014-06-22 22:40 UTC, James Livingston
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker REMJMX-78 0 Major Open Make XNIO and Remoting options be configurable 2016-04-19 16:28:02 UTC
Red Hat Knowledge Base (Solution) 906213 0 None None None Never

Description James Livingston 2014-06-22 22:38:38 UTC
A JMX client can be used by multiple threads, with concurrent queries/invocations going across it. If too many are done at once, you can see an error "ChannelBusyException: Too many open outbound writes".

This is due to the default max outbound message limit of 80. We should have a way to raise that limit for standalone clients. One option would be to add https://issues.jboss.org/browse/REMJMX-78, which would allow for the configuration of arbitrary remoting options.

Comment 1 James Livingston 2014-06-22 22:40:40 UTC
Created attachment 911196 [details]
reproducer

This is a simple class which can be used to reproduce the problem, by having 100 threads share an mbean connection to a running JBoss instance

Comment 2 Darran Lofthouse 2014-11-19 18:43:51 UTC
Going to set a NACK as adding additional property support in this way is really a RFE.


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