Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Apache Flink will be delivered by IBM Confluent.

For more information, see the support lifecycle transition and software ordering completion announcement.

Flink instances cannot access SQL Runner JAR file

Symptoms

When creating an instance of a FlinkDeployment to deploy jobs in production environments by using the Apache SQL Runner sample environment, the Flink Job Manager pods go into CrashLoopBackOff state and an error similar to the following is displayed in the logs:

Caused by: java.io.IOException: JAR file can't be read '/opt/flink/usrlib/sql-runner.jar'

Causes

The non-root user running the Flink instance is unable to read the SQL runner JAR file as the non-root user does not have the required permissions.

Resolving the problem

To resolve the problem, complete the following steps:

  1. Modify the file system or the Dockerfile to have the read permissions (644) for your JAR file.
  2. Build a new docker image.
  3. After the new image is pushed to your registry, update your FlinkDeployment custom resource to use the new image.