I believe your assumptions are corrct Alessandro.
naming conventions are usually hard to enforce in a multiuser environment
i believe job-type based routing would be a cleaner solution
time for an RFE maybe
The property Job type is not available anywhere, that can be a RFE. You can add a Custom property something like ‘Purpose’ to use in the job execution rules rather than relying on the name.
What version/SP are you on when you observe the slowdown w/ PAJ?
we're on 8.0 SP7
This might be an expensive query but can you run:
Select count(*) from job_run_event where message = ‘Task has timed out, canceling command execution.’
or you could search the appserver logs for:
grep 'Bl-exec' appserver.log* | grep "Task has timed out" | wc -l
(use your appserver log file names)
If that returns something in the millions of rows, you should look at applying SP8 – there is a problem w/ patch analysis jobs that causes millions of these timout messages and seems to 'slow down' the appservers in my experience.
no "Task has timed out" found
it doesn't seem to be our case