Apache 2 + Sun Java 8.1 load balancer connector dies under load

Hi,
We are testing the apache module "mod_loadbalancer.so" for connecting an apache 2 to a Sun Java 8.1 App Servers running on a different box.
When we perform a basic load testing (60 concurrent users) we are experiencing a very high CPU usage: apache's CPU consumption is around 30-40%per child.
This generates or very slow responses from the App Server or at some point the apache thread die, and therefore, lose of connection to the app server, generating an internal server error.
If we perform this same test directly to the App Server httpd listener, it bahaves fine. We have also performmed the same test againt static content of apache, and again the everything is ok, we even have tried using iWS instead of apache, and the CPU does not go over 4%, so it looks like the problem resides on the apache connector.
Have any of you experienced something similar?
This is the basic conf:
Web Server:
SunOS 5.9 Generic_118558-19 sun4u sparc SUNW,UltraSPARC-IIi-cEngineApache 2.0.54 with MPM worker (threads support) compiled with gcc
apache:~>/apps/WebServer/apache/2.0/bin/httpd -v
Server version: Apache/2.0.54
Server built:   May 23 2006 07:10:19
apache:~>/apps/WebServer/apache/2.0/bin/httpd -l
Compiled in modules:
core.c
mod_access.c
mod_auth.c
mod_log_config.c
mod_env.c
worker.c
http_core.c
mod_mime.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_alias.c
mod_so.c
httpd.conf:
#                   Sun AppServer Load Balancer Configuration                          #
LoadFile /usr/lib/libCstd.so.1
LoadModule apachelbplugin_module /apps/WebServer/apache/2.0/modules/mod_loadbalancer.so
config-file /apps/WebServer/apache/apache2-sunsecd1/conf/loadbalancer.xml
locale en
loadbalancer.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE loadbalancer PUBLIC "-//Sun Microsystems Inc.//DTD Sun ONE Application Server 7.1//EN" "sun-loadbalancer_1_1.dtd">
<loadbalancer>
<cluster name="sunsecd1">
    <instance disable-timeout-in-minutes="30" enabled="true" listeners="http://appserver:38082" name="sunsecd1"/>
    <web-module context-root="petstore" disable-timeout-in-minutes="30" enabled="true"/>
    <web-module context-root="opc" disable-timeout-in-minutes="30" enabled="true"/>
    <web-module context-root="admin" disable-timeout-in-minutes="30" enabled="true"/>
    <web-module context-root="supplier" disable-timeout-in-minutes="30" enabled="true"/>
    <health-checker interval-in-seconds="30" timeout-in-seconds="10" url="/"/>
</cluster>
<property name="response-timeout-in-seconds" value="60"/>
<property name="reload-poll-interval-in-seconds" value="60"/>
<property name="https-routing" value="false"/>
<property name="require-monitor-data" value="false"/>
<property name="route-cookie-enabled" value="true"/>
</loadbalancer>

Hi Balaji,
The Apache webserver runs on Solaris 9 on a Netra T1:
$ /usr/platform/`uname -i`/sbin/prtdiag
System Configuration: Sun Microsystems sun4u Netra t1 (UltraSPARC-IIi 440MHz)
System clock frequency: 110 MHz
Memory size: 1024 Megabytes
========================= CPUs =========================
                    Run   Ecache   CPU    CPU
Brd CPU   Module   MHz     MB    Impl.   Mask
0     0     0      440     2.0   12       9.1
========================= IO Cards =========================
     Bus# Freq
Brd Type MHz   Slot Name                              Model
0   PCI-1 33     1   ebus
0   PCI-1 33     1   network-SUNW,hme
0   PCI-1 33     2   scsi-glm                          Symbios,53C875
0   PCI-1 33     3   network-SUNW,hme
0   PCI-2 33     1   pci-pci1011,22The Sun App Server is Sun Java System Application Server Enterprise Edition 8.1_02 (build b11-fcs)
Did I miss anything else?

Similar Messages

To Load Balance or Not to Load Balance? ISE and F5 Big IP

