Jerry Sawa

Forum Replies Created

Viewing 15 replies – 1 through 15 (of 47 total)
  • Author
    Replies
  • in reply to: TLS TCP/IP HL7 #121970
    Jerry Sawa
    Participant

      They did.  Sorry, I neglected to include.

      The mode can be ClientAuth,

      SSl Protocol — TLS 1.3.   

      Cipher list — TLS_AES_128_GCM_SHA256.

       

      in reply to: TLS TCP/IP HL7 #121965
      Jerry Sawa
      Participant

        I would put the URL in the “Host:” field?  See “PDF TCPIP Properties” attachment.

        Not sure what to enter in the fields in the “CA Path  CA File” attachment.

        Attachments:
        You must be logged in to view attached files.
        in reply to: Cloverleaf API #121639
        Jerry Sawa
        Participant

          Following…..

          Infor – Is there any documentation?

          in reply to: Threaded write failed: Broken pipe! #121182
          Jerry Sawa
          Participant

            Not sure what type of logging configurations you have setup, but you can try Infor’s “enable_all“.  Keep in mind that this will add A LOT of entries into your log.  I only use “enable_all” for trouble shooting issues then I remove it when the issue is resolved.  There are other configurations but I don’t know if they’ll give you what you need.

            Within the thread on the “Properties” tab, “Engine Log Configuration“.  Click list to get a listing of all Engine Log Configurations available.

            in reply to: Threaded write failed: Broken pipe! #121170
            Jerry Sawa
            Participant

              I’ve receive base64 encoded PDF msgs larger than 10mb without issue.  So your issue may reflect back to what Jeff Dinsmore previously stated.   Unfortunately, I don’t know how to increase the size of the max files configuration.

              Are there any other entries in your log other than the Broken Pipe entry?  You may need to increase the logging level of the thread to see if more entries are listed regarding the error that may guide you to the cause/resolution.

              in reply to: Threaded write failed: Broken pipe! #121166
              Jerry Sawa
              Participant

                From my experience with Broken Pipe, thread was unable to write because the connection dropped.  Make sure vendor side has the same settings in Prod as it does in Test.

                in reply to: “and” alert and Source Count #121104
                Jerry Sawa
                Participant

                  Hi Lauri.  I really didn’t need the alert I was trying to set up, just wanted to test how Source Count works.  Looks like it doesn’t work the way it’s supposed to.

                  I’ve never used “in” before and don’t know anything about it.  I’ll test that and see how it goes.

                  Thanks.

                  in reply to: “and” alert and Source Count #121097
                  Jerry Sawa
                  Participant

                    I found the following

                    Source Count – This specifies how many of the selected entities must satisfy the condition for the alert to trigger.

                    Has anyone had any success using Source Count?

                    • This reply was modified 1 year, 2 months ago by Jerry Sawa.
                    • This reply was modified 1 year, 2 months ago by Jerry Sawa.
                    in reply to: “and” alert and Source Count #121095
                    Jerry Sawa
                    Participant

                      Correct.  I want the alert to trigger if one or the other are true.  With Source Count valued as “any” or “at least 1”, I was hoping that would work.  Is that not possible?

                      in reply to: High Inbound Message Threshold alert? #121007
                      Jerry Sawa
                      Participant

                        So you look for a threshold of 4000 for how many minutes?

                        in reply to: High Inbound Message Threshold alert? #121005
                        Jerry Sawa
                        Participant

                          Looks like I may be able to use “transactions/sec”.

                          in reply to: Unable to bind tcp/ip socket: Address already in use #120788
                          Jerry Sawa
                          Participant

                            Thanks everyone.  I never heard anything about ephemeral ports.  I appreciate the input and we will take that into consideration in the future for new threads.  However, we’ve been on Cloverleaf for many years and have many many many many threads.  We’ll see what ports we can change for existing interfaces, but until we do, does anyone know of a way to send an alert when this happens?   Protocol status is “opening”, so we can’t check for “error”.

                            • This reply was modified 1 year, 7 months ago by Jerry Sawa.
                            in reply to: Unable to bind tcp/ip socket: Address already in use #120783
                            Jerry Sawa
                            Participant

                              Thanks so much for your help James.  The command didn’t work for me (-bash: /usr/sbin/no: No such file or directory), but I’ll see what I can find.  The range you gave earlier was a big help.

                              in reply to: Unable to bind tcp/ip socket: Address already in use #120777
                              Jerry Sawa
                              Participant

                                Unfortunately, the Protocol Status is “opening“.   Sorry, I should have mentioned that before.

                                How can I find out what the ephemeral range for ports is?

                                in reply to: Unable to bind tcp/ip socket: Address already in use #120774
                                Jerry Sawa
                                Participant

                                  Port number — 53021

                                  OS is Redhat 8

                                  It doesn’t happen often, and it is not just one thread that has the issue.  It doesn’t happen very often, maybe once every couple of months.

                                Viewing 15 replies – 1 through 15 (of 47 total)