cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re: problems after upgrading jetty and hessian to the latest version
Date Tue, 23 Nov 2010 08:46:29 GMT
Haven't tried the latest Hessian, but historically Hessian arbitrarily changed the serialization
protocol between versions, so switching to a newer version required some tweaking on our end.

Jetty 7 on the other hand just works... The only thing that caused me trouble with 6->7
upgrade about a year ago, was a change in cookie encoding algorithm. 


On Nov 17, 2010, at 12:33 AM, Marcin Skladaniec wrote:

> Hello
> I was wondering if someone has tried cayenne with jetty 7 and hessian 4.
> After some trial and error I finally got to the stage where servlet is replying, but
cayenne fails to establish ClientChannel. this is the log
> org.apache.cayenne.CayenneRuntimeException: [v.3.0.1 Aug 04 2010 18:38:23] Error establishing
remote session. URL - http://localhost:8181/angel-server-cayenne; CAUSE - expected integer
at 0x53 java.lang.String (org.apache.cayenne.remote.RemoteSession)
>    [java]   [O] S [\x00'org.apache.cayenne.remote.RemoteSession\x94\x04name\x09sessionId\x12eventBridgeFactory\x15eventBridgeParameterso\x90N\x1913mrh1ds35gq3cu0vcyroaazzNNz]
> at org.apache.cayenne.remote.hessian.HessianConnection.connect(
>    [java]     at org.apache.cayenne.remote.hessian.HessianConnection.getServerEventBridge(
>    [java]     at org.apache.cayenne.remote.ClientChannel.setupRemoteChannelListener(
>    [java]     at org.apache.cayenne.remote.ClientChannel.<init>(
>    [java]     at org.apache.cayenne.remote.ClientChannel.<init>(
>    [java]     at org.apache.cayenne.remote.ClientChannel.<init>(
>    [java]     at ish.oncourse.ContextManager.getDataChannel(
>    [java]     at ish.oncourse.ContextManager.getChannel(
>    [java]     at ish.oncourse.ContextManager.getNewDedicatedContext(
>    [java]     at ish.oncourse.controller.ViewController.getContext(
> seems like something has changed on the deserialisation level(?) in hessian, but I cannot
pinpoint what.
> Has someone hit or maybe solved this problem?
> Thanks
> Marcin

View raw message