Currently my team is debating whether to put our two ISE appliances (PSN nodes) behind our F5 load balancing deployment.
Our network is relatively small in size (5K users) with a small wireless deployment (4 Cisco controllers with 300 Access points). Network growth should remain relatively minimal over the coming years.
We will be rolling out wired Dot1X, followed by posture assessment and remediation. (BYOD is not an option).
On one hand, the Big IP features could make it easier for us to perform load balancing, maintenance and troubleshooting.
On the other hand, the Big IP adds another element of complexity into an already complex deployment. We already have the capability to load balance from the switches themselves. Load balancing for wireless should not be an issue as our deployment is very small and I expect it to remain so. Given the size of my environment, there seems to be relatively little to gain for the additional effort and potential pitfalls.
Would anyone care to share their honest opinion on this issue?
Thanks,
Phill

Load balancers are elegant and do their job nicely when it comes to distributing the load between servers. You already have one so I would suggest using it if you have the technical expertise to configure it.
With that being said, if your team is not 100% comfortable with F5 then you should definitely skip it. Instead, you can configure your WLCs to use Node #1 as primary and Node #2 as secondary Radius server and then your Switches to use Node #2 as primary and Node#1 as secondary.
I hope this helps!
Thank you for rating helpful posts!

Client side load balancing and server side load balancing

Hello Team,
I need to know how to set up client and server side load balancing in oracle rac. What all things to be implemented like creating a service, tnsnames.ora settings etc.
And also if i used SCAN ip instead of VIP. how the settings will change.
Regards,

Hi,
please find here an Whitepaper with the information
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11gr2-client-failover-173305.pdf
kind regards

LOGON LOAD BALANCING WITH THIRD PARTY LOAD BALANCERS

Hello Everybody,
We would like to implement third party Application Load Balancers for all our Applications including SAP Landscape (HTTP and SAP LOGON).
Could you please indicate which third party load balancers are compatibles with SAP LOGON GROUP LOAD BALANCING ?
Thanks for your help.
Mauricio Cardozo.

Hello Mayank,
how we we can maintain the logon load balancing for http requests
Use the SAP webdispatcher (and logon groups on services) for that ....
http://help.sap.com/saphelp_nw04/helpdata/en/5f/7a343cd46acc68e10000000a114084/content.htm
Regards
Stefan

Network Load Balancing - "access denied" when loading configuration information from host2

We have 2 Windows 2012 R2 servers, both are running on workgroup.
We set up NLB cluster. When we open NLB Manager on the server2, then message shows "loading configuration information. Access denied. Error connecting to server1".
There is no issue doing this on server1, NLB Manager is able to connect to both servers. We login using default administrator account, both account name and password are the same for 2 servers.
When we check security event log on server1, there is this strange Audit Failure log using account "test_nlb" from server2 which related to "Access denied" error. Please let us know how to resolve this. Thanks in advance.
      Event ID: 4776
      The computer attempted to validate the credentials for an account.
      Authentication Package:
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
      Logon Account:
test_nlb
      Source Workstation:
WPAAP2
      Error Code:
0xc0000064
      An account failed to log on.
Event ID: 4625
Subject:
    Security ID:
S-1-0-0
    Account Name:
    Account Domain:
    Logon ID:
0x0
Logon Type:
3
Account For Which Logon Failed:
    Security ID:
S-1-0-0
    Account Name:
test_nlb
   Account Domain:
WPAAP2
Failure Information:
    Failure Reason:
Unknown user name or bad password.
    Status:
0xc000006d
    Sub Status:
0xc0000064
Process Information:
    Caller Process ID:
0x0
    Caller Process Name:
Network Information:
    Workstation Name:
WPAAP2
    Source Network Address:
192.168.70.45
    Source Port:
55136
Detailed Authentication Information:
    Logon Process:
NtLmSsp
    Authentication Package:
NTLM
    Transited Services:
    Package Name (NTLM only):
    Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Hi Zhong Gang,
When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated
the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. Please disable your nodes firewall and
try again.
The related KB:
Add a Host to the Network Load Balancing Cluster
http://technet.microsoft.com/en-us/library/cc753744.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Two isp load balancing on cisco ACE(load balancer)

I don't know much about load balancer(ACE).
Is this is possible to load balance two isp's on load balancer (ACE). If so, how i can do so , any configuration example, or cisco document.

