ActiveMQ Browser V2.5.2.8 can't connect to ActiveMQ V5.12.1 - activemq

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.

Related

ActiveMQ Bridge Configuration for Solace

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

Mule ActiveMQ connector not able to reconnect after broker restart

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.

Consumer Proxy unable to pick up messages from queue due to service configuration in flux

The Consumer proxy is not picking up messages from queue. We have redeployed service and restarted servers. But it did not help. I am attaching logs in here.
<01-Mar-2019 10:39:53 o'clock GMT>
<01-Mar-2019 10:39:53 o'clock GMT>
According to Oracle support document 1573359.1:
CAUSE
The service has been re-deployed/changed while there were messaging being processed. Review Doc ID 1571958.1 "OSB SBConsole Activation - Limitations for configuration or deployment changes in production" for other reasons that this error can occur.
SOLUTION
Stop consumption on the jms queue, delete and re-deploy service.
Log in to Weblogic Console
Expand services -> Messaging -> JMS Modules -> Select the Queue your service is interacting with.
Select the Control tab
For both production and consumption, select pause.
Wait a short while (5 minutes) and restart the queue
Re-deploy your Proxy Services
If message still persist please check config.xml and make sure that there is a correct number of applications with name starting with "ALSB". The correct number depends on the kind of services you have deployed. JMS request-response, JMS plain request, JMS topic etc...
The easiest way to make sure that config.xml is correct is to do the following:
Delete all the JMS proxies from OSB configuration
Open WLS console go to "Deployments" and make sure that there are no application "_ALSB_xyz" deployed. If they are present delete them.
Re-deploy JMS proxies
Alternately, check Note 1382976.1 to locate the related deployments. Delete any application deployments starting with "ALSB" which are not related to any actively deployed JMS proxy service.

Activemq pauses other application in mule standalone

I have deployed two application in my mule standalone in which one application requires ActiveMQ up and running because I have applied reconnect-forever policy for connection.
but without starting ActiveMQ broker if i start mule.bat file it doesn't even deploy other applications which are not dependent on ActiveMQ.
What can be done to solve this issue so that only ActiveMQ dependent applications wait for the connection and other application start working.
Thank You.
Have you set blocking="false" in the reconnect?

Multiple war in Tomcat 7 using a shared embedded ActiveMQ

I'm working on a project where I have several war files inside a tomcat 7 have to communicate with a single embedded activeMQ (5.5.1) broker inside the same Tomcat.
I'm wondering what was the best practice to manage this and how to start and stop the broker properly.
Actually I try tu use a global JNDI entry in server.xml and in each war gets my activemq connection with a lookup. The first connection to the broker implicitly starts it. But with this method I run into various problems like instance already existing or locks in data store.
Should I use instead an additional war which uses a BrokerFactory to start the broker explicitly? In this case how to make sure that this war executes first in Tomcat ? And how do I stop my broker and where?
Thanks for the help.
from the docs...
If you are using the VM transport and wish to explicitly configure an
Embedded Broker there is a chance that you could create the JMS
connections first before the broker starts up. Currently ActiveMQ will
auto-create a broker if you use the VM transport and there is not one
already configured. (In 5.2 it is possible to use the waitForStart and
create=false options for the connection uri)
So to work around this if you are using Spring you may wish to use the
depends-on attribute so that your JMS ConnectionFactory depends on the
embedded broker to avoid this happening. e.g.
see these pages for more information...
http://activemq.apache.org/vm-transport-reference.html
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html
http://activemq.apache.org/how-do-i-restart-embedded-broker.html