Bug #1461

RSB does not create server socket immediatly at startup when using transport.socket

Added by H. Riechmann almost 11 years ago. Updated almost 11 years ago.

Status:RejectedStart date:04/12/2013
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Socket Transport
Target version:rsb-0.9

Description

I would exspect the RSB server prozess to listen to the server port on startup. Currently, it seems to listen only after an Informer was created?
I would like to start all my prozesses and have them connected before doing anything else. Especially, because some of my prozesses create informer on the fly based on the data types they have to send. Which means my server prozess might not create informers before the clients want to connect.
As this setting worked before I think somethin changed between 07/0.8 and current trunk

History

#1 Updated by J. Moringen almost 11 years ago

Currently, it seems to listen only after an Informer was created?

Correct. The socket transport opens the server socket when the first participant (listener, informer, RPC etc.) is created.

I would like to start all my prozesses and have them connected before doing anything else.

Does a specific process have to be the server? From your description I would assume that you want one process to be the server and then start all processes in a particular order to ensure the server process is started first.

If you want to follow that approach, I would recommend creating a "dummy" informer in the server process and maybe also in the client processes, depending on whether you want everything "connected" or just the server started.

Another solution would be running a server in a different process such the RSB logger (http://docs.cor-lab.de//rsb-manual/trunk/html/logger.html): the logger process could act as server and run all the time. Your processes could be started, stopped and restarted arbitrarily.

Finally, you could use the automatic server selection of the socket transport (http://docs.cor-lab.de//rsb-manual/trunk/html/specification-socket.html#options).

#2 Updated by J. Moringen almost 11 years ago

As this setting worked before I think somethin changed between 07/0.8 and current trunk

Could you provide more information regarding this? Which version of RSB did you previously use? Which configuration did your processes use? Do you have a test case?

#3 Updated by J. Moringen almost 11 years ago

  • Status changed from New to Feedback

#4 Updated by H. Riechmann almost 11 years ago

Thanks for the quick reply.

I implemented the "dummy" informer, which works fine. Maybe I should switch to the RSB log solution, because I would like to be able to restart processes.

I am quite sure that, in the techfak lucid system, I was able to start my clients before starting the server. I cannot provide my old tests, though, as the lucid system is down.
I would, therefore, consider this bug closed and work with a server process running all the time.

#5 Updated by J. Wienke almost 11 years ago

  • Status changed from Feedback to Rejected

Also available in: Atom PDF