Re: Update Broker Bridging while running?

2009-01-29 Thread project2501
vents. Is this possible the way I described? thanks. James.Strachan wrote: > > 2009/1/28 project2501 : >> >> Hi, >> Is there a way to inform ActiveMQ to bridge to a new static tcp: broker >> address after it is running? >> I need to dynamically update t

Update Broker Bridging while running?

2009-01-28 Thread project2501
Hi, Is there a way to inform ActiveMQ to bridge to a new static tcp: broker address after it is running? I need to dynamically update the snf bridges, but won't have multicast ability. Can I do this without modifying the config and restarting it? Maybe via API or REST interface? thanks, Darre

Re: Restricting Connectors to single interface?

2009-01-19 Thread project2501
Address is returning on > your host. > > 2009/1/19 project2501 : >> >> Hi, >> I am trying to run activemq over my openvpn network interface to secure >> all the messaging traffic. >> I specified my connectors to a specific network interface address >> 10.8.

Restricting Connectors to single interface?

2009-01-19 Thread project2501
Hi, I am trying to run activemq over my openvpn network interface to secure all the messaging traffic. I specified my connectors to a specific network interface address 10.8.0.1, yet I can still see AMQ listening on the other addresses port 61616. This is a security hole I want to close. I saw

Re: Discovery & Store and Forwarding Queues

2009-01-16 Thread project2501
here? thank you. Gary Tully wrote: > > long shot I know, but would the following be relevant: > http://activemq.apache.org/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.html > > 2009/1/14 project2501 : >> >> Hi, &

Discovery & Store and Forwarding Queues

2009-01-14 Thread project2501
Hi, I read that multicast broker discovery is enabled by default and in my 5.2 AMQ it seems its configured that way. What I want to do is run 2 ActiveMQ 5.2 instances on a subnet, on different machines and have them auto-discover each other - and have messages sent to any local broker to propa

Re: pyactivemq: No Matching Factory Registered for format := tcp

2009-01-13 Thread project2501
Thank you for pointing that out. I checked out the 2.2.1 baseline (also referred in the pyactivemq docs) and it works. Very relieved. project2501 wrote: > > Hi, > I followed the build instructions for pyactivemq. activemq-cpp builds > fine and the tests all complete. I insta

pyactivemq: No Matching Factory Registered for format := tcp

2009-01-13 Thread project2501
Hi, I followed the build instructions for pyactivemq. activemq-cpp builds fine and the tests all complete. I installed all the packages I think are needed. I am using Ubuntu 8.10 server. pyactivemq builds and install fine. The broker is running and I can telnet to the port, yet this error occur