The Imapd Process Continually Reports General Error: JmqNotify JMQ Initialization Error Could Not Connect To Broker (Doc ID 1509209.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Messaging Server - Version 7.0.0 to 7.0.4 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

JMQ is being used for ISS on several backend store systems. There are separate ISS and JMQ servers.

On many, but not all the backend store systems, the following errors are being reported by each imapd process once every 30 seconds (note the different pid in each message):

# tail -f imap | grep -i error
[21/Sep/2012:20:53:25] <hostname> imapd[5003]: General Error: jmqNotify JMQ initialization error Could not connect to broker
[21/Sep/2012:20:53:26] <hostname> imapd[5035]: General Error: jmqNotify JMQ initialization error Could not connect to broker
[21/Sep/2012:20:53:26] <hostname> imapd[5015]: General Error: jmqNotify JMQ initialization error Could not connect to broker
[21/Sep/2012:20:53:26] <hostname> imapd[5032]: General Error: jmqNotify JMQ initialization error Could not connect to broker

Further examination shows the errors did not just start recently - they have been happening at this rate since these imapd processes were started.

The startup messages show a 3 minute pause between "connecting index" and "JMQ initialization error Could not connect to broker":

[11/Sep/2012:21:17:12 ... General Notice: iBiff plugin loaded: ms-internal
[11/Sep/2012:21:17:12 ... General Notice: iBiff plugin loaded: mqs
[11/Sep/2012:21:17:12 ... General Notice: jmqNotify plugin loaded: index
[11/Sep/2012:21:17:12 ... General Notice: jmqnotify: connecting index
[11/Sep/2012:21:20:12 ... General Error: jmqNotify JMQ initialization error Could not connect to broker
[11/Sep/2012:21:20:12 ... ... Messaging Server IMAP4 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012) starting up

Also, when imapd was restarted, due to that 3 minute pause, the startup sequence, which would normally look like:

Starting imap server .... 27952

Instead looked like the following:

Starting imap server ....................... failed

But the sysadmins ignored that because when they looked, they found all the imap processes had started.

Cause

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