Hi Eric (And John West),
I haven't been able to get the auto-discovery to work yet, but from your
sample connection strings, I think you will need to change them to the
following to have any chance of getting them to work:
activemq:discovery:multicast://default
or
activemq:failover:discovery:m
Thanks for the heads up on the web-page problems. I updated the NMS Getting
Started page and restored the sample code and made sure it was up to date.
It may take a day or so for the update to be propagated, though. Try
refreshing the page later today, or possibly by tomorrow. I don't know wha
I haven't tested out the failover code yet, but I've been told that it is
working. I would suggest taking out the failover: specifier in your
connection string to see if a normal connection works. Then work up to
using failover.
wangchao wrote:
>
> Hello everyone:
> I encountered a proble
ication with
ActiveMQ operating as the instant messaging server. I don't know if that
will help or not, but maybe it will get you going with some ideas on how to
approach using XMPP with ActiveMQ.
Best,
Jim
semog wrote:
>
> I use Pidgin connected to ActiveMQ. I then have our Hudso
We are also having message flow problems, but our problems are with a 100%
Java solution. No NMS or .NET stuff in the mix. Our current suspects are
either ActiveMQ 5.1.0 or JBOSS, or some combination thereof. Like you, we
can get messages to go for a while, and then the consumer just stops gett
ies.
>
> In browsing the packages I noticed the WCF provider. I'm very interested
> in this, can you provide a brief description?
>
> Thanks again.
> - Will
>
>
> semog wrote:
>>
>> Hi Will,
>>
>> It wasn't intentionally removed, it just
Here's a simple tracer implementation that will connect NMS to log4net.
In your client code, add the following line before making any NMS calls:
Apache.NMS.Tracer.Trace = new MyTrace();
Here's the implementation of MyTrace:
// Configure log4net using the .config file
[assembly: log4net
Bryan,
Thanks for your trouble-shooting report. Looks like you guys were trying
everything. I logged a JIRA (AMQNET-114) to enable the KeepAlive feature in
NMS. Even though you were able to solve your issue with a work-around, you
shouldn't have to do that, and the next person may not be able
Hi Bryan,
I can't get to your source code examples. My work internet is filtering out
that site. So, I would first check to make sure that you are calling
Acknowledge on the received messages. It may be that the Broker is stopping
the send to your clients, because it thinks they are "slow" (i.
I re-worked the sample test code that Stefan posted so I could use it to test
my changes. I'm not sure really how to turn this in to a unit-test, since
it's simply an implementation evaluation test tool, and not really a
validation test. Anyway, I had to change to use high-resolution timers,
bec
t to turn on the NoDelay flag.
activemq:tcp://localhost:61616?transport.TcpNoDelayEnabled=true&wireformat.TcpNoDelayEnabled=true
This would set both the client side and broker side sockets to turn on the
NoDelay flag.
I haven't committed these changes yet. I'd like to get your
Hi Allen,
Thanks for the feedback. I checked in changes that will fix that compiler
error. Please let me know if you have any other issues. Although, perhaps
you can just copy/paste the relevant error message instead of the entire
build output. Scrolling down that far is very hard to do on my
Hi,
I reorganized the folders to have framework specific versions of the nUnit
assemblies and updated the nant scripts to reference the appropriate
version. Try updating to the latest, and you should be able to successfully
compile.
Thanks,
Jim
aschrum wrote:
>
> This may be related to recen
Currently there is no support for the ActiveMQ BLOB messages in the NMS API.
You could enter a JIRA requesting to add support for them.
However, in the meantime, you could probably roll your own solution fairly
simply. Place your data in a central location, and send a text message
with a URI o
Hi Scott,
The connect/reconnect scenario is implementation specific, which means it'll
be manual. I've done something similar to what you are trying to do, but
the re-connect is quiet since my application doesn't have any user
interface. Some applications may not want to re-connect, others may
15 matches
Mail list logo