APAR status
Closed as program error.
Error description
Error Message: Thread hang in CICS when it uses the ORB to make an EJB request . Stack Trace: The hung thread will be similar to the following stack trace: semop -320479B2 CELQLIB semopWrapper+00000026 *PATHNAM j9shsem_wait+00000130 *PATHNAM Java_com_ibm_tools_attach_javaSE_IPC_waitSemaphore +00000088 *PATHNAM Keyword: Attach API kixdcfzos113
Local fix
No workaround for this issue has been reported to resolve the issue. Disabling the attach API does not take effect via the CICS Profile. Java 6.0.1 SR2 is available. Please update to a recent PTF maintenance level of Java 6.0.1 to resolve this issue.
Problem summary
Thread hang when CICS makes an EJB request using the ORB. This is due to the Connection not moving to ESTABLISHED state.An outgoing new request is waiting forever for the Connection to move to ESTABLISHED state.
Problem conclusion
This defect will be fixed in: 6.0.1 SR2 7.0.0 SR1 6.0.0 SR10 FP1 5.0.0 SR13 FP2 . The ORB has been fixed to move the Connection to ESTABLISHED state prior to the Reader Thread getting created.
Temporary fix
Comments
APAR Information
APAR number
IX90080
Reported component name
ORB
Reported component ID
620700123
Reported release
260
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-04
Closed date
2012-03-12
Last modified date
2012-06-20
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
ORB
Fixed component ID
620700123
Applicable component levels
R260 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"260","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
06 January 2022