glassfish
  1. glassfish
  2. GLASSFISH-19351

[UB]GlassFish Server 3.1 Administration Guide has incorrect steps for mod_jk

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2.2
    • Fix Version/s: 4.1
    • Component/s: docs
    • Labels:
      None

      Description

      In To Enable mod_jk:
      http://docs.oracle.com/cd/E18930_01/html/821-2416/gfaad.html
      step 5 creates an http-listener on port 8009 with this asadmin command:

      create-http-listener --listenerport 8009 --listeneraddress 0.0.0.0 --defaultvs server listener-name

      Then in step 6, another network listener is created on port 8009:

      create-network-listener --protocol http-listener-1 \
      --listenerport 8009 --jkenabled true jk-connector

      Step 5 is unnecessary if you're doing step 6, and results in an unstartable domain, as GlassFish attempts to create two listeners on port 8009.

      The instructions should either be to create an http-listener as in step 5, then enable jk on that already-created listener like this:

      set configs.config.server-config.network-config.network-listeners.network-listener.<listener name>.jk-enabled=true

      or to use step 6, which does it all in one step.

      It's also weird to not specify the listener name in step 5, but then to use an example listener name in step 6 ("jk-connector").

        Activity

        Ian Evans created issue -
        Hide
        Ian Evans added a comment - - edited

        Also, step 6 assumes that the user is using a glassfish-jk.properties file in their domain, and not a workers.properties file with Apache httpd:

        set server-config.network-config.network-listeners.network-listener.\
        jk-connector.jk-configuration-file=domain-dir/config/glassfish-jk.properties

        This command is unnecessary if you're configuring mod_jk on the Apache httpd side, and also uses an explicit listener name.

        Show
        Ian Evans added a comment - - edited Also, step 6 assumes that the user is using a glassfish-jk.properties file in their domain, and not a workers.properties file with Apache httpd: set server-config.network-config.network-listeners.network-listener.\ jk-connector.jk-configuration-file=domain-dir/config/glassfish-jk.properties This command is unnecessary if you're configuring mod_jk on the Apache httpd side, and also uses an explicit listener name.
        Paul Davies made changes -
        Field Original Value New Value
        Assignee Paul Davies [ pauldavies ] Mike Fitch [ oncered ]
        Fix Version/s 4.0 [ 10970 ]
        Hide
        Paul Davies added a comment -

        The target of the link in the description is the documentation for release 3.1. The corresponding section (To Enable mod_jk) in the documentation for release 3.1.2 has been updated and seems to address the duplication of the instruction to create a network listener in Step 5 and Step 6.

        Show
        Paul Davies added a comment - The target of the link in the description is the documentation for release 3.1 . The corresponding section ( To Enable mod_jk ) in the documentation for release 3.1.2 has been updated and seems to address the duplication of the instruction to create a network listener in Step 5 and Step 6.
        Hide
        Ian Evans added a comment -

        Paul, if you do a Google search for "glassfish mod_jk" you get the 3.1 doc as the very first link, with the title of "Administering mod_jk - Oracle GlassFish Server 3.1 Administration ...". I dug through the search results, and the 3.1.2 page (with the corrected info) is on page 4, with the far less useful title of "Administering Web Applications" (the chapter title, not the section). Links to older versions of the same section for GlassFish 3.0.1 and 2.1.1 appear on page 3 of the results. In between are a lot of blog entries, forum posts, and answer web site entries, all of them with more enticing titles than "Administering Web Applications".

        In other words, the latest documentation is not only far down on the list, but maybe the least likely link to be clicked out of all of them. Perhaps this is something that should be addressed by the tools and web teams.

        Show
        Ian Evans added a comment - Paul, if you do a Google search for "glassfish mod_jk" you get the 3.1 doc as the very first link, with the title of "Administering mod_jk - Oracle GlassFish Server 3.1 Administration ...". I dug through the search results, and the 3.1.2 page (with the corrected info) is on page 4, with the far less useful title of "Administering Web Applications" (the chapter title, not the section). Links to older versions of the same section for GlassFish 3.0.1 and 2.1.1 appear on page 3 of the results. In between are a lot of blog entries, forum posts, and answer web site entries, all of them with more enticing titles than "Administering Web Applications". In other words, the latest documentation is not only far down on the list, but maybe the least likely link to be clicked out of all of them. Perhaps this is something that should be addressed by the tools and web teams.
        Paul Davies made changes -
        Fix Version/s 4.0.1 [ 16061 ]
        Fix Version/s 4.0 [ 10970 ]
        Paul Davies made changes -
        Summary GlassFish Server 3.1 Administration Guide has incorrect steps for mod_jk [UB]GlassFish Server 3.1 Administration Guide has incorrect steps for mod_jk
        Romain Grécourt made changes -
        Fix Version/s 4.1 [ 16387 ]
        Fix Version/s 4.0.1 [ 16061 ]

          People

          • Assignee:
            Mike Fitch
            Reporter:
            Ian Evans
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: