LO82084: TELL TRAVELER BIND ENABLE IS NOT STICKY AFTER SERVER RESTART
Closed as program error.
The Notes Traveler server has a diagnostic command which can be used in a Traveler High Availability pool and which binds a user's monitor to a single server in the pool. Once bound, all of the user's sync requests should come to this server until the user is "unbound". This command is: tell traveler bind enable <userid> This binding should persist even if the user's server is shutdown and restarted and an error in the Traveler server logic for this command is preventing this from working properly. Prior to this fix, if a user was bound to a Traveler server using this command, and then this server was restarted, there was a good chance that the user would be moved to another active server. Note that this fix is very specific to this command which is not normally needed except in some extreme diagnostic situations in the first place.
Do not use the bind command or if needed, do not restart the server where the user is bound. If the server must be restarted, manually issue the bind command again.
Traveler bind command can be useful for troubleshooting purposes. It restricts the user specified to a single Traveler server in an HA pool. A bug in the processing made the command so it was not persistent if the server in question was restarted.
The Notes Traveler server was updated to make the bind command persistent across restart. To remove bind use tell traveler bind remove <username> command.
This fix is included 220.127.116.11 IF8, 9.0.1 IF7 and will be included in any future releases. For the latest available Notes Traveler maintenance releases see this article: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels