1 Reply Latest reply on Jan 15, 2004 7:07 AM by darranl

    Why "all" configuration?

    bentzy

      At /usr/jboss/jboss-3.2.3/server/default/deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml we see:

      In order to activate HTTP Session clustering for Tomcat
      make sure you run JBoss's "all" configuration i.e.
      "run -c all"
      (the default configuration doesn't contain clustering)

      I'm implementing a cluster and I don't need HTTP sticky sessions.
      As I understand the JK2 connector is the responsible of switching between the various JBoss instances,so

      Have I need "all" configuration?
      Why?

      Thanks

      bentzy.

        • 1. Re: Why
          darranl

          The default configuration is not configured for clustering.

          The all configuration is configured for clustering.

          That is why you are reccomended to use the all configuration for a clustered feature.