Since the last upgrade our client application can no longer receive any events from the server, this issue does not affect .net clients. An old version of our client (which was built with 6.0.45.821) will connect to the server fine and receive events.
We are using the SuperTCPChannel
The code has not changed on the client, any ideas?
Registers the client to receive server callback events of the specified type. Must be called for every client that needs to receive events in LegacyEvents = false mode.
this sort of implies that you dont have to if LegacyEvents = true
Exactly. We did so to make the transition smooth for existing applications. I'm surprised because of your broken one. Moreover, superchannels work differently compared to simple channels and they were not affected by the LegacyEvents stuff.
Which platform is your server on, .NET or Delphi? Could you write a simple client-server app with events to test if it works? If it doesn't we'd like to see it, including compiled binaries for investigation.
We have managed to fix the issue, not really sure whats causing it, its a really strange one. Its only started happening with the latest version of RO. Also if we downgrade RO the issue goes away!
To explain :
Both server and client are Delphi (we also have .net clients but they are working fine)
If we call a method on the server straight after connecting we can get events through,
If we do not make any method calls to the server straight away we will not get any events…
I will create a simplified test client and server and submit them when I have a bit of free time…
ianrobinsonoakcouk said: If we call a method on the server straight after connecting we can get events through,
If we do not make any method calls to the server straight away we will not get any events..
Thanks, that's valuable information bringing some light to this case. Events need session to work because events are per session, not per connection. But the session is normally created when the first remote method is called. Superchannel servers have AutoRegisterSession property to work this around, perhaps something has got broken there. We'll investigate.