tcp connections

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf tcp connections

  • Creator
    Topic
  • #47639
    David Harrison
    Participant

      Cloverleaf 5.2 on Solaris 8 with Veritas clustering.

      I’m trying to get a raw ip connection working (not using a pdl) using the default settings. As soon as I get any inbound data I get the following error: ‘tcp :read:ERR /0:   TEL_CLI_IN] Length encoding wrong?; read len of 1145132076’.

      Can anyone shed any light on what the settings should be?

      Dave

    Viewing 6 reply threads
    • Author
      Replies
      • #56324
        Jim Kosloskey
        Participant

          Have you tried hcitcptest utility? That might help you find out what they are sending you. You could also turn up the EO.

          However, you need to know what length encoding mechanism the sending system is employing (if any). Once you know that, then you can configure Cloverleaf appropriately.

          Jim Kosloskey

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

        • #56325
          Rob Abbott
          Keymaster

            Sounds like he wants a “raw” tcp connection.

            Cloverleaf needs something to define a message in the stream – either length encoding or encapsulation.

            Rob Abbott
            Cloverleaf Emeritus

          • #56326
            Anonymous
            Participant

              David,

              What does the message look like?  Can you include a hex dump from the log?  We might be able to make a suggestion after seeing the message.

            • #56327
              David Harrison
              Participant

                Here is a couple of  example messages from our CliniCom PAS (enclosed in square braces for readability):

                [DAT001001NLS0030NP      100BB0]

                [DAT002001END0266NP103000000000                                                      00000000                                                                                                                                                       00000000      102      ]

                Different types of message have different lengths but the byte count is contained in pos 14-16. How can Cloverleaf use this byte count?

              • #56328
                Jim Kosloskey
                Participant

                  I believe the length encoded tcp-ip protocol provided by Cloverleaf requires the length to be at the beginning of the message (rightfully so in my opinion).

                  I suspect you are looking at using a PDL to support this message structure unless you can convince the vendor to place the count at the beginning where I believe it belongs.

                  Jim Kosloskey

                  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

                • #56329
                  David Harrison
                  Participant

                    Thanks, I think I’ll use a pdl.

                    Dave

                  • #56330
                    Dirk Engels
                    Participant

                      David,

                      we have the Clinicom PAS here in germany as well and we connected it with a pdl and an ib tcl proc which collects all single buffers to a message. Clinicom splits all messages in buffers of max. 256 bytes.

                      Dirk

                  Viewing 6 reply threads
                  • The forum ‘Cloverleaf’ is closed to new topics and replies.