Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The IBM HTTP Server on z/OS uses msgctl (BPX1QCT) passing in IPC_RMID to delete the IPC message queue has part of cleanup. There are times, the the wrong IPC message queue id is used. If the userid the server runs with has UID 0, has read access to BPX.DAEMON, or shares the same userid as some other application, that application's message queue is deleted. If this isn't the case, then the system log will contain this ICH408I message: ICH408I USER(webid ) GROUP(webgroup ) NAME(user)) CL(IPCOBJ ) ID(0000000026) INSUFFICIENT AUTHORITY TO MSGCTL CMD(IPC_RMID) EFFECTIVE UID(uuuuuuuu) EFFECTIVE GID(gggggggg) . ADDITIONAL SYMPTOMS: We have seen this issue affect TCPIP applications PAGENT and IKED if the IPC message queues they use are deleted. Their logs will contain messages with these errors: errno 121 (EINVAL - EDC5121I INVALID ARGUMENT) errno2 11800302, 070B0302, 07500302 (JRIPCBADID)
Local fix
To stop the IHS server from deleting some other application's IPC message queue, do not have the IHS server run with UID 0, have read access to BPX.DAEMON, or share the same userid as some other application. This will stop the actual delete of the IPC message queue from being done. But, will cause an ICH408I message for INSUFFICIENT AUTHORITY TO MSGCTL CMD(IPC_RMID) to be written to the system log since the server no longer has the authority to delete another application's IPC message queue.
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM HTTP Server (powered by * * Apache) on * * z/OS. * **************************************************************** * PROBLEM DESCRIPTION: IBM HTTP Server may generate "ICH408I" * * messages in the system log or interfere * * with other applications message * * queues. * **************************************************************** * RECOMMENDATION: * **************************************************************** IBM HTTP Server was removing message queues in a cleanup function but sometimes passing uninitialized memory for the message queue ID field.
Problem conclusion
IBM HTTP Server was updated to only remove our own message queue ID. This fix is targeted for IHS fixpacks: - 8.5.5.10 - 9.0.0.1 (Does not apply to older releases)
Temporary fix
Comments
APAR Information
APAR number
PI64628
Reported component name
WAS IHS ZOS
Reported component ID
5655I3510
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-21
Closed date
2016-06-23
Last modified date
2016-06-24
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
WAS IHS ZOS
Fixed component ID
5655I3510
Applicable component levels
R850 PSY
UP
R90P PSY
UP
Document Information
Modified date:
04 May 2022