TCP.onread error when sending message to channel

[batjko]

Hi there,

Just tried this out and couldn't get it to send a message using your example file:

This is my spread config of the service, which is running fine:

Spread_Segment  127.0.0.255:14803 {
    localhost   127.0.0.1
}

This Spread service is used without a problem by a major application which I am trying to hook into.
But alas, getting the error above.

Any ideas?

Cheers

[batjko]

Interestingly, in the first attempt you can see in the screenshot, it didn't do anything (and I know it didn't work as I think the channel didn't exist).

My guess is that I am getting the error with the second channel (_LOCAL) because it does exist but sending a message to it failed for some reason.

[Joe-Jones]

Hi,

I can reproduce this. The server appears to close the socket as soon as a message is sent. I'll see if I can work out what the problem is.

Regards

Joe

[batjko]

cool, thanks 👍

[Joe-Jones]

Hi Patrick,

are you using a spread packaged by your operating system distribution (Ubuntu?), or have you compiled from the source tar ball. I think compiling the latest spread spread (4.4.0) from source may fix your problem, are you able to do this.

I'll need to investigate this further but I think this is an endian issue. The spread protocol allows client to speak big or little endian as they choose. And the server to be big or little endian. Little endian is indicated by the bit mask 0x80000080 added to certain fields. I chose big endian when developing the library, no particular reason, perhaps it was the easer choice. Although I haven't looked into this I suspect the servers ability to handle non native endian is a compile time option that has somehow been missed in the Ubuntu package that I assume I was using. Compiling from source has resolved the problem for me.

It looks like the library needs to support little endian in order to talk to all possible servers.

Regards
Joe

[batjko]

Hi Joe,

Thanks for the explanation.
I'm afraid I have little influence on the spread version in use. In fact I am trying to connect to an existing Spread service that is part of a distributed enterprise application.
The entire thing, including the Spread services, is running on Windows machines.

But it is quite possible that the version they use is very old, since I don't think it has been updated in over 6 or 7 years.

Not sure what else to try except to attempt to make a newer version of Spread work with the main application I suppose.