Hi Eric,
Hubert, Eric wrote:
Hello Ruwan,
here comes a short and very brief feedback from my first hessian test of
this SNAPSHOT-build.
1) It really fixes the blocking issue. Great!
2) The fault handling needs some enhancement.
On the server side I find the following exception in the log:
2008-04-01 20:26:13,266 1040147606 ERROR
[org.apache.catalina.core.ContainerBase] (http-10.35.30.41-8180-1:)
Servlet.service() for servlet HessianService threw exception
com.caucho.hessian.io.HessianProtocolException:
findAlbumsNewReleases__6: expected long at 83
at
com.caucho.hessian.io.Hessian2Input.error(Hessian2Input.java:2408)
[...]
On the client side the hessian client receives an HTTP 200 and reads the
reply (HessianInput.readReply()), but the reply does not start with an
'r'-Tag (no valid Hessian reply). So it creates a new
HessianProtocolException on the client with message: "expected hessian
reply".
Yes, I will fix that in the next build...
While having a short look at the bytes of the InputStream I got the
impression that this might be a hessian fault just without the needed
reply header (r x02 x00)?
Yeah. You are exactly correct.
In the end the client only receives something like:
com.caucho.hessian.client.HessianRuntimeException:
com.caucho.hessian.io.HessianProtocolException: unknown code:c
which is the client side exception. Any information about the server
side exception is hidden.
So it might be that we are very close to an optimal solution. I'm not
sure. It depends on the content of the reply which right now is no valid
hessian reply. Besides that it seems to be the right approach to send a
hessian fault within a HTTP 200 reply.
I will wait for your reply and decide whether it would make sense to
wait for a new build or do more tests with the current build.
Well, I will write the formatter and builder pair to get the HTML
message and pass it to the client. You may continue on the successful
path where as the next build will provide the fixes to the fault path..
Again I would like to express that you guys did a great job on the
hessian side so far and I'm quite optimistic that we will also solve the
hopefully last issue on this.
Yes. I think we can solve this issue, I will provide a build to you by
tomorrow.
Thanks,
Ruwan
Regards,
Eric
-----Original Message-----
From: Ruwan Linton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 2:14 PM
To: [email protected]
Cc: Hubert, Eric
Subject: Re: [esb-java-dev] Re: Feedback Hessian-Support in
SNAPSHOT-Build
Hi Eric,
I will test the ESB for some more scenarios and let you know
tomorrow,
after making a build available to you.
Here is the build [1] which fixes the blocking issue and the fault
handling, you may go through the test cases and provide us with the
feedback. (You will need to put the configuration attached with this
for
Hessian message routing, just replace the synapse.xml file found at
$ESB_HOME/webapp/WEB_INF/classes/conf folder before starting the ESB)
[1] -
http://ww2.wso2.org/~ruwan/jamba/v3/wso2-esb-java-SNAPSHOT-bin.zip
Thanks,
Ruwan
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
