RE: Slightly Urgent: Same configuration, Protocol Exception

Toby,

Are you overloading any methods in your remote interface. I believe that
I have observed unpredictable behavior in Hessian's handling of
overloaded remote methods. Sometimes it picks the right one, sometimes
you get a HessianProtocolException.

I believe (though I'm not positive and it does sound bizarre) that I
have seen overloaded remote methods go from working to not working with
seemingly unrelated changes in environment or code base.

A bit of a shot in the dark, but worth looking at.

Alon

> -----Original Message-----
> From: owner-hessian-interest@xxx.com [mailto:owner-hessian-
> interest@xxx.com] On Behalf Of Toby Hede
> Sent: Monday, April 18, 2005 5:59 PM
> To: hessian-interest@xxx.com
> Subject: Re: Slightly Urgent: Same configuration, Protocol Exception
>
> We're still chasing this one down. Just about at the point where
moving
> to another transport seems about the only solution. When the system
was
> moved to production, Hessian started returning ProtocolException.
> Debugging Hessian shows that the server is returning "HTTP 500:
Internal
> Server Exceptions", even though the server logs don't reveal any
> Exceptions ... the server is successfully being called, we can trace
the
> method call through our business logic, it even gets to the return
> statement. I am presuming the problem is somewhere in the Hessian
> Serialization.
>
> Any ideas would defnitely be appreciated.
>
> Toby Hede
>
>
>
>
>
> Toby Hede wrote:
>
> > We're in the process of deploying a system built using Hessian to
> > production. We have the same classes and configuration as the
staging
> > server but we are receiving Hessian Protocol Exceptions when we
> > communicate. We have literally copied the files from the staging
> > server to production, all config is the same, but it suddenly
doesn't
> > work.
> >
> > Hessian is definitely working on the production server - we added a
> > simple test method to return a String and this works fine. The
minute
> > we try and access a method returning one of our classes, the error
> > occurs.
> >
> > We've been banging our heads against this one for a while and any
> > ideas, however obvious or left-field, would be appreciated.
> >
> > Cheers,
> > Toby Hede
> >
>
>
> --
> Toby Hede
> Software Engineer
>
> WebAlive Technologies Pty Ltd
> Level 1, Innovation Building, Digital Harbour
> 1010 La Trobe Street
> Docklands Melbourne VIC 3000
> P: +61 3 9934 0888
> F: +61 3 9934 0899
> E: toby.hede@xxx.biz
> W: www.webalive.biz
>
> "Your Business, Your Web, Your Control."
>
>
> This email (including all attachments) is intended solely for the
named
> addressee. It is confidential and may contain legally privileged
> information. If you receive it in error, please let us know by reply
> email, delete it from your system and destroy any copies. This email
is
> also subject to copyright. No part of it should be reproduced, adapted
or
> transmitted without the written consent of the copyright owner.
Emails
> may be interfered with, may contain computer viruses or other defects
and
> may not be successfully replicated on other systems. We give no
warranties
> in relation to these matters. If you have any doubts about the
> authenticity of an email purportedly sent by us, please contact us
> immediately.
>
>
Received on Tue 19 Apr 2005 11:27:12 -0700