I am using the ActiveMQ Connector to connect to an ActiveMQ Artemis broker. While Mule and ActiveMQ Artemis are running if suddenly I stop and start again or restart the ActiveMQ Artemis instance alone then Mule is not able to connect again.
You need to configure appropriate re-connection strategy, in the global elements properties JMS Config, Advanced tab. change it to forever and should work.
Related
I have a requirement to create a bridge between a Queue in ActiveMQ and a Queue in Solace. When ever there is a message in ActiveMQ Queue it should automatically get transferred to SolaceQ.
I'm struggling to find the steps for this configuration. I have ActiveMQ installed on my local machine. Request you to please throw some light on this.
FYI: I'm very new to ActiveMQ/Solace
I think you'll need to do this via JMS since both ActiveMQ and Solace support it. Check out ActiveMQ's docs here: https://activemq.apache.org/jms-to-jms-bridge
I'm using Apache ActiveMQ Artemis (N1) for my work, and recently I've got a task to send some messages to another ActiveMQ "Classic" (N2) which is used by another system. However, I don't know how should I write divert configurations at broker.xml file. Is it possible? Could you give an example of divert to another URL-address and queue. Where should I write login/password for connection to N2?
Diverts in ActiveMQ Artemis only work with local resources. To send messages to another instance of ActiveMQ Artemis you'd use a core bridge. However, that only works between instances of ActiveMQ Artemis. ActiveMQ "Classic" doesn't support the protocol which the core bridge uses.
In order to send messages from ActiveMQ Artemis to ActiveMQ "Classic" you'd need to use something like Camel or the JMS bridge shipped with ActiveMQ Artemis. Both of these solutions can be deployed as web applications using the embedded web application server in ActiveMQ Artemis. We ship examples of both. The Camel example is in examples/features/standard/camel/ and the JMS bridge example is in examples/submodules/inter-broker-bridge.
I tried to connect to ActiveMQ V5.12.1 with ActiveMQ Browser V2.5.2.8, they are installed on the same computer. but failed.
ActiveMQ Browser always complaining
/*
Could not start QBrowserV2
Failed to connect to ActiveMQ JMX Server.
*/
I followed its instruction to use Jms=true on broker elment of activemq.xml,
also set connectorPort="10000", rmiServerPort="10001" on managementContext element.
I left other configuations default and restart activemq by double clicking the activemq.bat file which located under ACTIVEMQ_HOME\bin\win64
but still no luck.
Meanwhile, I noticed that i can use jconsole to connect ActiveMQ successfully.
Anyone had met same problems? What I want to use ActiveMQ Browser is to monitor the incoming messages, when it is not consumed by subscriber and is in dispatched queue, I want to extract the concrete message contents.
I checked the question, but it is Activemq 5.8.0.
Apache ActiveMQ browser can't connect to JMX console
I had this problem now with ActiveMQ 5.13.4 and my problem was that I didn't copy the correct activemq jar files to AvtiveMQBrowser folder.
https://sourceforge.net/p/activemqbrowser/discussion/962581/thread/464131a8/#0ce4
Copy activemq-all-<version>.jar from the <installation folder> of ActiveMQ broker to ActiveMQBrowser_<version> folder.
Copy activemq-web-<version>.jar from the <installation folder>/lib of ActiveMQ broker to ActiveMQBrowser_<version> folder.
Update run_activemq_browser.bat with paths to the correct activeMQ jar files including correct version number.
The above steps allowed me to connect.
I have a problem using Message Driven Beans in CLUSTERED Glassfish 3.1.1. The problem is with the queue in the Glassfish, the queue is not synchronized between the instances. I am trying by best to explain the scenario below.
I created 2 instances in a GlassFish cluster, created a JMS QueueConnectionFactory, created a JMS Queue. Their targets were made towards the cluster. Then I deployed the web application and the MessageDrivenBean module in the cluster. The web application sends a TextMessage to the JMS Queue.
Everything works well here, like the message is sent to the queue and served by the message driven beans in both the instances.
Then I disable the MessageDrivenBean module. Request the web application which sends the message to the JMS Queue in both the instances. Then I shutdown myInstance2. Re-deploy the MDB in the cluster. Now here is the problem, the MessageDrivenBean only receives the messages of myInstance1 and not the messages sent to myInstance2 queue. The messages in the queue of myInstance2 are only served when myInstance2 is started. Can anyone help me here with the settings that GlassFish uses to synchronize the queue in both the instance so that even for some reason when one instance is down and there are messages in that instance’s queue, the other instance will take the messages of that queue and serve them.
I am using OpenMQ, GlassFish 3.1.1 and I have turned on the HA(high availability) option in GlassFish, but still it does not work.
Thanks
The high-availability options for GlassFish and the high-availability options for Message Queue are configured separately. You need to configure your message queue cluster to be an "enhanced cluster" rather than a "conventional cluster". This is described in the GlassFish 3.1 High Availability Administration Guide.
I have Sun's Message Queue 4.3. Default installation on localhost using imqbroker daemon. Opened one queue.
I want to consume messages written to the queue above from .NET.
I understood there is ActiveMQ solution, version 5.3.
Checked ActiveMQ for .NET (version 1.1) and it works OK for ActiveMQ queues which are similar to Sun JMS.
My problem is that I want to bridge my existing Sun MQ 4.3 to an ActiveMQ queue and the documentation in http://activemq.apache.org/jms-to-jms-bridge.html
is not very clear.
can someone point exactly how to map activemq's config file to bridge:
Sun MQ queue named QUEUE1 on imqbroker#localhost:7676 (maybe jms port 1545? default install)
to
ActiveMQ queue named QUEUE2 on activemq:tcp://localhost:61616
I'm loosing it .... Thanx
You can use Apache Camel JMS component to connect the different brokers:
AFAIK Camel is included in ActiveMQ.