Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1112032

Summary: "ChannelBusyException: Too many open outbound writes" when using concurrent JMX connections
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: JMXAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.1CC: darran.lofthouse, hrupp, joallen, onagano
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:48:33 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducer none

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.