-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
JBoss A-MQ 6.3
-
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
- is duplicated by
-
ENTMQ-2231 EOFException warning is over-zealous
- Closed