Hi,
How can I find out the originator of a queued message via the web console?
The messages (delivered via Stomp) have an JMSXUserID property which
contains the authenticated sender name of the incoming connection which
dropped the Message into the queues.
But I cannot find a way to show those p
As i continue to work on this problem and dig further into the AMQ docs,
additional clarifying questions have come up about network configuration in a
store-and-forward scenario in which the broker A publishes to topics on broker
A, and broker B subscribes to identically-named topics on broker B
5.4 has a jetty 7 dependency, wonder if that is the problem?
On Sunday, August 22, 2010, jackygurui wrote:
>
> After changed the version of activemq-web from 5.3.2 to 5.4.0 in maven's
> pom.xml (NOTHING ELSE has changed) I get the following exception, where it
> was all working before.
>
> The re
I'm interested in writing new STOMP client and broker implementations --
where is the current centre of STOMP development?
Codehaus seems moribund.
James
Gary,
I'm using simple perl client, using the Net:Stomp module.
Theo
On Mon, Aug 23, 2010 at 1:00 PM, Gary Tully wrote:
> what client are you using, that npe is coming from an expected
> destination attribute in the message which is not there in that stack
> trace.
>
> On 22 August 2010 15:12,
what client are you using, that npe is coming from an expected
destination attribute in the message which is not there in that stack
trace.
On 22 August 2010 15:12, Theo Bot wrote:
> Hi all
>
> When I start the ActiveMQ (5.4.0) on a CentOS 5.5 server with the
> activemq-stomp.xml file and I try t
yea, it is. Full reference in the java doc, see selectors:
http://download-llnw.oracle.com/javaee/1.3/api/javax/jms/Message.html
On 23 August 2010 07:53, James Green wrote:
> I believe I've traced this.
>
> The value 21211 must be enclosed in single quotes. Without quotes it
> does not work. Encl
