RP/MSQ 4.0A (UNIX,NT) / MSQ 5.0 (UNIX, NT) - Link listener does not log problem when port already in use (Doc ID 772363.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle MessageQ / MessageQ / 4.0,5.0
Information in this document applies to any platform

Goal

No error message is written to the log if the link driver cannot get the port. 
The group init file declares the TCP/IP port numbers to use for the connection with other nodes.  When the Message
Queue group is started, the dmld process tries to bind this TCP port and wait for incoming connections. The command
"netstat -a" shows this port as being in the listen state.

However, if another process happens to be using this port when MessageQ is started, dmld fails to bind this port, and
does not wait for incoming connections. As a result, no other nodes are connected. No errors are reported in the
dmqlog.log 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