HTTP proxy support for EJB clients

[bhawthorne]

We have a standalone application client connecting to a Wildfly 9.0.1 server. Client is using the jboss-ejb-client library and we are looking up remote beans with JNDI. We migrated from JBoss 6 a while back, and while that supported proxies, it seems that an EJB client connecting to Wildfly ignores any system properties such as java.net.useSystemProxies or http.proxyHost.

Is it at all possible for the EJB client to be directed to the server via proxy? I have seen this question asked a few times before, but not with any clear answers.

Thanks.

[nlsurfman]

I am facing the same issue. Properties like http.proxyHost and its brethren seem to be ignored. It doesn't sound impossible to run the JBoss http-remoting client through a proxy. Did we miss a setting somewhere?

[jhayes007]

I am having same issue; -Dhttp.proxyHost=10.1.0.149 -Dhttp.proxyPort=3128 seem to be ignored when running the lastest JBoss example HelloWorldJMSClient.

[jbertram]

I've seen you post about this issue at https://developer.jboss.org/thread/250368 as well.  I work on the JMS implementation so I might be able to help, but I don't understand the full use-case here.  If you started a new thread with a full explanation of your use-case, what you expect to happen, and what is actually happening then maybe I can help.

[jhayes007]

I am using EAP7 and running the jboss-eap-quickstarts-7.0.0.GA\helloworld-jms example.

Using the -Dhttp.proxyHost=10.1.0.149 -Dhttp.proxyPort=3128 command line options when invoking the client program is expected to go through the proxy server at 10.1.0.149:3128 however continues to use the address encoded in the PROVIDER_URL.

[jbertram]

As I said before, if you started a new thread with a full explanation of your use-case, what you expect to happen, and what is actually happening then maybe I can help.  Hijacking this thread related to EJB clients probably isn't the best way to get your question answered.

[jhayes007]

I created a new thread pertaining to my current issue as suggested, please find this at Running jboss-eap-quickstarts-7.0.0.GA\helloworld-jms through proxy.  and reply with a comment.

[elisabethwidow]

I am facing the same issue (as the original post) using wildfly 9.0.1.

A standalone server is behind a proxy and can be reached by a browser with the appropriate proxy settings.

A Java client is started with options -Dhttp.proxyHost=... -Dhttp.proxyPort=... -Dhttps.proxyHost=... -Dhttps.proxyPort=... but cannot connect.

The client is NOT using JMS, only trying to invoke a method in a session bean which it obtained by a JNDI lookup.

With JBoss 4.2.3, it worked fine. The wildfly client seems to ignore the options.

If access through http proxy is not supported, does anybody know whether there is a workaround, or whether it will be supported in the future?