Root Causes#
Coverage: 0.0% (0 of 27 items OK)
[PARTIAL] TRLC Rootcause message_passing_fta.BE_HandlerErrorUnpropagated
Message handler returns an error that is not propagated to the client
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_HandlerNoReply
Message handler does not call Reply within OnMessageSentWithReply
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_HandlerNotRegistered
Message callback or connection handler not registered at StartListening
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_MessageTooBig
Message exceeds configured max_send_size or max_reply_size
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_NotifyCallbackMissing
Client notification callback not registered via Start
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_NotifyQueueExhausted
Notification dropped because max_queued_notifies is zero or exhausted
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_NotifyTooBig
Notification exceeds configured max_notify_size and is rejected
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_NotifyTransportFault
OS IPC transport failure on the notification path
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_RequestDisconnectMisuse
RequestDisconnect invoked outside a valid call context
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_SendQueueExhausted
Send queue capacity exhausted or configured as zero
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_ServerQueueConfig
Server factory queue size configured below the required minimum
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_SyncConnectDeadlock
sync_first_connect connection established from within a callback causes deadlock
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.BE_UnintendedDisconnect
Unintended RequestDisconnect drops a live channel
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.CallFlowConformance
Send or reply triggered outside intended call flow
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ClientIdentityIntegrityCheck
Client Identity wrong or swapped
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ClientIdentityValidation
Client Identitiy incomplete or empty
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ClientRetryPolicy
Client cannot connect to server at runtime
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ConnectCallbackReturnValueValidation
Connect callback returns wrong data
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ConnectCallbackValidation
Connect callback returns null or incomplete data
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.LifecycleOrderEnforcement
API invoked before lifecycle initialization completes
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.OsIpcFaultHandling
OS IPC transport failure not detected or handled
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.SendBufferArgumentValidation
Invalid buffer or size argument passed to SendWaitReply
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.ServerHealthCheck
Server not accepting connections at runtime
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.StartupArgumentValidation
Startup arguments missing or incorrect
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.StateMachineVerification
State machine transitions not covered by verification
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.TimingSupervision
OS scheduling or IPC queue delay not bounded by timing supervision
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from:
[PARTIAL] TRLC Rootcause message_passing_fta.UniqueServerNamePolicy
Duplicate Server Name
Traces to:
missing reference to Component Requirements or Safety Measures
Derived from: