IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

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.  invalid TCP Header received ?

    Posted Tue November 09, 2004 11:30 AM

    Dear Friends,


    How can i solve this problem ?


    by " BROKER with CLASS RPC" Call , we receive


    “Broker Error 0013 0310: Broker call failed: Invalid TCP header received, length = 20”



    Here is the Profile for it !

    11:14:47 ***** NATURAL SYSPARM UTILITY ***** 2004-11-09
    - Display Profile -
    > RPC=(SERVER=ON,SRVNODE=BKRXXX,SRVNAME=SPBBNXX,MAXBUFF=28,SIZE=128,TRANSP=ACI,TRACE=0) <
    Which parameter is responsible for this error ?

    thank you in advance


    kind Regards ,

    Serdar


    #EntireX
    #Mainframe-Integration
    #webMethods


  • 2.  RE: invalid TCP Header received ?

    Posted Tue November 09, 2004 12:26 PM

    Dear Sedo,

    you get this error in a Java application which is issuing Broker calls. Basically, the problem is that the Broker cannot process the request issued by the Java application in the TCP/IP communicator.

    There are 2 ways to get more information: you might check the output of the TCP/IP communicator task for error messages. Or you can run the Java application with trace enabled, use -Dentirex.trace=3 in this case and post the output here or send it to support.

    Usually this error is due to resource shortages (especially NUM-COMBUF and NUM-WQE).

    Kind regards,
    Rolf


    #EntireX
    #webMethods
    #Mainframe-Integration


  • 3.  RE: invalid TCP Header received ?

    Posted Thu November 11, 2004 11:29 AM

    Dear Rolf,

    you wrote ;

    " There are 2 ways to get more information: you might check the output of the TCP/IP communicator task for error messages. "

    Could you please explain me a little bit more ?

    I send to you a section from file

    ETB.TCP.RCVR.00908.996


    14.10.2004:06.09.20:ETB:5.3.1.5::I::Receive Task started
    03.11.2004:09.26.48:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:09.35.01:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.40.46:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.46.44:ETB:5.3.1.5::I::Allocate memory for TcpCon buffer failed
    03.11.2004:10.46.44:ETB:5.3.1.5::I::TcpConRecv: rc: 1, errno:10014
    03.11.2004:10.46.58:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.46.58:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.47.24:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.47.37:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.47.41:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.47.41:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.48.57:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.50.17:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.50.17:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.56.49:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.56.49:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.18:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.18:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.33:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.37:ETB:5.3.1.5::I::Allocate memory for TcpCon buffer failed
    03.11.2004:10.57.37:ETB:5.3.1.5::I::TcpConRecv: rc: 1, errno:10014
    03.11.2004:10.57.49:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.49:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.53:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.57.56:ETB:5.3.1.5::I::Allocate memory for TcpCon buffer failed
    03.11.2004:10.57.56:ETB:5.3.1.5::I::TcpConRecv: rc: 1, errno:10014
    03.11.2004:10.58.08:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.58.09:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    03.11.2004:10.58.18:ETB:5.3.1.5::I::Allocate memory for TcpCon buffer failed
    03.11.2004:10.58.18:ETB:5.3.1.5::I::TcpConRecv: rc: 1, errno:10014
    04.11.2004:10.50.15:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    05.11.2004:15.17.11:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    09.11.2004:14.35.50:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:08.49.28:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:11.01.01:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:13.39.47:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:14.19.02:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:14.19.02:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:14.24.01:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:14.25.16:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    10.11.2004:14.25.36:ETB:5.3.1.5::I::Allocate memory for TcpCon buffer failed
    10.11.2004:14.25.36:ETB:5.3.1.5::I::TcpConRecv: rc: 1, errno:10014
    11.11.2004:08.10.58:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    11.11.2004:08.10.58:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    11.11.2004:08.11.26:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed
    11.11.2004:08.12.05:ETB:5.3.1.5::I::Allocate memory for Reply buffer failed

    and our attribute file :

    ** ENTIRE Broker attributes *****************************

    DEFAULTS = BROKER
    AUTOLOGON = YES
    BROKER-ID = ETB097
    TCPPORT = 1972
    CLIENT-NONACT = 5M
    CONV-DEFAULT = 1000
    LONG-BUFFER-DEFAULT = 200
    NUM-CLIENT = 200
    NUM-CONVERSATION = 5000
    NUM-LONG-BUFFER = 200
    NUM-SERVER = 100
    NUM-SERVICE = 100
    NUM-SHORT-BUFFER = 5000
    NUM-WORKER = 3
    SECURITY = NO
    SERVICE-UPDATES = YES
    SHORT-BUFFER-DEFAULT = 1000
    TRACE-LEVEL = 0
    NUM-CCOM = 5
    NUM-COMBUF = 100
    NUM-WQE = 200

    MAX-UOWS=30
    MAX-MSG=1000000
    DEFERRED=YES
    STORE=BROKER
    PSTORE=COLD
    UWSTATP=1
    UWTIME=10M

    Broker Parameters introduced in ETB52 *
    TRANSPORT=TCP-NET
    MESSAGE-CASE=UPPER
    SECURITY-PATH=usrsec.dll
    PSTORE-PATH=btpsi.dll
    ODBC-PARMS=UOWODBC.txt

    ENTIRE Broker Services ******************************

    ------------- some example services -------------------------

    DEFAULTS = SERVICE
    CONV-LIMIT = UNLIM
    CONV-NONACT = 4M
    LONG-BUFFER-LIMIT = UNLIM
    NOTIFY-EOC = YES
    SERVER-NONACT = 5M
    SHORT-BUFFER-LIMIT = UNLIM
    TRANSLATION = SAGTCHA
    TRANSLATION = c:\brokerexit\tranexit.dll
    CONVERSION = SAGTCHA

    CLASS = ACLASS, SERVER = ASERVER, SERVICE = ASERVICE
    CLASS = BCLASS, SERVER = BSERVER, SERVICE = BSERVICE
    CLASS = CCLASS, SERVER = CSERVER, SERVICE = CSERVICE
    CLASS = GAME, SERVER = CHESS, SERVICE = MAIL

    ------------- ENTIREX/NATURAL RPC services -------------------------

    DEFAULTS = SERVICE
    CONV-NONACT = 5M
    NOTIFY-EOC = NO
    SERVER-NONACT = 3M
    SHORT-BUFFER-LIMIT = UNLIM
    TRANSLATION = SAGTCHA
    TRANSLATION = sagtrpc.dll

    <<<<<<<< 50 services like this >>>>>>>>>>>>
    CLASS = RPC , SERVER = SEBBNAU1 , SERVICE = CALLNAT


    Please write your recommendation about these values !


    Thank you in advance !

    kind Regards,

    Sedo


    #EntireX
    #Mainframe-Integration
    #webMethods


  • 4.  RE: invalid TCP Header received ?

    Posted Fri November 12, 2004 03:19 PM

    we have increased NUM-COMBUF Parameter. Now we are testing the environment.

    It seems to work :wink:


    #webMethods
    #EntireX
    #Mainframe-Integration


  • 5.  RE: invalid TCP Header received ?

    Posted Tue November 16, 2004 09:44 AM

    Increasing of value

    << NUM-COMBUF >> from 100 to 150

    helped to solve this problem.

    Thank you !


    ciao

    Sedo


    #webMethods
    #Mainframe-Integration
    #EntireX