pdl problem

  • Creator
    Topic
  • #47819
    Nick Schneider
    Participant

      having a problem with some messages being received.  It looks to be a mlp_tcp_pdl problem but I am not sure.  I see the no more phrases to try entry in the error log.  I pumped the EO up to enable all.  From what I can tell it looks like we receive the start block then several lines after that I get some things happening that I don’t expect (I say this because I was comparing it to a successful message).  Then the next portion of the message comes in and this is where the no more phrases to try starts.  I believe that something is killing the first part of the transmission so when the second portion of the message comes across the PDL is looking for the start block once again and when it doesn’t see it I get the no more phrases to try.  

      I am attaching a portion of a log from a successful message and an unsuccessful message.

    Viewing 2 reply threads
    • Author
      Replies
      • #56789
        Jim Kosloskey
        Participant

          Nick,

          On the message that failed you timed out between the receipt of a single byte (start of the mlp encapsulation) until the rest of the message.

          The timeout is at 15 seconds so that is a long time for delivery of portions of a message.

          I might suspect there is a problem with the sending system or perhaps the network in between.

          Jim Kosloskey

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

        • #56790
          Nick Schneider
          Participant

            After pouring through snifer traces I discovered exactly where this timeout was occurring.  The app that was connecting to us would establish a socket connection send the beginning of block packet, we would then ACK that packet then the app would go out and format the message to be sent.  This formatting is taking 18 seconds which is where the timeout occurs.  Unfortunately like all projects we are always forced to figure out why the other end is broken.

          • #56791
            Jim Kosloskey
            Participant

              Nick,

              I am glad you found it.

              Fortunately we can do it.

              Hopefully our collective management understands the value of that.

              Jim Kosloskey

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

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