I'm observing logs like the following in the server.log

2015-02-24 07:51:09,048 ERROR [Remoting_Connector_ThreadPool-976]-[org.jboss.remotingjmx.protocol.v2.ServerCommon] org.jboss.remoting3.ChannelBusyException: Too many open outbound writes

After enabling TRACE logging on "org.jboss.remoting.remote", I see that this happens when the outbound message is close to the default limit of 80. Here are the trace logs:

2015-03-06 22:52:56,649 TRACE [AMS_Remoting_Connector_ThreadPool-336]-[org.jboss.remoting.remote] CAS Channel ID 4214c3cf (inbound) of Remoting connection 737d64cf to /100.1.1.208:51101

        old: RS=false WS=false IM=0 OM=79

        new: RS=false WS=false IM=0 OM=78

2015-03-06 22:52:56,649 TRACE [AMS_Remoting_Connector_ThreadPool-336]-[org.jboss.remoting.remote] Closed outbound message on Channel ID 4214c3cf (inbound) of Remoting connection 737d64cf to /100.1.1.208:51101

2015-03-06 22:52:56,646 TRACE [AMS_Remoting_Connector_ThreadPool-1238]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,645 TRACE [AMS_Remoting_Connector_ThreadPool-1218]-[org.jboss.remoting.remote] Closed outbound message on Channel ID 4214c3cf (inbound) of Remoting connection 737d64cf to /100.1.1.208:51101

2015-03-06 22:52:56,645 TRACE [AMS_Remoting_Connector_ThreadPool-299]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,645 TRACE [AMS_Remoting_Connector_ThreadPool-936]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,645 TRACE [AMS_Remoting_Connector_ThreadPool-893]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,645 TRACE [AMS_Remoting_Connector_ThreadPool-1019]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,644 TRACE [AMS_Remoting_Connector_ThreadPool-938]-[org.jboss.remoting.remote] Message window is open, proceeding with send

2015-03-06 22:52:56,644 ERROR [AMS_Remoting_Connector_ThreadPool-304]-[org.jboss.remotingjmx.protocol.v2.ServerCommon] org.jboss.remoting3.ChannelBusyException: Too many open outbound writes

2015-03-06 22:52:56,644 TRACE [AMS_Remoting_Connector_ThreadPool-1143]-[org.jboss.remoting.remote] CAS Channel ID 4214c3cf (inbound) of Remoting connection 737d64cf to /100.1.1.208:51101

        old: RS=false WS=false IM=0 OM=79

        new: RS=false WS=false IM=0 OM=80

From JMX mbean, "jboss.remoting.handler:*" dumpConnectionStateToString method I get the following output (only an excerpt)

Result Connection state for Remoting remote connection provider 4bf3938d for endpoint "endpoint" <185f79c0>:

  Connection /100.1.1.207:48212 <-> sys-208_prim/100.1.1.208:9999

  Channel: org.xnio.channels.FramedMessageChannel around org.xnio.ssl.JsseConnectedSslStreamChannel around TCP socket channel (NIO) <5d2bd7d0>

  * Flags: supports-message-close

  * 0 (max 40) inbound channels

  * 1 (max 40) outbound channels

  * Channels:

  Outbound channel ID 9dd53eec summary:

  * Flags:

  * 0 pending inbound messages

  * 0 (max 80) inbound messages

  * 0 (max 80) outbound messages

  * Pending inbound messages:

  * Inbound messages:

  * Outbound messages:

Is there a way I can configure the max outbound/inbound message for the remoting connection?