mod_cluster proxy connections from JBoss to Apache only use the default interface

Solution Verified - Updated -

Issue

  • We use mod_cluster with JBoss and JBoss is bound to a secondary virtual ip we've added. We still see that mod_cluster creates it's proxy connection to apache on the default interface and not the specified bind address. Is there anyway we can configure mod_cluster to use the designated ip for this connection?

  • mod_cluster does not use the interface specified by -b (jboss.bind.address) option. The default interface is used instead. How can I get mod_cluster to use the specified interface?

  • It does not appear that the modcluster subsystem 1.1 is sending the mcmp request to apache via the jboss.bind.address. Instead, the request is sent from the host server's ip instead. Is there a way to configure the mcmp request to apache to use the jboss.bind.address?

Environment

  • JBoss Enterprise Application Platform (EAP)

    • mod_cluster
  • JBoss Enterprise Web Server (EWS)

    • Apache httpd

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