Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2235

Lot of warnings messages : Transport Connection to: tcp://x.x.x.x:<port> failed: java.io.EOFException when using probes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • JBoss A-MQ 6.3
    • container-image
    • None

      ActiveMQ instances deployed on OpenShift. Using the standard TCP connector on port 61616 for the readiness/liveness probes for OpenShift to detect the container's status. However, this produces a lot of noise in the logs, as we get the following warn message every few seconds:

      2018-09-10 16:12:44,528 | WARN | Transport Connection to: tcp://x.x.x.x:36674 failed: java.io.EOFException

      oc logs amq63-openshift-4-9gdkc | grep java.io.EOFException | wc -l
      196

      Probe used:

      readinessProbe:
      failureThreshold: 3
      initialDelaySeconds: 30
      periodSeconds: 10
      successThreshold: 1
      tcpSocket:
      port: 61616
      timeoutSeconds: 1

              Unassigned Unassigned
              rhn-support-vkamble Varsha Kamble
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: