When using the Sterling Search Index feature,
some threads used by your application server may be reported as stuck
or hung.
Problem
When using the Sterling Search Index
feature, some threads that are used by your application server will
run for the lifetime of the server, and will result in the thread
being reported as stuck or hung.
Solution
You can either:
- Disable ’stuck thread reporting’ and ’hung thread reporting’ for
the EJB-based thread pools configured as part of the parallel processing
feature configuration, or for the application server altogether.
- Ignore any ’stuck thread’ and ’hung thread’ exceptions in the
log files if the exception trace contains references to the PeriodicBatchIndexer
class.