ory. If I send 1 messages at once, it will
use the same connection for all of them, but if there's an interval between
sending 2 messages, it will use 2 different connections.
Any ideas?
Alex
Ale Sarco wrote:
>
> Further investigation led to find this one, by setting the log to D
the connection being tried to be closed in the first place, instead
of being reused? Can this be avoided by setting
wireFormat.maxInactivityDuration=0 in the broker? What would be the impact
of doing this?
Thanks!
Alex.
James.Strachan wrote:
>
> On 4/17/07, Ale Sarco <[EMAIL PROTECTE
n 4/17/07, Ale Sarco <[EMAIL PROTECTED]> wrote:
>>
>> Hi James,
>>
>> Using ActiveMQ 4.1.1 with Spring I experienced this "unable to create new
>> native thread" exception in one of my production servers last night. The
>> thing is that server
Hi James,
Using ActiveMQ 4.1.1 with Spring I experienced this "unable to create new
native thread" exception in one of my production servers last night. The
thing is that server does not has a large messaging traffic, it just send 2
or 3 messages every couple of minutes to another webapp running
