[GLASSFISH-14541] support text only install of glassfish-lbconfigurator plugin Created: 09/Nov/10  Updated: 13/Dec/10

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Pavel Bucek Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 14,541

 Description   

lb configurator can be installed only by using GUI; it should be possible to
install it by using text interface only (servers usually don't have
installed/running X server).






[GLASSFISH-13301] DEBUG messages for Preferred failover instance is not seen Created: 07/Sep/10  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: jothir Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 13,301
Tags: 3_1-exclude

 Description   

Tested failover with Preferred failover instance feature on LB.

DEBUG messages from lbrouter CANNOT be seen even after setting webserver's log
level to FINE.

The messages can be seen only after adding LogVerbose On to
<webserver-instance>/config/magnus.conf



 Comments   
Comment by kshitiz_saxena [ 06/Oct/10 ]

Setting target milestone as 3.1_ms07

Comment by kshitiz_saxena [ 15/Nov/10 ]

The best option is to use log-level set in server.xml. However to make required
changes, new dependencies are introduced. These new dependencies are causing
issue, and load-balancer plugin is not loaded in web server 7.0.9.

This will require load-balancer plugin to be build against web server 7.0.9
instead of web server 6.1. Cannot be fixed now. This issue will be fixed in
later release.

Comment by Nazrul [ 18/Nov/10 ]

Excluding from 3.1 query

Comment by Tom Mueller [ 07/Feb/13 ]

Moving to 4.0.1 since this issue does not need to be fixed for the Java EE 7 RI/SDK release.





[GLASSFISH-8367] mod_loadbalancer does not work with Sun GlassFish Web Stack Created: 15/May/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: v2.1.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: usabada Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 8,367

 Description   

mod_loadbalancer does not work with Sun GlassFish Web Stack 1.4/1.5. There are 2
issues
1. mod_loadbalancer needs to be compiler specifically for Sun GlassFish Web
Stack since the compile options are different
2. mod_loadbalancer depends on libsasl.so that is not available in web stack
supported RHEL 5 platform



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-15651] Unable to install lb-plugin using lbconfigurator on Windows 2008 & iWS 7. Created: 21/Jan/11  Updated: 21/Oct/11

Status: Reopened
Project: glassfish
Component/s: load_balancer
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2008, iWS 7 web server.


Tags: 3_1, 3_1-exclude, 3_1-next, 3_1_1-scrubbed, 3_1_2-exclude, glassfish

 Description   

LB configurator fails with this exception on the next screen after collecting web server information.

$ java -jar glassfish-lbconfigurator-3_1-b04.jar
Condition already registered.
Condition already registered.
Condition already registered.
Condition already registered.
Condition already registered.
Condition already registered.
Condition already registered.
java.io.FileNotFoundException: C:\Program Files (x86)\LBPlugin\Uninstaller\unins
taller.jar (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
at com.izforge.izpack.installer.UnpackerBase.putUninstaller(Unknown Sour
ce)
at com.izforge.izpack.installer.Unpacker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)

I checked and the specified file does not exist. But I guess the installer should create it.

C:\Program Files (x86)>dir
Volume in drive C has no label.
Volume Serial Number is F46D-A90A

Directory of C:\Program Files (x86)

01/21/2011 11:07 AM <DIR> .
01/21/2011 11:07 AM <DIR> ..
01/21/2011 11:08 AM <DIR> Common Files
01/11/2011 10:12 PM <DIR> Internet Explorer
01/21/2011 11:07 AM <DIR> Java
01/12/2011 08:53 AM <DIR> Mozilla Firefox
01/12/2011 08:48 AM <DIR> Symantec AntiVirus
01/12/2011 03:15 AM <DIR> Windows Mail
07/13/2009 09:37 PM <DIR> Windows NT
0 File(s) 0 bytes
9 Dir(s) 87,917,252,608 bytes free



 Comments   
Comment by Homer Yau [ 04/Feb/11 ]

We may need to release note that the user who install load-balancer Configurator need to have full system installation right. "Administrator" usually should have the right to create directory in the restricted path.

Comment by Scott Fordin [ 03/Mar/11 ]

Instructions added to HA Admin Guide.

Comment by Scott Fordin [ 24/Mar/11 ]

Information was added to HA Admin Guide, but as this was not a doc issue, I should not have closed it.

Comment by Nazrul [ 09/May/11 ]

Windows 2008 is useful to support.

Comment by scatari [ 10/Jun/11 ]

Fix already documented and it is well known that most installations on Windows require Admin privileges.

Comment by kshitiz_saxena [ 08/Jul/11 ]

Changing priority to Major





[GLASSFISH-17804] The LB Configurator needs to provide correct error message for unsupported version of web server Created: 23/Nov/11  Updated: 03/Jan/12

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: varunrupela Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 312_qa, 3_1_2-exclude

 Description   

LB plugin on Linux is only supported on a 64-bit webservers. Currently LB plugin gets installed without errors on 32-bit webserver but then the webserver fails to launch the LB Plugin.

