the server can't work. it says:
2014-04-11 11:53:49,591 | WARN | Transport Connection to:
tcp://192.168.11.172:45734 failed: java.net.SocketException: Broken
pipe | org.apache.activemq.broker.TransportConnection.Transport |
ActiveMQ InactivityMonitor Worker
even I stop the server and restart it.
There is no way in ActiveMQ to clear those messages from memory while the
transaction is ongoing. The data structure for the transaction holds the
message references.
Once in memory for a Queue, a message is only made available to the JVM GC
by one of the following:
* Acknowledgement of the messa
If you have a newer client version and an oler broker version, make sure to
include the activemq-legacy-openwire dependency in the client. Otherwise,
the client only supports a small number of versions, including the most
recent in that version.
--
View this message in context:
http://activemq
Thanks for your help.
2014-04-04 23:27 GMT-06:00 Claus Ibsen :
> Hi
>
> You can find it in maven central
> http://search.maven.org/#search%7Cga%7C1%7Cactivemq-rar
>
>
> On Sat, Apr 5, 2014 at 12:31 AM, Rodrigo Ramos
> wrote:
> > Hello
> >
> > I want to download activemq 5.9 resource adapter,
Hi,
the client and the broker should negotiate the protocol version they use
and they should use the lowest version there is. I'm not sure why your old
client is trying to use the newest protocol version. Having said that 4.0
is really old and not supported, so you should be considering an upgrade
FYI, I have posted a similar question to StackOverflow:
http://stackoverflow.com/questions/22977299/in-activemq-is-it-possible-to-limit-the-memory-required-for-an-open-consumer-tra
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Transactions-and-memory-consumption-tp42248
Hello:
I've got a question about non-durable topics ( ie, without durable
subscribers ) & persistent messages
If I send a *persistent* message to a *non-durable* topic ( and topic
doesn't have durable consumers ),
- is the message stored into database before sending non-durable subscribers ?
-
So currently ActiveMQ's health mbean only reports problems, i.e. if you
force an issue to occur you'll see that green header turn to orange or read
with some additional messaging indicating what component is reporting an
issue. So the broker name in green is a good thing, i.e. no news is good
news
Just see the broker name in green. Thought there would be more to it than that.
-Original Message-
From: chubr...@gmail.com [mailto:chubr...@gmail.com] On Behalf Of Dejan Bosanac
Sent: Thursday, April 10, 2014 11:19 AM
To: users@activemq.apache.org
Subject: Re: Hawt.io Health tab
Hi Bar
Hi Barry,
no, this should work automagically. Do you see anything when you access
Health MBean of your broker over JMX?
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action
Hi,
Can a produce and consumer running on different activemq versions exchange
messages?
My producer is running in latest ActiveMQ version (5.9.0) where as my
consumer is running in ActiveMQ 4.0.1. I am getting following exception in
consumer
Exception in thread "ActiveMQ Transport: tcp:///x.
Hi,
Can a produce and consumer running on different activemq versions exchange
messages?
My consumer is running in latest ActiveMQ version (5.9.0) where as my
producer is running in ActiveMQ 4.0.1. I am getting following exception in
consumer
Exception in thread "ActiveMQ Transport: tcp:///14
12 matches
Mail list logo
