Ticket #190 (new enhancement)

Opened 10 months ago

Last modified 4 weeks ago

PMC connect time out is 60 s. Configurable?

Reported by: jasper Owned by: jasper
Priority: major Milestone: Backlog
Component: COBIA Marshalling Version:
Keywords: Cc:

Description

Currently the PMC connection time out is 60 seconds. This may be insufficient, or disturbingly large.

Should this be configurable? If so,

  • one override for the local host?
  • one override per registered PMC (in the PMC registry)?

Change History

comment:1 Changed 10 months ago by kyle

  • Component changed from COBIA core to COBIA Marshalling

comment:2 Changed 10 months ago by jasper

For TCP/IP transport, this time-out is implemented in TCPIP_PME_Transport::PMCConnect. For memory based transport, this time-out is implemented in WaitConnect?()

comment:3 Changed 7 months ago by jasper

In COM there is a machine registry setting that applies to all types.

In COBIA I suppose we are better off being able to configure this per primary PMC registration: remote PMCs may need a larger time out.

comment:4 follow-up: ↓ 5 Changed 6 months ago by kyle

  • Milestone changed from Phase III WP1 to Backlog

comment:5 in reply to: ↑ 4 Changed 4 weeks ago by kyle

Replying to kyle:

M&T SIG favours:

  • Default timeout of 60 sec
  • "one override per registered PMC (in the PMC registry)"
  • Adapt the registrar to allow specifying the timeout at installation time
Note: See TracTickets for help on using tickets.