Three possible scenarios for SAP Spartacus server-side rendering

Execute to code 166 That's ok , Give the control logic to expressEngine after , spot F8 after , The following three different colored code blocks may be called to ：

1. Green code block

explain timeout The specified time interval has expired .timeout：Time in milliseconds to wait for SSR rendering to happen, wait for SSR Timeout for rendering start , instead of SSR Rendered duration.

2. Yellow code block

SSR The execution time is too long , Not finished yet . If exceeded maxRenderTime, Will forcibly release concurrency slot, Allow new requests to be SSR Respond to . however , For timeout SSR The service request , The resources requested have not been released , May cause memory leak . The default time is 5 minute .

3. Red code block

So if I go here , also maxRenderTimeout Not for undefined, The explanation is normal SSR Render the successful execution of the request .

timeout

Time in milliseconds to wait for SSR rendering to happen.

It does not mean the actual duration spent by a SSR rendering request, but the range between the timestamp when SSR receives a render request and that request actually gets processed by SSR server.

wait for SSR When rendering occurs （ In Milliseconds ）.

It doesn't mean SSR The actual duration of the rendering request , It is SSR The timestamp when the rendering request is received is the same as the time when the request was actually received SSR The range between server processing .

forcedSsrTimeout

Time in milliseconds to wait for rendering when SSR_ALWAYS render strategy is set for the request.

Default value is 60 seconds.

in file optimized-ssr-engine.ts, we set a timer with timeout value specified by line 130, this.getTimeout function call:

Set for request SSR_ALWAYS Time to wait for rendering while rendering policy （ In Milliseconds ）.

The default value is 60 second .

In file optimization ssr-engine.ts in , We set a timer , The timeout value is determined by 130 Please specify ,this.getTimeout Function call ：

The logic of final timeout value is determined as below:

1. if request rendering strategy is specifed explicitly by customers to ALWAYS_SSR, then the timeout is coming from forcedSsrTimeout option. If customers specify ALWAYS_SSR but forget to fill forcedSsrTimeout, then 60 seconds is used as default value.

2. In most cases customers will use RenderingStrategy.DEFAULT as default strategy. In this case, timeout value comes from option timeout.

In other words, forcedSsrTimeout only takes effect, if customer uses RenderingStrategy.ALWAYS_SSR.

1. If the customer explicitly specifies the request rendering strategy to ALWAYS_SSR, So the timeout comes from forcedSsrTimeout Options . If the customer specifies ALWAYS_SSR But forget to fill in forcedSsrTimeout, Then use 60 Seconds as the default .

2. in the majority of cases , Customers will use RenderingStrategy.DEFAULT As the default policy . under these circumstances , The timeout value comes from the option timeout .

let me put it another way , Only when used by customers RenderingStrategy.ALWAYS_SSR when ,forcedSsrTimeout Will take effect .