Redis causes a wrong behavior for Block Semaphore and Block Resource commands
About this task
For IBM RPA on premises only: Redis version 3.0.504 causes a wrong behavior for Block Semaphore and Block Resource commands.
The wrong behavior occurs when a script Y doesn't get the lock after script X releases it, even if it's within the timeout span. It only gets the lock if it identifies that it was released before the command ran.
Before you begin
- This procedure is available for Redis instance on Docker™ instances and Linux™ machine only.
- The latest stable version of Redis on Windows™ doesn't support this fix.
- Download and install the latest stable version of Redis. It works on Redis 4.0.8 version or later.
- Set the value
KEAto the property
notify-keyspace-eventson Redis config file. For more information about changing Redis configuration file, see Redis configuration .
What to do next
For on-premises environments on Windows™, you might use a Redis instance separately in a Docker™ instance or a Linux™ machine. In this case, you need to enter the Redis instance location in the connection string while you install IBM RPA or enable it on IBM RPA Control Center. For more information, see Redis.