It will help to have the LB Configurator abort installation with an appropriate message when LB is being installed on an unsupported webserver.



 Comments   
Comment by varunrupela [ 20/Dec/11 ]

Will update version to GF 3.1.2 as it also affects 3.1.2

Comment by kshitiz_saxena [ 03/Jan/12 ]

Will not be fixed for 3.1.2





[GLASSFISH-17490] Deleting a cluster which is target of LB still leaves this cluster name in domain.xml Created: 25/Oct/11  Updated: 14/Nov/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1.1_b05
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Anissa Lam Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-17474 HTTP Status 500 Error when trying to ... Closed
Tags: 3_1_2-exclude

 Description   

This is related to an issue filed against admin console, GLASSFISH-17474.
Currently, as of 3.1.2 build 06, user is allowed to delete a cluster that is referenced by lb-config.
After the deletion, lb-config still reference this cluster.

<lb-configs>
<lb-config name="TEST-LB_LB_CONFIG">
<cluster-ref ref="clusterABC">
<health-checker url="/"></health-checker>
</cluster-ref>
</lb-config>
</lb-configs>
<clusters></clusters>

I think this should be fixed, that this cluster-ref should be removed if the cluster is deleted.

If user is NOT allowed to delete a cluster that is ref. by lb-config, then there should be enforcement.

The code to remove the cluster-ref from lb-config after the cluster is deleted, or prevent user from deleting the cluster should be in the backend instead of the GUI, since user can use other client to perform this operation.



 Comments   
Comment by kshitiz_saxena [ 14/Nov/11 ]

The creation of load-balancer and its association with cluster is manual. There is no existing support for automatic detection of cluster change including its deletion.

Apart from that currently there is no constraint that cluster being referenced by load-balancer config cannot be deleted.

This issue will be fixed when auto cluster change detection is implemented in load-balancer.

For now, I am marking this issue as 3_1_2-exclude.





[GLASSFISH-17479] Device Host value shouldn't accept other than hostname & IP address in LB Config Created: 25/Oct/11  Updated: 14/Nov/11

Status: In Progress
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1.2_b06
Fix Version/s: None

Type: Bug Priority: Major
Reporter: arunkumar_s Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_2-exclude

 Description   

Steps:
1) Login to Glassfish Admin GUI
2) Click HTTP Load Balancers in Tree view (in left pane)
3) Click New button and enter all fields with device host as 200 (number)
4) Click OK button

Issue --> Device Host value shouldn't accept other than hostname & IP address for LB creation



 Comments   
Comment by Anissa Lam [ 25/Oct/11 ]

This kind of validation should be enforced by the backend, as user can do the same thing using other client.
Transferring to backend.





Application specific configuration for load-balancer service (GLASSFISH-17609)

[GLASSFISH-17610] Only proxy users request for deployed applications Created: 03/Nov/11  Updated: 07/Nov/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 4.0
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: kshitiz_saxena Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Bring in logic to proxy requests to back-end application server only for deployed applications. The request for other applications will be rejected at load-balancer itself. This may require application url configuration at virtual server level.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate component that will be impacted by this task.





[GLASSFISH-17345] LB doesn't work after stopping and starting cluster Created: 26/Sep/11  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: admin
Affects Version/s: 4.0
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: carlavmott Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MacOS


Attachments: File SimpleSessionDemo.war    
Tags: 3_1_x-exclude

 Description   

running in native mode with load balancer setup and deploy a web application. Web page comes up as expected. stop and then start the cluster and go to the web page and I get a 404.



 Comments   
Comment by Mahesh Kannan [ 26/Sep/11 ]

We have seen this behavior in native mode.

Steps to reproduce:

1. asadmin start-domain
2. deploy the attached SimpleSessionDemo.war
3. Access the app from browser (localhost:50080/SimpleSessionDemo/DemoServlet)
(The above works)
4. asadmin stop-cluster SimpleSessionDemo
5. asadmin start-cluster SimpleSessionDemo
6. Now try to access localhost:50080/SimpleSessionDemo/DemoServlet. THIS FAILS

Comment by prasads [ 18/Feb/13 ]

Moving this to 4.0.1 since the LB support is not available in 4.0





[GLASSFISH-19129] Sun java System webserver-7, not equally distributing requests among glassfish-V-9.1_02 (build b04-fcs) jvms Created: 05/Oct/12  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: v2.1, 4.0_b04
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: tejas.pathak Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day
Environment:

Linux / Rhel-5 Operating system 64-bit



 Description   

We have a RHEL-5 server running Glassfish (Version-Sun Java System Application Server 9.1_02 (build b04-fcs)) and webserver- (Sun Java System Web Server 7.0U8 B01/20/2010 (32-bit)). This webserver instance is loadbalancing requests among 4-jvm glassfish cluster using default "round-robin" policy with each jvm instance having equal weight. Plugin Version used for this configuration is aslb-9.1.1-b13.jar.

