There are some problems in its address parsing code that I am working on right
now. I have not been able to confirm anthing beyond that yet.
- Jim
-Original Message-
From: Eric Bouer
Date: Mon, 1 Jun 2009 09:33:47
To:
Subject: Re: Discovery and NMS
Can anyone confirm it's working
Can anyone confirm it's working ?
Or any other information on discovery in NMS ?
semog wrote:
>
> I have not used the discovery code additions. Are there any unit test
> samples that use it that might give you an idea on the format? If there
> aren't, we should probably add some. You may wa
On Mon, 2009-06-01 at 04:35 -0700, Sahay wrote:
> Thank you Tim.
>
> We encourage not to send either as a byte Array or multiple messages between
> CMS to JMS. We are expecting to perform the push-pull mechanism between CMS
> and JMS by sending the single ActiveMQStreamMessage.
>
> The CMS base
Hi Mark,
http(s) transport uses XStream (http://xstream.codehaus.org/) to
marshall/unmarshall messages and it should do just fine with binary data. As
for performances, they are the same as in all similar systems (xml over
http). We don't have any metrics though, so if you come up with some please
Thank you Tim.
We encourage not to send either as a byte Array or multiple messages between
CMS to JMS. We are expecting to perform the push-pull mechanism between CMS
and JMS by sending the single ActiveMQStreamMessage.
The CMS based producer would create the StreamMessage with outputstream(f
Thanks to Andreas for helping me out there. Now I have another problem. The
above solution worked fine for a test setup on my local machine, now when I
move this to a network testbed with the brokers on different machines I get
an error:
INFO DemandForwardingBridge - Network connection b
Is it possible to specify destination Queue of MDB as a jndi name? According
to resource adapter documetnation "destination" activation config property
is required and specifies physical name of destination queue. How to ommit
this property specifying jndi name?
--
View this message in context:
