On 6/7/13 9:35 AM, Alan Wright wrote: > Hi > > We are sending messages using hessian from our server to another server. > > When both servers were on Resin 2.1.17 all was OK. > > We have since upgraded to Resin 4.0.36 on our server (when will the 4.1 > series come out by the way?)
Hmm. I'm not sure. We've been working on getting a usable 7.0.0 out. > > Now the client code no longer works - throwing the following error on > our server (the client) at the point where the remote method is invoked. > > I am I doing something stupid expecting the 2 to communicate. Is it > possible to get a Hessian 2 client to talk to a hessian 1 server? > I'm not sure about 2.1.17. It's very old. Hessian 2/1 are designed to interoperate (basically the caller sends at Hessian 1 call with a note that it can upgrade to Hessian 2.) -- Scott > > com.caucho.hessian.client.HessianRuntimeException: > com.caucho.hessian.io.HessianProtocolException: ' > ' is an unknown code > at > com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:222) > at $Proxy0.addRegistrant(Unknown Source) > at > com.athene.jaffa.xbatch.admin.MarketMakerTransferXBatch.main(MarketMakerTransferXBatch.java:77) > Caused by: com.caucho.hessian.io.HessianProtocolException: ' > ' is an unknown code > at > com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:220) > ... 2 more > > > > Thanks > > > > Alan > _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
