webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Sun cluster + Broker monitor

    Posted Wed December 20, 2006 11:17 PM

    I have 2 brokers running on sun cluster, sharing the same territory (SAN) and configured on the same resource group.
    Every day almost at the same time, both broker servers go down, causing the cluster failover (only for this rsource group). I am getting this error, .

    Apr 9 15:31:50 -20 awbrokermon: [ID 702911 local5.alert] #1023 Cannot bind main socket to port 6850: Address already i
    n use – Another Broker Server may be running already. – [EXITING]
    Apr 9 16:12:11 20 awbrokermon: [ID 702911 local5.alert] #1023 Cannot bind main socket to port 6850: Address already i
    n use – Another Broker Server may be running already. – [EXITING]
    Apr 9 16:15:18 -20 last message repeated 1 time

    I do appreciate any help

    mairag


    #Universal-Messaging-Broker
    #webMethods
    #broker
    #Integration-Server-and-ESB


  • 2.  RE: Sun cluster + Broker monitor

    Posted Thu December 21, 2006 01:06 AM

    Was broker installed in a high availability configuration for a Sun cluster?

    Having just done this yesterday for AIX HACMP 5.4, I can attest to the fact that it requires attention to details both to install Broker successfully and to setup the cluster properly.

    No way to answer your question without knowing how your Sun cluster was configured, what start/stop scripts the cluster calls upon failover/failback and what monitoring conditions the cluster uses to determine whether to failover. webMethods PS provides scripts to probe the brokers (probably using broker_ping) and kick off a failover if the probe fails a specified number of times.

    WM will usually not support a Broker HA config unless PS was retained to do the initial config and testing or at least to audit what you and your OS sysadmin setup.

    HTH,

    Mark


    #Integration-Server-and-ESB
    #webMethods
    #Universal-Messaging-Broker
    #broker


  • 3.  RE: Sun cluster + Broker monitor

    Posted Wed January 17, 2007 05:50 PM

    Thank you very much, problem related with port 6850 is solved, the cluster script that is starting the broker servers was trying to startup the broker monitor, but I am still having problems with Broker servers, I can’t find any reason about why they are getting down, almost daily at the same hour.

    Thank


    #broker
    #webMethods
    #Universal-Messaging-Broker
    #Integration-Server-and-ESB


  • 4.  RE: Sun cluster + Broker monitor

    Posted Wed January 17, 2007 05:51 PM

    Thank you very much, problem related with port 6850 is solved, the cluster script that is starting the broker servers was trying to startup the broker monitor, but I am still having problems with Broker servers :frowning: , I can’t find any reason about why they are getting down, almost daily at the same hour.


    #Integration-Server-and-ESB
    #broker
    #Universal-Messaging-Broker
    #webMethods


  • 5.  RE: Sun cluster + Broker monitor

    Posted Fri July 06, 2007 07:22 PM

    Hi!
    Is me again. Problem with Broker servers were caused by a performance issue on the Storage(6320), we moved the broker servers to another storage and now it is working.

    thank you!!


    #Integration-Server-and-ESB
    #webMethods
    #broker
    #Universal-Messaging-Broker