What is the current (AMQ 5.3) recommended implementation for producer
connection factories? The wiki page for Spring Support suggests
the org.apache.activemq.pool.PooledConnectionFactory which appears to have
been removed from the API.
Thanks,
Mark Greene
Turns out the problems was having explicitQosEnabled=true and a short
timeToLive. The system clocks of producer, broker and consumer deviated
hence messages were expired before they were ever delivered.
--
View this message in context:
http://old.nabble.com/Debug-JMS-environment-tp18426484p26851
Hello All
On 5.3.0.4 and 5.3.0.5
Seeing some odd behaviour with a messageproducer.send
Sometimes it takes a very long time. ranging from < 10 milliseconds to > 60
seconds!
I have all persistence turned off, flow control off and can't see any reason
for it.
Running a standalone broker with a s
hi
Thanks for the info.
I set the transportConnector at the consumer side like this
Now it gives an error everytime a message is sent to the consumer but retry
of the same message succeeds.
-thanks
-vasanth
Dejan Bosanac wrote:
>
> Hi,
>
> in 5.3 we changed how localh
It sounds to me like an embedded broker is what you're look for?
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html
With this feature the broker and client both execute within the same JVM.
Joe
http://www.ttmsolutions.com
#include_fto wrote:
>
> I need my Broker
I need my Broker (MQ 5.0.3) to have a client behavior, I got tired trying to
find something related to this in the forum (Found Nothing)
Anyway I think they are only two possibles ways:
1- To have a client directly connected (on the same machine of the broker)
and get and send messages by l
Call tags are placed into jetty.xml configuration file.
This file is imported from the broker-config.xml file and used for activemq
configuration.
Thank you for the response
--
View this message in context:
http://old.nabble.com/HTTPS-configuration---HELP%21-tp26628876p26845928.html
Sent from
>From what I can see from my use, is the fact that the XARessource not being
Serializable, the Recovery engine of JBoss fails reacquire the context for
Transaction recovery.
I tried using a custom Transaction recovery based on the JBossMQ one.
(MessagingXAResourceWrapper and MessagingXAResourceRe
Okay I figured out how to get rid of the error related to not being able to
bind to the jmx address, however, I am still not sure if I can set up my
system the way I want, what I really want is to forward messages recieved
via REST on tomcat to my already running broker, is this possible? I really
Hi,
I guess you need to add spring-jms to your application's class path
(http://repo1.maven.org/maven2/org/springframework/spring-jms/3.0.0.RELEASE/)
if you want use jms-specific spring features.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
Hi,
can you raise a Jira issue with all these info?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Dec 17, 2009 at 8:54 PM, stirlingc wrote:
>
> J
11 matches
Mail list logo