On 08/06/2009 04:41 PM, lroloson wrote:
I have the latest version built from the trunk on one machine, and I want to
deploy it to a machine I use for testing (same version and distro of Linux).
Is there a way to move the run times to the test machine without building it
there?
You can tar up th
lroloson wrote:
I have the latest version built from the trunk on one machine, and I want to
deploy it to a machine I use for testing (same version and distro of Linux).
Is there a way to move the run times to the test machine without building it
there?
make dist
regards
Carl.
--
I have the latest version built from the trunk on one machine, and I want to
deploy it to a machine I use for testing (same version and distro of Linux).
Is there a way to move the run times to the test machine without building it
there?
--
View this message in context:
http://n2.nabble.com/How
On 08/06/2009 04:31 AM, Gordon Sim wrote:
Alan Conway wrote:
On 08/05/2009 02:45 AM, Gordon Sim wrote:
This looks messy:
listener.subscribed(session.subscribe("message_queue", listener));
Informing the listener can be done as part of the implementation of
session.subscribe(), it doesn't
need t
I will work on getting the latest broker to build from the trunk, and I will
repeat the test. I will post the results here when completed. Thanks !
--
View this message in context:
http://n2.nabble.com/0.5-C%2B%2B-example-listener-hangs-during-testing-tp3344401p3399777.html
Sent from the Apache
lroloson wrote:
Carl,
I tried you experiment this AM, and basically - if I unplug the cable on the
linux end, and kill the listener on the other end (today I was using a linux
listener on a separate machine), it works fine. When I plug the cable back
in (a couple minutes later) & restart the li
Carl,
I tried you experiment this AM, and basically - if I unplug the cable on the
linux end, and kill the listener on the other end (today I was using a linux
listener on a separate machine), it works fine. When I plug the cable back
in (a couple minutes later) & restart the listener, all the m
lroloson wrote:
I turned on the additional logging as suggested - and ran some additional
tests today, using the 0.5 broker on Linux & the 0.5 listener on Windows
(which I modified to reconnect). When I tested again today the messages were
all delivered, however they were out of order. I have att
Alan Conway wrote:
On 08/05/2009 02:45 AM, Gordon Sim wrote:
This looks messy:
listener.subscribed(session.subscribe("message_queue", listener));
Informing the listener can be done as part of the implementation of
session.subscribe(), it doesn't
need to be left to the user.
I'll have a think
