Application Server pod can no longer communicate with Database pod after a cluster restart or pod migrating to another application node

Solution Unverified - Updated -

Issue

When the MySQL pod migrates to another application node (after a cluster reboot or a node scheduling change) the application server can no longer communicate with the database.

Environment

  • OCP 3.7
  • Java Based Application Server Containers: eap64-openshift, eap71-openshift, webserver31-tomcat7-openshift, webserver31-tomcat8-openshift
  • Database: mysql-57-rhel7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In