I do not know if it is useful yet.
But to hide the message what has to be added to the log4j properties file
is:
log4j.logger.org.apache.activemq.transport.failover.FailoverTransport=ERROR
instead of
log4j.logger.org.apache.activemq.transport.failover.FailoverTransport.level=ERROR
The first one
If a client or broker abnormally dies, without the inactivity monitor
you are dependent on OS level timeouts to notice the absence of
network activity. So OS level tcp/ip settings for read timeouts etc.
Essentially you get half closed sockets so the other end is in the
dark. But the OS has options
sure. and link it to https://issues.apache.org/jira/browse/AMQ-2306
I think it makes sense to have that in core so that it is more easily
accessible.
On 5 September 2012 23:31, Gaurav Sharma wrote:
> Gary - Thanks for the pointers. For my in-house work, I am testing
> with the comma-separated l
Claus Ibsen wrote:
And then use the link below, and find the org/apache/activemq in the repo.
thanks! (it looked like a Maven - only repository first but then I found
the binaries too)
--
Michael Justin
On Thu, Sep 6, 2012 at 11:31 AM, Michael Justin wrote:
> Hello,
>
> Is the binary snapshot build of ActiveMQ 5.7 still available?
>
> The page http://activemq.apache.org/download.html
>
> no longer has a link to the snapshot builds.
>
Hi
Read the page :)
> If you want to run against a more recen
Hello,
Is the binary snapshot build of ActiveMQ 5.7 still available?
The page http://activemq.apache.org/download.html
no longer has a link to the snapshot builds.
Many thanks in advance
Michael Justin
Hi,
I want to create a small application that listens in a specific topic
and react if some consumer request either a missing message or all
transmitted messages.
This comes because using ActiveMQ along with retroactive consumer is
limited to the subscription recovery policy, which cannot be un