We are facing issue wherein the load is not equally distributed between 4-jvms, only 2-jvms are participating in handling the requests.



 Comments   
Comment by shreedhar_ganapathy [ 13/Dec/12 ]

-> Kshitiz
To triage the bug for 4.0 release or to close it if its no longer an issue.

Comment by prasads [ 18/Feb/13 ]

Moving this issue to 4.0.1 since the LB support is not available in 4.0





[GLASSFISH-16782] status not available for http load balancers Created: 02/Jun/11  Updated: 21/Oct/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: srinik76 Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16763 Porting Load Balancer Console Pages f... Closed
Tags: 3_1-next, 3_1_, 3_1_1-exclude, 3_1_1-next, 3_1_1-scrubbed, 3_1_2-exclude

 Description   

In v2.1.1, while listing http load balancers table contains data (name,target,status)

status is found with the following code

LoadBalancer lb = AMXUtil.getDomainRoot().getLoadBalancerMap().get(key);
if( lb != null)

{ status = GuiUtil.getMessage(lb.isApplyChangeRequired()? "loadBalancer.needApply" : "loadBalancer.upToDate"); }

In v3, to find status what is the call for lb.isApplyChangeRequired(). If back end call is there, we need to create rest api conversion for this.



 Comments   
Comment by srinik76 [ 06/Jun/11 ]

Fix required for 3.1.1

Comment by kshitiz_saxena [ 07/Jun/11 ]

This issue requires some support implementation to detect changes in the load-balancer xml. This implementation must detect changes to cluster, instance, application, loadbalancer config etc. There is significant amount of work involved to achieve it, and cannot be fixed within timeline for 3.1.1. This issue will be taken up post 3.1.1.

In GUI we can remove column showing apply-changes status. It is already documented that auto-detection of load-balancer xml does not exist in 3.1 and will continue in 3.1.1 as well.





[GLASSFISH-16616] ReadMe.UserDefinedLB needs an update for 64-bit compilation and correct gcc. This doc should perhaps be moved to GF user guides. Created: 12/May/11  Updated: 24/Jan/12

Status: Reopened
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris Sparc 10 + Apache2.2 64 bit + glassfish lb plugin 3.1.1


Issue Links:
Dependency
depends on GLASSFISH-17106 [UB]Add userdefined library informati... In Progress
Tags: 3_1_1-scrubbed, 3_1_2-exclude

 Description   

I compiled roundrobin.so file for the user-defined testsand generated the .so file with -m64 flag in gcc command and still the library could not be read.

Setup is on aroot@sf-171s-163.india.sun.com:/export/ha/64-bit/apache2.2



 Comments   
Comment by kshitiz_saxena [ 17/May/11 ]

This issue is not reproducible. I compiled roundrobin.c with below command and it works fine :
gcc -m64 -shared -fPIC -I glassfish-lbplugin/lib/install/templates roundrobin.c -o roundrobin.so

Comment by varunrupela [ 01/Jul/11 ]

Apache/LB is unable to load the user-defined policy file - roundrobin.so after it is correctly compiled with the above instructions.

The following messages appear in apache error log:
"FGRP1009: Error in loading the library /space/gf-ha/dft/controller-repository/glassfish-samples/roundrobin.so, check the library is present and has proper permissions"

******
[Fri Jul 01 15:57:35 2011] [info] LBInstance created on virtual server 10.12.171.163 ...
[Fri Jul 01 15:57:35 2011] [info] is_virtual = 1 defn_name = /export/ha/64-bit/apache2.2/conf/extra/httpd-vhosts.conf ...
[Fri Jul 01 15:57:35 2011] [warn] lb.configurator: XML_VALIDATOR_WARNING: Cookies will not be rewritten 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 work.
[Fri Jul 01 15:57:35 2011] [warn] lb.configurator: Preferred failover instance feature is enabled.
[Fri Jul 01 15:57:35 2011] [crit] lb.failovermanager: FGRP1009: Error in loading the library /space/gf-ha/dft/controller-repository/glassfish-samples/roundrobin.so, check the library is present and has proper permissions
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon http://sf-171s-163.india.sun.com:28080 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon https://sf-171s-163.india.sun.com:28181 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon http://sf-171s-163.india.sun.com:28081 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon https://sf-171s-163.india.sun.com:28182 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon http://sf-171s-163.india.sun.com:28082 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon https://sf-171s-163.india.sun.com:28183 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon http://sf-171s-163.india.sun.com:28083 has been intialized.
[Fri Jul 01 15:57:35 2011] [warn] lb.runtime: RNTM2019: Daemon https://sf-171s-163.india.sun.com:28184 has been intialized.
[Fri Jul 01 15:57:35 2011] [notice] lb.runtime: RNTM2003:After LBDaemonManager::init()
[Fri Jul 01 15:57:35 2011] [info] This virtual server already exists in map; Hence just retrieving the pointer to LBInstance...
[Fri Jul 01 15:57:36 2011] [info] This virtual server already exists in map; Hence just retrieving the pointer to LBInstance...
[Fri Jul 01 15:57:36 2011] [error] [client 129.146.11.110] File does not exist: /export/ha/64-bit/apache2.2/htdocs/favicon.ico
[Fri Jul 01 16:03:44 2011] [info] This virtual server already exists in map; Hence just retrieving the pointer to LBInstance...
[Fri Jul 01 16:03:44 2011] [error] [client 129.146.11.110] File does not exist: /export/ha/64-bit/apache2.2/htdocs/favicon.ico
********

