Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7116

Improper handling of domain included in jvmRoute

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Don't include the domain in the server.xml jvmRoute value; just use a distinct node name for each node. The mapping from node name to domain can be specified in the mod_jk or mod_cluster load balancer configuration and doesn't need to be included in the jvmRoute itself.

      For configuring the domain with mod_jk, see the "domain" directive on http://tomcat.apache.org/connectors-doc/reference/workers.html.

      For mod_cluster, see the "domain" attribute at http://www.jboss.org/mod_cluster/java/properties.html#proxy

      Show
      Don't include the domain in the server.xml jvmRoute value; just use a distinct node name for each node. The mapping from node name to domain can be specified in the mod_jk or mod_cluster load balancer configuration and doesn't need to be included in the jvmRoute itself. For configuring the domain with mod_jk, see the "domain" directive on http://tomcat.apache.org/connectors-doc/reference/workers.html . For mod_cluster, see the "domain" attribute at http://www.jboss.org/mod_cluster/java/properties.html#proxy

      Description

      org.jboss.web.tomcat.service.session.Util doesn't handle a domain.node as the jvmRoute format:

      public static String getRealId(String sessionId)
      {
      int index = sessionId.lastIndexOf("."); // WRONG!! Use String.indexOf('.', 0);
      if (index > 0)

      { return sessionId.substring(0, index); }

      else

      { return sessionId; }

      }

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            brian.stansberry Brian Stansberry added a comment -

            Note that some commits for this issue we're inadvertently committed under JBAS-7016.

            Show
            brian.stansberry Brian Stansberry added a comment - Note that some commits for this issue we're inadvertently committed under JBAS-7016 .
            Hide
            brian.stansberry Brian Stansberry added a comment -

            Reopen to correct Fix Version

            Show
            brian.stansberry Brian Stansberry added a comment - Reopen to correct Fix Version

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development