Wrong forum, post in "Datacenter". You can move your posting with the Actions panel on the right.

Help.. Desperation kicks iN! Tomcat 4.1.24 dies under load

If tomcat 4.1.24 is hit with heavy load, it quickly reaches its max configured processors (regardless of what I set it to), and then hangs. Its not dead, but doesn't serve out pages.
I've tried everything from setting more memory for the JVM using -Xmx to altering the acceptcount, min/max processors, but nothing stops the inevitable...
Any assistance would be appreciated.
Under normal load conditions, the tomcat is fine for days.

Even we had a few problems using TomCat:
No Connection Pooling- Special coding is necessary to instigate this functionality
- No Caching Capabilities
- Tomcat does not include functionality outside the J2EE specification designed to increase performance and enhance scalability for production application
We have moved out with Oracle.....and we have stopped worrying about support

Load balancing not functioning

Is load balancing actually supposed to load balance? I have two servers in the failover group, with 125 DTUs on one and 0 on the second one. The documentation is a little vague on this and it says that the load balancing will only take effect if one server goes down (meaning if you have three equal servers and one drops the new connections will be distributed across the two remaining servers).
Is there a way to balance between my two Sun servers?

Yes, load balancing is supposed to balance load. This is not restricted to the case of failover.
But load balancing happens only at certain times in the lifecycle of connections/sessions. It can occur when a DTU connects, when a smart card is inserted or removed, when a user logs out or when a kiosk session exits. For a new connection or token, it obviously occurs only when there is not yet a (non-"idle") session for the connecting token. Load balancing happens before the login prompt is shown, so if the client sits showing a login prompt for a long time, it will not be rebalanced when the user actually turns up and logs in. (Only with NSCM there may be load balancing after the user has entered her name.) Load balancing does not happen, if the user never logs out or if a kiosk session never exits. This includes cases where a kiosk session loops internally between user sessions instead of exiting - that is one of the reasons for the '-t timeout' option of the Sun Ray Windows Connector kiosk session type.
Sessions may accumulate on one server as you describe, if you don't use mobile sessions (smart cards or NSCM) and your users rarely log out or your kiosk session never exits. You may easily get into this situation, if one server is down or slow to come up when all the DTUs connect after a cold (re)start or other downtime.
Other reasons why loadbalancing may fail are:
- The server group isn't formed properly. The servers page in the admin GUI or the utgstatus(1M) command must show all servers in the group as trusted, online, up and available. (This must be true from either server.)
- You forgot to include the -g option to utpolicy(1M), when setting server policy on the command line.
- You manually edited the auth.props(4) file and disabled it.

Any difference between Sun Java System Web Server - Update 1 and update 2

Any configuration changes need to be made particularly for Sun Java System Web Server - Update 2 in the load balancing. because i face issue in load balancing with Sun Java System Web Server - Update 2 , but load balancing is working fine with Sun Java System Web Server - Update1

using Sun Java System Web Server - Update 2 as forward proxy. and here is my obj.conf file entries
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# You can edit this file, but comments and formatting changes
# might be lost when you use the administration GUI or CLI.
<Object name="default">
AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"
NameTrans fn="ntrans-j2ee" name="j2ee"
NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Program Files/Sun/WebServer7/lib/icons" name="es-internal"
PathCheck fn="uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index-j2ee"
PathCheck fn="find-index" index-names="index.html,home.html,index.jsp"
ObjectType fn="type-j2ee"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD|POST)" type="*~magnus-internal/*" fn="send-file"
Service method="TRACE" fn="service-trace"
Error fn="error-j2ee"
AddLog fn="flex-log"
</Object>
#this line was added for weblogic clustering
<Object name="webapp" ppath="*/webapp/*">
Service fn=wl_proxy WebLogicCluster="ip:7002,ip:7003"
</Object>
<Object name="j2ee">
Service fn="service-j2ee" method="*"
</Object>
<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
<Object name="send-precompressed">
PathCheck fn="find-compressed"
</Object>
<Object name="compress-on-demand">
Output fn="insert-filter" filter="http-compression"
</Object>
<Object name="tunnel" ppath="*/HTTPClnt*">
Service fn=wl_proxy WebLogicCluster="ip:7002,ip:7003"
</Object>

