Topic
  • 6 replies
  • Latest Post - ‏2013-04-18T17:01:57Z by Morag Hughson
SystemAdmin
SystemAdmin
8523 Posts

Pinned topic TCS-IP connection default setting on SOLARIS SPARC 9

‏2013-03-23T17:09:59Z |
Sorry for asking some OS specific question on MQ platform.

I want to know default TCS-IP connection setting on Sun SOLARIS SPARC 9 and Windows server 2003.

I am using MQ client-Server communication, It is working on (Windows-Windows) but it's not working on (Solaris-AIX) in order to client-server respectively.

I want connect MQ server on my Apps initialization and call service method for MQPUT, I am using C lang.

Please ask me if you need more clarification.
Thanks in Advance.
Updated on 2013-04-03T22:15:59Z at 2013-04-03T22:15:59Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: TCS-IP connection default setting on SOLARIS SPARC 9

    ‏2013-03-24T23:31:20Z  
    > it's not working on (Solaris-AIX)

    It would be helpful to post the error message or codes that were displayed.

    >TCS-IP

    Do you really mean TCP-IP ?

    >MQ client-server communication configuration is the same on Windows, Solaris and AIX. Make sure the client channel is configured with the correct host name and port number of the queue manager. Make sure the SVRCONN channel name is correct.

    HTH, G.
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: TCP-IP connection default setting on SOLARIS SPARC 9

    ‏2013-03-29T09:36:31Z  
    > it's not working on (Solaris-AIX)

    It would be helpful to post the error message or codes that were displayed.

    >TCS-IP

    Do you really mean TCP-IP ?

    >MQ client-server communication configuration is the same on Windows, Solaris and AIX. Make sure the client channel is configured with the correct host name and port number of the queue manager. Make sure the SVRCONN channel name is correct.

    HTH, G.
    Sorry for confusion, Yes it is TCP-IP.

    This is i am receiving on AIX sever. My was disconnected from MQ server after some time. but it is not happening at windows MQ server.
    Could you tell me which attribute is affecting this process. I already check TCP-IP connection keepAlive parameter.

    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9271: Channel 'SYSTEM.DEF.SVRCONN' timed out.

    EXPLANATION:
    A timeout occurred while waiting to receive from the other end of channel
    'SYSTEM.DEF.SVRCONN'. The address of the remote end of the connection was
    '192.168.23.42'.
    ACTION:
    The return code from the select() TIMEOUT 65 seconds call was 0 (X'0').
    Record these values and tell the systems administrator.

    amqccita.c : 3773
    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9999: Channel program ended abnormally.

    EXPLANATION:
    Channel program 'SYSTEM.DEF.SVRCONN' ended abnormally.
    ACTION:
    Look at previous error messages for channel program 'SYSTEM.DEF.SVRCONN' in the
    error files to determine the cause of the failure.
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: TCP-IP connection default setting on SOLARIS SPARC 9

    ‏2013-04-01T22:15:24Z  
    Sorry for confusion, Yes it is TCP-IP.

    This is i am receiving on AIX sever. My was disconnected from MQ server after some time. but it is not happening at windows MQ server.
    Could you tell me which attribute is affecting this process. I already check TCP-IP connection keepAlive parameter.

    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9271: Channel 'SYSTEM.DEF.SVRCONN' timed out.

    EXPLANATION:
    A timeout occurred while waiting to receive from the other end of channel
    'SYSTEM.DEF.SVRCONN'. The address of the remote end of the connection was
    '192.168.23.42'.
    ACTION:
    The return code from the select() TIMEOUT 65 seconds call was 0 (X'0').
    Record these values and tell the systems administrator.

    amqccita.c : 3773
    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9999: Channel program ended abnormally.

    EXPLANATION:
    Channel program 'SYSTEM.DEF.SVRCONN' ended abnormally.
    ACTION:
    Look at previous error messages for channel program 'SYSTEM.DEF.SVRCONN' in the
    error files to determine the cause of the failure.
    >ACTION:
    >The return code from the select() TIMEOUT 65 seconds call was 0 (X'0').
    >Record these values and tell the systems administrator.

    It looks like an issue with the TCP stack on the local server. The TCP-IP socket call select() should not time out. I suggest that you follow the advice of the MQ message, and contact the system administrator.

    HTH, G.
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: TCP-IP connection default setting on SOLARIS SPARC 9

    ‏2013-04-02T14:22:19Z  
    >ACTION:
    >The return code from the select() TIMEOUT 65 seconds call was 0 (X'0').
    >Record these values and tell the systems administrator.

    It looks like an issue with the TCP stack on the local server. The TCP-IP socket call select() should not time out. I suggest that you follow the advice of the MQ message, and contact the system administrator.

    HTH, G.
    Thanks,

    Sorry for my question may be it is more related to OS.
    How can we track TCP setting at MQ client and server.
    MQ client at: Solaris 9 Sparc
    MQ server at: AIX
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: TCP-IP connection default setting on SOLARIS SPARC 9

    ‏2013-04-03T22:15:59Z  
    Thanks,

    Sorry for my question may be it is more related to OS.
    How can we track TCP setting at MQ client and server.
    MQ client at: Solaris 9 Sparc
    MQ server at: AIX
    >How can we track TCP setting at MQ client and server.

    What do you mean by that? Do you want to track settings in the TCP stack, or in MQ?

    In MQ, you can use runmqsc display the channel definition, and display the channel status while it is attempting to start. You can also run MQ trace to see more gory details.

    To track what is happening in TCP you will need to speak to a networking / communications specialist.

    HTH, G.
  • Morag Hughson
    Morag Hughson
    140 Posts

    Re: TCP-IP connection default setting on SOLARIS SPARC 9

    ‏2013-04-18T17:01:57Z  
    Sorry for confusion, Yes it is TCP-IP.

    This is i am receiving on AIX sever. My was disconnected from MQ server after some time. but it is not happening at windows MQ server.
    Could you tell me which attribute is affecting this process. I already check TCP-IP connection keepAlive parameter.

    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9271: Channel 'SYSTEM.DEF.SVRCONN' timed out.

    EXPLANATION:
    A timeout occurred while waiting to receive from the other end of channel
    'SYSTEM.DEF.SVRCONN'. The address of the remote end of the connection was
    '192.168.23.42'.
    ACTION:
    The return code from the select() TIMEOUT 65 seconds call was 0 (X'0').
    Record these values and tell the systems administrator.

    amqccita.c : 3773
    03/29/13 03:50:44 - Process(516096.28) User(mqm) Program(amqrmppa)
    Host(paibib1_nr)
    AMQ9999: Channel program ended abnormally.

    EXPLANATION:
    Channel program 'SYSTEM.DEF.SVRCONN' ended abnormally.
    ACTION:
    Look at previous error messages for channel program 'SYSTEM.DEF.SVRCONN' in the
    error files to determine the cause of the failure.

    This is caused by a receive timing out. There are various times when responding channels wait for a response from the partner, and a feature known as ReceiveTimeOut stops them from waiting for a very long time and relying on KeepAlive if the network connection is actually broken. The amount of time that a receive will wait for is based on the heartbeat value plus a little extra time to account for latency. Since the error message shows that your timeout was after 65 seconds. From this I can guess that your heartbeat is set to 30 seconds. The default configuration is to multiply your heartbeat by 2 if it is less than 60 seconds. The extra 5 seconds are added to ensure that the client-conn and server-conn don't send heartbeats at exactly the same time from both ends.

    So, to answer "which attribute is affecting this process" the answer is the heartbeat and the default setting of ReceiveTimeOut.

    Have a read of MD0C: WebSphere MQ - Keeping Channels Up and Running for more information on these settings.