360eyes - Critical Error during query on the infostore, Job aborted

360eyes - Critical Error during query on the infostore, Job aborted

Symptoms

  • A 360eyes job fails before it finishes.
  • The issue mostly happens on 360eyes Webi or CMS jobs.

Error Message

Message:

com.wiiisdom.common.JobException: Critical Error during query on the infostore, Job aborted
Caused by: com.crystaldecisions.sdk.exception.SDKServerException: CMS operation timed out after 9 minutes.

Steps to Reproduce

  1. In 360Suite, run a 360eyes job (Webi or CMS) on the SAP BusinessObjects environment.
  2. The job sends a series of queries to the infostore.
  3. One query exceeds the CMS timeout. The job is aborted and the error above appears in the job logs.

Cause

  • Context: the error happens when one of the queries 360eyes sends to the BusinessObjects infostore takes longer than the default CMS timeout of 9 minutes.
  • Technical explanation: several causes are possible:
    • Infostore instability over time (most common): the infostore slows down as the job runs, so each query takes longer until one reaches the 9-minute timeout. SAP does not recommend raising this timeout, although it is possible (see SAP Note 1273102).
    • Overall CMS slowness: if the very first query sent by 360eyes times out, stability over time is not the cause. The CMS is most likely responding slowly in general.
    • Problem objects: one or more specific objects can prevent the infostore from responding in time, for example because of document size, or slow access to the data source caused by complexity or security settings.

We recommend applying the resolution below first, to rule out infostore instability or slowness. If the problem continues, the next step is to look for problem objects.

Resolution

360eyes uses the blocksize parameter to set how many objects are processed in a single query (batch). The default value is 1000.

Option 1: The timeout happens during the job (infostore instability over time)

Increase the blocksize value. 360eyes then sends fewer queries, each containing more objects, which gives the infostore time to recover between queries. Keep in mind that larger queries can also affect infostore responsiveness. You need to find the right balance between query size and number of queries, which often takes a few adjustments of the blocksize parameter.

  1. In 360Suite, open the configuration of the 360eyes job.
  2. In the Overridden parameters section, add (for example):
    -blocksize=10000
  3. Save, then run the job again.

Option 2: The timeout happens on the first query (overall CMS slowness)

  1. Check the overall CMS response performance with SAP Support first.
  2. As a workaround, you can decrease the blocksize value so that 360eyes sends lighter queries from the very start. In the Overridden parameters section of the job, add for example:
    -blocksize=100
  3. Save, then run the job again.

Additional Information

  • SAP Note 1273102 – CMS timeout
  • If the issue persists, please contact Wiiisdom Support with the 360eyes job logs, the blocksize value you tested, and the steps you followed in this article.

Keywords: 360eyes, infostore, blocksize, timeout, CMS, Job aborted