Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImplRepo race condition at server shutdown/start #889

Closed
jwillemsen opened this issue Apr 12, 2019 · 0 comments

Comments

@jwillemsen
Copy link
Member

commented Apr 12, 2019

Assume that the locator has requested the activator to start taotester and it starts with process 61216, after that the following happens:

  • taotester is doing a controlled shutdown and informs the locator that it is shutting down but the process 61216 hasn’t finished yet
  • the locator marks taotester with pid 61216 as dead
  • there is a new client request for taotester and the locator asks the activator to start taotester through a CORBA call
  • there is a OS signal that the process 61216 for taotester has gone so the locator cleans more internal administration
  • we think that the activator now doesn’t start taotester because the process 61216 is still running (there is a very very small time between shutdown of the POA and the exit of the process), the request to start taoserver happens before the activator gets the signal that the process 61216 is gone. The activator reports this back to the locator through an exception, the log just lacks some important information which we need to add to the code for future logging.
  • the locator now has an incorrect internal state, it thinks taotester is started with pid 61216 but it is dead and the process exited.
  • some code is now trying to use the old object reference for taotester with 61216 which results in an exception

@jwillemsen jwillemsen changed the title ImpleRepo race condition at server shutdown/start ImplRepo race condition at server shutdown/start Apr 12, 2019

@jwillemsen jwillemsen closed this Apr 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.