From: <forums_at_java.net>
Date: Wed, 20 Apr 2011 00:23:50 -0500 (CDT)
*According from my system environment in
(http://www.java.net/forum/topic/glassfish/glassfish/cluster-can-not-handle-session-please-help)
I have 3 Physical Machine*
*1> server hostname is 'linuxgf175'(192.168.1.175) main cluster control (DAS)
and Install iPlanet Webserver with gflb-configurator
2> server hostname is 'linuxgf170'(192.168.1.170) server for node1(n1) has
Instance1 (i1)
3> server hostname is 'linuxgf180'(192.168.1.180) server for node2(n2) has
Instance2 (i2)*
*1. I was install iPlanet Web Server to same DAS machine. (192.168.1.175)
2. And create Server Certificates request. *
Certificate Details
Nickname cert-linuxgf175
Subject CN=linuxgf175
Issuer Self Signed
Key Type RSA
Key Size (bits) 1024
Valid From April 18, 2011 7:30:09 PM ICT
Valid Till April 18, 2012 7:30:09 PM ICT
Fingerprint CE:D8:5E:97:DB:56:89:00:56:A7:0F:EB:0D:D4:4A:06
Serial Number 00:94:26:11:AB
Server Name linuxgf175
(Picture :
http://s138.photobucket.com/albums/q262/madoatz/?action=view¤t=iPlanet_1.png
)
*3. And create new http-listenser (SSL for communicate with DAS port 8082 )*
(Picture :
http://s138.photobucket.com/albums/q262/madoatz/?action=view¤t=iPl...
[1] )
4. And import cert file(s1as.rfc) to glassfish-lbconfigurator wizard. (run
lb-configure command #java -jar glassfish-lbconfigulator.jar )
I was exported that file like this command :
/ keytool -export -rfc -alias s1as -keystore
/usr/glassfish3/glassfish/domains/domain1/config/keystore.jks -file
./s1as.rfc/
5*. Create and Apply http-lb to DAS domain success !! :)*
/asadmin> create-http-lb --devicehost linuxgf175 --deviceport 8082 --target
c1 cluster_lb
Enter admin user name> admin
Enter admin password for user "admin">
Command create-http-lb executed successfully.
asadmin>
asadmin> apply-http-lb-changes cluster_lb
Enter admin user name> admin
Enter admin password for user "admin">
Command apply-http-lb-changes executed successfully./
*7.try to open application , use browser open to iPlanet webserver *
http://192.168.1.175:80/ [2] (It's success display iPlanet Home screen )
(Picture :
http://s138.photobucket.com/albums/q262/madoatz/?action=view¤t=iPlanet_4.png
)
*8.try to open to "clusterjsp" application . t's failed. why It's can not to
route to both instance on both node ? (include context path /clusterjsp )*
http://192.168.1.175:80/clusterjsp [3]
(Picture :
http://s138.photobucket.com/albums/q262/madoatz/?action=view¤t=iPlanet_5_error.png
)
9.*iPlanet Startup log
*/Oracle iPlanet Web Server 7.0.9 B07/04/2010 01:31
info: reports: Initializing lbplugin BuildId: GlassFish 3.1 load-balancer
plugi n b05
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.6.0_20] from
[Sun M icrosystems Inc.]
config: , name-trans-passthrough reports: init-passthrough has not been
called
config: , name-trans-passthrough reports: init-passthrough has not been
called
config: , name-trans-passthrough reports: init-passthrough has not been
called
warning: reports: lb.router: XML_VALIDATOR_WARNING: No web modules configured
f or cluster c1. For Load Balancing to be performed on the cluster, at least
one w eb module needs to be configured.
warning: reports: lb.configurator: XML_VALIDATOR_WARNING: Cookies will not be
r ewritten by web server. All cookie updates will be handled by application
server . If you are using older version of application server, then failover
will not w ork.
warning: reports: lb.configurator: Preferred failover instance feature is
enabl ed.
warning: reports: lb.runtime: RNTM2019: Daemon //http://linuxgf170:28082/
[4]/ has been intialized.
warning: reports: lb.runtime: RNTM2019: Daemon //https://linuxgf170:28183/
[5]/ has bee n intialized.
warning: reports: lb.runtime: RNTM2019: Daemon //http://linuxgf170:24850/
[6]/ has been intialized.
warning: reports: lb.runtime: RNTM2019: Daemon //http://linuxgf180:28082/
[7]/ has been intialized.
warning: reports: lb.runtime: RNTM2019: Daemon //https://linuxgf180:28183/
[8]/ has bee n intialized.
warning: reports: lb.runtime: RNTM2019: Daemon //http://linuxgf180:24850/
[9]/ has been intialized.
info: HTTP3072: http-listener-1: //http://linuxgf175:80/ [10]/ ready to
accept requests
info: HTTP3072: http-listener-2: //https://linuxgf175:8082/ [11]/ ready to
accept request s
info: CORE3274: successful server startup/
