My Oracle Support Banner

MSQ 4.0A - Link listener does not log problem when port already in use (Doc ID 765717.1)

Last updated on JANUARY 29, 2025

Applies to:

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

Goal

PRODUCT: BEA MessageQ
VERSION: 4.0A
PLATFORM: UNIX/NT

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

To view full details, sign in with your My Oracle Support account.

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

In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.