Bug in ServerMultiMessage class of .Net

Remoting SDK
1

RO version: 7.0.71.1093
Development Platform : VS2012

serverChannel: ipHttpServerChannel

protected override void DoReadFromStream(Stream stream)
{
// Stream passed here could be still not seekable one
// Yet stream passed to the DetectActiveStream method has to be seekable
// (otherwise it would be not possible to properly pass the data to
//
Stream lSeekableStream = StreamHelpers.StreamToSeekableStream(stream);

        this.DetectActiveMessage(stream);              <-----------

        this.fActiveMessage.ReadFromStream(stream);    <-----------
        this.SerializerInstance = this.fActiveMessage.SerializerInstance;
        this.InterfaceName = this.fActiveMessage.InterfaceName;
        this.MessageName = this.fActiveMessage.MessageName;
    }

class HttpIncomingStream does not support method : Seek

fix it and work:

protected override void DoReadFromStream(Stream stream)
{
// Stream passed here could be still not seekable one
// Yet stream passed to the DetectActiveStream method has to be seekable
// (otherwise it would be not possible to properly pass the data to
//
Stream lSeekableStream = StreamHelpers.StreamToSeekableStream(stream);

        this.DetectActiveMessage(lSeekableStream);              <-----------

        this.fActiveMessage.ReadFromStream(lSeekableStream);    <-----------
        this.SerializerInstance = this.fActiveMessage.SerializerInstance;
        this.InterfaceName = this.fActiveMessage.InterfaceName;
        this.MessageName = this.fActiveMessage.MessageName;
    }
2

Hello

Thank you for your report. This issue has been logged and fixed as “70025: ServerMultiMessage fails to read data from a non-seekable stream”

3

after that about

this.MessageName = this.fActiveMessage.MessageName;

add one row code below this

this.ClientID = this.fActiveMessage.ClientID;

4

Hmm, the ClientID property is very important on the client side. But on the server side where this message resides there is not actual need to copy this property over.

5

Missing this code

this.ClientID = this.fActiveMessage.ClientID;

SessionManager create a new session Every time the same clientchannel&message call remote method(check Remobjects.SDK.Server.Invoker.InvokeService)

set Service.RequiresSession = True ,all remote call on this Service will fail

6

Hello

Seems that was not the only issue, there are also bugs in even polling support. Seems the issues I found are fixed now. Send a mail to support@ if you need a fixed pre-Beta version.

Regards