Send Email issue using "Mail Server Load balancer" (Cisco ACE 20)

I have asked this question in SAP MII forum too but it appears issue could be in NetWeaver Mail API. Please let me know if someone have experienced this kind of issue or any suggestions.
The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
MII still sends email if direct ip address of email server provided instead of Email Load balancer but not through Load balancer .
Any suggestions ?
Could not authenticate mail account (Unknown Source)
[EXCEPTION]
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at javax.mail.Service.connect(Service.java:169)
at javax.mail.Service.connect(Service.java:118)
at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)

Hi Ahmed,
I don't have experience with Blackberry, but, as the document mentions, the first thing to do would be making sure that the connection timeout is set to something high enough
You can find more details on how to modify this value at the link below:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/security/guide/tcpipnrm.html#wp1074289
I hope this helps
Daniel

Load balancing across 4 web servers in same datacentre - advice please

Hi All
Im looking for some advice please
The apps team have asked me about load balancing across some servers but im not that well up on it for applications
Basically we have 4 apache web servers with about 2000 clients connecting to them, they would like to load balance connections to all these servers, they all need the same DNS name etc.
what load balancing methods would I need for this, I believe they run on Linux
Would I need some sort of device, or can the servers run some software that can do this, how would it work? and how would load balancing be achieved here?
cheers

Carl,
What you have mentioned sounds very straightforward then everything should go well.
The ACE is a load balancer which takes a load balancing decisions based on different matching methods like matching virtual address, url, source address, etc then once the load balance decision has been taken then the ACE will load balance the traffic based on the load balance method which you have configured (if you do not configure anything then it will use the default which is "round robin"), then it will send the traffic to the servers which it has available and finally the client should get the content.
If you want to get some details about the load balancing methods here you have them:
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/overview.html#wp1000976
For ACE deployments the most common designs are the following.
Bridge Mode
One Arm Mode
Routed Mode
Here you have a link for Bridge Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_Bridged_Mode_on_the_Cisco_Application_Control_Engine_Configuration_Example
Here you have a link for One Arm Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_One_Arm_Mode_with_Source_NAT_on_the_Cisco_Application_Control_Engine_Configuration_Example
Here you have a link for Routed Mode and a sample for that:
http://docwiki.cisco.com/wiki/Basic_Load_Balancing_Using_Routed_Mode_on_the_Cisco_Application_Control_Engine_Configuration_Example
Then as you could see in all those links you may end up having a configuration like this:
interface vlan 40
description "Default gateway of real servers"
ip address 192.168.1.1 255.255.255.0
service-policy input remote-access
no shutdown
ip route 0.0.0.0 0.0.0.0 172.16.1.1
class-map match-all slb-vip
2 match virtual-address 172.16.1.100 any
policy-map multi-match client-vips
class slb-vip
    loadbalance vip inservice
    loadbalance policy slb
policy-map type loadbalance http first-match slb
class class-default
    serverfarm web
serverfarm host web
rserver lnx1
    inservice
rserver lnx2
    inservice
rserver lnx3
    inservice
rserver host lnx1
ip address 192.168.1.11
inservice
rserver host lnx2
ip address 192.168.1.12
inservice
rserver host lnx3
ip address 192.168.1.13
inservice
Please mark it if it answered you question then other users can use it as reference in the future.
Hope this helps!
Jorge

OSB jms clustering - load balancing seems to be not working

