WebSphere 6.x doesn’t start with its EJB Container disabled
WebSphere 6.x appears to be tightly linked to its EJB container so much so that we can’t start the server without the EJB container. The administration console does allow preventing the EJB container from starting. But then on server bootstrap Scheduler service complains that it can’t find the EJB container. And guess what, the scheduler service cannot be disabled in 6.x, at least in a documented way. In a nutshell, my server start up failed. I had to go hand-edit the server.xml to be get my server working again.
Why should environments running plain web applications have to bear with the EJB container footprint unnecessarily? And what could be the reason behind introducing a dependency on a nested container for the server to work normally. And how about actually telling the user they shouldn’t be doing this action because their server won’t startup after that?
