Is this still a problem? I would trace into the convertAndSend() call - you
want to get down to the ActiveMQMessageProducer's send() call and verify
that it has NON_PERSISTENT mode set.
If NON_PERSISTENT mode is set on the ActiveMQMessageProducer's send() call,
and the messages are getting to the
I'm running AMQ 5.7.0 with a camel application (using camel 2.10.7, in
case that's relevant) and recently, the app has started logging these
messages:
WARN o.a.c.c.j.DefaultJmsMessageListenerContainer - Setup of JMS
message listener invoker failed for destination 'play.save' - trying
to recover.
karaf@root> features:install activemq-broker
Error executing command: No feature named 'spring' with version '[3.1,4)'
available
activemq-karaf/src/main/resources/features-core.xml, line 25:
spring
should read
spring
Thanks,
Geurt
Is this 100 connections from a single instance of the Application? If so,
how about a connection pool?
Using an embedded broker might do the trick, but keep in mind that ActiveMQ
is not a light solution. Embedding it has its downsides. Also, my first
thought was you have 100 application instanc
A 1GB message size is intense - I can't imagine getting that to work as the
entire message needs to be in the broker JVM's memory at one time. It's
hard to imagine a JVM not running out of memory with such a large message.
Another concern is the possibility of losing connections while transferrin
Have you considered using Quartz, or another approach to scheduling?
I like to keep scheduling outside of the messaging layer since they are very
different responsibilities. Especially with an embedded broker, any benefit
with using ActiveMQ's scheduler seems to be eliminated (that is, having a
s
Ah, very interesting use-case. Aren't there networking-level solutions that
will handle such a scenario at the ip-packet-routing level? That would
eliminate the need to solve it at the higher, ActiveMQ level.
Just an idea.
--
View this message in context:
http://activemq.2283324.n4.nabble.co
Yes, an InvalidClientIDException is thrown on duplicate ID.
It's not possible to have more than one consumer for a durable subscription
- that's a weakness of durable subscriptions, although it's actually more of
a Topic vs Queue isssue. Look at VirtualTopic's to get the semantics of
durable cons
Thanks for your answer
ActiveMQ provides a resource adapter. You can deploy a Resource Adapter
under JBoss, in my case this is the one that I'm using:
http://repository.jboss.org/nexus/content/groups/fs-public/org/apache/activemq/activemq-rar/5.8.0.redhat-60024/
A resource adapter is basically a
Hi again
Now I got a stacktrace, because obviously this problem is not related to
TcpTransport class at all, It just makes what It is designed to do, closing
the Connection is something for that TcpTransport class has no
responsibility. Here is the stack trace:
Daemon Thread [IdleRemover] (Suspen
That's what it looks like. Both bridges (A to B, and B to A) are defined on
one broker.
Looks good.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-Bridge-vs-Network-of-Brokers-tp4681063p4681121.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
The JMS bridge is a good solution to use. I disagree with the statement in
the referenced discussion that the demand-forwarding bridge is always more
efficient and a better choice always for ActiveMQ-to-ActiveMQ.
Without getting into too much detail, the JMS bridge is a good choice when
there is
Hi,
Using ActiveMQ 5.8
I was doing a performance test for ActiveMQ with increasing number of
destination(both topic as well as queue). Below is the behavior I observed:
Test: Previously all the msgs were send to a single destination, now by
increasing destination those messages are redistribute
In most cases, I would expect a 1GB message to cause out-of-memory
conditions.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Exception-in-thread-ActiveMQ-Broker-localhost-Scheduler-java-lang-OutOfMemoryError-Java-heap-space-tp4680994p4681001.html
Sent from the ActiveMQ
Thanks for the response.
To answer your question: What we want is a non demand forwarding bridge
from Broker A to Broker B for one queue. And a non demand forwarding bridge
from Broker B to Broker A for another queue.
After doing some more fiddling around, I think we got it to work. Here is
how w
Is there a way in jmeter to set properties on the JMS producer? That might
work.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Testing-against-ActiveMQ-with-JMeter-how-to-set-JMSPriority-and-JMSExpiration-values-cannot-be-seen-r-tp4680960p4681003.html
Sent from the Act
ActiveMQ version 5.8.
Seeing a strange behavior where a consumer is connected to the broker but
throwing "InvalidClientIDException".
which says that one more connection is trying to connect to the the broker
using the same client_id. But I am only creating one connection: Single
consumer, subscr
More destinations may not improve throughput. With more destinations or
fewer destinations, the messages must be stored by the broker in a similar
manner. In fact, in an ideal implementation, there should be no improvement
by adding Queues meaning that time for the broker to store messages is
fai
Yikes - WS got missed want to raise a jira?
On 7 May 2014, at 03:43, surfnerd wrote:
> Hi,
> Actually link stealing doesn't work for MQTT + Webscokets.
> Simple testing:
> Connect with MQTT WS client library ( Eclipse Paho) and connect-disconnect
> multiple times.
> It will give error of client
One of our legacy applications creates over a hundred JMS connections to a
topic (non persistent messages) on a remote broker (one per servlet
basically). Each connection is receiving the same messages (ie same message
selector). We have over a hundred instances of this application running.
I am
Dear Listers,
We have written a loader class to test the load on the ActiveMq queues. The
queue number size is 7.
When we are passing files upto 100MB it works fine and sends the data to the
ActiveMQ queues.
When we are passing a file above 100 MB till 200 MB , the loader class is
getting an e
The following documentation mentions a "Master/Slave" setup whereby messages
are replicated between two brokers. This sounds different then the "Shared
Filesystem Master/Slave" configuration in other docs, which lets a passive
slave wake-up and take over for a failed master.
Is this replication-s
Hi,
[ActiveMQ 5.8 + LevelDB]
I've not been able to constantly reproduce this, but we have seen the
following warning different times in the log:
Affected queues are composite queues, both those who are addressed directly
and those to which messages are forwarded.
The effect is - it seems to me
Hi,
We have a three node network brokers set up and was working fine. (named
respectably, mq01, mq02 and mq03)
Recently we decided to separate the connector for topic from the connector
for queue,
and we started to see exceptions flooding in broker's log like the
following:
javax.jms.Invalid
24 matches
Mail list logo
