RP/MSQ 5.0 (VMS) - Timeouts received after large number of transactions (Doc ID 769426.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle MessageQ / MessageQ / 5.0 (VMS)
Information in this document applies to any platform

Goal

While upgrading from V4.0A to V5.0 on OpenVMS and UNIX systems, the following problem is found:

VMS to VMS on different machines using either TCPIP or DECNET, the sending and receiving processes timeout after a
large number of correct transactions.

VMS to VMS on same machine - no problems.

UNIX to VMS using TCPIP, a timeout is received after a large number of messages are processed.

No errors appear in either the EVL or group log file.

This is NOT a problem with MessageQ for UNIX, V4.0A or MessageQ for OpenVMS, V4.0A.
With V4.0A, the processes continue on with no timeouts received

Test cases can be found on pecan:

              $1$DIA4:[WONGM.kadaster]                                      (for V4.0A)
              $1$DIA4:[WONGMkadasterv50]                                 (for V5.0)

On lcdux2:

             /nfs/home4/wongm/lcdux2/cases/mq/kadasterv40a    (for V4.0A)
             /nfs/home4/wongm/lcdux2/cases/mq/kadaster             (for V5.0)

On VMS, I turned on DMQ$DEBUG tracing, output is in the EVL log file
On UNIX, I turned on PAMS_TRACE, output is in the trace.* file.

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