Troubleshooting 'RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed'

Problem(Abstract)

User launches Controller. User runs a standard report (also known as a "system report"). User receives error message. Typically the problem is intermittent - if the user runs the report later in the day (or the next morning) then the report works OK.

Symptom

RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed

Cause

There are many different potential causes for this error message. For example:

• Scenario #1 - (most likely) Underpowered / virtual (VMWare/ESX) hardware being used, causing timeout issues
  • See separate IBM Technote #1470677 for more details
• Scenario #2 - (very rare) Old/incompatible version of Adobe Acrobat Reader installed on client device
  • See separate IBM Technote #1340663 for more details
• Scenario #3 - (fairly likely) Networking problems/issues
  • See separate IBM Technote #1385378for more details

However, this IBM Technote shall specifically look at the following scenario from now on:

• Scenario #4 - Customer using an external 'load-balancing' network device to distribute requests to multiple gateway servers.
  • In this scenario, the Cognos BI Report Server is incorrectly configured to use "Weighted Round Robin" (instead of the correct "Cluster Compatible").

More Information on Scenario#4
The setting "Weighted Round Robin" causes the Cognos Reporting Engine to handle multiple gateways/dispatchers itself. In other words, it will distribute requests to different gateways/dispatchers according to the Cognos BI logic.

The setting "Cluster Compatible" causes the Cognos Reporting Engine to allow an external load balancing device (a network router designed to help with failover/fault-tolerance/redundancy etc.) to take over the job of distributing the requests to multiple gateways.

Environment

Scenario #4

Customer has:

• Multiple (2 or more) separate 'gateway' servers
• Configured Controller to use a virtual DNS entry (for example .) for its report server
• . resolves to a network load balancer device (for example a Cisco load balancing router "CSS") which provides DNS Round Robin routing to the multiple gateway servers.

Resolving the problem

Scenario #4

Launch Cognos Connection, and reconfigure the Cognos reporting engine to use the setting "Cluster Compatible".

Steps:

1. Obtain a short period of downtime (no users on the system)
2. Launch Cognos Connection ()
3. If prompted, log into IBM Cognos Connection as an Administrator
4. Depending on what screen you see, either (a) click "Administer IBM Cognos content" or (b) in the upper-right corner, click Launch, IBM Cognos Administration.
5. On the Status tab, click System.
6. Click the arrow for the Actions menu next to System and click Set properties
7. Click the Settings tab.
8. Select Tuning from the Category list.
9. In the Value column, select the value for the Load Balancing Mode.
10. Modify the setting to "Cluster Compatible"
11. Click OK

原文地址：