Hi All,
I have one admin server and two managed servers running ( one of these managed server is running in the remote linux machine) in a cluster
I have connectionfactory created with load balance enabled with round robin
and server affinity is disabled
I have queue created as uniformly distributed Q
I have a proxy service with load balancing as roundrobin and endpoint URL as below
jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
If I execute this proxy sending messages it always go to one server only. There is no message going to the other server.
If I shutdown the server that receives messages then the other server is receiving messages. Seems like fail-over is working but not the load-balancing
There is one point may be worth mentioning here is, from the admin console if I look at the servers for the clusters it has below information
Name      State      Drop-out Frequency      Remote Groups Discovered      Local Group Leader      Total Groups      Discovered Group Leaders      Groups      Primary
synergyOSBServer1     RUNNING     Never     0     synergyOSBServer1     1     synergyOSBServer1     *{synergyOSBServer1}*     0
synergyOSBServer2     RUNNING     Never     0     synergyOSBServer1     1     synergyOSBServer1     *{synergyOSBServer1, synergyOSBServer2}* 0
one server has groups as {synergYOSBServer1} instead of {synergyOSBServer1, synergyOSBServer2}. Does that look correct?
here is my jms xml file
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
*<connection-factory name="synergyConnectionFactory1">*
*<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
*<default-targeting-enabled>false</default-targeting-enabled>*
*<jndi-name>synergyConnectionFactory1</jndi-name>*
*<client-params>*
*<client-id-policy>Restricted</client-id-policy>*
*<subscription-sharing-policy>Exclusive</subscription-sharing-policy>*
*<messages-maximum>10</messages-maximum>*
*</client-params>*
*<transaction-params>*
*<xa-connection-factory-enabled>false</xa-connection-factory-enabled>*
*</transaction-params>*
*<load-balancing-params>*
*<load-balancing-enabled>true</load-balancing-enabled>*
*<server-affinity-enabled>false</server-affinity-enabled>*
*</load-balancing-params>*
*<security-params>*
*<attach-jmsx-user-id>false</attach-jmsx-user-id>*
*</security-params>*
*</connection-factory>*
<uniform-distributed-queue name="errorQ">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<jndi-name>errorQ</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-queue name="undlvQ">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<jndi-name>undlvQ</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
*<uniform-distributed-queue name="MM_gridQ0">*
*<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
*<default-targeting-enabled>false</default-targeting-enabled>*
*<jndi-name>MM_gridQ0</jndi-name>*
*<load-balancing-policy>Round-Robin</load-balancing-policy>*
*<forward-delay>5</forward-delay>*
*<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>*
*</uniform-distributed-queue>*
<saf-imported-destinations name="synergySAFImportedDest1">
<sub-deployment-name>synergySubDeploy1</sub-deployment-name>
<default-targeting-enabled>false</default-targeting-enabled>
<saf-queue name="gridQ0">
<remote-jndi-name>MB_gridQ0</remote-jndi-name>
<local-jndi-name>gridQ0</local-jndi-name>
<non-persistent-qos>At-Least-Once</non-persistent-qos>
<time-to-live-default>0</time-to-live-default>
<use-saf-time-to-live-default>false</use-saf-time-to-live-default>
<unit-of-order-routing>Hash</unit-of-order-routing>
</saf-queue>
<jndi-prefix>MB_</jndi-prefix>
<saf-remote-context>synergySAFContext1</saf-remote-context>
<saf-error-handling>synergySAFErrorHndlr1</saf-error-handling>
<time-to-live-default>0</time-to-live-default>
<use-saf-time-to-live-default>false</use-saf-time-to-live-default>
<unit-of-order-routing>Hash</unit-of-order-routing>
</saf-imported-destinations>
<saf-remote-context name="synergySAFContext1">
<saf-login-context>
<loginURL>t3://rdoelapp001013:7001</loginURL>
<username>weblogic</username>
<password-encrypted>{AES}z9VY/K4M7ItAr2Vedvhx+j9htR/HkbY2LRh1ED+Cz5Y=</password-encrypted>
</saf-login-context>
<compression-threshold>2147483647</compression-threshold>
</saf-remote-context>
<saf-error-handling name="synergySAFErrorHndlr1">
<policy>Log</policy>
<log-format xsi:nil="true"></log-format>
<saf-error-destination xsi:nil="true"></saf-error-destination>
</saf-error-handling>
</weblogic-jms>
Any help will be greatly appriciated
Edited by: 818591 on Feb 16, 2011 11:28 AM

