Service Desk Practitioners Forum
cancel

My scheduled db rule task blocked app server's performance !!

Highlighted
James Chen_2
Respected Contributor.

My scheduled db rule task blocked app server's performance !!

Hi:
I created a db rule to check when the current time exceed the sc's expiration time and sc's status is not closed, send alert email to related people.
But today morning customer found their clients can't link to the server anymore. I had to restart the app server service and it's OK. When I checked server log, I found there are full of the db rule's scheduled task and no other db rules are excuted.
I think there are too many sc(1000 scs per day) which exhausted server's performance.
Does anyone encounter problem like this and have solution?
Thank!!
6 REPLIES
Ramaprasad N
Outstanding Contributor.

Re: My scheduled db rule task blocked app server's performance !!

Scheduled tasks will have direct impact on the server's performance. We have faced such an issue before, in aan environment here. We then implemented the multiple servers solution. It will enhance the performance. From my experience, normally an OVSD server instance can handle upto 600 scheduled tasks, efficiently.
James Chen_2
Respected Contributor.

Re: My scheduled db rule task blocked app server's performance !!

I have used two load-balanced appserver but the two server all can't be linked or show very low response(That is right what I descirbed ).

Also I have modified memory used by JVM (min 300MB) before configuring schedule db rules.

Do you have some suggestion?
Thanks!

Ruth Porter
Acclaimed Contributor.

Re: My scheduled db rule task blocked app server's performance !!

Hi James,

Can you post exactly how you defined your rule because sometimes a small adjustment to the condition of a scheduled DB rule can assist.

Regards

Ruth
http://www.teamultra.net
James Chen_2
Respected Contributor.

Re: My scheduled db rule task blocked app server's performance !!

Hi,Ruth:
My db rule is like this:
DB RULE NAME: unfinished sc alarm
Apply this rule:
when create or change scs.
Conditions:
status is not equal to closed
check this condition 1 minute after sc's temination time.(execute only once)

Actions:
mailto related people.

There also are server logs in the attachement, please check it.
Ruth Porter
Acclaimed Contributor.

Re: My scheduled db rule task blocked app server's performance !!

Hi there,

When you say "termination time" what do you mean?

If yu mean Deadline I would suggets the following:

When SC is created or modified
Conditions:
1. Deadline is not empty (with "Evealuate this rule ..." set)
2. Scheduled at 1 minute after Deadline, Status not equal to closed, only execute once

Hope this helps

Ruth
http://www.teamultra.net
James Chen_2
Respected Contributor.

Re: My scheduled db rule task blocked app server's performance !!

Hi,Ruth:
Termination time is Deadline, I didn't add deadline not empty condition because all scs have deadline in my environment.
But in my environment one day nearly 800 scs, I think maybe it's the main reason.
I don't how to handle with it.