APAR status
Closed as program error.
Error description
There is a limitation with the size of kafka cluster name. If a user names multiple kafka clusters the same name across different domains and the name is too long there might be a conflict and users might see errors like: kafka-cluster (CUSTOMER_KAFKA_MPG_Handler_Cluster_customer-service): Failed to bind socket. Error 98 - Address already in use
Local fix
Users should choose a kafka cluster name that is shorter than 60 bytes
Problem summary
Kafka cluster names can not exceed 60 bytes.
Problem conclusion
Fix is available in 10.0.1.17, 10.5.0.9, and 10.5.3.0. For a list of the latest fix packs available, please see: https://www.ibm.com/support/pages/node/83105
Temporary fix
Comments
APAR Information
APAR number
IT43425
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-03-24
Closed date
2023-12-01
Last modified date
2023-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 December 2023