Hi Wouter,
You have to follow the below steps , to see port 8009 being used
after you configure mod_jk:
In Step 4 : in the below blog:
http://weblogs.java.net/blog/amyroh/archive/2009/06/running_glassfi.html
After you install GFV3 and start domain1, you have to :
1) deploy a webapp to start the webcontainer.
2) |asadmin create-http-listener --listenerport 8009 --listeneraddress
0.0.0.0 --defaultvs server my-connector
3)asadmin set
configs.config.server-config.network-config.network-listeners.network-listener.jk-connector.jk-enabled=true
4) stop domain1
5) start domain1
Now if you issue URL : Ex:
http://hostname:80 will be forwarded to GF.
You can see that port 8009 being used when you do netstat.
Thank you
Shaline.
|
+ /export/hudson/workspace/quicklook-on-mod_jk-config/jdk/jdk1.6.0_14/label/jws-cust-280-3.sfbay.sun.com/glassfish-v3-image/glassfishv3/glassfish/bin/asadmin start-domain domain1
Waiting for DAS to start.
--
Wouter van Reeven wrote:
> Hi,
>
>
> Today I found this web log article
>
> http://weblogs.java.net/blog/amyroh/archive/2009/06/running_glassfi.html
>
> about running Apache2 and GlassFish v3 and using mod_jk to manage the
> communication between Apache and GF. I followed the steps in the article
> and found that no port 8009 is used when I execute the commands
>
> asadmin create-http-listener --listenerport 8009 --listeneraddress 0.0.0.0 --defaultvs server jk-connector
> asadmin set configs.config.server-config.network-config.network-listeners.network-listener.jk-connector.jk-enabled=true
>
> even when I make sure that the connector in the second command (jk-connector)
> is the same as in the first command (it is wrong in the article).
>
> However, I reinstalled GFv3 (build 57) and then omitted the second
> command. Now port 8009 is used as I can show with a netstat command. Is
> this the intended behaviour?
>
> Next steps are to test if I can run any application using port 80
> through Apache instead of using port 8080 and running it on GF directly.
>
>
> Wouter
>
>