Could you try with a more recent version like 1.1.2 or 1.0.10
Hey Mike, defnitely try the new version if possible, otherwise we would need logs and conf :-)
But what do you mean you can't enable the context? So the context is appearing in the mod_cluster-manager? Enabling and disabling works like a charm there. Maybe you mean that the context is not accessible or is not appearing in the manager at all. Any chance you are running into https://issues.jboss.org/browse/MODCLUSTER-190 when ENABLE-APP is sent before the connectors are started so immediately upon accessing it you get an error and mark the node to error state.
This is just happening with our ejb based apps. The non ejb apps are working like a charm with mod cluster manager.
When I say enable context I'm referring to "Enable Contexts Disable Contexts" shown below.
Enable Contexts Disable Contexts
Balancer: mycluster,Domain: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Elected: 6,Read: 16368,Transferred: 0,Connected: 1,Load: 84
Virtual Host 1:
/tap, Status: ENABLED Disable
I see now. So I assume you are exposing them with @javax.jws.WebService and @javax.jws.WebMethod?
We upgraded to mod cluster 1.0.10 and saw an improvement but it still wasn't stable enough so we went back to mod_jk.
Sad to hear that. I am keen on fixing your issue. Would you be able to provide any form of sample of that EJB app (with possibly Apache conf snippet) and your use case? (If you cant remove sensitive parts from the code we can try to resolve it via email, off the community forums).