I would like to bring your attention to the SPR# RMAA88UAGF – server crashes when clients synchronize unread marks on Domino 8.5.2 servers.
I ran into this last week when we had some unexplainable server crashes for apparently no good reason – one of them happened when I was showing a help desk tech how to synchronize unread marks between replicas from the client. I investigated and the crash report that Domino gave me pointed me right to this error – now fixed in FP1. It is a regression bug and is not fixed in either of the previous hot fixes for the Domino 8.5.2 code stream. I had servers with both the SMTP patch and the interim fix (IF) as well – they all crashed at one time or another. I installed HF 1 on all servers and now they are safe from this issue – I tested it on all of them just to be on the safe side.
If you don’t have HF 1 installed yet – do it soon, this one can happen at anytime during the day and there is no warning whatsoever. only a big “boom” when the server disappears from the face of the (electronic) earth. Incidentally, there are allot of other problems that are fixed in that HF as well – I suggest you look into it right away and consider upgrading all your Domino 8.5.2 servers soon.
I just checked – IBM’s Fix Central website finally has FP5 available for download for all versions of Domino and Notes. Go forth and upgradedth thy servers!!
Finally! I spent all of 25 minutes yesterday to upgrade my main Domino server to 8.5.2 with the new HF for SMTP that came out yesterday. I waited on this fix and all I can say is that the upgrade (from 8.5.1 FP4) was quick, simple and even the old HW that my server runs on had no issue with it. What took the longest was the download of the Domino install (15 minutes) and everything else was quick.
I do have clients that want to wait until FP1 comes out – somewhat short-sighted but I do understand some hesitation. That is exactly why I did not upgrade my servers immediately when the new version came out – I like to wait and see what issues and downright problems are found by those braver than me. Once I see a lull – then I go ahead and make a decision.
So, if Mr cautious did it last night while watching TV and sipping a nice glass of Cabernet Sauvignon and upgrading Symantec on another server, what are you waiting for?
Interesting topic from the point of view of somebody who was once on “my side” of divide (client) and is now with a vendor. Of course, giving some “secrets” away is paramount to shooting herself into the foot ….
Once the presentations become publicly available, I suggest a quick look at it.
I will be attending IamLUG 2010 this year, and am very much looking forward to thew whole affair again. Once more, I will be accompanied by cheap slave labor (aka my son Kenneth) who will be helping out as a room monitor again. Insofar as I am paying for his trip and tickets to a Cardinals game (it’s his birthday) IamLUG is not free for me 😉 – he also eats allot and I will be passing a hat around during sessions asking for donations to help me keep this monster fed.
Looking forward to seeing y’all there!
I my last post I talked about what the main advantage of going 64 bit Windows for Domino – shared addressable memory – but I really did not go into detail on whether 32 bit or 64 bit Domino is the better choice for an installation.
As I mentioned previously, the main advantage of going 64 bit Windows is that your Domino instance will not have 4 GB of addressable shared memory available. The kicker is that this holds true for both 32 bit and 64 bit Domino on 64 bit Windows. This fact came as quite a surprise to me when I found out, this is due to the way that the Domino memory system and the memory handles are currently designed.
So the question becomes, why would I choose 64 bit Domino if 32 bit does the same for me?
Personally, I believe the main deciding factor is whether you plan to run add-in tasks in your Domino instance or not. To run an add-in task on a 64 bit Domino server the add in task also needs to be 64 bit. To run an add-in task on a 32 bit Domino server the add-in task needs to be 32 bit as well.
The logical conclusion therefore is: if you plan to run ANY add-ins (e.g.: Anti Virus, etc.) on your 64 bit Domino server you need to determine if that program is available in 64 bit as well. If it is and any other products you might consider running are available in 64 bit as well – then you can go ahead (but test first anyway – of course!!) and install 64 bit Domino. If this is not the case your choice will need to be 32 bit Domino.
“Elementary, my dear Watson.”
I have been absent for a while but with good reason – a new project that keeps me VERY busy.
Being busy though also has it’s advantages though, since it also means that I get to be exposed to allot of new things and learn more and more.
So, 32 bit vs 64 bit – what is the difference? Well, first of all let’s state that I am talking about Domino on Windows. To run 64 bit Domino you require 64 bit OS. What that also means is that any add-in tasks that you want to run inside of Domino will also need to be 64 bit – 32 bit 3rd party processes will not run on a 64 bit Domino/Windows server.
What is it that you gain? Well, the main gain you get is shared addressable space. Under 32 bit domino the maximum shared address space you get is 2 GB. that means that any add-in task you run (such as an anti virus product etc.) has a maximum shareable shared address space of 2 GB. On a busy server that can can be tight. The reason I know that is that in the first week I started my present project we saw what happens to a server that runs out of available shared address space – it will will present you with a crash and a wonderful NSD file ….
Now, when you change to 64 bit you now double your shared addressable space to 4 GB. this gives you PLENTY of space for a busy server (user sessions, applications, third party add-ins, etc.).
I will blog more about this topic in the near future and hopefully be able to shed some more light on this interesting subject.