This is happening repeatedly causing memory consumption to balloon locally
and message queues to build remotely.
Googling around isn't revealing much. Can anyone take a look and tell me if
this stuff is normal or not? Need to narrow down the investigations.
Thanks,
James
On 30 October 2012 11:3
All:
I have configured a pure (shared nothing) master/slave setup (both are running
ActiveMQ 5.3.1).
One of the documentation points for this configuration is:
A slave of a master broker consumes all message states from the master -
messages, acknowledgments and transactional states.
Howev
Using the Camel File component to consume files from a directory. Works fine,
but once in a week, ActiveMQ is out-of-heap space. Have been experimenting with
Xmm and Xms (currently "-Xms384M -Xmx384M"), but higher values just delay the
moment where it goes out-of-heap. With jConsole, it's clear
Gary,
Spoke config:
On the hub, I captured this: http://pastebin.co
James,
so using ?transport.trace=true should work for your case here.
There is a bug with our introspection utils class that sets trace on the
transport when configured using ?trace=true
I opened this JIRA (https://issues.apache.org/jira/browse/AMQ-4145) and we
resolve asap.
Thanks,
Christian
that does seem odd, enable trace=true on the tcp transport to see the
advisory consumer subscription command from the bridge, and the
corresponding advisory composite destination. This will all be part of
bridge setup and should be informative.
you need to enable debug logging for
org.apache.activ
So using your orignal steps to recreate the issue, can you fill in where
you do the queue browsing?
* I have a test which puts 10 messages on a queue. This queue is being read
> via a transacted consumer.
> * I then shutdown the broker without committing or rolling back the
> session.
> I am doin
On 30 October 2012 14:32, Gary Tully wrote:
> using priority support should do it, but there is no api that allows
> you to change the order of a pending message on a queue. You would
> have to consume and re send.
>
> Using the jms api, find the message using a browse, consumer with
> selector ma
Gary,
On our test cluster one of our spokes has been configured thus:
.117 is our test hub.
Against the spoke we subscribed to the Outbound.
using priority support should do it, but there is no api that allows
you to change the order of a pending message on a queue. You would
have to consume and re send.
Using the jms api, find the message using a browse, consumer with
selector matching the message id and issue a new message send.
You
Thanks. I will try to. In part of my test I am using a QueueBrowser to
inspect what is on the queue. I do this to check the state at various
points to make sure it meets expectations. When I removed these checks
(which weren't completely necessary), the problem when away. So my concern
here is
there are two different filters involved.
The bridge gets notification of demand on a destination, ie:
consumers, using an advisory consumer.
To reduce the advisory traffic, the set of matching advisory
destinations subscribed to can be filtered. Using the
destinationFilter property or generated f
James,
I was wrong. The correct log4j logger would be this...
log4j.logger.org.apache.activemq.transport.stomp.StompIO=TRACE
(therefore, your original setting would have been correct)
but even so, there does seem to be an issue with "trace" being set on the
Stomp transport filter. I'm digging t
Take a look at the following test case (attached).
I cannot seem to reproduce on 5.7.0 or on trunk.
Can you modify the testcase to fit your use case?
On Fri, Oct 26, 2012 at 5:47 AM, mserrano wrote:
> I am using 5.7.0 with Java 1.7.0_07 on a linux 64 system. Messages are
> persisted using Kah
http://activemq.apache.org/networks-of-brokers.html states for
dynamicallyIncludedDestinations that "destinations that match this list *
will* be forwarded across the network *n.b.* an empty list means all
destinations not in the exluded list will be forwarded".
This reads to me that, given an emp
in your case you need to provide a destinationFilter b/c it is only
auto built from not excluded
destinations.
Do you know up front what you want to bridge or just what you want to ignore?
A the moment, afaik, we don't have a way of providing a negative
filter which seems to be what you want.
Below is the config file. I don't have persistence set to true and the
ActiveMQ heap size is 1024mb.
http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.apache.org/schema/core";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframewo
We are running 5.7.0 on hub and spokes, forgot to mention.
On 30 October 2012 12:08, James Green wrote:
> Gary,
>
> I think you're saying that subscription advisories for excluded
> destinations should be suppressed.
>
> On the hub we're seeing advisories for queues on that spoke. Is there
> the
Gary,
I think you're saying that subscription advisories for excluded
destinations should be suppressed.
On the hub we're seeing advisories for queues on that spoke. Is there
therefore a bug?
James
On 30 October 2012 11:58, Gary Tully wrote:
> the destinationFilter does the job of narrowing t
the destinationFilter does the job of narrowing the list of
interesting consumers by limiting the advisory consumer to a subset of
destinations.
This is auto generated if it is not configured from 5.6.0, but needs
both ends of the networkconnector to be => 5.6
Have a peek at:
https://issues.apache
that looks like a regression from https://issues.apache.org/jira/browse/AMQ-3224
you need to provide a specific destination or use the wildcard
AnyDestination otherwise.
It needs to be a bean reference:
then apply the destination property with something like:
...
can y
If your broker JVM is running out of memory, then your broker configuration is
most likely not appropriate for your JVM settings (JVM max heap size).
What JVM max heap size do you use and what is the section
configured for?
Your memoryUsage setting must be lower than the JVMs max heap size.
R
That made no difference :(
The entire log4j.properties file is below. If it helps the JMX console says
that the stompURL property of the broker is
stomp://localhost:61612?trace=true
log4j.rootLogger=INFO, console, logfile
log4j.logger.org.apache.activemq.spring=WARN
log4j.logger.org.apache.active
Part of my intention of declaring excluded destinations was to reduce the
amount of traffic over the ADSL line that exists between hub and the spokes.
However, despite the instruction to ban messaging on these destinations,
the amount of traffic and instructions that the hub receives has not
chang
24 matches
Mail list logo
