|
Problem IT17796
|
Status: Geschlossen |
RSS SERVER MAY NOT RECONNECT FOLLOWING A RESTART OF THE PRIMARY SERVER |
| Produkt: |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 |
| Problembeschreibung: |
When an RSS server is successfully connected to its primary and
the primary is then restarted it is possible that the RSS server
may not fully reconnect. This problem may only occur when the
SMX_NUMPIPES onconfig parameter is set to a value greater than
1. The probability of the failure to reconnect increases with
higher values of SMX_NUMPIPES and a shorter period of primary
downtime.
In the primary server's online log following the server restart
there will be no message of the form "RSS Server <server name> -
state is now connected." For the RSS server messages of the
following form appear when the primary is shut down:
17:12:55 SMX thread is exiting
17:12:57 RSS: Lost connection to primary_svr
On restart of the primary no additional messages appear in the
RSS server log.
Use of the command "onstat -g ath" on both primary and RSS
servers show a number of smxrcv and smxsnd threads to show that
network connections are established but the primary will not
show the correct number of threads associated with RSS
processing.
Note that this problem only occurs when NUM_SMXPIPES is greater
than 1. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 12.10xC7W1 or latest 11.70.xC9 release *
**************************************************************** |
| Local-Fix: |
A restart of the RSS server should resolve the issue. |
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 03.11.2016
09.06.2017
09.06.2017 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
11.70.xC9,
12.10.xC7
|
| Problem behoben lt. FixList in der Version |
