I'm not sure exactly what functionality you require, but you might browse the
JMS 1.1 standard - section 3.5 "Message Properties".
"JMSXGroupID and JMSXGroupSeq are standard properties clients should use if
they want to group messages. *All providers must support them*."
The ActiveMQ reference is
Hi ,
Can anyone provide more details on what are the information that are
contained in the Admin console Topics,Queues tabs.
The scenario is this,
I have a virtual topic and three physical queues corresponding to that
virtual topic.
The Topic tab in admin console is showing the virtual topic nam
So the idea is that you use the stop method on the
org.apache.activemq.broker.jmx.NetworkBridgeView, so on an individual
bridge created by the network connector. There are two mbean in the
mix. The parent org.apache.activemq.broker.jmx.NetworkConnectorView
and the nested NetworkBridgeView.
static
It might help if I show you a piece of my active.xml file that sets up the
NetworkBridges.
From: billy [via ActiveMQ] [mailto:ml-node+s2283324n4653842...@n4.nabble.com]
Sent: Tuesday, July 10, 2012 3:13 PM
To: Billy Buzzard
Subject: Re: JMX and Networ
Gary I'm sorry I have to ask this silly questions but when I stop the
NetworkConnector via the NetworkConnectorViewMBean what *auto-restarts* the
NetworkConnector? Perhaps I missed something in the configuration and
that's my problem. Or, maybe the auto-restart does work and it's not
updating the
Logged: https://issues.apache.org/jira/browse/AMQCPP-413 (Producer connection
that causes broker to reach its memory/disk limits doesn't get the 'all
full' exception even though the broker is configured to send it for Producer
Flow Control.)
Thank you for your help.
-=John
--
View this message i
Hi there,
ITextMessage Message = consumer.Receive(ts) as ITextMessage;
I'm using the above statement to read messages, If the massage is big the
above statement will return null but will dequeue the message.
What do I need to do in order to read big messages and to prevent the
statement from Deq
Hi,
it's not supported. Also xmpp protocol is a bit obsolete. What's your
use case? Maybe you can consider using Stomp
(http://activemq.apache.org/stomp.html) instead.
Regards
--
Dejan Bosanac
Senior Software Engineer | FuseSource Corp.
dej...@fusesource.com | fusesource.com
skype: dejan.bosana