How to setup JNDI / EJB / JMS over HTTP in JBoss EAP 6

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.4
    • 6.3
    • 6.2
    • 6.1.x
    • 6.0.x

Issue

  • While migrating an application from JBoss EAP 5.x to 6.0, that was using EJB over HTTP in JBoss EAP 5.x, how can we do this in JBoss EAP 6 ?

  • Does JBoss EAP 6.x support RMI over HTTP?

  • We are migrating to JBoss EAP 6 and our client has this error: Failed to retrieve Naming interface for provider http://host:8080/invoker/JNDIFactory [Root exception is java.io.FileNotFoundException: http://host:8080/invoker/JNDIFactory]

  • How to configure the HTTP Invokers behind an Apache HTTPD reverse proxy such that the clients could retrieve the initial reference via a well-known URL, and from there on, use EJB3 (or JMS) as normal.

  • The older JBoss releases allowed calling EJB remote over HTTP proxy, is it possible to execute remote EJB calls via an HTTP proxy?

  • How to use an external load balancer for EJB calls in JBoss EAP?

Resolution

EAP 7.1

See: How to invoke an EJB over HTTP in EAP 7.1

EAP 6

Does NOT have a feature to use JNDI, EJB, JMS over a HTTP transport similar to EAP 5.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments