Last updated on JULY 30, 2012
Applies to:Oracle Directory Server Enterprise Edition - Version 6.3 and later
Information in this document applies to any platform.
On : ISW 6.0 version, Administration
ISW / MQ keep degrading to a state where the MQ begins to fail handling message transactions between ISW components (core, connector, etc) and the DS. This ultimately results in the message queue becoming unresponsive to requests.
the following errors are seen
from /var/adm/messages the following exception is announced we see both ISW and the MQ announcing exceptions, with MQ aborting the ISW connection
Jun 8 14:54:57 frutti ns-slapd: [ID 446431 user.error] Failed to write log, error -5993 (Operation interrupted by anot
her thread.): - WARNING - isw - conn=-1 op=-1 msgId=-1 - Plugins BasicSaintRPC.cpp:341(logCode=0, connectionID=0) BasicSaintRPC::run() exiting because 'The TCP connection was forceably aborted.' (1603)
Jun 8 14:58:18 frutti imqbrokerd_isw-broker: [ID 457532 daemon.error] ERROR javax.naming.CommunicationException:test-ldap1.example.com:389:
Jun 8 14:58:18 frutti com.sun.messaging.jmq.auth.LoginException: javax.naming.CommunicationException:test-ldap1.example.com:389
The connector also announces within the ISW logging loss of connectivity to MQ (different time, not same event)
[08/Jun/2012:00:00:21.681 +0200] SEVERE 10 CNN101 frutti "Failed to establish a connection to the Sun Java(TM) System Message Queue Broker because of a JMSException: javax.jms.JMSException: [C4090]: Invalid port number. Broker is not available or may be paused: [test-ldap1.example.com,-1]"
[08/Jun/2012:00:00:21.778 +0200] WARNING 10 CNN101 frutti "Could not establish a connection to the message queue because '[C4090]: Invalid port number. Broker is not available or may be paused: [test-ldap1.example.com,-1]'. Will continue to retry."
The issue can be reproduced at will with the following steps:
1. Start IMQ and ISW and the DS, allow to run under production workload for a period
2. Eventually services will fail and connectors will go from syncing to ready
3. restart of services is required to restore functionality, at this time the environment is scheduled for proactive restarts on a periodic basis.
The issue can be mitigated hrough a restart of services; it is however masking underlying issues with the ISW/MQ components. MQ could be overloaded by error conditions being hit within ISW, or there could be a problem within MQ, triggering a flood of error messages from ISW (they inter-operate so closely the one can trigger impact in the other very quickly if it becomes responsive for an extended period of time). Due to this issue, the threat of an un-controlled outage is possible. As it is visible now, the problem should be addressed before this happens.
No changes have taken place, but ISW will degrade to a non working state over time, forcing a restart of all components to avoid the issue.
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