Comment by kshitiz_saxena [ 01/Jul/11 ]

It works with library created using given command :

gcc -m64 -shared -fPIC -I glassfish-lbplugin/lib/install/templates roundrobin.c -o roundrobin.so

OR

cc -m64 -G -xcode=pic32 -I glassfish-lbplugin/lib/install/templates roundrobin.c -o roundrobin.so

Issue was with version of gcc used. It works when compiled with following gcc :
sparc-sun-solaris2.10-gcc (GCC) 4.0.4 (gccfss)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

However it fails when compiled with following gcc :
gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

It is better to use sun studio compiler on solaris.

Docs need to be updated to reflect the same.

As of now instructions to compile of user defined library is bundled as ReadMe.UserDefinedLB along with GlassFish load-balancer plugin, making it difficult to be updated frequently. It can be probably added to GlassFish load-balancer documentation itself.

Comment by varunrupela [ 01/Jul/11 ]

Kshitiz figured out that the gcc we needed to use was sparc-sun-solaris2.10-gcc and it was available from /usr/bin/gcc. We were earlier using gcc from "/usr/sfw/bin/gcc". This issue now becomes one of updating the ReadMe for user-defined.

  • We found that the ReadMe.UserDefinedLB available under glassfish-lbplugin/lib/install/templates location also needs an update for 64 bit compilation.
Comment by varunrupela [ 01/Jul/11 ]

Updated the summary to reflect findings.

Comment by kshitiz_saxena [ 26/Jul/11 ]

Readme is actually bundled with load-balancer plugin. So to update it, a new load-balancer plugin library need to be generated. It is not possible to generate and integrate new load-balancer plugin library now.

It will be better to add this readme to documentation itself as it is easy to update and maintain it there. I will create a new documentation bug to track it.

Comment by kshitiz_saxena [ 26/Jul/11 ]

Marking this issue as being dependent on GLASSFISH-17106

Comment by Joe Di Pol [ 24/Jan/12 ]

Scrubbing from the 3.1.2 list assuming docs is fixing 17106 (which is on the 3.1.2 list)





[GLASSFISH-16373] Log messages from loadbalancer plugin not the same for different webservers Created: 18/Apr/11  Updated: 21/Oct/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-next, 3_1_1-scrubbed, 3_1_2-exclude

 Description   

The log messages coming from loadbalancer plugin is not the same across different webservers : Oracle Iplanet Webserver, Apache2.2 and IIS7.5

i) Retry of Idempotent URL - When servlet response times out - "timed out waiting for response" message is not appearing in Apache and IIS.

ii) Custom Error Page - When the custom error page is missing - "lb.runtime: RNTM3007: Invalid / Missing custom error-url / page: error.html for web-module: infiniteCustomErrorHtml." message is not appearing in Apache.

iii) Auto apply lb changes - When lb xml is deleted - "Error occured while initializing Loadbalancer config Parser" message is not appearing in Apache.






[GLASSFISH-21067] ClassCastException: org.glassfish.web.ha.session.management.ReplicationWebEventPersistentManager cannot be cast to org.apache.catalina.session.StandardManager Created: 18/May/14  Updated: 18/May/14

Status: Open
Project: glassfish
Component/s: load_balancer, web_container
Affects Version/s: 4.1_b05
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Eng.Fouad Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I have a cluster with 2 instances. When I deploy a web module on the cluster level and enable the option "Availability", the following exception occurs:

java.lang.Exception: java.lang.ClassCastException: org.glassfish.web.ha.session.management.ReplicationWebEventPersistentManager cannot be cast to org.apache.catalina.session.StandardManager
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:168)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:122)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:291)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:352)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:500)
at com.sun.enterprise.v3.server.ApplicationLifecycle.enable(ApplicationLifecycle.java:2169)
at com.sun.enterprise.v3.server.ApplicationLifecycle.enable(ApplicationLifecycle.java:113)
at com.sun.enterprise.v3.server.ApplicationConfigListener.enableApplication(ApplicationConfigListener.java:272)
at com.sun.enterprise.v3.server.ApplicationConfigListener.handleOtherAppConfigChanges(ApplicationConfigListener.java:223)
at com.sun.enterprise.v3.server.ApplicationConfigListener.transactionCommited(ApplicationConfigListener.java:170)
at org.jvnet.hk2.config.Transactions$TransactionListenerJob.process(Transactions.java:365)
at org.jvnet.hk2.config.Transactions$TransactionListenerJob.process(Transactions.java:356)
at org.jvnet.hk2.config.Transactions$ListenerNotifier$1.call(Transactions.java:213)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at org.jvnet.hk2.config.Transactions$Notifier$1$1.run(Transactions.java:167)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

