> > Some of the Opensaf threads are indeed run in real-time mode (that is, > if you are running Opensaf with "root" priviledges). However, that may > not be enough to handle stress on the following: > > (1) Memory: I see that the "java" process has a huge size. What do > the top few lines of your "top" dump show? > > (2) Network Traffic: Heart-beats may be getting queued (and delayed) > behind ordinary traffic if network traffic is very high. This may (just > may :-)) be the case if your CPU load is associated with lot of network > traffic. > > It may be useful to check the above two possibilities to help isolate > the root cause. >
Others in HP have reported the same behavior just with a normal priority process stuck in a CPU-bound infinite loop. Chad
_______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
