Still acting weird

When WebSphere freaks out, it's because of an exception caused by: com.ibm.ejs.sm.active.ActiveEJBServerProcess. Apparently it's unable to ping the default server and decides it's time to restart it. I've got two different machines installed with WebSphere and both exhibit the same behavior. Research on the web shows at least two other people have had this exact same issue crop out of nowhere, one on WAS 3.5 and one on WAS 4.0.2. We're running WAS 4.0.1.

Unfortunately, neither questions have answers.I've adjusted the ping/default time out settings for both servers and will continue to watch them to see if this solves the problem. One post seemed to indicate that this had worked for them on one server, but not another. We'll see what happens.