struct ara::exec::ExecutionErrorEvent

Data structure ara::exec::ExecutionErrorEvent serves to encapsulate error events when a process terminates unexpectedly within a function group. For this purpose, it bundles the specific error code of the affected process via attribute executionError [SWS_EM_02545] with the associated functionGroup [SWS_EM_02546] in which the incident occurred. Based on this data, higher-level error handling can analyze the context and initiate appropriate restart or fallback measures for the respective function group. As a pure data structure, the type provides no methods of its own and requires external synchronization under concurrent access.

more ›

Context

Structure ara::exec::ExecutionErrorEvent is used in module exec to represent an execution error that occurred within a function group. In the AUTOSAR Adaptive Platform, processes are logically structured into function groups to control their state and lifecycle in an orderly manner. If a critical error occurs during execution of a process that leads to its unexpected termination, this state is mapped as a structured event. For this purpose, the data structure encapsulates the relevant details by linking the error code that occurred with the affected function group.

The primary interaction partners include the affected process, whose unexpected abort causes the concrete error value executionError [SWS_EM_02545], as well as the associated function group functionGroup in whose context the error occurred [SWS_EM_02546]. A higher-level entity of the overall system acts as an additional communication partner. Interpretation: This monitoring entity is likely to receive and evaluate the event to initiate coordinated responses at group level. Question (open)

Context diagram: Interaction of the participating components when an execution error occurs. Sources: [SWS_EM_02545], [SWS_EM_02546]

Lifecycle

The definition as struct ExecutionErrorEvent final designates the type as a final, non-polymorphic data structure without inheritance relationships. As a pure data and value object, the structure has no internal state machines and no independent lifecycle phases. An instance arises event-driven precisely when a process terminates unexpectedly and this incident is captured. During creation, the two public member variables are initialized: field executionError with the system-specific error value of the process [SWS_EM_02545], and field functionGroup with the instance of the affected function group [SWS_EM_02546].

With respect to ownership, the structure is usually created as a local value object and passed to processing and notification routines either directly by copy of value or via const references. Dynamic memory allocation is normally not required for the object itself. Destruction occurs deterministically upon leaving the scope of the respective handler routine. Regarding concurrency, the structure does not implement access synchronization of its own. Interpretation: If instances of ExecutionErrorEvent are passed across thread boundaries, callers must synchronize concurrent read and write access externally. Question Q-839283a2c3c3e269 (open)

Usage Path

The typical usage path comprises detection, forwarding, and evaluation of the error event:

• Event creation: A monitored process within an active function group aborts unexpectedly. The system then instantiates an object of type ExecutionErrorEvent.
• Parameter assignment: The attributes are populated with the contextual data of the incident. The specific error value is stored in field executionError [SWS_EM_02545], while functionGroup handles the association with the executing function group [SWS_EM_02546].
• Handover to handler routines: The initialized event is forwarded to the responsible error monitoring or restart management.
• Evaluation and reaction: The receiving entity analyzes functionGroup [SWS_EM_02546] to locate the subsystem and reads out executionError [SWS_EM_02545]. Interpretation: Based on this information, the monitoring entity is likely to decide on process restarts or a state change of the function group. Question (open)

Error Scenarios

Structure ExecutionErrorEvent itself defines no error codes, return values, or exceptions. It functions exclusively as an information carrier for error states that originated at process level. The primary error scenario is therefore the unexpected termination of a process whose cause is mapped in field executionError [SWS_EM_02545].

As a precondition for correct processing, both member variables must be populated consistently. An event without a valid process error [SWS_EM_02545] or without an association with an existing function group [SWS_EM_02546] prevents targeted error handling. As a postcondition of event evaluation, the affected function group [SWS_EM_02546] is to be transitioned back into a defined, safe state.