JMXInvokerServlet invoked by a standalone program
Hi,
I've been searching in different forums, i can?t found anybody who already met the following issue:
I got connection refused when i invoke the JMXInvokerServlet remotely from a standalone application in JBoss/Tomcat bundle 4.0.5 behind Apache 2.0 using mod_jk 1.2.20.
I need to access JBoss ejb tier through http avoiding rmi calls. The following tests j've made run locally on Windows xp environment , and remotely on Redhat Lunix.
The application is downloaded and deployed through java Web Start and uses JNDI over http provided by http-invoker.sar to access the server. Within jnlp file, all resources come from the same server.
I?m using mod_jk configuration exactly as described at http://www.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss and my uriworkermap.properties contains:
/invoker=loadbalancer
/invoker/*=loadbalancer
The application works fine on the localhost with the following jndi.properties:
java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory
java.naming.provider.url=http://localhost/invoker/JNDIFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
and with the jboss-service configuration snippet code of the HTTP invoker service:
<attribute name=InvokerURLPrefix>http:// < /attribute>
<attribute name=InvokerURLSuffix>/invoker/JMXInvokerServlet < /attribute>
Also, every thing goes well when accessing directly and remotely JBoss/Tomcat by shunting Apache+mod_jk using:
- java.naming.provider.url=http://www.mydomain.com:8080/invoker/JNDIFactory
and
- <attribute name=InvokerURLSuffix>:8080/invoker/JMXInvokerServlet < /attribute>
But i got connection refused when accessing JBoss/Tomcat remotely through Apache, and mod_jk with the following:
- java.naming.provider.url=http://lwww.mydomain.com/invoker/JNDIFactory
and
- <attribute name=InvokerURLSuffix>/invoker/JMXInvokerServlet < /attribute>
see message below.
I can't figure out what's wrong or missing, any help will greatly be appreciated.
Thanks.
Alain
Caused by: java.rmi.ServerException: IOE; nested exception is:
java.net.ConnectException: Connection refused: connect
at org.jboss.invocation.http.interfaces.HttpInvokerProxy.invoke(HttpInvokerProxy.java:118)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
at org.jboss.naming.interceptors.ExceptionInterceptor.invoke(ExceptionInterceptor.java:42)
... 34 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at org.jboss.invocation.http.interfaces.Util.invoke(Util.java:145)
at org.jboss.invocation.http.interfaces.HttpInvokerProxy.invoke(HttpInvokerProxy.java:103)
... 37 more