On Thu, 2012-05-24 at 08:14 -0700, gauche wrote:
> OK, I've found out what's causing this and would greatly appreciate some
> advice for moving forward. I'm not even sure that this is an AMQ issue
> anymore...
>
> The internal framework I depend on uses spring-integration-jms to wrap the
> JMS me
OK, I've found out what's causing this and would greatly appreciate some
advice for moving forward. I'm not even sure that this is an AMQ issue
anymore...
The internal framework I depend on uses spring-integration-jms to wrap the
JMS message. The code in question looks like this:
On Fri, 2012-05-18 at 08:59 -0700, gauche wrote:
> Hmmm, I assume it is an AMQ issue rather than an NMS one. I just stepped
> through the NMS code and can see that it is not modifying the headers at
> all. If I explicitly set JMSXUserID then it gets sent, if I don't then it
> doesn't. Guess I'm th
Hmmm, I assume it is an AMQ issue rather than an NMS one. I just stepped
through the NMS code and can see that it is not modifying the headers at
all. If I explicitly set JMSXUserID then it gets sent, if I don't then it
doesn't. Guess I'm thinking it is AMQ's responsibility to use the connection
us
On Fri, 2012-05-18 at 08:26 -0700, gauche wrote:
> Hi,
>
> I am trying to get JMSXUserID to pass from producer (client) to consumer
> (server) but am having no luck.
>
> My client is a .NET app using NMS V1.5.0.2194, with STOMP V1.5.2.2508. My
> server is a Java app using (indirectly via an inte