It seems that the webapp cannot be started because of this line (com.sun.enterprise.web.WebModule:1752):

StandardManager manager = (StandardManager) getManager();

http://grepcode.com/file/maven.java.net/content/groups/promoted/org.glassfish.main.web/web-glue/4.0.1-b01/com/sun/enterprise/web/WebModule.java#WebModule.loadSessions%28java.util.Properties%29

`getManager()` returns a reference of type `org.glassfish.web.ha.session.management.ReplicationWebEventPersistentManager`, whereas it doesn't inherit from `org.apache.catalina.session.StandardManager`.






[GLASSFISH-6835] Load Balanced EJB Web Service Created: 24/Nov/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: vpower Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 6,835

 Description   

Environment - I'm using JDK 6u10 with GlassFish ESB (20081003).
Sun Web Server 7.0u3, and aslb-9.1-u2-b1

Background - When I deploy any WAR (or EAR) with a servlet based web
service, GlassFish will update the HTTP Load Balancer with its information.
When I deploy an EJB based web service the configuration of the HTTP Load
Balancer is not updated to reflect the new object.

Work around - If I manually update the loadbalancer.xml that the web
server is using to include a new web-module with the appropriate URI it
will work, but manually updating all the different copies of the
loadbalancer.xml I have is not an easy task.



 Comments   
Comment by harpreet [ 01/Dec/08 ]

Pankaj - can you see if this is critical for v2.1 release. I do not see it as such.

Comment by harpreet [ 01/Dec/08 ]

Pankaj has got back indicating that this is a place holder for a subsequent release. Removing 911ToScrub
tag.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kshitiz_saxena [ 02/Feb/09 ]

Assigning this issue to myself.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4517] Glassfish Connection pool issue Created: 27/Mar/08  Updated: 25/Jan/11

Status: Open
Project: glassfish
Component/s: admin
Affects Version/s: v2.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: md7777 Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,517

 Description   

Problem Description : Glassfish -Sun Java System Application Server 9.1
(build
b58g-fcs) monitoring statistics does not report the reclaimed leaked
connections.

Issues :

1.Monitoring statistic does not show reclaimed leaked connection.
2.How to find out if the leaked connections are reclaimed and put back
in to
the connection Pool ?
3.Connection Instances are created from the reclaimed or released
connections
back into Pool and ConnectionPoolDataSOurce cannot be used directly and
makes
of no use if the connections are not released/reclaimed back to the
Pool as
there wo'nt be any connection instances and it will make physical
connections
if server is not set to resize and reclaim connections.

Monitoring Statistics : PoolCounters:
maxNumConnUsed = 15
minNumConnUsed = 0
currNumConnUsed = -44
maxNumConnFree = = 52
minNumConnFree = 0
currNumConnFree = 52
numConnCreated = 1592
numConnDestroyed = 1584
numConnFailedValidation = 0
numConnTimedOut = 0
numConnAcquired = 7502
numConnReleased = 7418
currConnectionRequestWait = 0
minConnectionRequestWait = 0
maxConnectionRequestWait = 1377
totalConnectionRequestWait = 36821
numConnSuccessfullyMatched = 0
numConnNotSuccessfullyMatched = 0
numPotentialConnLeak = 83



 Comments   
Comment by km [ 27/Mar/08 ]

Siraj, can you please take a look?

Comment by harpreet [ 04/Sep/08 ]

Marking target milestone as 9.1.1

Comment by sirajg [ 16/Sep/08 ]

There was some work done for Connection leak tracing in V2. Transferring to
Kshitiz for comments.

Comment by kshitiz_saxena [ 17/Sep/08 ]

If connection-leak-reclaim attribute is set to true, then numPotentialConnLeak
is equal to number of connection reclaimed. There are no separate statistics for
it as both values are same. I hope this answers point 1.

Point 2 : If you want to see it working, create a pool of max-pool-size=1. Then
create connection, and hold it till it is reclaimed. Now you can again create a
new connection. Even though max-pool-size is 1, client will be provided with
reclaimed connection.

Regarding point 3, I am not sure whether I got it correctly. However if your
question is whether released/reclaimed resources are put back in pool, then
answer is yes. All released/reclaimed resources are put back in pool and
available for other clients.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 25/Jan/11 ]

Cleared the Fix version since this issue isn't going to be fixed in 9.1.1.





[GLASSFISH-7171] Load Balancer Plugin does not work on Open Solaris 2008/11 Created: 11/Feb/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: arungupta Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,171
Status Whiteboard:

