Thursday, October 18, 2012

Mulesoft MMC 3.3.1 Could not register server: Could not pair servers (500) with MuleSoft ESB 3.3.1



To fix this error:

For RedHat specific with Virtual IP running and load balancing using Pulse:

Configuration:
    Server A - MMC IP  : 110.100.100.1
    Server B - ESB IP 1: 110.100.101.1

First and foremost, stop your ESB Server in Server B

Note: If you don't use PULSE in Virtual IP, please ignore Step 1 and Step 8.

1. Disable the "PULSE" service in Server B (i.e. sudo service pulse stop;)
2. Open your Server A hosts file (/etc/hosts)
Add the following to your hosts file
110.100.101.1 <your ESB dns name>
3. Open your Server B hosts file (/etc/hosts)
Add the following to your hosts file
110.100.101.1 <your ESB dns name>
4. Go to your Server B and open the wrapper.conf file under your <MULE_HOME>/conf and add the following:
wrapper.java.additional.4=-Dmule.mmc.bind.host=110.100.101.1
     Note: 

         For wrapper.java.additional.4 I choose "4" because that's available
5. Delete the folder ".mule" (i.e. rm <MULE_HOME>/.mule -R)
6. Start your ESB Server B
7. Go to your MMC Web Console and now register it.
8. Start your PULSE service in Server B to enable the Load Balancing again (i.e. sudo service pulse start;)
9. Enjoy...



2 comments:

Anonymous said...

Great tips. Thanks a lot.

nasreen basu said...

excellent piece of information, I had come to know about your website from my friend kishore, pune,i have read atleast 8 posts of yours by now, and let me tell you, your site gives the best and the most interesting information. This is just the kind of information that i had been looking for, i'm already your rss reader now and i would regularly watch out for the new posts, once again hats off to you! Thanx a lot once again, Regards, mulesoft training in hyderabad