I am not getting you here "the right approach is to make OSB run on the man server cluster and not on admin server. "
I have a jms proxy service that I created from admin console
And also I have gone thru the step 5 in the link below
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/deploy/config.html#wp1524235
If I am not wrong, the proxy service endpoint URI determines where it is pointing to. If it is a cluster environment, it should point to a clustered address
My proxy has below endpoint URI
jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
and rdoelapp001011:61703,rdoelapp001013:61703 is my cluster address
As per your suggestion "To fix your problem, *make osb to run on the cluster* and specify the same URL for the jms proxy service"
Could you please provide some instruction how would I "make osb jms proxy service to run in a cluster"
As a note, I have Q defined as a distributed Q and connection factory targets to the cluster. UDQ also targtes to the cluster.
Just for a testing I have created another manged server running local to the machine where my admin server is running
And I created a proxy by following steps as I mentioned above and with endpoint URI as below
jms://rdoelapp001011:61703,rdoelapp001013:61703,*rdoelapp001011:61700*/synergyConnectionFactory1/MM_gridQ0
where the new address of my cluster is rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700
It did create consumers in both the managed servers in the cluster that are running locally, but no consumers in the remote managed server.
So I am kind of leaning towards thinking that there is some incorrect setup for the remote managed server and may be admin server is not able to communicate to the remote server for some reason but not sure about it..
As a note the cluster is setup to communicate using "unicast" channel
and I created a channel in each manged server with the same name
here is the cluster configuration
<name>synergyCluster1</name>
<cluster-address>rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700</cluster-address>
<default-load-algorithm>round-robin</default-load-algorithm>
*<cluster-messaging-mode>unicast</cluster-messaging-mode>*
*<cluster-broadcast-channel>synergyChannel1</cluster-broadcast-channel>*
*<number-of-servers-in-cluster-address>3</number-of-servers-in-cluster-address>*
</cluster>
here are the twoOSBserver configuration
<server>
<name>synergyOSBServer1</name>
<machine xsi:nil="true"></machine>
<listen-port>61703</listen-port>
<cluster>synergyCluster1</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>weblogic.jms.saf</name>
<enabled>true</enabled>
</debug-scope>
<debug-jmssaf>true</debug-jmssaf>
<debug-saf-sending-agent>true</debug-saf-sending-agent>
</server-debug>
<listen-address>localhost</listen-address>
<network-access-point>
*<name>synergyChannel1</name>*
*<protocol>cluster-broadcast</protocol>*
*<listen-address>localhost</listen-address>*
*<listen-port>61702</listen-port>*
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
*<outbound-enabled>true</outbound-enabled>*
*<enabled>true</enabled>*
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<jta-migratable-target>
<user-preferred-server>synergyOSBServer1</user-preferred-server>
<cluster>synergyCluster1</cluster>
</jta-migratable-target>
</server>
<server>
<name>synergyOSBServer2</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine xsi:nil="true"></machine>
<listen-port>61703</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster>synergyCluster1</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>rdoelapp001013</listen-address>
<network-access-point>
*<name>synergyChannel1</name>*
*<protocol>cluster-broadcast</protocol>*
*<listen-address>rdoelapp001013</listen-address>*
*<listen-port>61702</listen-port>*
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
*<outbound-enabled>true</outbound-enabled>*
*<enabled>true</enabled>*
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<java-compiler>javac</java-compiler>
<jta-migratable-target>
<user-preferred-server>synergyOSBServer2</user-preferred-server>
<cluster>synergyCluster1</cluster>
</jta-migratable-target>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<server>
Edited by: 818591 on Feb 18, 2011 11:26 AM

Reg Load Balancing

Hi,
How to configure server side load balancing.
I saw two types Load based and Session based.
How to specify the options for the both
I know by setting parameter load_balance=on will enable in tnsnames.ora file.
whether above parameter enable client side load balancing or server side load balancing
Suggest me any document which explains both with example.
Thanks
Krishna

