Lotus Domino 6.5.5 FP2: Download disponibile

NEWS nuova release lotus 6.5.5 fix pack 2

  • 0 commenti
Da poco dispobibile il download del Fix pack 2 della R 6.5.5. Come potete leggere dall'estratto di Lotus/IBM ecco l'elenco delle FIX apportate da questa patch:

Link al Database Fix List:
6.5.5 FP2

Image:Lotus Domino 6.5.5 FP2: Download disponibile
Notes/Domino Fix List

Notes/Domino 6.5.5 FP2 Maintenance Release
November 7, 2006

IBM Lotus announces Domino 6.5.5 Fix Pack 2.  IBM strongly recommends upgrading to the latest Fix Pack, since Fix Packs address a small percentage of defects that impact the broadest set of customers.  This is a scheduled Fix Pack of a limited number of low-risk/high-impact fixes to help customers safely avoid known problems.  Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments.  Fix Packs go through the same level of fix, regression and interoperability testing that occurs with our Maintenance Releases.  Domino 6.5.5 Fix Pack 2 may be applied on any language version of Domino 6.5.5.

All fixes in this Fix Pack have already been successfully deployed at customer sites.  Fix Pack fixes are included in the next shipping Maintenance Release, so 6.5.5 FP2 fixes will also ship in 6.5.6.  Customers unable to upgrade to later Maintenance Releases will want to install Fix Packs to benefit from later fixes made to the product.  By providing a small number of fixes, customers are able to accept fewer code changes with lower risk, allowing them to "patch" an older Maintenance Release until a more extensive upgrade to the current Maintenance Release is possible. Fix Packs may be downloaded from the web, but will not be distributed on CD.

While Fix Packs provide important fixes and IBM strongly recommends applying the latest Fix pack available for a Maintenance Release, IBM still recommends that customers upgrade to the latest Maintenance Release + Fix Pack combination to receive the broadest set of fixes available.  You will receive more overall fixes with a later Maintenance Release + Fix Pack than with a set of Fix Packs on top of an earlier maintenance Release.

The following is a list of the problems fixed in this 6.5.5 Fix Pack.

1. There are 2 fixes below with a plus symbol (+) before the SPR number. This symbol indicates fixes for regression bugs. A regression bug is a bug that was introduced in a Maintenance Release that did not exist in previous releases of that code stream. For example, a bug that appears in R6.5.5 but did not exist in R6.5.3 is a regression.
2. Technote Numbers are displayed in parenthesis following the fix description.

IBM Lotus Domino Web Access:
  • SPR# MSER6H2AXN - Fixed a crash during the initialization of spell check.  The following Notes.ini variable is required to enable this fix: "iNotes_WA_SingleThreadSpellCheck=1".   (TN# 1211007)

  • SPR# ASCR6KNHTK - Fixed a potential replication memory leak (BLK_CL_OPENED_NOTE). (TN# 1242086)
  • SPR# ASCR6LVBZ6 - Better shared memory management under low memory conditions. (TN# 1230991)
  • SPR# BHAL6KWT2X - This fix prevents a semaphore deadlock that can lead to a server hang. (TN# 1228482)
  • SPR# CMCY6KBQAR - Fixed a problem during namelookups.  This problem is observed if you see that the $users, $peoplegroupsflat, and $serveraccess views were getting rebuilt during the day, causing slowdowns.
  • SPR# CTOI68RDMH - Fixed an occasional crash in DIIOP under heavy loads when there is an off by one condition during recycling events.  This means that the actual number of objects that need to be recycled does not match the count we maintain.  (TN# 1196707)
  • SPR# DCOY6MQL7X - NSD now uses an alternative method of mapping addresses to function names in system modules so issues with sym files are avoided.  Prior to this fix, Notes/Domino would sometimes crash attempting to generate sym files for system modules.  With this fix, sym files are no longer created.
  • SPR# DDAN6D7RD3 - Server crashed PANIC: OSBBlockAddr: Bad BBlock handle (FFFFFFFF) due to bad RTRUNIDTableIdx count.  This problem has been fixed in 7.0.2 and 6.5.5 FP2.
  • SPR# DPOS4KEK4E - Fixed a problem with container leaks in IMAP. (TN# 1214977)
  • SPR# DSTT6APL83 - This fix provides Notes.ini variables to control the maximum amount of shared memory the backup process will consume before using temporary files on disk.  The Notes.ini variable "NSF_Backup_Memory_Constrained=1" enables the feature with a default size of 20Mb, the Notes.ini variable "NSF_Backup_Memory_Limit" is provided to tune that size.  The default is NSF_Backup_Memory_Limit=20000000.
  • SPR# EPOD6J9SVK - AdminP move user corrupted a mailfile when moving from Windows to AIX.  A problem was uncovered where cross platform copied databases resulted in the folder directory structure not sorting properly.  A workaround is to run fixup -v on the target platform until this fix is applied.
  • +SPR# FTMN6A5KHC - Fixed an intermittent crash in the DIIOP task which could occur if a CItem object is invalid.  This regression was introduced in 6.5.2.   (TN# 1223447)
  • SPR# GHAN6MBPPG - Fixed a memory leak for BLK_OPENED_NOTE which caused a server crash.   (TN# 1242086)
  • +SPR# GLAS6M3NSM - The chair of a meeting will not receive an approval notice when the room owner accepts the meeting.  Also, the room will not be reserved, as the accept notification is dropped by the router and never processed.  This regression was introduced in 6.5.5.
  • SPR# GRCE6ADT4R - During a mail file move, the AdminP failed with the errors:  "Error: Unable to obtain mail archive settings for mailfile" and "Error: Signer does not have the required access rights to the source database."  In most cases this error can be resolved by having the mail file owner access the archive profile in the mailfile, and accept the current settings.  This should resign the profile with the appropriate name and allow the operations to complete.  The administrator can then restart the request which failed.  Most likely either "Create New Mailfile Replica" or "Push Changes to New Mail Server" will need to be restarted from the admin4 database.   (TN# 1233114, TN# 1242086)
  • SPR# GRCE6EJKU3 - Replaced a panic with a graceful error return.  Prior to this fix, the panic would return "PANIC: OSAddressInVARRAY: VARRAY element index is too large (1748 > 174".  (TN# 1238830)
  • SPR# HZHG6DV367 - Fixed a server crash because of a Windows Access Violation.   (TN# 1248347)
  • SPR# JACE6LB9DB - Fixed a memory leak when resources for a form were in an external database.  (TN# 1248814)
  • SPR# JCHN5YXJ8Q - Fixed LkMgr crashes.  There were some problems in the usage of the database locking mechanism that resulted in many code paths not properly handling error conditions.  The number of code paths and the conditions to hit them are many and the timing and error conditions fairly subtle that it really can not be described very easily into exact reproducible scenarios.
  • SPR# JCHN6K4TV6 - Fixed a crash when running updall on a corrupt note.
  • SPR# JCHN6MX5WW - This fix prevents situations where the logger could not flush transactions to a database because the database reference in DbDirMan had been nulled out.  If the databases were not reopened, this could lead to a log full situation.    (TN# 1233564)
  • SPR# JGRP6AU7P9 - If a user attempts to create an archive database from an archive database, a profile handle would be leaked.  This problem has been fixed.   (TN# 1242086)
  • SPR# JMAN6GUN9U - This fix prevents a server slowdown if flushing does not succeed. (TN# 1248023)
  • SPR# JPAI6RUKRA - Fixed a Domino Server problem that caused the creation of too many BLK_OPENED_NOTE pools without first utilizing previous pools created, which can cause memory utilization spikes and out of handle crashes.   (TN# 1242086)
  • SPR# KEMG6SRKEM - Fixed a potential security issue.
  • SPR# LFOS6H3UAZ - Fixed a memory leak when using a multiple server single sign-on.
  • SPR# LMAN6AAPWF - Fixed a panic during open archive settings when there was a policy with no criteria. (TN# 1240466)
  • SPR# LORN6FKK9Q - Fixed an issue where group names were not properly componentize during filter qualification.  This problem occurred with LDAP searches whose filters contained the CN attribute, and did not return the correct result set.    (TN# 1215368)
  • SPR# LVAE69UHAZ - Fixed a Semaphore deadlock involving SEM_RM_TRAN "Recovery Manager:Transaction list synchronization semaphore" and a database semaphore (TN# 1206294)
  • SPR# LVAE6H5PAJ - Fixed a potential Router crash when transferring a message over SMTP. (TN# 1220977)
  • SPR# MKIN6JKSZQ - Fixed a leak of block type 0x3A33 BLK_HTTP_INPROCESSMEM that caused http to use too much memory.  (TN# 1248814)
  • SPR# MSAN6FTFQN - Fixed a memory leak for  BLK_OPENED_NOTE.  (TN# 1242086)
  • SPR# MSAN6LFF3G - Fixed a potential server crash when the Notes.ini variable NSF_DOCCACHE_THREAD is set.     (TN# 1247551, TN# 1242086)
  • SPR# NBRR6DETXC - Starting on May 19, 2006, Web users may see a message stating that the certificate has expired when Domino applets are loaded by the JVM or JRE in a Web browser.  Applets have been re-signed and are available as support downloads for multiple versions of Domino.  The certificate expiration has been extended until 2009. (TN# 1238081)
  • SPR# NORK6NLNDB - Fixed an http crash when opening a document with a corrupt GIF image.
  • SPR# RBEE6RNKUZ - This fix completes the work done to resolve the problem reported in the SPR TFER6BPKSX "Domino time clock display 'jumps' backwards and forward in time".  Both SPR's, RBEE6RNKUZ and TFER6BPKSX,  are required to resolve the time jumping issues on AIX.
  • SPR# RBRE6J6LCW - Fixed a deadlock between nif and fixup.  (TN# 1226175)
  • SPR# SLED6LRN9K - This fix stops Domino from incorrectly setting items protected when a note was modified by a user with Author access and the database was in Directory Assistance.  The item name was also not a reserved item name.  This problem was fixed in 6.5.5 FP2. (TN# 1237167)
  • SPR# SKAI6J58UL - Fixed a Domino server hang with 0x0244 database semaphore when the cleanup thread was loaded.  Prior to this fix, there was a timing issue with the creation of the osfdg shutdown thread and the process shutdown which can result in a loss of an the OSCreateThread event and thus block any thread creation from then on. (TN# 1248297)
  • SPR# TFER6BPKSX - Fixed instances a problem on some AIX systems where the time in the log would jump forward and backward.  The fix for this problem has been completed in SPR RBEE6RNKUZ.  Both of the SPR's, RBEE6RNKUZ and TFER6BPKSX, are required to resolve the time jumping issues on AIX. (TN# 1232862)
  • SPR# TJOR6GVSUW - Fixed a crash in the LDAP server when performing a Domino UNID search against the condensed directory catalog (CDC).  (TN# 1225761)
  • SPR# VDES6H9JA9 - Under some situations $Writers replicates to replica servers, but never gets removed when the note is unlocked. (TN# 1236863)
  • SPR# VOHL6F6QZ3 - This fix prevents a potential server crash with "PANIC: OSAddressInVARRAY: VARRAY element index  is too large".
  • SPR# WTHE6FLPXW - Fixed a server hang/crash caused by semaphore deadlock or lockouts.  (TN# 1247969)
  • SPR# WMUY6HJPLW - Fixed a crash cycling through paragraph styles and another crash opening a mime newsletter that had an open anchor tag followed by tables. (TN# 1230882)
  • SPR# WWHN6MJKH5 - Server crash on the nserver task with the error "PANIC: OSVBlockAddr: Bad VBlock handle (FFFF\0)".  To fix this problem, an index check was fixed that allowed access off the end of an array.
  • SPR# YFEG6FMW3Y - Fix for the ServerTranSchRetrieve() busytime transaction to properly handle cases where a failure could result in a server crash when an invalid memory handle gets reused. (TN# 1239070)
  • SPR# YPHG6L4A9A - On AIX 5.3, if /etc/resolv.conf is missing, Domino can crash. This fix prevents the crash. (TN# 1238728)
  • SPR# YYUN6TNDYZ - Renewed signing certificate for .cab files.

0 Commenti:

    Nessun Commento Trovato
Commenta articolo

Questo spazio web è stato creato da per un uso pubblico e gratuito. Qualsiasi tipo di collaborazione sarà ben accetta.
Per maggiori informazioni, scrivete a info@dominopoint.it

About Dominopoint
Dominopoint social presence: