IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
Back to discussions
Expand all | Collapse all

Socket Problems in a Cluster environment

  • 1.  Socket Problems in a Cluster environment

    Posted 12/16/09 06:21 AM

    Originally posted by: ChB


    Hello guys,

    do you have an idea, what this is? We are using DSTX 8.0 under Solaris 10 in a cold standby system.

    Tonight we had some issues and we want to find out, what it is.

    This is from one of our launcher logs:

    
ASCL-TX-ES-E-4105 - Wed Dec 16 01:38:39 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 01:55:20 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 01:59:01 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:03:21 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:18:09 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:20:43 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:20:48 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:20:53 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:23:04 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:32:07 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:34:58 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:38:50 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:38:56 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:39:01 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:39:06 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621) ASCL-TX-ES-E-4105 - Wed Dec 16 02:39:12 2009 - tid:    37 inst:    -1 - Socket error : err=0 socket=112 ret=0 (mstatsoc.c:4621)


    We can see in the var/adm/messages the following entries:

    
Dec 16 01:38:41 DDIDH055 [ASCL.scdstx,ebib_appl-rg,DataStage_TX-rs]: [ID 702911 daemon.error]  FLCOND:Monitor failed to get info: Error=106 Dec 16 01:55:18 DDIDH055 [ASCL.scdstx,ebib_appl-rg,DataStage_TX-rs]: [ID 702911 daemon.error]  FLCOND:Monitor failed to get info: Error=106 Dec 16 02:20:53 DDIDH055 [ASCL.scdstx,ebib_appl-rg,DataStage_TX-rs]: [ID 702911 daemon.error]  FLCOND:Monitor failed to get info: Error=99 Dec 16 02:32:07 DDIDH055 [ASCL.scdstx,ebib_appl-rg,DataStage_TX-rs]: [ID 702911 daemon.error]  FLCOND:Monitor failed to get info: Error=106 Dec 16 02:38:52 DDIDH055 last message repeated 2 times Dec 16 02:39:05 DDIDH055 [ASCL.scdstx,ebib_appl-rg,DataStage_TX-rs]: [ID 702911 daemon.error]  FLCOND:Monitor failed to get info: Error=106

    So it looks like, the monitor was not able to "talk" to the launcher anymore. The result was: the launcher was trying to stop (not successful, but this is another story) the launcher.

    As the launcher was running fine, I have no idea, what the problem could have been. Have you seen this before? Any ideas to prevent this? Are there other logs to see?

    Thanks in advance

    Christian
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender