BlackBerry® Enterprise Service 10

[stubbo]

Hello -

The BAS console has become very slow to load/refresh in the last weeks, e.g. a user search can take 5-10 minutes to return a result.

We are running on Windows Server 2003 R2 with all the Windows updates and BES 5.0.3 MR4.

Today we patched to 5.0.3 MR6 but this has not fixed it.

It's running with 2 GB of RAM and 1 vCPU on VMware. BAS-AS.exe is using approx 900 MB in Task Manager.

SQL is running on another machine, and we are running 300 BB handsets.

There's a repeating warning in the BBAS logs which may or may not be significant:-

(02/11 11:22:23:428):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.resources.arjunacore.noresource] [com.arjuna.ats.internal.jta.resources.arjunacore.noresource] No XAResource to recover < 131075, 31, 29, 1--53eff739:484:4f184cd4:7a8816-53eff739:484:4f184cd4:7a8825  

Any advice please?

Thanks.

[Oyasumi]

Hello,

May I know if you found a way to solve your problem ?

I have the exact same problem presently, and I did not succeed in finding any relevant information

Thanks & regards.

Oya

[knottyrope]

I dont have this issue on SP3 MR8

Are you able to apply latest version?

[Oyasumi]

Hello,

BES for Exchange was in SP3 MR5.

I just applied the latest version as you advised : SP3 MR8.

However I still have the same problem : BAS webconsole, or webdesktop, are very very slow : it's almost impossible to browse or find a user.

Everything was working fine, and this problem occured suddenly (around one week ago).

I spent several hours trying to find out the cause... but in vain.

Here is the persistent log I can find in th BBAS-AS log file :

{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.resources.arjunacore.noresource] [com.arjuna.ats.internal.jta.resources.arjunacore.noresource] No XAResource to recover

Before the problem, there was usually 3 BBAS-AS log files weighing around 512MB per day.

Since the problem, there's only one BBAS-AS log file weighing around 1KB.

If anyone has an idea about how to solve this problem... It would be really appreciated

Thanks & regards,

Oya

[stubbo]

Hello again -

We discovered the BESMgmt DB had grown way too large (i.e. 24 GB in our case) 

More specifically, JBM_MSG table was around 22GB in size, and also excessively large JBM_MSG_REF table

So we truncated the tables and BAS returned to normal

Also discussed here

Does this help?

[knottyrope]

thats an interesting cause for your slowness.

Thanks for sharing your solution.

[Oyasumi]

Dear Stubbo,

I confirm you that truncate the two tables (JBM_MSG and JBM_MSG_REF) has solved the problem.

Thank you very much for your help !!

Oya