[m4ilm4n]

Prior to upgrading to 4.1.6 on Domino, BES ran fine for weeks without a restart. Post upgrade, we've incurred several incidents where BES will simply stop processing - it shows that it's running, it's just not doing anything. If I issue a "tell bes quit", it just sits there - it doesn't shut down unless I restart the Domino server. So far I haven't found anything to indicate what the issue might be - there's nothing in the logs or console to indicate an error, it just stops processing.

Has anyone else seen this and if so, have you found a solution? TIA.....

John
BES 4.1.6 on Domino 8.0.1

[m4ilm4n]

Finally dug deep into the log files and found this:

[20149] (08/18 20:30:00.626):{0x152C} Thread 1734, utilization=98.9453%, failed health check 26 times
[20148] (08/18 20:30:00.626):{0x152C} Thread:  *** No Response ***  Thread Id=0x1734, Handle=0x768, WaitCount=26, Last Activity: Scanning for new mail for user

About an hour and a half later, the log just stops.

[gibson_hg]

I'm not a Domino BES expert but I did find this on RIM's TKC:

BlackBerry Search Results

Might be of use to you, it describes the No Reponse thread you are seeing in your logs.

Here's another that you might find helpful:

BlackBerry Search Results

Let us know what you find.

[m4ilm4n]

Thanks - I'd seen those; KB03034 is kinda old (v2.2), so I don't know how much of it still applies, but I can still try to run a user dump. KB03124 refers to possible network communication issues between the Domino server where the user's mail file resides and the BES - in our case, both servers are connected to the same network switch.

This has only happened once before, and coincidentally (or not) it also happened during an outage on our production network where our NOC sent out outage notifications. I'm trying to correlate that outage with this one to see if there's a relationship between what the NOC sends and the BES becoming unresponsive. I will post back what I find.

[rsun]

I had this issue on my BES after upgrading to 4.1.6, the fix was to disable both options related to HTML processing, and that solved it. RIM created an SDR for me and said that the MR1 of SP6 should have this fix included.

[m4ilm4n]

Interesting - I may give that a try. Thanks. One fortunate side-effect I've noticed after applying SP6 is that the version of the Emergency On-Call application I had worked on (and never got to work right) suddenly started working fine. I suppose if I turn off the HTML options it will probably break again.

[m4ilm4n]

OK - just had it happen again, under different circumstances (it was MY mailbox thread that hung), so it's not related to the outage notifications I mentioned before.

Richard - which two HTML options were those? I hunted thru my config and couldn't find them.

[Nico57]

Same issue here.
Our BES freezed several times during the last few weeks (about once or twice a week), following an upgrade to BES 4.1.6.
Most messaging servers (and BES) are running Domino 7.0.3 FP1, and a few ones Domino 6.5.6 FP2.

Disabled HTML and inline images processing for now; I hope this will help getting rid of the freezes.

Oh well, I also customized the Servers view in our Domino Address Book during the same timeframe, but I don't think that's related.

[Nico57]

BTW, HTML and inline images processing can be disabled in BlackBerry Manager, in the properties of your BES server, Messaging section.
Rich Content Enabled -> False
Inline Images Enabled -> False

[markkk01]

Just upgraded to SP6 and I have started to get the problem described above. Large utilization, health check failed, etc. So, I am going to turn off the HTML processing as well until the fix is out. Thanks for this posting was going nuts trying to find out what the problem was.

[x14]

Started having this problem last night after 3 weeks of trouble free operations. Locked up last night and mid-day today. This server only has 2 users on it.

Put the workaround in. Will see what happens.

[Joe1004]

We started having the same issue as soon as we upgraded to 4.1.6.

Haven't had much time to research it. I am the only user on a device with 4.5. No one else has upgraded yet, so I guess turning off rich content and inline images would only affect me.

Any word on when MR1 will be out?

[siemp]

Same issue here . After a few weeks of no problems the server suddenly freezes. Luckely I only have upgraded in our test environment.

Domino 8.0.1 / BES 4.1.6 / 20 users in test.

[m4ilm4n]

Originally Posted by Joe1004

Haven't had much time to research it. I am the only user on a device with 4.5.

In every occurance, the thread that hangs is associated with a user that has been upgraded to BB OS v4.5. Granted, in our case it's technically unsupported (T-Mo has not released 4.5), but I believe it's directly related (if not the actual cause).

Knock on wood - we've been running well for over a week now.

[woerner]

I am having the same issue 4.1.6 on domino 8.0.1, I turned off Rich Content Enabled and Inline Images Enabled. We will see what happens!

[x14]

Had no problems since I turned off Rich Content and Inline Images.

[m4ilm4n]

Well, so much for causality - twice in two days, the server just simply stopped processing messages to particular devices (but kept going for others), and the affected devices have not been upgraded to OS v4.5. What's worse is that this time there were no log entries indicating a hung thread, and no threads occupying the CPU. Very puzzling....

[BigA]

Same issues as above. On Domino 7.0.2 BES 4.1.6.. It happens about once a week.

[m4ilm4n]

I turned off rich content and inline images; so far it's holding up. The good thing is that links still work, although they show up as text instead of an icon, so the apps I've been working on still work.

[Bunk454]

Add me to the list....I have been experiencing the exact same problem.
More often than not, I'm rebooting the server once per day.

I just disabled HTML and inline images processing, and am hoping this resolves the problem. Only 15 users, and I'm the only person on 4.5, so no harm done.

I'm anxiously awaiting a real world resolution to the problem!