Error message "javax.naming.CommunicationException: WFHTTP000005: Invalid response code 400" seen on EJB connection

Solution Verified - Updated -

Issue

  • An EJB Application is split into two different Red Hat OpenShift Container Platform (RHOCP) clusters.
  • The communication is working over an EJB connection.
  • The communication is running fine in Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.3.
  • After migrating both EJB client and the EJB to RHOCP 4 and to JBoss EAP 7.4 the communication is no longer working.
  • The following errors are seen in the logs:

    • EJB client side:

      "Caused by: javax.naming.CommunicationException: WFHTTP000005: Invalid response code 400"
      
    • EJB side:

      "Authentication failed with message ELY05169: [DIGEST] Clients response token does not match expected token and mechanism DIGEST for HttpServerExchange" 
      

Environment

  • Red Hat JBoss Enterprise Application Platform (JBoss EAP)
    • 7.4
  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content