v3_exclude, v2.1.1_exclude


 Description   
  • Open Solaris 2008/11
  • Sun Web Server 6.1 (whatever the latest patch is)
  • GF v2.1
  • LB plugin from EE bits

Starting up the Web server gives the following error:

– cut here –
arun@opensolaris:/usr/SUNWwbsvr/https-opensolaris# ./start
Sun ONE Web Server 6.1SP5 B08/18/2005 00:48
info: reports: Initializing lbplugin BuildId: A701212-164111
catastrophe: CORE3260: Server crash detected (signal SIGSEGV)
info: CORE3261: Crash occurred in NSAPI SAF load-modules
– cut here –



 Comments   
Comment by kumara [ 14/Sep/09 ]

LB plugin not being shipped with v3, does not apply to v3 release and hence excluded from bug tracking.

Comment by Ed Bratt [ 15/Oct/09 ]

Will not fix in v2.1.1

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16128] Incorrect information given during loadbalancer plugin installation Created: 02/Mar/11  Updated: 02/Mar/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: ramapulavarthi Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

While installing the loadbalancer pluging on Iplanet Web Server, It printed the following on the installer screen.
Notice it says "For the Load Balancing Plugin to work, it needs access to a cluster configuration file in XML format, namely load-balancer.xml." But, the plugin accepts only accepts loadbalancer.xml not load-balancer.xml

--------------
Post-Installation Procedures for Oracle iPlanet Server

After installing the GlassFish Load Balancing Plugin on Oracle iPlanet Server, it may be necessary to update the Oracle iPlanet Server library path to include all dependent libraries. The Load Balancing Installer usually updates the Oracle iPlanet Server library path automatically. However, in some cases, additional manual changes may be required.
For the Load Balancing Plugin to work, it needs access to a cluster configuration file in XML format, namely load-balancer.xml. The load-balancer configuration can be created with the GlassFish asadmin command. After creating load-balancer configuration load-balancer xml can be brought to web server in either of two ways:
If web server is configured in SSL mode and DAS certificate is imported, then user can use push load-balancer xml to web server over the wire using asadmin command apply-http-lb-changes. Please ensure run-as user for web server has write permission in configuration directory.
If web server is not configured in SSL mode or DAS certificate is not imported, then user can manually export load-balancer xml using asadmin command export-http-lb-config. User need to manually copy load-balancer xml to web server configuration directory. Now user can restart the web server for load-balancer configuration to take effect.
For more details about this procedure, see Configuring Web Servers for HTTP Load Balancing in the Oracle GlassFish Server 2.1.1 High Availability Administration Guide.
---------------






[GLASSFISH-16090] during load-balancer configurator installation and configuration, it requires 8 char iWS Admin password Created: 23/Feb/11  Updated: 20/Apr/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1_b43
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Homer Yau Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

load-balancer configurator b05 iws 7.0.9


Tags: 3_1, glassfish, plugin, rel_notes_candidate

 Description   

during load-balancer configurator installation and configuration, it requires 8 char iWS Admin password.

The is a test scenario we face if iplanet webserver admin password is shorter than 8 character.

Workaround:
It is to use wadm to reset the admin password, restart the iws admin-server and then continue load-balancer configurator's installation.
reset web server admin password
cd <webserver_install_dir>/bin

  1. ./wadm reset-admin-password --user admin --host localhost --port 8989
    Please enter admin-password> <new_passsword>
    Please enter admin-password again> <new_password>


 Comments   
Comment by Homer Yau [ 23/Feb/11 ]

We need to accommodate/support for the user that have existing or new iPlanet Web Server that have admin password that have less than eight character in the future release.

Comment by Scott Fordin [ 20/Apr/11 ]

Added note to 3.1 HA Admin Guide.





[GLASSFISH-2795] The connections created are method local variables are maintained in bean context Created: 09/Apr/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: jdbc
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: kshitiz_saxena Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,795

 Description   

The connections created as local variables are maintained in bean context. So if
a connection is not closed, it is always maintained in bean context and is in
every transaction. The issue is actually of bad programming practices. However
we should be able to handle such mistakes.



 Comments   
Comment by gfbugbridge [ 09/Apr/07 ]

<BT6543922>

Comment by Mahesh Kannan [ 09/Apr/07 ]

Assigning this to jdbc category

Comment by kshitiz_saxena [ 12/Apr/07 ]

Not a show stopper

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-2595] Make com.sun.enterprise.connectors.work.WorkCoordinator implementation thread safe Created: 13/Mar/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: jca
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: kshitiz_saxena Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,595

 Description   

The com.sun.enterprise.connectors.work.WorkCoordinator code is not thread safe.
Need to rewrite object to make it thread safe.

Lloyd comments on code is as follows:

1. Please fix the risky use of using the same name for an instance variable as
a parameter ("waitMode"). This is an awful coding practice guaranteed to
confuse. The fact that "this.waitMode" is used in places doesn't remove the
risk of future errors. The simplest approach is to change the name of the
parameter.

