If you read apache pages you ll see that you do not have to create a
specific queue. It is enough just to publish a message and the queue
will be created automatically behind the scene.
I am using this feature and it works very well.
Regards,
Daniel
SBenj wrote:
(MQ 4.1, Java 1.6, Redhat)
I h
If you read apache pages you ll see that you do not have to create a
specific queue. It is enough just to publish a message and the queue
will be created automatically behind the scene.
I am using this feature and it works very well.
Regards,
Daniel
SBenj wrote:
(MQ 4.1, Java 1.6, Redhat)
I h
html
now it works.
Daniel Gradecak wrote:
Hello,
I am using a lot of different softwares (liferay/james/activemq ...)
and for un uknown reason right now the JVM is crashing ...
I have a lot of threads, but I doubt it craches because of that
without giving any reasons.
I am posting it here bec
Hello,
I am using a lot of different softwares (liferay/james/activemq ...) and
for un uknown reason right now the JVM is crashing ...
I have a lot of threads, but I doubt it craches because of that without
giving any reasons.
I am posting it here because I saw in the log "Current thread
(0x
BTW thats really intended for folks who are using the JMS API directly
rather than JmsTemplate
So for better performances it is better to use the API directly ?
No you can't. JmsTemplate creates/closes all the JMS resources each
time so you're only hope is to use only sending along with
Pool
I wonder if if this configuration does the pooling correctly?
class="org.apache.activemq.ra.ActiveMQResourceAdapter">
name="serverUrl">${jms.brokerUrl}
class="org.jencks.factory.TransactionManagerFactoryBean">
name="defaultTransactionTimeoutSeconds">${jms.transaction.timeou
Hi,
I would like to make an ActiveMQ participate in a XA Transaction. I have
speial needs is that i may suspend a transaction and resume it in
antoher thread. I am using spring for configuring all that together
and its JmsTmplate. I saw
http://activemq.apache.org/jms-and-jdbc-operations-in-one
Hello,
I would like to dispatch messages to queue "listeners (receivers)" with
different policies. As it is guaranteed for topics (
http://activemq.apache.org/total-ordering.html ),
I would like to plug some policies such as "less messages read" for
example, meaning that the message will be de
