|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
There are at least two fairly big deal updates in this release. If I read correctly, the very long standing issue some people have had where servers would seem to become unavailable unless you time-out and reconnect may have been resolved in this release. The other key issue I see is something I've experienced since moving to 7.0 which was that if your server failed to connect on a replication schedule, it didn't reschedule the connection which could mean replication would not happen unless either the other server initiated replication, you restarted your server, or you issued a replication command at the server console.
Here's the info from the larger fix list document
This fix makes the client close sockets as soon as they detect the server has closed the sockets.
SPR# RBEO6HZM89 Regression in 7.0
Fixed a problem that can cause Scheduled Replication to stop rescheduling itself. This regression was introduced in 7.0.
Please wait while your document is saved.
SPR# CAOA6F78Z2 - Fixed a problem where scheduled agents stopped running. The
problem seems to occur when using an agent set to run during a certain time
(for example 3:00 - 2:00), not all day. (We've seen this happen at least once.)
SPR# JCHN6DRS62 - Fixed an intermittent problem that can cause documents to not
show up in views properly when soft deletions are being used in a database.
Affected databases can be fixed by running fixup -f followed by updall -R. (I
believe this is part of what's happening in our environment with docs not being
"deleted" or restored properly in mail...)
SPR# MKIN6FARE7 - Fixed an erroneous debug in http request logs when we have a
cache hit for DWA.