2. workStats.submittedWorkCount++ and (maybe)
workStats.incrementWaitQueueLength() are not thread safe. Can more than one
thread call submitWork()?

3. Is WorkQueue 'queue' thread safe?

4. The object is very badly designed; it cannot be made thread safe as far as I
can tell:

a) what if two threads call submitWork() with different values for waitMode?
Then one will overwrite 'waitMode'.
b) setState() is synchronized, which is pointless...if two threads call
preInvoke(), then one overwrites the other. Ditto for postInvoke().



 Comments   
Comment by gfbugbridge [ 13/Mar/07 ]

<BT6533876>

Comment by kshitiz_saxena [ 20/Mar/07 ]

Declared variable waitMode volatile. This class need more fixes. All issues will
be fixed as part of bug fix 2595.

Comment by kshitiz_saxena [ 20/Mar/07 ]

Above comment is for other bug. This bug still need fixes.

Comment by kshitiz_saxena [ 12/Apr/07 ]

Not a show-stopper

Comment by Jagadish [ 18/Jan/10 ]

Evaluation of the issue for GlassFish V3/V3 UR1 :

< Lloyd comments on code is as follows:

< 1. Please fix the risky use of using the same name for an instance variable as
< a parameter ("waitMode"). This is an awful coding practice guaranteed to
< confuse. The fact that "this.waitMode" is used in places doesn't remove the
< risk of future errors. The simplest approach is to change the name of the
< parameter.
> This can be fixed in v3.

< 2. workStats.submittedWorkCount++
> New monitoring statistics calucation takes care of the issue
< and (maybe)
< workStats.incrementWaitQueueLength() are not thread safe.
> Not applicable w.r.t new monitoring stats implementation in v3

< Can more than one
< thread call submitWork()?

> No. There is one workCoordinator per work instance

< 3. Is WorkQueue 'queue' thread safe?
> WorkQueue implementation is provided by ORB. Yes, its implementation is thread
safe.

< 4. The object is very badly designed; it cannot be made thread safe as far as I
< can tell:

< a) what if two threads call submitWork() with different values for waitMode?
< Then one will overwrite 'waitMode'.
> No two threads will call it as there is one WorkCoordinator per Work instance.

< b) setState() is synchronized, which is pointless...if two threads call
< preInvoke(), then one overwrites the other.

> Two threads will not call pre-invoke() for the same work instance/ work
coordinator.

< Ditto for postInvoke().
> Above explanation applies for postInvoke()

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3047] thread safety: CommonWorkManager Created: 22/May/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: jca
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: llc Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS X
Platform: All


Issuezilla Id: 3,047

 Description   

com.sun.enterprise.connectors.work.CommonWorkManager:

  • variable 'wm' is not used.
  • various instance variables are not 'final'.
  • 'isMonitoringEnabled' is not thread safe
  • creation and access to variable 'workStats' is not thread safe.
  • ...etc...

WorkStats:

WorkStats has many mutable variables which are not thread safe [eg reset()]. Is it never the case that a
WorkStats could be seen by more than one thread? It seems not, since there are 'synchronized'
methods in the class. Better to design an immutable class.



 Comments   
Comment by gfbugbridge [ 22/May/07 ]

<BT6560927>

Comment by Sivakumar Thyagarajan [ 22/May/07 ]

requesting Kshitiz to investigate

Comment by kshitiz_saxena [ 29/May/07 ]

The class is not written to work in multi-thread environment. The variable are
mostly read operation, except for isMonitoringEnabled. This will not be modified
by multiple threads are same time.

Comment by llc [ 29/May/07 ]

"The class is not written to work in multi-thread environment".

That's rather hard to believe, given that it maintains a thread pool. Certainly, if it is indeed true, then
there ought to be very clear javadoc comments as to why it's OK.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-2121] thread-unsafe null-check idiom in com.sun.enterprise.resource.RecoveryResourceRegistry Created: 19/Jan/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: jca
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: llc Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,121

 Description   

Visibility and race condition problems:

public static RecoveryResourceRegistry getInstance() {
if (rrr == null)

{ rrr = new RecoveryResourceRegistry(); }

return rrr;
}



 Comments   
Comment by km [ 19/Jan/07 ]

Hmmm. Submitter should have checked where this class belongs.

Comment by binod [ 20/Jan/07 ]

The method is executed just once during the startup. It is meant only for single
threaded uses.

Comment by gfbugbridge [ 20/Jan/07 ]

<BT6515532>

Comment by gfbugbridge [ 05/Apr/07 ]

<BT6543318>

Comment by kshitiz_saxena [ 25/Apr/07 ]

Assigning it to myself

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16105] Need to add iWS installed bin path for LB configurator to reconize the certutil and wadm command Created: 25/Feb/11  Updated: 25/Feb/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1_b43
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Homer Yau Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2008 R2, GlassFish 3.1, iPlanet Web Server 7.0.9,


