You need to check the ports in conf/jetty.xml, as well as the JMX port in
bin/activemq.bat or bin/activemq
You could disable JMX for ActiveMQ if required.
On Tue, May 24, 2011 at 11:55 PM, teapot wrote:
> Hello;
>
> We configure AMQ on our app server via spring bean and specify the port of
> tra
Starting WebConsole .war in embedded Jetty.. JNDI config?
Hi there,
I'm getting started using ActiveMQ, have searched this list and googled but
I'm going in circles. My environment is a Jetty embedded server, running my
main web app which starts ActiveMQ via jndi.properties. Now I am trying to
Hi all,
I'm trying to setup a pure master slave configuration with a
persistent queue, but the moment I put some load on it (about 30 JMS
text msg/sec, no transactions), I get these kinds of errors in the
master:
2011-05-24 21:36:37,008 | ERROR | Slave Failed |
org.apache.activemq.broker.ft.Mast
By default, doesn't ActiveMQ use auto-acknowledge mode? If you change
that to "transacted", throwing an exception should make Spring roll back
the transaction.
On 05/24/2011 07:13 AM, Dejan Bosanac wrote:
> Hi,
>
> the advisory is sent when the message is acknowledged to the broker (as
> consumed)
> To get more control of the scheduling, you will need to specify the
> TaskRunnerFactory for the broker and specify 1 for the
> maxIterationsPerRun so that it will move on to another task (each
> destination dispatch is a task) immediately.
How do I do the above? I grepped for TaskRunnerFactory
I am running ActiveMQ on machine A where it receives JMS messages from
another system (Mule ESB) on a queue named queue/test. This part works.
I would like these messages to be processed by an MDB running inside a JBoss
AS on machine B. Here I don't know how to proceed.
I do not wish to use the J
Hi Dejan
Thanks for replying. So it seems advisory for consumed isnt going to serve
the purpose of tracking consumed messages.
Is there any way of approach that might help in tracking successfully
consumed messages...
Thanks alot
--
View this message in context:
http://activemq.2283324.n4.nabb
Hello;
We configure AMQ on our app server via spring bean and specify the port of
transportConnector as follows:
We want to run multiple instance of our app server on the same machine. So
we change the 61616 to different port number available on that machine(we
already assigned different p
Dejan, thanks for the response.
I removed the line, but I am still seeing the message de-queued immediately.
On the server side, I have set the schedulerSupport="true" in my
conf/acticemq-specjms.xml file, not sure what else to do ...
--
View this message in context:
http://activemq.2283324.n4.
Hi,
"static" protocol should try to reconnect indefinitely by default. It has
the similar functionality as failover transport and can be tuned with the
similar parameters (
http://activemq.apache.org/discovery-transport-reference.html)
You should enable debug logging on
"org.apache.activemq.trans
Hi.
We have a setup where we use "static" definitions to connect 2 brokers to a
central broker. Alle messages are going through these 2 brokers and are
boing forwarded to a single central broker.
That is from the 2 brokers we have a definitions saying uri="static:(tcp:
for the transport.
We hav
Hi,
the advisory is sent when the message is acknowledged to the broker (as
consumed). Not sure about your Spring setup but it seems that even if you
throw an exception it will consider the message as successfully consumed.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
Hello,
I have a requirement to get the messages that have been successfully
consumed.
My application is using the DefaultMessageListenerContainer of spring for
the listeners.
I have enabled the advisoryForConsumed.
My Queue name is 'Test' and it has a listener .
Correspondingly there is an adv
One of our staff just reported that a queue on our "hub" machine was not
being read any more.
Checking the logs of the PHP app we're getting:
exception 'StompException' with message 'Unexpected EOF while reading from
socket'
Inside AMQ (5.5.0/Linux and configured with ACTIVEMQ_OPTS_MEMORY="-Xms5
The problem is that you are specifying job id. It is used only for other
actions on the already scheduled message (like remove). Try removing it and
it should work fine.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - h
15 matches
Mail list logo