Projects
Wiki     Timeline     Roadmap     Browse Source     View Tickets     New Ticket     Search

Ticket #162 (closed Defect: Software changed)

Opened 3 years ago

Last modified 3 years ago

MultiProcess mode with a single process tries to connect to pydirector but pydirector isn't running.

Reported by: wsanchez@… Owned by: dreid@…
Priority: 1: Blocker Milestone: CalendarServer-1.0
Component: Calendar Server Severity: Crash/data loss
Keywords: Cc:

Description

4/18/07 3:05 PM David Reid:

MultiProcess mode with a single process tries to connect to pydirector but pydirector isn't running.

This is a result of the child process not being aware that it is the only slave process. And is listening directly on the TCP ports.

Change History

Changed 3 years ago by dreid@…

  • status changed from new to closed
  • resolution set to fixed

Ok, This should be fixed in r1496. I pass the real ProcessCount to all the child processes and they can use that to handle the ProcessCount=1 case where we don't want a PDClientAddressWrapper.

Note: See TracTickets for help on using tickets.