Hi Aman,
Your thoughts on the below Statements.
Setting the REMOTE_LISTENER parameter has the following effect -
The PMON process on that node will register with the remote listeners specified in the REMOTE_LISTENER value.
This means PMON process will update the remote listeners about the work load status on the local node.
When REMOTE_LISTENERS are set on all nodes, all PMON processes register with all other listeners.
When the client makes a connection and the connection goes to a specific listener (either using load_balance on or off),the listener that accepts the connection will check the load on all nodes to see which is the least loaded.
The listener is able to do this since PMON processes from all nodes have updated the listener about the statuses.and that listener will redirect the connection to the node with the least load and start a dedicated process on that node .
Now how does the PMON know which is the least loaded machine.
It gets the information from the FAN framework and load balance advisory.
FAN framework consists the following processes
MMON,PMON,ONS and AQ. (ONS is specific to Java clients and AQ is specific to ODI.Net clients)
Load Balancing advisory calculates the goodness of a node and forwards to MMON.
MMON builds the advisory and forwards it to PMON. And thus PMON is able to update all the listeners.
Setting the REMOTE_LISTENER parameter has the following effect -
The PMON process on that node will register with the remote listeners specified in the REMOTE_LISTENER value.
This means PMON process will update the remote listeners about the work load status on the local node.
When REMOTE_LISTENERS are set on all nodes, all PMON processes register with all other listeners.
When the client makes a connection and the connection goes to a specific listener (either using load_balance on or off),the listener that accepts the connection will check the load on all nodes to see which is the least loaded.
The listener is able to do this since PMON processes from all nodes have updated the listener about the statuses.and that listener will redirect the connection to the node with the least load and start a dedicated process on that node .
Now how does the PMON know which is the least loaded machine.
It gets the information from the FAN framework and load balance advisory.
FAN framework consists the following processes
MMON,PMON,ONS and AQ. (ONS is specific to Java clients and AQ is specific to ODI.Net clients)
Load Balancing advisory calculates the goodness of a node and forwards to MMON.
MMON builds the advisory and forwards it to PMON. And thus PMON is able to update all the listeners.
Regards
Krishna

NW04 Portal and Cisco Load balancer

Hi everybody,
does anyone have a similar landscape as I have?
Reverse Proxy - Cisco Content Switch Module for Load Balancing - two NW04 Portal Servers.
How did you configure the stickyness / Load balancing mechanism on the load balancer in order to get it running?
Cheers
Jochen

Hi,
Web AS Java issues a cookie called saplb.
You can check its value by connecting to the portal and then launching the command
"javascript:alert(document.cookie)"
within the browser. You will get a cookie value like
saplb_*=(J2EE6202500)6202551
The value in brackets determines the Instance; the second number equals the actual ClusterID (can also be found in the VisualAdmin. Usually 50 indicates the 1st server node, 51 the second one etc.
The saplb_*-cookie can be checked by the cisco see Cisco-Link above. Just configure the Cisco to be sticky on the instance number (value in the first brackets, in the example 6202500).
Several Customers do it like this, and actually the SAP Webdispatcher is also using this cookie to determine the instance to distribute the request to.
Good luck Bernhard

Load Balancer virtual URL not working with analytics page

We have configured Load Balancer virtual URL. But it is working for only iAS. We have Oracle Application Server 10.1.3
Our OBIEE is 10.1.3.4.1
Here is the virtual configuration
Listen 7877
+<VirtualHost default:7877>+
+# General setup for the virtual host+
DocumentRoot "/apps_base/obiee/ias/Apache/Apache/htdocs"
ServerName uat.bi.company.com
ServerAdmin [email protected]
ErrorLog "|/apps_base/obiee/ias/Apache/Apache/bin/rotatelogs /apps_base/obiee/ias/Apache/Apache/logs/error_log 43200"
TransferLog "|/apps_base/obiee/ias/Apache/Apache/bin/rotatelogs /apps_base/obiee/ias/Apache/Apache/logs/access_log 43200"
Port 443
+# SSL Engine Switch:+
+# Enable/Disable SSL for this virtual host.+
SSLEngine on
https://uat.bi.company.com -> WORKS great
https://uat.bi.company.com/em -> WORKS great
https://uat.bi.company.com/analytics -> page cannot be displayed
We have SSO configured. So i do get the SSO login page, but clicking on submit button, I get page cannot be displayed.
Everything works if I disable the load balancer virtual.
THe Load Balancer is configured to listen on 443 and then routes to 7877 on the physical server coorldas04.company.com
Can you assist in this one ??

Is this still a problem?

Apache 2 + Sun Java 8.1 load balancer connector dies under load

Similar Messages

Maybe you are looking for