Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Finally figured out what was the problem with help from the GlassFish open-source forum (summarized below for others to reference). In the original posting above, I used:</p> <p>Problem #1 (broken AJP connection between mod_jk and GlassFish, original posted problem)</p> <pre><code># ./asadmin asadmin&gt; asadmin start-domain --port 4850 asadmin&gt; deploy /path/to/file/hello.war --port 4850 asadmin&gt; create-http-listener --listenerport 8009 --listeneraddress 0.0.0.0 --defaultvs server gf_listener --port 4850 asadmin&gt; create-network-listener --protocol http-listener-1 --listenerport 8009 --jkenabled true jk-connector --port 4850 asadmin&gt; set server-config.network-config.network-listeners.network-listener.jk-connector.jk-configuration-file=/home/glassfish/glassfish3/glassfish/domains/domain1/config/glassfish-jk.properties --port 4850 asadmin&gt; restart-domain --port 4850 </code></pre> <p>This came from the Administrator's Guide. While the HTML file is correct <a href="http://docs.oracle.com/cd/E18930_01/html/821-2416/gfaad.html" rel="nofollow">here</a> (http://docs.oracle.com/cd/E18930_01/html/821-2416/gfaad.html), if you select PDF and go to page 151, step 5 uses a variable called <em>listener-name</em>. However, this <em>listener-name</em> must agree with the use of jk-connector in step 6. Thus either <em>listener-name</em> must be jk-connector in step 5, or jk-connector in step 6 must be <em>listener-name</em> in step 5. In my case (see original posting code above), I set <em>listener-name</em> to gf_listener in step 5 and used jk-connector in step 6. This created the situation where two listeners were listening on the same port, which isn't allowed. A better solution is to simply avoid issuing the create-http-server command, which is deprecated and shown only for backward compatibility (although not documented as such).</p> <p>Problem #2 (SEVERE errors noted above)</p> <p>The other problem is that the worker properties must go into the file ~/apache/conf/worker.properties, and all connector attributes (e.g. and NO worker properties) go into the domain-dir/conf/glassfish-jk.properties file. This is confusing because the PDF document above page 153 example 6-7 explicitly states <code>This example shows a workers.properties or glassfish-jk.properties file that is set for load balancing...</code> where they show setting worker properties in the glassfish-jk.properties file. This is wrong (given the directory structure and commands used above in the same document). </p> <p>Problem #3 (WARNING noted above for thread pool)</p> <p>I eliminated the WARNING for threadpool.max_threads_too_low because I had mistakenly increased the Default configuration rather than the Server configuration's settings in the web console (after I increased the server configuration's settings the warning went away). Increasing this value can be done at the command line or even easier using the web admin console (Configuration > server-config > thread pools). The command line way is: </p> <pre><code>configs.config.server-config.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=200 </code></pre> <p>for 200 threads (example).</p> <p>Solution:</p> <p>Here's my final and complete bring-up for GlassFish:</p> <pre><code>asadmin&gt; start-domain asadmin&gt; deploy /home/glassfish/apps/hello.war asadmin&gt; create-network-listener --protocol http-listener-1 --listenerport 8009 --jkenabled true jk-connector asadmin&gt; set server-config.network-config.network-listeners.network-listener.jk-connector.jk-configuration-file=/home/glassfish/glassfish3/glassfish/domains/domain1/config/glassfish-jk.properties asadmin&gt; restart-domain </code></pre> <p>Note: there's no create-jvm-options setting (as found in admin guide PDF above, step 7) since this relates to http-listener which is not used here anymore.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload