activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Producer is blocking...
Date Fri, 19 Apr 2013 20:04:57 GMT
On 04/19/2013 03:47 PM, SledgeHammer wrote:
> Good call (sort of) :). Turned off producer flow control and it seems like
> its not getting stuck anymore. However, now its throwing a few exceptions
> when I get to around ~500 messages:
>
> A first chance exception of type 'System.IO.EndOfStreamException' occurred
> in mscorlib.dll
> Additional information: Unable to read beyond the end of the stream.
> A first chance exception of type 'System.Net.Sockets.SocketException'
> occurred in System.dll
> Additional information: An existing connection was forcibly closed by the
> remote host
> A first chance exception of type 'System.IO.IOException' occurred in
> System.dll
> Additional information: Unable to write data to the transport connection: An
> existing connection was forcibly closed by the remote host.
>
> A send is taking approximately 15ms now.
>
> Also, when I switched to nms instead of jms, I got an exception on useAsync
> not being a valid flag. The crash is probably more important to me though
> :(.
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Producer-is-blocking-tp4666069p4666072.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
You need to configure sensible memory limits for your Broker to match 
your use case.

You need to read the NMS Documentation for the correct configuration 
options.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message