Netboot servers not load balancing
We have 2 netboot servers that have been happily load balancing eachother for about a year ( 10.5.4, diskless netbooting, everything works fine, know about index numbers, etc). Recently, I replaced one of those servers with a new machine. Now, basically all the netboot clients boot to the new server. I have tried deleting the client files on the old server ( it was in the 7000s) as well as /var/bsdp_clients file to try to get my old server to reset its client numbers to zero ( I am convinced that they won't start load balancing again until the client numbers match up, I have seen this before). The occasional new client that boots to my old server will create a shadowfile numbered in the 7000s.
Anyone have any ideas?
We have 2 netboot servers that have been happily load balancing eachother for about a year ( 10.5.4, diskless netbooting, everything works fine, know about index numbers, etc). Recently, I replaced one of those servers with a new machine. Now, basically all the netboot clients boot to the new server. I have tried deleting the client files on the old server ( it was in the 7000s) as well as /var/bsdp_clients file to try to get my old server to reset its client numbers to zero ( I am convinced that they won't start load balancing again until the client numbers match up, I have seen this before). The occasional new client that boots to my old server will create a shadowfile numbered in the 7000s.
Anyone have any ideas?
Similar Messages
-
Cluster not load-balancing, ideas?
I've been struggling to identify why my JMS producers are not load-balancing against a remote cluster.
I've ruled out the producer as being the problem (I see the same non-load-balancing behavior regardless of what I use to create messages - Hermes, ALSB, simple Java producer...) I also don't think the JMS Connection Factory config is the problem, judging by the help I've received from folks over on the jms forum.
I believe something is wrong with our cluster setup because in addition to the problem I just mentioned, we also are not seeing JNDI entries propagate to all managed servers - for example, if I create one jms queue on m1, that queue does not appear in the jndi tree on m2.
I've been trying to find any documentation on what settings I should look at to verify the cluster configuration. If I go through the WLS console and look at the Cluster settings, I see both managed servers there, is there some other place that the configuration could be messed up?
Added 6/11, 9:30 am:
We're focusing on multicast now as the most likely problem. Can anyone tell me whether clusters on the same multicast address but different ports will interfere with each other? It looks like the infrastructure team has set up 5 clusters like that (same multicast address in each cluster, but different ports).
We've got a ticket open with BEA but it's been two weeks now and nothing except requests for more information.
Any ideas/help are much appreciated!
Meghan
Edited by pietila at 06/11/2008 7:38 AMMeghan Pietila wrote:
> I've been struggling to identify why my JMS producers are not load-balancing against a remote cluster.
>
> I've ruled out the producer as being the problem (I see the same non-load-balancing behavior regardless of what I use to create messages - Hermes, ALSB, simple Java producer...) I also don't think the JMS Connection Factory config is the problem, judging by the help I've received from folks over on the jms forum.
>
> I believe something is wrong with our cluster setup because in addition to the problem I just mentioned, we also are not seeing JNDI entries propagate to all managed servers - for example, if I create one jms queue on m1, that queue does not appear in the jndi tree on m2.
>
> I've been trying to find any documentation on what settings I should look at to verify the cluster configuration. If I go through the WLS console and look at the Cluster settings, I see both managed servers there, is there some other place that the configuration could be messed up?
>
> Added 6/11, 9:30 am:
> We're focusing on multicast now as the most likely problem. Can anyone tell me whether clusters on the same multicast address but different ports will interfere with each other? It looks like the infrastructure team has set up 5 clusters like that (same multicast address in each cluster, but different ports).
>
> We've got a ticket open with BEA but it's been two weeks now and nothing except requests for more information.
>
> Any ideas/help are much appreciated!
>
> Meghan
>
> --
> Edited by pietila at 06/11/2008 7:38 AM
You could be right. I think we have had problems where the same IP but
different ports were used for multicast. This is on 8.1 though.
I think as a rule, it's best to have a different ip and port for each
cluster.
Also - can you be sure that no one else is using the multicast addresses
on the network for anything else - we had someone bring up a test
cluster using our addresses which caused a few issues and took a while
to find! We also have security cameras which also use multicast, which
if they are using the same address/port can cause issues!
We're using 239.192.1.4:8001 for one cluster and 239.192.1.3:7001 for
the other - I think it's best to keep those as different as you can.
In 8.1, there is also the multicast monitor utility - there's a support
pattern on e-support on how to diagnose it. I've found this useful in
the past when I've suspected a cluster issue.
https://support.bea.com/application_content/product_portlets/support_patterns/wls/MulticastErrorsPattern.html
Check also that you're using a valid range for the address - we weren't
for a while and had odd problems from time to time.
There are also cluster debug flags available which you'll see listed in
the support document.
Are you seeing dropped multicast packets?
Hope that helps.
Pete -
ACE module not load balancing across two servers
We are seeing an issue in a context on one of our load balancers where an application doesn't appear to be load balancing correctly across the two real servers. At various times the application team is seeing active connections on only one real server. They see no connection attempts on the other server. The ACE sees both servers as up and active within the serverfarm. However, a show serverfarm confirms that the load balancer sees current connections only going to one of the servers. The issue is fixed by restarting the application on the server that is not receiving any connections. However, it reappears again. And which server experiences the issue moves back and forth between the two real servers, so it is not limited to just one of the servers.
The application vendor wants to know why the load balancer is periodically not sending traffic to one of the servers. I'm kind of curious myself. Does anyone have some tips on where we can look next to isolate the cause?
We're running A2(3.3). The ACE module was upgraded to that version of code on a Friday, and this issue started the following Monday. The ACE has 28 contexts configured, and this one context is the only one reporting any issues since the upgrade.
Here are the show serverfarm statistics as of today:
ACE# show serverfarm farma-8000
serverfarm : farma-8000, type: HOST
total rservers : 2
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: server#1
x.x.x.20:8000 8 OPERATIONAL 0 186617 3839
rserver: server#2
x.x.x.21:8000 8 OPERATIONAL 67 83513 1754Are you enabling sticky feature? What kind of predictor are you using?
If sticky feature is enabled and one rserver goes down, traffic will leans to one side.
Even after the rserver retuns to up, traffic may continue to lean due to sticky feature.
The behavior seems to depend on the configuration.
So, please let me know a part of configuration?
Regards,
Yuji -
2 nodes in a RAC not load balanced well
Our db is 2 nodes RAC with version of 10.2.0.3.0 on window 2003 server. I am wondering what else we may need to look into besides tnsnames.ora file to well balance the load between those two instances. Currently our
db is not well balanced based on the following two things:
1) query against gv$session
2) different amount of archive log files created in those two servers
Any help is greatly appreciated.
Shirley1) query against gv$sessionMay be check the load on the individual servers as well and check to make sure that the LOCAL_LISTENER and REMOTE_LISTENER parameters are set correctly.
2) different amount of archive log files created in those two serversI don't think measuring this would be a valid metric to evaluate the effectiveness of load balancing and this is not taken into consideration by oracle while load balacing the connections....
HTH
Thanks
-Chandra Pabba -
Clustering not Load balancing on solaris with apache
apache weblogic plugin does not do round-robin , it's kind of random when
direct the request to the appserver. anyone has seen this problem?
weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2
Actually, the random load-balancing when using Apache is caused by the fact
that Apache (<2.0) spawns multiple processes, so single Apache instance
will have several plug-in instances running.
Mike Reiche <[email protected]> wrote:
> You are using the weblogic plug-in, aren't you?
> Only new requests are round-robinned. A second request from the same browser
> is sent to the same server it hit the first time (sticky load-balancing).
> Mike
> "Tony Lu" <[email protected]> wrote:
>>apache weblogic plugin does not do round-robin , it's kind of random
>>when
>>direct the request to the appserver. anyone has seen this problem?
>>
>>weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2
>>
>>
Dimitri
-
Load Balancing not load balancing!
Hi,
We have inherited a 6.3 2005 Q1 installation of Access Manager that has the following problem.
All logons appear to be load balanced correctly however all Policy Agent requests are expressing a preference for one or other node at a time.
For example, during the last 4 days all PA traffic has been hitting Srv01. This leads to an 80/20 balance. This morning on Srv01 an error in the amSession logs appeared on Srv01, "SessionRequestHandler NullPointerException" and from this point on Srv02 started to take the Policy Agent requests. So now the traffic is still 80/20 but wth Srv02 handling the 'lion's share'.
Can anyone point me to documentation that describes in detail how Load Balancing working in the products?
Thanks,
EddieTHi,
Sorry I should have been more specific. The error we are seeing has been reported before but no resolution posted.
Thanks.
29/05/2009 08:57:05:119 AM IST: Thread[service-j2ee,11,main]
ERROR: SessionRequestHandler encounterd exception
com.iplanet.sso.SSOException: Session was not obtained.
at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:177)
at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:305)
at com.sun.identity.session.util.RestrictedTokenContext.unmarshal(RestrictedTokenContext.java:125)
at com.iplanet.dpro.session.service.SessionRequestHandler.processRequest(SessionRequestHandler.java:139)
at com.iplanet.dpro.session.service.SessionRequestHandler.process(SessionRequestHandler.java:112)
at com.iplanet.services.comm.server.PLLRequestServlet.handleRequest(PLLRequestServlet.java:195)
at com.iplanet.services.comm.server.PLLRequestServlet.doPost(PLLRequestServlet.java:147)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at sun.reflect.GeneratedMethodAccessor203.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:234)
at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2124) -
WLS proxy plugin does not load balance
I have a cluster created with two app servers in separate boxes and a Weblogic proxy plug-in to forward the client requests to the servers. However, the proxy doesn't distribute the load equally. Very often 90% of the user sessions go to one server and 10% to the other. Both boxes have the same hardware specs.
Does the WLS plugin really support round-robin load balancing ? I'd appreciate any information to solve this problem.
Thanks
- Miguel
I'm using WLS 6.1 SP2.
Are you load balancing the web servers? What kind of web servers are you
using?
Miguel Vilar wrote:
>I have a cluster created with two app servers in separate boxes and a Weblogic proxy plug-in to forward the client requests to the servers. However, the proxy doesn't distribute the load equally. Very often 90% of the user sessions go to one server and 10% to the other. Both boxes have the same hardware specs.
>Does the WLS plugin really support round-robin load balancing ? I'd appreciate any information to solve this problem.
>Thanks
>- Miguel
>I'm using WLS 6.1 SP2.
>
-
WLS 8.1.4 cluster is does not load balance correctly
Hi WLS gurus!
I have a problem with my apache load balancer....
it seems apache does not see all WLS instances with DynamicServerList ON!
all connections come in to, in my case, instance 2...
my cluster runs on 2 separate machines..
any ideas? problem with DNS maybe?
thanks
MichaelHi,
Go through the following link and check whether you configured load balancing settings correctly or not.
http://e-docs.bea.com/wls/docs81/cluster/load_balancing.html
Regards
Anilkumar kari -
CSM not load-balancing properly
Folks,
I'm seeing that CSM is not loadbalancing properly to all the servers in the serverfarm.
I simulated a failover of one of the servers TS05 and brought it back. After coming online, CSM sent no traffic to that server, as shown below:
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
TS02-RADIO, weight = 8, OPERATIONAL, conns = 4
TS03-RADIO, weight = 8, OPERATIONAL, conns = 2
TS04-RADIO, weight = 8, OPERATIONAL, conns = 4
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 1
TS02-RADIO, weight = 8, OPERATIONAL, conns = 3
TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
TS04-RADIO, weight = 8, OPERATIONAL, conns = 3
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
TS02-RADIO, weight = 8, OPERATIONAL, conns = 4
TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
TS04-RADIO, weight = 8, OPERATIONAL, conns = 3
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
TS03-RADIO, weight = 8, OPERATIONAL, conns = 0
TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 2
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 3
C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 4
My config is attached with this post:
Can there be anything wrong with my VARIABLES?
C7606-1#show mod csm 1 variable | i SLOW
REAL_SLOW_START_ENABLE 1
C7606-1#Folks - I upgraded the code to 4.2(6) and thought that bug CSCei26434 was solved, but still see the same error where CSM is not balancing properly.
No Traffic Running:
===================
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
Started Traffic
===============
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 60
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 101
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 188
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
The newly ALIVE server passed the probe test:
=============================================
C7606-1#show mod csm 1 probe detail | inc 102
192.168.122.102:1813 RADIUS RADIUS (default) OPERABLE
192.168.122.102:9202 WSP_SCL WSP_SCL (default) OPERABLE
192.168.122.102:9201 WSP_CO WSP_CO (default) OPERABLE
192.168.122.102:9200 WSP_CL WSP_CL (default) OPERABLE
192.168.122.102:8080 WHTTP WHTTP (default) OPERABLE
192.168.122.102:8080 TP_8080 TP_8080 (default) OPERABLE
192.168.122.102:7080 PUSH_WWW PUSH_WWW (default) OPERABLE
Still no connections:
=====================
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 583
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
C76061#
Brought another server on-line:
================================
C7606-1#
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:8080 in serverfarm 'WHTTP'
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:8080 in serverfarm 'TP_8080'
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:7080 in serverfarm 'PUSH_WWW'
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9200 in serverfarm 'WSP_CL'
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:1813 in serverfarm 'RADIUS'
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9201 in serverfarm 'WSP_CO'
C7606-1#
C7606-1#
1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9202 in serverfarm '
No connections to the NEW Server even
======================================
C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
TS01-RADIO, weight = 8, OPERATIONAL, conns = 2988
TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
TS06-RADIO, weight = 8, OPERATIONAL, conns = 0 -
Wireless does not load balance and Connection drops to 1Mbps at a certain time
Hi,
We had wireless LAN setup and it seems that every afternoon, the connection notification on their laptop drops to 1Mbps and slowness on the network is experienced. how can I identify the cause of this drop connection speed?
Also when one of the APs went down, the other nearby APs does not cover for the AP that went down, is it not supposed to cover for the downed AP?
BTW out setup is LAP with 4400 series WLC with VoWLAN running on it but on differed radio and SSID. Data is on b/g while VoWLAN is on A.also i am seeing a lot of coverage hole detection on the logs.
is there any problems with the coverage of the APs? should I place additional APs to cover up the holes?If you have available funds/resources then putting additional APs won't hurt ... especially if one of the APs fail. Putting additional APs will also help distribute the clients.if it is cause by rouge AP how can i prevent it.
First, you have to know what radios is the AP using. For example, if the Rogue AP is using 802.11b then disable your 802.11b or use a different channel. I'm curious to know this is the case since the WLC would've used a different channel if a Rogue AP is broadcasting on similar channel (unless there's just too many Rogue APs using 802.11b).
you recommed any steps on how can i trace sudden surge of wireless use I'd like to identify/isolate how correct is my hypothesis that it's due to the sudden surge of wireless use. If this is the case, then I'd also like to know what application(s) are being used to overwhelm the wireless. -
Load balancing across multiple application servers not working with JCo RFC
We have a problem where inbound messages to the Mapping Runtime engine (ABAP -> J2EE) are not load balanced over application servers. However, load balancing does take place across server nodes within one application server.
Our system comprises of the following:
Central Instance (2 X server nodes)
Database Instance
2 X Dialog Instances (with 2 X server nodes each)
The 1st application server that starts is usually the one that is used for inbound messaging.
We have looked at the sap gateway configuration and have tried various options without much luck:
i.e.: local gateways vs. one central gateway, load balancing type by changing parameter gw/reg_lb_level, see: http://help.sap.com/saphelp_nw70/helpdata/EN/bb/9f12f24b9b11d189750000e8322d00/frameset.htm
Here are our release levels:
SAP_ABA 700 0012 SAPKA70012
SAP_BASIS 700 0012 SAPKB70012
PI_BASIS 2005_1_700 0012 SAPKIPYJ7C
ST-PI 2005_1_700 0005 SAPKITLQI5
SAP_BW 700 0013 SAPKW70013
ST-A/PI 01J_BCO700 0000 -
Any help would be greatly appreciated.
Many thanksTim
Did you follow the guide here:
How to Scale Up SAP Exchange Infrastructure 3.0
Learn what the most likely scaled system architecture looks like, and read about a step by step procedure to install additional dialog instances. The guide also walks you through additional configuration steps and the application of Support Package Stacks.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c3d9d710-0d01-0010-7486-9a51ab92b927
We followed this guide for XI3.0 and PI7.0 and works successfully! -
Load Balancing Directory Servers with Access Manager - Simple questions
Hi.
We are in the process of configuring 2 Access Manager instances (servers) accessing the same logical LDAP repository (comprising physically of two Directory Servers working together with Multi-Master Replication configured and tested) For doing this, we are following guide number 819-6258.
The guide uses BigIP load balancer for load balancing the directory servers. However, we intend to use Directory Proxy Server. Since we faced some (unresolved) issues last time that we used DPS, there are some simple questions that I would be very grateful to have answers to:
1. The guide, in section 3.2.10 (To configure Access Manager 1 with the Directory Server load balancer), talks about making changes at 4 places, and replacing the existing entry (hostname and port) with the load balancer's hostname and port (assuming that the load balancer has already been configured). It says that changes need not be made on Access Manager 2 since the LDAPs are in replication, and hence changes will be replicated at all places. However, the guide also states that changes have to be made in two files, namely AMConfig.properties, and the serverconfig.xml file. But these changes will not be reflected on Access Manager 2, since these files are local on each machine.
Question 1. Do changes have to be made in AMConfig.properties and serverconfig.xml files on the other machine hosting Access Manager 2?
Question 2: What is the purpose of putting these values here? Specifically, what is achieved by specifying the Directory server host and port in AMConfig.properties, as well as in serverconfig.xml?
Question 3. In the HTTP console, there is the option of specifying multiple primary LDAP servers, as well as multiple secondary LDAP servers. What is the purpose of these? Are secondary servers attempted when none of the list in the primary list are accessible? Also, if there are multiple entries in the primary server list, are they accessed in a round robin fashion (hereby providing rudimentary load balancing), or are other servers accessed only when the one mentioned first is not reachable etc.?
2. Since I do not have a load balancer setup yet, I tried the following deviation to the above, which, according to me, should have worked. If viewed in the HTTP console, LDAP / Membership / MSISDN and Policy configuration all pointed to the DS on host 1. When I changed all these to point to the directory server on host 2 (and made AMConfig.properties and serverconfig.xml on host 1 point to DS of host 2 as well), things should have worked fine, but apparently Access manager 1 could not be started. Error from Webserver:
[14/Aug/2006:04:30:36] info (13937): WEB0100: Loading web module in virtual server [https-machine_1_FQDN] at [search]
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Exception in thread "EventService" java.lang.ExceptionInInitializerError
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.iplanet.services.ldap.event.EventServicePolling.run(EventServicePolling.java:132)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at java.lang.Thread.run(Thread.java:595)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Caused by: java.lang.InterruptedException
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.sun.identity.sm.ServiceManager.<clinit>(ServiceManager.java:74)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: ... 2 more
In effect, AM on 1 did not start. On rolling back the changes, things again worked like previously.
Will be really grateful for any help / insight / experience on dealing with the above.
Thanks!Update to the above, incase anyone is reading:
We setup a similar setup in Windows, and it worked. Here is a detailed account of what was done:
1. Host 1: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST1:389)
2. Host 2: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST2:389)
3. Host 1: Started replication. Set to Master
4. Host 2: Started replication. Set to Master
5. Host 1: Setup replication agreement to Host 2
6. Host 2: Setup replication agreement to Host 1
7. Initiated the remote replica from Host 1 ----> Host 2
Note that since default installation uses abc.....xyz as the encryption key, setting this to same was not an issue.
9. Started webserver for Host 1 and logged into AM as amadmin.
10. Added Host 2 FQDN in DNS Aliases / Realms
11. Added http://HOST2_FQDN:80 in the Platform server (instance) list.
12. Started Host 2 webserver. Logged in AM on Host 2, things worked fine.
At this stage, note the following:
a) Host 1:
AMConfig.properties file has
com.iplanet.am.directory.host=host1_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host1_FQDN" port="389" type="SIMPLE" />
b) Host 2:
AMConfig.properties file has
com.iplanet.am.directory.host=host2_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host2_FQDN" port="389" type="SIMPLE" />
c) If one logs into AM, and checks LDAP servers for LDAP / Policy Configuration / Membership etc services, they all contain Host2_FQDN:389 (which makes sense, since replica 2 was initialized from 1)
Returning back to the configuations:
13. On Host 1, login into the Admin server console of the Directory server. Navigate to the DPS, and confgure the following:
a) Network Group
b) LDAP servers
c) Load Balancing
d) Change Group
e) Action on-bind
f) Allow all actions (permit modification / deletion etc.).
g) any other configuations required - Am willing to give detailed steps if someone needs them to help me / themselves! :)
So now, we have DPS configured and running on Host1:489, and distributing load to DS1 and DS2 on a 50:50 basis.
14. Now, log into AM on Host 1, and instead of Host1_fqdn:389 (for DS) in the following places, specify Host1_fqdn:489 (for the DPS)--
LDAP Authentication
MSISDN server
Membership Service
Policy configuation.
Verified that this propagated to the Policy Configuration service and the LDAP authentication service that are already registered with the default organization.
15. Log out of AM. Following the documentation, modify directory.host and directory.port in AMConfig.properties to point to Host 1_FQDN and 489 respectively. Make this change in AMConfig.properties of both Host 1 as well as 2.
16. Edit serverconfig.xml on both hosts, and instead of they pointing to their local directory servers, point both to host1_FQDN:489
17. When you start the webserver, it will refuse to start. Will spew errors such as:
[https-host1_FQDN]: Sun ONE Web Server 6.1SP5 B06/23/2005 17:36
[https-host1_FQDN]: info: CORE3016: daemon is running as super-user
[https-host1_FQDN]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amserver]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [ampassword]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amcommon]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amconsole]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [search]
[https-host1_FQDN]: warning: CORE3283: stderr: netscape.ldap.LDAPException: error result (32); matchedDN = dc=sun,dc=com; No such object (DN changed)
[https-host1_FQDN]: warning: CORE3283: stderr: Got LDAPServiceException code=-1
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:357)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:314)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:253)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:184)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:194)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:1248)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.(DataLayer.java:190)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:215)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:246)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:156)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.(SMSLdapObject.java:124)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance0(Class.java:350)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance(Class.java:303)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.SMSEntry.(SMSEntry.java:216)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ServiceSchemaManager.(ServiceSchemaManager.java:67)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetector.java:219)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.(AMClientDetector.java:94)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3271)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3747)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: failure: WebModule[amserver]: WEB2783: Servlet /amserver threw load() exception
[https-host1_FQDN]: javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: ----- Root Cause -----
[https-host1_FQDN]: java.lang.NullPointerException
[https-host1_FQDN]: at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]:
[https-host1_FQDN]: info: HTTP3072: [LS ls1] http://host1_FQDN:58080 [i]ready to accept requests
[https-host1_FQDN]: startup: server started successfully
Success!
The server https-host1_FQDN has started up.
The server infact, didn't start up (nothing even listening on 58080).
However, if AMConfig.properties is left as it originally was, and only serverconfig.xml files were changed as mentioned above, web servers started fine, and things worked all okay. (Alright, except for some glitches when viewed in /amconsole. If /amserver/console is accessed, all is good. Can this mean that all is still not well? I am not sure).
So far so good. Now comes the sad part. When the same is done on Solaris 9, things dont work. You continue to get the above error, OR the following error, and the web server will refuse to start:
Differences in Solaris and Windows are as follows:
1. Windows hosts have 1 IP and hostname. Solaris hosts have 3 IPs and hostnames (for DS, DPS, and webserver).
No other difference from an architectural perspective.
Any help / insight on why the above is not working (and why the hell does the documentation seem so sketchy / insecure / incorrect).
Thanks a bunch! -
Could not retrieve Enterprise Global Template - Load balancer issue
Hi,
We have 4 Project Server 2010 servers. The 4 web servers are load balanced by networking team with sticky session configured.
When we try to connect to the Project Server using MPP 2007 SP2, it fails saying 'Could not retrieve Enterprise Global template'. It works perfect when we point to a specific server by specifying the IP address for server name in the 'hosts'
file.
Earlier we observed some errors in the event viewer related to the SharePoint's internal load balancer for which restarted the 'Project Server Application' on each web server and it got fixed.
Now, the only entries that we see related to load balancer are as mentioned below as Information (not errors).
SharePoint Web Services Round Robin Service Load Balancer Event: Initialization
Process Name: w3wp
Process ID: 15080
AppDomain Name: /LM/W3SVC/539065287/ROOT-1-130462463500778047
AppDomain ID: 2
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:ae7c7ee5c09b4e8198bdbb1ecb8c1c1b#authority=urn:uuid:9f626d347784423eb14bde4a1f4d13fc&authority=https://lonms12546:32844/Topology/topology.svc
Active Endpoints: 4
Failed Endpoints:0
Endpoint List:
http://lonxxx2532:32843/ae7c7ee5c09b4e8198bdbb1ecb8c1c1b/PSI
http://lonxxx2545:32843/ae7c7ee5c09b4e8198bdbb1ecb8c1c1b/PSI
http://lonxxx2546:32843/ae7c7ee5c09b4e8198bdbb1ecb8c1c1b/PSI
http://lonxxx2566:32843/ae7c7ee5c09b4e8198bdbb1ecb8c1c1b/PSI
Could the issue be due to network load balancer?
Could the issue be due to Sticky session configuration on the load balancer.?
How can we get to the root cause of the issue?
Which logging category should we set to 'Verbose' that can give us some hint.
Update: We tried to capture the requests through fiddler and observed that when fiddler is running on the client computer then the connection works perfectly fine even through the load balancer. Probably fiddler is reformatting the SOAP
envelop of the web service requests the way it should before sending the request to the server.
If we do not run fiddler and run some other similar tool (like Charles) then it again gives the issue and the request stucks at /PWA/_vti_bin/psi/winproj.asmx
We ran Wireshark on the servers and found the following for that web service call:
[TCP Previous segment not captured] Continuation or non-HTTP traffic.
Please let me know if someone could provide any hint what can be done next.
Regards, Amit GuptaThere are several ways to configure your load balancer. I would suggest that you work with the network engineer, the load balancer vendor and your project administrator to resolve this issue.
Basically you need URL to be resolved correctly. Also, I don't believe PS2007 did a good job handling load balancing, so you may need to bring someone in good with IIS and see they can tweek IIS to manage the cache better.
As I go back and look at your analysis, I think you should probably look at upgrading to Project Server 2013. They made some improvement in load balancing and the management of distributive cache.
I assume you have 4 WFE because you have thousands of project users. Roughly how many you have? Over 1000, over 5000
Have you tried to see if using two load balancing work? How about just one front end. I often see companies scaling SharePoint and Project server to extremes.
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries -
Load balancing multiple J2ee servers - each running it's own CI
Is it possible to load balance multiple J2ee servers(running Portal), both running it's own Central Instance?
We do not have the resources (SAN storage) to implement MSCS for Portal...so instead we want to use two complete Portal servers HW load balanced with the ability to keep running in case one fails.
thanks for any info !
LinwoodHi Linwood,
in a nutshell, the difference between an ordinary J2EE server instance and the central instance are the central services. The central services (enqueue server, message server) are only needed once. Basically, they are required for the communication between the server instances (and to the load balancer). What you should go for is a cluster installation with one central instance and another ordinary server instance (both running the SAP NetWeaver Portal). But be aware that you have to use the same database for both server instances (otherwise you cannot guarantee consistent data).
For load balancing the two server you can use the SAP Web Dispatcher or any other load balancer tool you like.
You will find more and detailed information on load balancing in the SAP Library. Have a look into section <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/611724f410254ca12a3f396ec5ae85/frameset.htm">Java Cluster Architecture</a>.
Hope I could help!
Best regards,
Martin -
How to load balance Agents across multiple Oracle Management Servers?
Hi everyone
We have the 2 OMS servers in our OEM environment. We would like to set up our management agents to load balance over these 2 servers...Or if not load balance then at least set up the agents so they can access either/or OMS.
I've looked through the documentation and in google, but can't seem to find the answer.
Can someone point me towards the documentation please
Thanks
ROMS is just an appserver with a repository. You can load balance the appservers with an F5. You can load balance the repository with RAC.
So ... your options for load balancing and resilience are :-
1. one agent on each server, multiple OMS appservers load balanced, one RAC database (with dataguard standby)
2. two agents per server, two appservers, two repositories.
Both architectures work. Option 1 offers the best load balancing and resilience.
Maybe you are looking for
-
What is difference between BP monitor and supplier monitor?
hi friends what is difference between BP monitor and Supplier Monitor what is tcode for BPmonitor Regards Vinny
-
PL/SQL Code not working without debug statements
Hi Guys, I have a pl/sql code in a procedure, logic iterates through almost 40K records, conditional delete and update. When I execute this code, I dont see the deletes and updates happening, though procedure executes for 8 minutes and exits wihtout
-
Tired of working with Verizon on a phone that does not work. FASCINATE.
Since I got my fascinate a six months ago I have had nothing but problems.. At this point in time, I don't get phone calls and can't make phone calls, I don't get text messages either at all or not for hours later and the ones I send people are not g
-
Will old iSight camera work with new Mac mini?
will an old isight camera work with a late 2014 Mac mini? If so what adapters will I need?
-
Transfer problem: slow and error -53
Hi i have a problem with my IPod classic 120Gb. When i upload music ti my IIpod from ITunes, the first 7 songs are uploaded normally, but then the transfer gets very slow, then it freezes and in some cases i get an error -53.