I was trying to start the mule mmc and mule-ee using the start launcher given in the mule mmc distribution package. When Ia m running the start.bat it was mentioning that the mule instance is already running.
When i checked the windows process I was not able to see any related java process running and in services I could see mul-ee in stopped state. When I am trying to start the mule-ee service it is mentioning that the file path cannot be identified.
I even tried to remove the service which also was not possible.
Could you please help in finding what might be issue ?.
Regards
Arun
I have resolved the issue temporarily by deleting the mule-ee service.
Below is the command used :
sc delete mule-ee
Regards
Arun
Same issue occur to me also, I find the port which running for mule instance, I have killed it and run start.bat file.. I am not sure about mule-ee is the problem.
I might guess that your are not stopped your mule and mmc instance while shoutdown the pc.
Related
I've installed RabbitMQ (latest version downloadable from RabbitMQ website) on my Windows 10 machine. It installed with ERlang 19.1.
I'm trying to install RabbitMQ Web UI Management Tools using the following command (using RabbitMQ Command Prompt):
rabbitmq-plugins enable rabbitmq_management
I'm getting the following error:
The directory name is invalid.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
Plugin configuration unchanged.
Applying plugin configuration to rabbit#[0x7FF9A8527044]... failed.
* Could not contact node rabbit#[0x7FF9A8527044].
Changes will take effect at broker restart.
* Options: --online - fail if broker cannot be contacted.
--offline - do not try to contact broker.
I've looked up on SO and tried stopping and restarting, overriding erlang cookie, but nothing helps.
I think there's a problem with RabbitMQ itself. The service itself is marked as started, but if I try to telnet the default port (5672) then it fails (it's not a firewall issue - I've disabled it).
Also I don't see an log files created for RabbitMQ or any related Event Logs messages. So it's hard to diagnose exactly the problem.
I also tried uninstalling and re-install both erlang and RabbitMQ. Still didn't help.
How do I further diagnose the problem?
Found a solution to the problem (downgrading Erlang did not work in my case, but just in case I left it on Erlang 18 in case there were other issues with ver 19).
What puzzled my eye was this line: Applying plugin configuration to rabbit#[0x7FF9A8527044]... failed.. Seems like it's trying to connect to rabbit instance at a wrong machine name.
I then ran rabbitmqctl.bat status which failed but again showed that it's trying to connect to [0x7FF9A8527044] while the node name was rabbit#my-mchine-name. So I started reading the configuration section at RabbitMQ website and the solution was simple - setting the node name manually.
All I had to do is add an environment variable named RABBITMQ_NODENAME with the node name being rabbit#localhost. And that's it. Problem solved!
you may be running into issues with Erlang 19 incompatibility. there has been some history of Erlang 19 support problems with RMQ. Try installing Erlang 18 instead.
If that fails, I would recommend using Docker for Windows and installing / running RabbitMQ in that. I've moved all my services like RabbitMQ, MongoDB, etc. into Docker containers and it's made my life as a dev so much simpler.
In my case I had to trash the local account config located at : %APPDATA%\RabbitMQ\.
Deleting the entire folder and reinstalling the service did the trick.
Rabbitmq 3.6.14
Erlang 20.1 OTP
what is the best way to monitor the Mule ESB instances. Is there a way i can get alerted when my mule instance goes down for some reason. I have 4 instances of Mule running and how will I come to know if 1 of them got down due to some reason.
Thanks!
I assume you are running community edition? (Enterprise edition provides a Management Console which allows you to define alerts). If you are using CE, then you are able to enable JMX monitoring on the instances and then use one of many ways to verify based on JMX info, whether your server is running. One way is to write your own application that retrieves JMX data programmatically and act accordingly.
HTH
If you are using Mule EE, you can use MMC to monitor all your instances as Gabriel has already suggested. My suggestion would be to install MMC inside tomcat on a separate server. This is to ensure that even if your Mule Server crashes or goes down, your MMC is still running and can send you alerts about your Mule server downtime. You can refer below link for details on how to setup server down and up alerts.
https://developer.mulesoft.com/docs/display/current/Working+With+Alerts
Additionally I would recommend to use MMC with database persistence to ensure you have ability to recover MMC workspace even if your MMC server crashes. You can refer about MMC setup with DB persistence at below link.
https://developer.mulesoft.com/docs/display/current/Configuring+MMC+for+External+Databases+-+Quick+Reference
If you don't have Mule EE, you may want to explore other tools or customer alerting applications as suggested by Gabriel.
HTH
You can set up a JMX agent by adding the following lines into your "conf/wrapper.conf" file :
wrapper.java.additional.19=-Dcom.sun.management.jmxremote
wrapper.java.additional.20=-Dcom.sun.management.jmxremote.port=10055
wrapper.java.additional.21=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.22=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.23=-Djava.rmi.server.hostname=127.0.0.1
don't forget to change the values accordingly. Also you can implement SSL authentication with a few extra lines.
Now once your monitoring platform is set up you can always activate Java pollers and start the server.
I am trying to start zookeeper on a remote virtual machine. I use this for my project regularly and I do not have any problems while starting the zookeeper. But lately when I am trying to start the server I am getting an error.
When I give ./zkServer.sh start it shows zookeeper server started.
When I check for status using ./zkServer.sh status it shows "Error contacting service. It is probably not running."
I am totally working with 5 Virtual Machines. All these machines were fine initially. I started getting problems with machine 1. But recently I have the same problem with all my virtual machines. Can someone tell me what the issue is and suggest me a way to clear this issue?
Most probably Zookeeper server exited.
If we are running it on a Linux box, use the linux commands. Some of them:
ps -ef | grep -i zookeeper
jps
etc.
Also, try running it in foreground
zkServer.sh start-foreground
In My case the issue was $PATH issue...
You will get what was the issue by running zookeeper in foreground
zkServer.sh start-foreground
I encountered same problem,too. In my case problem is about zookeeper locations configuration is not same for each node so zookeeper can not provide Quorum and mentioned nodes can not be part of cluster.
Please be sure server definition for each node is same.
For example for all nodes, server definition must be same as below
server.0=ip0:2888:3888
server.1=ip1:2888:3888
server.2=ip2:2888:3888
server.3=ip3:2888:3888
server.4=ip4:2888:3888
In my case the issue was some how ClientPort attribute's value was missed in one of the box so in console it was showing as invalid config path.With the help of command 'zkServer.sh start-foreground' investigated and found root cause.
How to verify if Mule server is deployed or not? My intention is to send a query(HTTP or something else) to Mule server and to see if it is up or down. This I want to do when no applications are deployed on the Mule server. This is to do validation post Mule server deployment. I am using community edition v3.3.0 and v3.4.0. I cannot use Mule EE version.
Thanks and Regards
Jai
That seems like a good idea.
The other option is to have you mule app sending a notification when started.
I know you said you can't use EE but the MMC module is probably what you need.
In any case they only problem with the previous approach is if you have a connectivity problem in the server you have your mule app running, but I reckon in that case you'll have several other problems.
HTH
Whenever hit the http we can see the response in console or in the logs.
First check whether your sever is running or not, give the proper url.
I am new to Mule ESB.
I have downloaded Mule Management Console(MMC).I have developed one simple application in which message(s) are put into queue which are then read by another queue. Now what i want to have two MMC instances running and on stopping one mule instance all the message flows through second instance.
Please let me know how to approach about it. Can I do it on my local machine? I mean can i create cluster on my local machine.
Mule based clustering.
Refer
http://www.mulesoft.org/documentation/display/current/Mule+High+Availability+HA+Clusters
http://www.mulesoft.org/documentation/display/current/1+-+Installing+the+Demo+Bundle
Hope this helps.!
Mule server doesn't allow you to link itself with two MMC instances at the same time thats because you register your mule server with MMC refer this: http://www.mulesoft.org/documentation/display/current/Architecture+of+the+Mule+Management+Console.
There is a way to have other MMC instance but that MMC instance has to be passive when the other is already running, MuleSoft has documented this refer it here: http://www.mulesoft.org/documentation/display/current/Persisting+MMC+Data+to+Oracle
So, in your case, when one mmc instance is stopped you can start the other one.