I was reading some old discussion threads on connection pooling. There seems
to be some conflicting information, specifically whether it's a good idea to
pool connections.
I have been using the jencks-amqpool package for pooling connections (and
also trying the pool package within activemq-core)
I've created an issue to track this: AMQ-1575
I've posted a patch there, created originally by 'hbruch'
Jason
Jason Rosenberg wrote:
>
> Rob,
>
> The attempt to get a connection over the failover transport hangs (it goes
> into it's reconnect sequence indefinitely)
>
> What I'd li
I think the uri parsing doesn't like nested '?'sProbably a bug?
But, if you have '?' inside the parens, then you can't use one outside the
parens...
So, you might have:
failover:(tcp://myserver?wireFormat.maxInactivityDuration=0)&maxReconnectDelay=1000
Jason
ramj2ee wrote:
>
> If I use
All,
I've filed an issue, and posted a patch for 5.1-SNAPSHOT, for this issue
(I've taken hbuch's patch and put it into the 5.1 source)...
See AMQ-1575
Jason
--
View this message in context:
http://www.nabble.com/Timeout-and-Failover-on-a-queue-tp13292887s2354p15328072.html
Sent from the Ac
All,
In my case, the issue is related to using connection pooling, which don't
expose the idleTimeout property...
I've created a work-around outlined in AMQ-1578, which is specific to the
connection pooling case.
Now my sessions stay alive
Jason
Jason Rosenberg wrote:
>
> Hi,
>
> I am
Hi,
Don't know if you are using connection poolingI've solved this issue by
setting the idle timeout to 0 (infinite timeout), for pooled
connections.Unfortunately, the PooledConnectionFactory doesn't expose
the idleTimeout property, so I sub-classed it as a work-around. I've filed
an iss
Hello,
I'm investigating using ActiveMQ for in an application with a very high
transaction rate. This is actually a follow up to a thread that Marc
started up a few months ago,
http://www.nabble.com/Questions-on-Network-of-Brokers-and-high-message-rates-to14145093s2354.html
and all of that discus
Is there a way to change the idle connection timeout for consumers in
ActiveMQ v5.0?
I'm having a problem that wasn't happening in ActiveMQ v4.x where the
connection of a consumer thats listening to a topic that is idle for about
an hour or so will 'silently die'. i.e. the connection dies (and is
I am having some trouble recreating it right now. Are there any tips you
could provide by viewing the reference from root to the message (shown
below)? Could this show that activemq is keeping references to the messages
because there is something wrong with transaction commits?
We recently modi
Please have a look at this urgent and critical issue which is still open
we are using activemq-all-5.0.0.jar
--
View this message in context:
http://www.nabble.com/Transport-failed%2C-attempting-to-automatically-reconnect-due-to...-tp15159638s2354p15306655.html
Sent from the ActiveMQ - User m
Done, although not sure it was done correctly. Key is AMQCPP-166
nmittler wrote:
>
> Sounds like a bug - mind opening a JIRA issue for this?
>
> Thanks,
> Nate
>
> On Feb 5, 2008, at 12:51 PM, Tom Johnson wrote:
>
>>
>> I was trying to use a map message from a C++ program. It appears
>>
11 matches
Mail list logo