Failure Modes

Coverage: 0.0% (0 of 8 items OK)

[PARTIAL] TRLC Failuremode MessagePassing.IpcChannelUnavailable

The IPC channel between client and server cannot be established or maintained

---

Traces to:

• message_passing_fta.BE_ServerQueueConfig

• message_passing_fta.BE_UnintendedDisconnect

• message_passing_fta.ClientRetryPolicy

• message_passing_fta.ServerHealthCheck

• message_passing_fta.StartupArgumentValidation

• message_passing_fta.UniqueServerNamePolicy

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:21:22

[PARTIAL] TRLC Failuremode MessagePassing.MessageNotDeliveredCorrectly

A message sent via the IPC channel is not, only partially with corrupted content delivered.

---

Traces to:

• message_passing_fta.BE_MessageTooBig

• message_passing_fta.BE_SendQueueExhausted

• message_passing_fta.OsIpcFaultHandling

• message_passing_fta.SendBufferArgumentValidation

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:33:22

[PARTIAL] TRLC Failuremode MessagePassing.NotificationNotDelivered

A server-initiated notification is not, only partially, delayed, with corrupted content or when not intended delivered.

---

Traces to:

• message_passing_fta.BE_NotifyCallbackMissing

• message_passing_fta.BE_NotifyQueueExhausted

• message_passing_fta.BE_NotifyTooBig

• message_passing_fta.BE_NotifyTransportFault

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:45:22

[PARTIAL] TRLC Failuremode MessagePassing.ServerMessageHandlingFailure

Server-side message or connection handler fails to process a received message or to produce a required reply.

---

Traces to:

• message_passing_fta.BE_HandlerErrorUnpropagated

• message_passing_fta.BE_HandlerNoReply

• message_passing_fta.BE_HandlerNotRegistered

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:57:22

[PARTIAL] TRLC Failuremode MessagePassing.MessageTimingViolated

A message or reply is delivered outside of the specified timing bounds required by the application.

---

Traces to:

• message_passing_fta.BE_SyncConnectDeadlock

• message_passing_fta.TimingSupervision

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:65:22

[PARTIAL] TRLC Failuremode MessagePassing.IpcApiMisuseOrLifecycleViolation

An IPC operation is invoked at the wrong lifecycle stage or outside its valid call context.

---

Traces to:

• message_passing_fta.BE_RequestDisconnectMisuse

• message_passing_fta.CallFlowConformance

• message_passing_fta.LifecycleOrderEnforcement

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:77:22

[PARTIAL] TRLC Failuremode MessagePassing.ConnectionContextDataWrong

Identity or cached context data associated with a server connection is absent, incomplete, or incorrect.

---

Traces to:

• message_passing_fta.ClientIdentityIntegrityCheck

• message_passing_fta.ClientIdentityValidation

• message_passing_fta.ConnectCallbackReturnValueValidation

• message_passing_fta.ConnectCallbackValidation

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:89:22

[PARTIAL] TRLC Failuremode MessagePassing.StateMachineError

GetState or GetStopReason returns an incorrect lifecycle state that does not match the actual connection state.

---

Traces to:

• message_passing_fta.StateMachineVerification

---

Derived from:

• missing up reference

---

Source: score/message_passing/dependability/safety_analysis/failure_modes.trlc:101:22