Be-engine consuming around 25 percent of the CPU and messages are not getting through TIBCO. One thread of BE-ENGINE running ~4% CPU and another one ~20%
Some of the pointers to the “possibly related” issues:
Quite verbose thread stack listing is at the bottom. But most importantly, what we found pointed us in the direction of upgrading TIBCO machines from jre 1.5 to 1.6u10+.
Currently, TIBCO admin guys are trying to let one of the TIBCO instances to run on 1.6u16 which turns out to be somehow a none trivial task. Will be back with results.
0:000> ~* e kb2000
X threads with the following stack: