Optimum number of jdbc notifications on an IS

Hello all,

I have observed that as the number of jdbc notifications on the server increase the IS startes throwing cronDaemon pool errors and unavailable thread errors.
This issue is eventually resolved by setting the watt.server.maxCronThreads property in the extended settings or by having a common notification table for multiple interfaces thereby reducing the no. of notifications on the IS.Also by setting the polling interval to a reasonable value like 15 - 30 seconds.

I would really appreciate if anyone has any suggestions or advice regarding the optimum number of notifications the IS can handle and any design suggestions when implementing a real time integration srategy on a common source system using jdbc notifications.

Thanks in advance,