Tags: 3_1, glassfish, plugin, rel_notes_candidate

 Description   

If user do not setup the certutil.bat or wadm.bat in correct path in windows or other platforms, lb-configurator could not execute the command.

wadm.bat and certutil.bat command files are from webserver for helping lb-configurator to add the glassfish das certificate into truststore list in webserver instance as trusted certificate for admin easy of use purpose.

<webserver_install_dir>\bin\wadm.bat
<webserver_install_dir>\bin\certutil.bat

Load-balancer Configurator need these two files to complete the task.

Workaround is to execute the command manually after configurator completed install.

Workaround:

i.e.

C:\webserver7\bin\certutil -A -a -n s1as -t TC -i C:\
\glassfish3\glassfish\domains\domain1\config\s1as.rfc -d C:\ha\ws7\https-myinstance\config

<webserver_install_dir>\bin\certutil A -a -n s1as -t TC -i <glassfish_3.1_install_dir>\glassfish3\glassfish\domains\domain1\config\s1as.rfc -d <webserver_install_dir>\https<your_instance>\config

note:
s1as.rfc is the certificate exported from the GlassFish DAS.

Command to export GlassFish Domain Admin Server Certificate (GlassFish DAS certificate):
e.g.
<JAVA_HOME>\bin\keytool -export -rfc -alias s1as -keystore <GLASSFISH_INSTALL_DIR>\domains\<DOMAIN_NAME>\config\keystore.jks -file s1as.rfc






[GLASSFISH-16101] iws wadm command fail during LB configurator if the webserver "admin password" or "wspass" not exist. Created: 24/Feb/11  Updated: 24/Feb/11

Status: Open
Project: glassfish
Component/s: load_balancer
Affects Version/s: 3.1_b43
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Homer Yau Assignee: kshitiz_saxena
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

GlassFish build 43 OGS on OEL with iws7.0.9


Tags: 3_1, glassfish, plugin

 Description   

iWS wadm command fail during LB configurator if the webserver "admin password" or "wspass" not exist.

However, the installation on the load-balancer plugin binary is still completed and successfully lay down the binary files.

There is a workaround see below.

Error will be found in the end of the installation.

Error log:

INFO: Command /export/ha/ws7/bin/wadm execution failed. Please refer to logs for
more details.
Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Command executed : /export/ha/ws7/bin/wadm pull-config --user=admin --pass
word-file=/export/ha/ws7/https-jan-vm8/../glassfish-lbplugin/wspass --host=jan-v
m8.us.oracle.com --port=8989 --verbose --config=jan-vm8 jan-vm8.us.oracle.com
Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Command exit code : 116
Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Command output :
Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Command error output : ADMIN3012: Node 'jan-vm8.us.oracle.com' is not part
of the server farm.

Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Command exception trace : : abnormal subprocess termination: Detailed Mes
sage:ADMIN3012: Node 'jan-vm8.us.oracle.com' is not part of the server farm.

Feb 24, 2011 5:26:43 PM LBConfigurator
FINE: Exception :
lb.ExecException: abnormal subprocess termination: Detailed Message:ADMIN3012: N
ode 'jan-vm8.us.oracle.com' is not part of the server farm.

at lb.ProcessExecutor.execute(ProcessExecutor.java)
at lb.ProcessExecutor.execute(ProcessExecutor.java)
at lb.ProcessExecutor.execute(ProcessExecutor.java)
at lb.Configurator.executeCmdAndReturnOutput(Configurator.java)
at lb.Configurator.executeCmd(Configurator.java)
at lb.SJSWSConfigurator.runPullAndDeployConfig(SJSWSConfigurator.java)
at lb.SJSWSConfigurator.pullAndDeployConfig(SJSWSConfigurator.java)
at lb.SJSWSConfigurator.install(SJSWSConfigurator.java)
at lb.Installer.install(Installer.java)
at lb.Installer.runInstaller(Installer.java)
at lb.Installer.main(Installer.java)
Feb 24, 2011 5:26:43 PM LBConfigurator
INFO: Completed installation of GlassFish Load Balancer Plugin
Feb 24, 2011 5:26:43 PM LBConfigurator
WARNING: GlassFish load-balancer plugin installation completed with errors. Please check logs for any WARNING or SEVERE messages. Some manual changes may be required.

Workaround:

The workaround for is to run the iPlanet webserver "wadm" command manually.

i.e.

Make the temp "wspass" file exist or create temporary for this use.

  1. vi <webserver_install>/glassfish-lbplugin/wspass
    wadm_password=adminadmin

#<webserver_install>/bin/wadm pull-config --user=admin --password-file=/export/ha/ws7/https-jan-vm8/../glassfish-lbplugin/wspass --host=jan-vm8.us.oracle.com --port=8989 --verbose --config=jan-vm8 jan-vm8
CLI201 Command 'pull-config' ran successfully






Generated at Fri Feb 05 23:01:41 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.