Thanks, so if the subs dont go away the broker thinks it can deliver the
messages to them even though the destination is gone? Seems that a temp
queue removal should result/trigger a cleanup of messages associated with
that destination.
I dont have JUnit test. Instead, I attach sources for a simp
Here it is:
- running ActiveMQ 5.6.0 standalone on its own JVM and using the default
configuration, so I guess no need to post those files? (let me know
otherwise)
- running both producer and consumer on separate instances of Apache Tomcat
7.0.27
- app is using Spring Framework 3.1.1
- this is the
Hi all, I've just started to write a small utility to debug
messages withing a KahaDB. Main use case is to offline understand what is
filled in the store
and why logs are not cleaned.
I've started the implementation, but I want to write this utility catching
*all the knowledged that is out ther
No, this is not the correct behavior. It should not matter if the consumer
is there or not.
Can you reproduce this? Or can you post your configs?
On Mon, Dec 10, 2012 at 12:34 PM, javierco wrote:
> Hi Christian, thanks for the quick response!
>
> I do want the broker to always send the message
Hi Christian, thanks for the quick response!
I do want the broker to always send the message "hey i got your message and
it's safely stored", but even when the consumer of that message is down.
The problem I'm having is that it looks like the broker wants to respond
"hey i got your message, but I
Raul, that was it, I upped the connection pool's idleTimeout and the log
messages go away...thanks
Raul Kripalani-2 wrote
> Hey Ben
>
> The default idleTimeout of the PooledConnectionFactory is only 30
> seconds. And physical connections are borrowed in a round-robin fashion.
>
> So if it takes
Hey Ben
The default idleTimeout of the PooledConnectionFactory is only 30
seconds. And physical connections are borrowed in a round-robin fashion.
So if it takes the application more than 30 seconds to cycle through the 5
connections, you'll start observing connection churn, which seems exactly
w
Hello, we have a Topic with one durable subscriber consumer and one producer.
If both are running, the messages flow with no issues. However, if the
consumer is down, when the producer sends a message, it waits for the broker
to acknowledge without ever coming back.
Is there a configuration proper
Not sure. I'd have to try it out.
I'll write a quick test case and see if I can reproduce what you're seeing.
On Mon, Dec 10, 2012 at 11:27 AM, boday wrote:
> thanks ceposta, so is this a bug with the FailoverTransport or an issue
> with
> my configuration?
>
> correct...I have 2 applications r
thanks ceposta, so is this a bug with the FailoverTransport or an issue with
my configuration?
correct...I have 2 applications running on separate brokers (no network of
brokers, etc). one application sends messages to the other broker via a
JMSTemplate...
is there a better way to do this than w
A first step would be to use a time to live on the error queue, so that old
messages get deleted. This is a message/producer property, but you could
build a plugin to apply a per destination expiry value broker side, using
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org
Nope, that shouldn't be expected. It should only log that if the connection
is first created:
if (firstConnection) {
firstConnection = false;
LOG.info("Successfully connected to " +
uri);
Hi Bill,
You need to insure that the working directory that you are storing you broker
data is different for each embedded broker.
--Claudio
>
> From: "Masters, Bill"
>To: "users@activemq.apache.org"
>Sent: Monday, December 10, 2012 10:19 AM
>Subject: Webl
I have 2 AMQ 5.7 brokers, one sends messages to the other via a
JMSTemplate/PooledConnectionFactory/FailoverTransport. It functions fine,
but I see these "Successfully connected to..." messages in my logs for every
message that is sent...is this expected?
I know I can suppress them with log4j s
I am running AMQ broker v.5.6 on linux with 10G Xmx, 5G limit memoryUsage,
producerFlowControl=false, no persistence, vmCursor and AUTO_ACKNOWLEDGE.
There are a hundreds of producers and consumers, a few queues and a couple
of hundred of temp queues. While watching broker memory in jConsole I notic
Hi,
I have a broker that has 2 queues: important.queue & problems.queue,
The important.queue contains messages that I need to process, and if I
have problems processing any of the messages I put the message into
the problems.queue with a bit of meta-data so I can look at it later.
It is like a DL
Hi all,
Does anyone use ldap broker discovery with broker authentication ?
Having worked out that the ldap discovery simply will not work if I have
useJMX="true" in the broker config, I now have it querying my ldap
directory for brokers, but since I have authentication enabled on my
brokers, t
So it seems I needed a few more parameters on the
cachedLDAPAuthorizationMap as the defaults wont work out of the box. If
anyone else is struggling, this is what my config ended up as - perhaps
someone could update the web documentation to reflect the changes in 5.7 ?
ldap://ld
usage should be less than xmx
发自我的 iPad
在 2012-12-7，3:00，"pebrian27 [via ActiveMQ]"
写道：
> lets say that I set my -Xmx (heap size) to 1G. Is it a good idea to also set
> my activemq memoryUsage limit to 1G. Why or why not?
>
>
>
>
> --
> View this message in context:
> http://activemq.2
the data package contents are generated as part of the maven build via
the activemq-protobuf
plugin.
The generated classes end up in target/generated-sources/proto
Best to do a maven build before importing into eclipse.
see: http://activemq.apache.org/building.html
On 8 December 2012 05:57, Noevi
Thank you both for your help, however i don t get it...
I tried 3 things (restarting the activemq process each time):
- add the
in the /opt/activemq/conf/activemq.xml
- add to the /opt/activemq/conf/activemq.xml (at the bottom) : and left the activemq-stomp.xml as it was
21 matches
Mail list logo
