Hi,
Please note that as
of the 8th February my email address has changed from [EMAIL PROTECTED] to [EMAIL PROTECTED].
Could you please update your address book, and direct any
email to my new address.
Cheers,
Lee
BEGIN:VCARD VERSION:2.1 N:Smith;Lee FN:Lee Smith ORG:Oracle Corporation Ltd.;Oracle Energy Downstream TITLE:Associate Software Engineer NOTE;ENCODING=QUOTED-PRINTABLE: TEL;WORK;VOICE:+44 (0) 1442 437774 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Hemel Hempstead;Breakspear Park=0D=0ABreakspear Way;Hemel Hempstead;Herts;H= P2 4UL;United Kingdom LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Hemel Hempstead=0D=0ABreakspear Park=0D=0ABreakspear Way=0D=0AHemel Hempstea= d, Herts HP2 4UL=0D=0AUnited Kingdom EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20010417T080725Z END:VCARD
--- Begin Message ---Hi. Lately I sent an email describing my problems with the rmi-http-tunneling. Many of you may have stumbled upon these problems. Well... I was able to run it, even over HTTPS!Problem description: The rmi-http-tunnel servlet bundled with Orion 1.5.2 (maybe other versions also) does not flush the response buffers, after sending the required response headers to the client. That results in a deadlock: 1. The client sends the request to the server. 2. The servers sets the required headers for the reply, so that the client understands, that this IS really a tunnel servlet. These are "tunnel-type: normal" and "dummy: normal" headers. 3. THE SERVLET SHOULD FLUSH ITS BUFFERS, so that the client receives the affirmative response for tunneling services. This is not done by the bundled servlet. 4. The client waits to hear the headers, that are required by it (those mentioned in 2). However the servlet has not flushed, and the client waits forever. It will not send the real rmi request, and the server will also not do anything. This results in a deadlock. The client waits for the headers in the response, the server waits for further request. Solution: Write your own tunneling servlet. If you want to deploy it with a name differnet than "rmi", then you should supply the "http.tunnel.path=/servlet/your_servlet_name" property in the jndi.properties, ot the environment properties. P.S. I'm not sure, if orion-boys will soon fix this. I'm also not sending my servlet, for obvious reasons. Lachezar--- End Message ---
