Jdk6 RMI Tunneling - ServletHandler - GET Operation no supported

Question

Hi there
I have downloaded the jdk6 docummentacion and I want to use the RMI tunneling sample. I have already set up the Apache/Tomcat in order to to a rewrite of the rmi-cgi call to the servlet
RewriteEngine on
RewriteLog /var/log/httpd/rewrite.log
RewriteLogLevel 0
RewriteRule cgi-bin/java-rmi\.cgi$ http://myhost/maindb_dev/rmi/tunnel
And testing the call to the cgi program it changes the url to the servlet one. So the configuration of the Servlet is OK
Then running the RMIClient provided by the jdk
it catches a remote exception
Error: Error unmarshaling return header; nested exception is:
     java.io.IOException: HTTP request failed
java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
     java.io.IOException: HTTP request failed
     at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:209)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at java.rmi.Naming.lookup(Naming.java:84)
     at SampleRMIClient.main(SampleRMIClient.java:89)
Caused by: java.io.IOException: HTTP request failed
     at sun.rmi.transport.proxy.HttpSendSocket.readNotify(HttpSendSocket.java:159)
     at sun.rmi.transport.proxy.HttpSendInputStream.read(HttpSendInputStream.java:66)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
     at java.io.DataInputStream.readByte(DataInputStream.java:248)
     at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195)
     ... 4 more
At the tomcat side the servletHandler outputs the following
400Java RMI Client ErrorGET Operation not supported: Can only forward POST requests.
So what it seems is that the RMI implementation uses a GET request instead of a POST. That is the one handle by the Servlet.
Any body solved this?
Thanks in advance
Alfonso.

Answer 1

Hello,
JSR 262 (Web Services Connector for JMX Agents) offers an HTTP based Connector that is compliant with JConsole.
The standard is not yet final but is already in public review and we don't expect major changes.
The latest Reference Implementation (early access 3) can be downloaded from http://ws-jmx-connector.dev.java.net
Reusing your Connector presentation I would say :
Use of JMX WS Connector
Advantages
* Standard
* Firewall friendly
Disadvantages
* Standalone. You need to add jars (quite a bunch actually) to JConsole classpath.
* Less efficient than RMI or JMXMP.
References
Project web site : http://ws-jmx-connector.dev.java.net
Article that cover the EA3 announcement : http://blogs.sun.com/jmxnetbeans/entry/web_services_connector_for_jmx#comments
Article that details the Connector architecture :
http://blogs.sun.com/jmxnetbeans/entry/up_the_metro_stack_to
Thanks.
Jean-Francois