SYSVIEW 17.0 - TASK ZABPROC is crashing after 1 hour of start.

Products

• SYSVIEW Performance Management

Issue/Introduction

Task ZABPROC is initialized, but the connection is dropped after an hour of waiting with APM Kafka.

The following messages appear in the Log.

BPXM023I (ZABUSER) ZABM001I z/OS APM Bridge 1.1.2 is starting                                    
BPXM023I (ZABUSER) ZABM005E z/OS APM Bridge is stopping due to connection issues with APM Kafka  
BPXM023I (ZABUSER) ZABM006I z/OS APM Bridge has stopped                                          

 

Environment

SYSVIEW 17.0

Cause

The ZABPROC task, responsible for the integration between SYSVIEW and the DXOP04 server, was running several connection tests with Kafka Broker. However, after approximately an hour of consecutive attempts, the task automatically terminated. 
 
1.Felix reported the error below when starting the ZABPROC task in SYSVIEW
 
08.23.03 STC10043  IEF403I ZABPROC - STARTED - TIME=08.23.03                                                       
08.23.06 STC10043  BPXM023I (ZABUSER) ZABM001I z/OS APM Bridge 1.1.2 is starting                                   
09.23.17 STC10043  BPXM023I (ZABUSER) ZABM005E z/OS APM Bridge is stopping due to connection issues with APM Kafka 
09.23.17 STC10043  BPXM023I (ZABUSER) ZABM006I z/OS APM Bridge has stopped                       
 
2. In DXOP04, it was identified that the infrastructure agent repeatedly logged the following alert in the Introscope log:
 
[WARN] [FileTransferEngine.FileTransferProcessor] - FileTransferProcessor error: Failed to process entry: file.txt. Retrying entry: file.txt one more time.
 
3. In the Kafka server log, a fatal error was found that caused the service to be unavailable:
 
ERROR Encountered fatal fault: caught exception (org.apache.kafka.server.fault.ProcessTerminatingFatalException)
java.nio.file.AccessDeniedException: E:\tmp\trait-combined-logs\__cluster_metadata-0-0000000000000000.checkpoint.deleted
 

Resolution

Full permissions were granted to the E:\tmp folder and its subfolders for the local dxop04 user responsible for running Kafka. The "Read-only" flag in the folder properties was also removed.
 
After the permission adjustments, the ZABPROC task was restarted, reestablishing communication between SYSVIEW and Kafka Broker. So far, there are no errors in the logs and the task remains active.