Re: Activemq not listening to 61613

The address [::0] is a new one on me in uri="stomp+nio://[::0]:61613 ” - did you mean [::] (without the trailing zero?) I would try stomp+nio://0.0.0.0:61613 - which is IPv4 - but usually the platform (Windows/Linux) can handle dual

Re: Virtual topics, custom prefix limitations

Tim, The documentation on this topic (haha!) was never 100% clear to me. Here's what we want to achieve given our architecture: Topology 12 broker network (full-mesh) All destinations dynamic (no static definitions) Clients connect and reconnect with random brokers (preference to local)

Re: HornetQ client connect to Artemis server

Thanks for your response. I looked into the extra-tests you talked about. I created a simple application acting as the hornetq client, using the code in the test. Here is my java code. package hornetqTest; import java.util.HashMap; import java.util.Map; import

Re: sudo update-rc.d activemq multiuser throws error

I am using ubuntu $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" Thanks, Maneesh -- View this message in context:

Activemq not listening to 61613

with the below simple configuration, I am not able to make activemq listen to 61613 Service is running fine, sudo service activemq status * Checking status of ActiveMQ instance activemqOK but netstat -an | grep 61613 doesnt now return anything. What am i doing wrong? Can anyone

sudo update-rc.d activemq multiuser throws error

When I execute the command, sudo update-rc.d activemq multiuser I get below error, $ sudo update-rc.d activemq multiuser update-rc.d: warning: activemq start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5) update-rc.d: warning: activemq stop runlevel arguments (none) do

Re: increasing number of pending message when consumer hit wrong url

. -- View this message in context: http://activemq.2283324.n4.nabble.com/increasing-number-of-pending-message-when-consumer-hit-wrong-url-tp4717857p4717893.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Virtual topics, custom prefix limitations

The description on the Network of Brokers wiki page says that what you're trying to do won't work without those flags set, so you should upgrade if this is a feature you need to use. Tim On Oct 13, 2016 6:33 PM, "Devlin" wrote: > Hi Tim, > > We managed to get working

Re: Duplicating messages published to a Topic to a Queue

Good to hear, Re: Your comments The "jms.topic." and "jms.queue." prefix requirements are causing a lot of confusion for many users, hopefully it'll be resolved soon, as part of: https://issues.apache.org/jira/browse/ARTEMIS-780 Regarding the divert name, we should probably throw an exception

Re: HornetQ client connect to Artemis server

Hi, Artemis does support HornetQ 2.4.7.final clients and should work out of the box. Could you provide a reproducer? We actually have some tests under /tests/extra-tests/protocols/hornetq that test the HornetQ client against the latest broker. If you could contribute a test here that'd be

Re: java.io.EOFException when ActiveMQ starts

Thanks Tim for making things clear. I tried out with the two brokers with each pointing to other broker in *JMS_X_SITE_CSV_URL* and both the brokers came up without any warning. This rules out the issue for any SSL. For the self configuration, I figured that if the value in *JMS_X_SITE_CSV_URL*