AnsweredAssumed Answered

Two MOMs in wily 9.1.1 cluster

Question asked by Manv1nder_B0para1 on Jul 6, 2012
Latest reply on Jul 30, 2012 by Srikant.Noorani
So here is the situation:

We have a Wily 9.1.1 cluster with 2 collectors and 1 MOM. That's working fine. But now we want to add another EM to the cluster as a MOM.
So the requirement is to connect two MOMs to the same cluster at same time (no active/passive thing as in case of hot-failover).

This was working in our 8.2.3.8 environment but after upgrading to 9.1.1 we are getting the following exception in MOM log file.
It seems that in 9.1.1 only one MOM can communicate to collectors because of some clamped value assigned to them. Is there a way to resolve this issue?

Other thing is even if we would be able to connect these 2 MOMs to the cluster,
will it be possible to report data(CEM and Triage Map info) from the 2 collectors in our cluster to two different Postgre instances?


**********************************************************************************************************************************************************************************************************************************************************************************************************************


00/00/12 00:00:00.683 AM EDT [DEBUG] [Collector ***.***.***.***@5001] [Manager.Cluster] Failed to connect to the Introscope Enterprise Manager at ***.***.***.***@5001 (21) because: The Collector has rejected the connection as the clamp value for MOM is reached[size=7][color=#ff4f4f][color][size].
00/00/12 00:00:00.683 AM EDT [DEBUG] [Collector ***.***.***.***@5001] [Manager.Cluster]

com.wily.isengard.messageprimitives.MaxMomsExceededException: MOM connection from Node=Workstation_26, Address=***.***.***.***/***.***.***.***:14880, Type=socket was rejected since the clamp value of 1 has been reached
at com.wily.introscope.server.beans.session.SessionBean.authenticateMOM(SessionBean.java:398)
at sun.reflect.GeneratedMethodAccessor511.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:75)
at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:29)
at com.wily.isengard.messageprimitives.service.MessageService.attemptMethodCall(MessageService.java:183)
at com.wily.isengard.messageprimitives.service.MessageService.handleMethodCallMessage(MessageService.java:135)
at com.wily.isengard.messageprimitives.service.MessageService.receiveMessage(MessageService.java:161)
at com.wily.isengard.postoffice.Mailbox.handleMessage(Mailbox.java:252)
at com.wily.isengard.postoffice.PostOffice.deliverInternal(PostOffice.java:501)
at com.wily.isengard.postoffice.PostOffice.access$1(PostOffice.java:447)
at com.wily.isengard.postoffice.PostOffice$DeliveryItem.run(PostOffice.java:786)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
at java.lang.Thread.run(Thread.java:662)

Outcomes