Skip to main content link. Accesskey S Skip to tab navigation link. Accesskey 1 Skip to sub navigation. Accesskey 2
  • Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Similar Entries

photo

Make the Fault Repor...

Blog:  The Notes Guy...
David Hablewitz
Updated 
RatingsRatings 1     No CommentsComments 0
photo

A lesson in Poker an...

Blog:  The Notes Guy...
David Hablewitz
Updated 
No RatingsRatings 0     No CommentsComments 0
photo

Re: What is in your ...

Blog:  Lotus Nut
Chris Whisonant
Updated 
No RatingsRatings 0     CommentsComments 1
photo

Secure Webservices

Blog:  Urs Meli
Urs Meli
Updated 
No RatingsRatings 0     CommentsComments 2
photo

Notes ID switching

Blog:  Urs Meli
Urs Meli
Updated 
No RatingsRatings 0     CommentsComments 2

+ Archive

+ Blog Authors  

Erik Brooks

8.5.1 UN-FAIL! The Fix is coming...

Erik Brooks |   | Tags:  8.5.1 ibm support bug lotus development notes designer domino | Comments (6)  |  Visits (1,413)
  
For those that were asking me, yes - IBM has finished a fix for the GetDocumentByKey problem. I won't steal any thunder about the formal announcement (also because I don't know all the details) but the way IBM explained to me how the refined algorithm works is awesome.
 
So awesome, in fact, that you may see your apps scale much, much, MUCH better under load than ever before.
  
I'll go into more detail after the formal announcement, but this fix (really a more-correct implementation of the infinite-loop fix) may be yet another reason to get on 8.5.1, ASAP!
 No RatingsRatings 0

Comments (6)

photo
1 Timothy Briley commented   Permalink No RatingsRatings 0

Any chance that the fix will also enter the 7.0x codestream? There's more than one company that's not in a position to move to 8.5.1 yet.

photo
2 Erik Brooks commented   Permalink No RatingsRatings 0

@1 - I think so. 7.0.4 was the first release affected so I'd bet they'll do a server IF (interim fix) or HF (hotfix). Likely the same for 7.0.4FP1 also.

 
 
The main question is the client codestreams. Something's got to be a pretty big deal to make it into a client-side fix, a "CCF" (critical client fix) update. This fix is probably high-enough priority though to warrant one.
 
 
Unfortunately I don't think that it will make it into 8.5.1FP2, which means there are effectively going to be a *lot* of different versions in the short term for which IBM will need to create this fix.

photo
3 Denny Russell commented   Permalink No RatingsRatings 0

Would love to see a 7.0x fix for this as well. We've got customers running 7.0x that can't get to 8.x any time soon.

photo
4 Maria Helm commented   Permalink No RatingsRatings 0

We put in a PMR earlier this week and received our fix today. (PTF for iSeries). It does require us to take down all the 8.5.1 servers on the partitioned iSeries to apply the PTF. (I was hoping we could only take down the application servers to apply to them immediately, and get the mail/other servers another time.)

 
 
So, for anyone who is chomping at the bit for a fix, if you've got support on a Passport account, call in a PMR.

photo
5 John Vaughan commented   Permalink No RatingsRatings 0

Thanks Erik for your blog post about this, we never would have known about it otherwise.

 
 
We opened a PMR about this as well. I've tested the Hot Fix with code I wrote to specifically test this issue and I could not reproduce the error (I was able to before the HF). We are running 8.5.1 in test, and about to deploy to production.

photo
6 Giulio Campobassi commented   Permalink No RatingsRatings 0

@1 & @3 Technote indicates that it's included in 7.0.4 and 7.0.4.1...

Add a Comment Add a Comment

Previous |  Main  | Next
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About