6 Replies Latest reply on Jun 5, 2011 4:03 PM by rhusar

    application context not enabled at startup

    mschwery
    mschwery May 12, 2011 11:02 PM

      We are running mod cluster 1.0.6 and I've noticed that when we start our ejb based web service applications they don't have the context enabled on the mod cluster manager web page at startup. Sometimes you can enable the context but mostly you can't enable the context after startup in the mod cluster manager web page. Has anyone seen this type of behavior.

      • 5948 Views
      • Tags:
        • 1. application context not enabled at startup
          jfclere
          jfclere May 13, 2011 3:47 AM (in response to mschwery)

          Could you try with a more recent version like 1.1.2 or 1.0.10

            • Actions
          • 2. application context not enabled at startup
            rhusar
            rhusar May 13, 2011 5:17 AM (in response to mschwery)

            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.

              • Actions
            • 3. application context not enabled at startup
              mschwery
              mschwery May 13, 2011 12:28 PM (in response to rhusar)

              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:

               

              Contexts:

               

              /tap, Status: ENABLED Disable

               

              Aliases:

               

              localhost

                • Actions
              • 4. application context not enabled at startup
                rhusar
                rhusar May 13, 2011 7:35 PM (in response to mschwery)

                I see now. So I assume  you are exposing them with @javax.jws.WebService and @javax.jws.WebMethod?

                  • Actions
                • 5. Re: application context not enabled at startup
                  mschwery
                  mschwery Jun 3, 2011 9:45 PM (in response to rhusar)

                  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.

                    • Actions
                  • 6. Re: application context not enabled at startup
                    rhusar
                    rhusar Jun 5, 2011 4:03 PM (in response to mschwery)

                    Hi Mike,

                     

                    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).

                     

                    Thanks

                      • Actions