PAMS-E-BADPARAM error on a PAMS_ATTACH_Q (Doc ID 841874.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle MessageQ - Version 5.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
5.0

Goal

Concurrent client access throws PAMS-E-BADPARAM error on a PAMS_ATTACH_Q. Below are the two traces from EVL logs,

 

Notice that the owner_pid is different than this_process_pid, which causes the PAMS-E-BADPARAM error. The client program that produces this error is running pams_attach_q(), pams_get_msgw(), and pams_exit() in an infinite loop, without a sleep in between pams_exit and pams_attach_q. The problem happens when six of these clients run concurrently.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms