Lotus Notes/Domino 7.0.4 Fix Pack 2 Release Notice
June 30, 2010
IBM Lotus announces the release of Notes/Domino 7.0.4 Fix Pack 2, a scheduled Fix Pack of a limited number of low-risk, high-impact fixes to help customers safely avoid known issues. IBM strongly recommends that customers running Notes/Domino 7.0.4 upgrade to this latest Fix Pack since it addresses a small percentage of defects that impact the broadest set of customers. Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments. They go through the same level of fix, regression and interoperability testing that occurs with Maintenance Releases. Future Fix Packs are always cumulative and contain all of the fixes from previous ones.
Notes/Domino 7.0.4 Fix Pack 2 addresses defects in the Server only. All Fix Packs are language independent and may be applied on any language version of Notes/Domino 7.0.4.
Download options
See technote #4023967 - "Download options for Domino 7.0.4 Fix Packs." Fix Packs will not be distributed on CD.
Decision to upgrade
Customers unable to upgrade to later 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 Release is possible.
However, 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 Release + Fix Pack combination to receive the broadest set of fixes available. You will receive more overall fixes with a later Release + Fix Pack than with a set of Fix Packs on top of an earlier Maintenance Release. For more information, see technote #1368141 - "Differences between Notes/Domino Maintenance Releases, Fix Packs and Cumulative Client Hotfixes."
Fixes contained in this Fix Pack
Note: A plus symbol (+) before the SPR number indicates a fix for a regression bug. A regression bug is an issue that was introduced in a Maintenance Release but did not exist in previous releases of that code stream. For example, a bug that appears in Release 7.0.4 but did not exist in Release 7.0.3 is a regression.
The Fix List database on developerWorks contains the description of each fix in this Fix Pack, and indicates which platform(s) have been fixed.
7.0.4 FP2 Fix List
Server:
- SPR# AJMO7AXLXE - Domino server leaks memory and results in "LDAP BPool Full" error on the console. This can occur when the server is configured with Directory Assistance to query a remote LDAP server and that remote LDAP server has connectivity issues. (Technote #1381690)
- SPR# AJAN7NZUEV - Fixed an HTTP crash caused by improperly formatted data being passed through the network. (Technote #1389332)
- SPR# CSAO7TGASZ - Enhancement that verifies URLs to avoid a potential Domino Web Server crash.
- +SPR# CSCT836HFL - View.getDocumentByKey and getAllDocumentsByKey fail on a very busy view, with the error "the collection has become invalid." This fix will allow collection retrieval under all commonly occurring conditions and is primarily for the server, but will pertain to both client and server.(Technote #1424178)
- SPR# CTOI7QFKSL - Domino server process NPROCMON was crashing with the error message "PANIC: Server Process terminated abnormally." A workaround to this problem is to enable the parameter Process_Monitor_Disabled=1 to disable the process monitor function.
- SPR# ESAR85MQL7 - Fix to update views during View.GetDocumentByKey/GetAllDocumentsByKey so self modifying views can see their modifications.
- SPR# GHAN7WUTNW - Fixed a non-reproducible crash which could occur when the Adminp process ran batch requests.
- +SPR# HNAA7XR9ZK - AMgr task terminates abnormally while pulling a string value from richtext.
- SPR# JCOL7SLL57 - Fixed an intermittent server crash during updall of database. (Technote #1416266)
- SPR# JFAA65GMQH - This fix will eliminate a crash in Endp_GetFirstRqst during normal operation of IMAP. (Technote #1196870)
- SPR# JPMS7F2NQN - Fixed a Domino crash when clicking on the "Analysis" tab in the Administrator Client if their are multiple Smart Upgrade mail-in databases defined in policies. (Technote #1306193)
- SPR# KLYH7ZPNC2 - Fixed IBM Lotus Domino LDAP buffer overflow vulnerability. See technote #1420749 for more information.
- SPR# LMIL7S9QSM - This fix addresses a problem when Domino attempted to serve out a message that had itemize errors and appended the MIME source as an EML attachment when itemized. The way Domino serves the information caused the crash.
- SPR# MKIN7TGMQV - Fix for Windows, where we had performance problem on high latency networks. We added/changed code to reduce latencies by changing how the winsock layer is used and by increasing the buffer size of network writes. (Technote #1403333)
- SPR# MKIN823SZZ - Improved network performance of the web server on W32 when using a high latency network. The web server needs to wait until all data is sent before calling EndRequest.
- SPR# MLEE7RUKB2 - Replication attempt with no matches crashes the server. (Technote #1405763)
- SPR# OIHZ7UVJ7T - Prior to this fix, an incorrect error was displayed when folders contained future TimeDates. The error "Error 4000: %a's Certification Log" will no longer be displayed. The correct error will be "The collection has become invalid." (Technote #1396849)
- SPR# SKAI7KGHG5 - Fixes a problem with Japanese filenames during TNEF conversion. Previously, some filenames had the wrong characters displayed.
- +SPR# SRIO7RKKNU - Fixed a Server crash when using the Domino console command "DBCache Flush." This regression was introduced in 7.0.4.
- SPR# UTOO7F3B3K - If a database cached by HTTP is attempting to be accessed again by HTTP while offline, the database will return "currently being used by someone else" until the server has been restarted.
- SPR# WBKK7EKQ7X - Fixed a problem where the time displayed by Domino would jump around, such that it would not correctly reflect the system time. (Technote #1327441)
 Go back |  |
|
|
|
|
|