Bpel cluster, soap adress in wsdl, soapSeverUrl, load balance - problem

Hello,
I've installed bpel into cluster of two nodes with RAC repository db behind.
I have followind problem ...
I want to loadbalance incomming requests.
Configuration description:
One public IP > load balancer > ( node1) or (node2) with private IPs.
My expectation was that parameter soapServerUrl ( set to loadbalancer address)
ensures that the address of load balancer will be inside wsdl in soap:address.
The real world situation is other :-(
In bpel console > processes > process WSDL sheet, WSDL location - here is the correct soapServerUrl
but inside the wsdl there isn't. There is node address inside wsdl.
So, was my expectation wrong?
If my expectation was wrong, is there any other solution?
How can I ensure that the address of loadbalancer will be inside the wsdl.
Karel

selfreply:
you have to re-deploy processes after you change soapServerUrl for a domain.
Karel

Similar Messages

BPEL Cluster: Failed to read wsdl

I want to start a bpel process over the dashboard from bpel pm.
If i click the bpel process on the dashboad, i get a timeout with the following error message:
Failed to read wsdl file at: "http://10.0.0.211:7778/orabpel/default/BPELCluster/1.0/BPELCluster?wsdl", caused by: java.net.SocketException. : Connection reset
But if i put the link into the same browser, i get the WSDL immediately.
10.0.0.211 is the ip of my load balancer....
Any comments?

I'm also facing the same exact error after clustering the BPEL Process Manager.
Were you able to solve this issue.
Please share your thoughts.

Cluster load balancing problems under heavy load.

          Hi,
          I am running 2 WLS 5.1 sp6 application servers on Solaris 7.
          2 Apache 1.3.12/Raven SSL webservers using the Raven proxy (also
          Solaris).
          My problem is this:
          The application appears to be load balancing and replicating
          session information fine under regular load. But when a heavy
          load is put on the system, load balancing seems to stop.
          One of the application servers processes all of the sessions
          while the other is just replicating session info. The CPU
          usage on the server doing all of the work was 60%, and on the
          secondary server it was only 2.5%.
          Do I have something set incorrect? I would think that if load
          balancing works for a small load on the system, it should be
          the same for a large load.
          Has anyone seen this type of behavior before?
          Thanks


1.5G of heap is quite huge. Take a thread dump when you see the slow down.
          Does each clients start a new session and maintain it for the duration of the test.
          There is no property called weblogic.cluster.bindAddr
          -- Prasad
          Nick Barbato wrote:
          > Hi,
          >
          > There are no 'timed out server" messages in the log. I don't think
          >
          > that is the problem because I can see the secondary server
          >
          > replicating session information.
          >
          > It is jdk1.2.2_005a. The java options I am using are:
          >
          > java $THREAD_ARG \
          > -ms1536m -mx1536m \
          > -classpath "$CYGENT_SYS_CP" \
          > -Dweblogic.class.path="$CYGENT_WLS_CP" \
          > -Dweblogic.system.home=$CYGENT_ROOT/runtime \
          > -Dweblogic.system.propertiesFile=$CYGENT_ROOT/runtime/conf/weblogic/weblogic.properties
          >
          > \
          > -Djava.security.manager \
          > -Djava.security.policy==$CYGENT_ROOT/runtime/conf/cygent.policy
          > \
          > -Dcygent.root=$CYGENT_ROOT/runtime \
          > -Dweblogic.cluster.enable=true \
          > -Dweblogic.cluster.name=mycluster \
          > -Dweblogic.cluster.bindAddr=166.37.216.142 \
          > -Dweblogic.cluster.multicastAddress=237.0.1.0 \
          > cygent.Server $CYGENT_ROOT/runtime/conf/
          >
          > Thanks,
          > Nick
          >
          > "Mike Reiche" <[email protected]> wrote:
          > >
          > >I've seen this before - when one WL instance drops out
          > >of the
          > >cluster.
          > >
          > >Look for 'Timed out server' messages in weblogic.log.
          > >
          > >What JDK are you using? What JVM options.
          > >
          > >Mike
          > >
          > >"Nick Barbato" <[email protected]> wrote:
          > >>
          > >>Hi,
          > >>
          > >>I am running 2 WLS 5.1 sp6 application servers on Solaris
          > >>7.
          > >>2 Apache 1.3.12/Raven SSL webservers using the Raven
          > >proxy
          > >>(also
          > >>Solaris).
          > >>
          > >>My problem is this:
          > >>The application appears to be load balancing and replicating
          > >>session information fine under regular load. But when
          > >>a heavy
          > >>load is put on the system, load balancing seems to stop.
          > >>One of the application servers processes all of the sessions
          > >>while the other is just replicating session info. The
          > >>CPU
          > >>usage on the server doing all of the work was 60%, and
          > >>on the
          > >>secondary server it was only 2.5%.
          > >>
          > >>Do I have something set incorrect? I would think that
          > >>if load
          > >>balancing works for a small load on the system, it should
          > >>be
          > >>the same for a large load.
          > >>
          > >>Has anyone seen this type of behavior before?
          > >>
          > >>Thanks
          > >

Load balancing problem

We need a load balancing setup that share the load for many web applications on multiple backend servers, but we don’t want the web apps to be activated on all backend servers at the same time. We want to configure all apps as “lazy” on all backend servers. They will then be activated when the first request to their DNS is made. Then the app is started on that backend server.
We have hundreds of apps and each backend server will become very slow if all apps are activated on all backend servers. The preferred solution would therefore be to not call all DNS names on all backend servers but to share the balance based on the DNS name in the requests. Sticky-session or sticky source-IP won’t be enough to solve this as they only stick to each user session.
If User-A request www.siteA.com he may be redirected to backend server 1 and then be kept there. But if User-B then requests the same www.siteA.com he may be redirected to backend server 2 and then be kept there. This means that the web application for siteA will be activated and loaded in both the backend servers. When we host hundreds of sites this will be a problem. We may have hundreds of backend servers but they will all end up loading all web apps over time and get out of memory.
The theory to get this work is a load balancer with the following logic:
1.     A request for a certain DNS comes in. For example: www.siteA.com
2.     Load balancer checks if this certain DNS has been redirected to a certain backend server before and if this server is alive
2.1.     (If not redirected before): Redirect the request to the backend server with least load. Store the selected backend route based on the DNS name.
2.2.     (If redirected before): Redirect the request to the assigned backend server for siteA.
3.     If a backend server is down then all DNS requests to this server will be redirected to another backend server with least load. All requests to these DNS names will be assigned to this backend server instead.
h3. Example of set up
Many DNS to one IP
192.168.1.1 www.siteA.com
192.168.1.1 www.siteB.com
192.168.1.1 www.siteC.com
Frontend load balancer
192.168.1.1 (load balancer)
Backend app servers
192.168.2.2 (App server 1)
192.168.2.3 (App server 2)
192.168.2.4 (App server 3)
h3. Snapshot of servers during load
App server 1
www.siteA.com (Activated)
www.siteB.com (Lazy)
www.siteC.com (Lazy)
App server 2
www.siteA.com (Lazy)
www.siteB.com (Activated)
www.siteC.com (Lazy)
App server 3
www.siteA.com (Lazy)
www.siteB.com (Lazy)
www.siteC.com (Activated)

Only from load balancing point of view cluster is not really needed.
apart from session replication and failover capabilities, few more benefits are there with clustering only if you are using a web server also.
Stuck threads can be due to lot's of problems like application issues, load issues etc, So first make sure you are getting stuck thread on both servers or only on one, if on one, then in this case your load balancing not working properly and sending more load to that server, and if you are getting stuck threads on both then try to add one more managed server.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com

Weblogic DB connection pool load balancing problem

hi all,
here is a strange issue. We have a clustered weblogic environment with2 servers. And the application is deployed to cluster. But strangely when we check the active connections for the connection pool that is being used by the application, we see that 2nd server has more connections when compared to 1st server, lets say 1st server has 4 active connections, 2nd server has 50 connections, What might be the problem.
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/jdbc-data-source" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/jdbc-data-source http://www.bea.com/ns/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
<name>##########</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@hostname:portnumber:Schema</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>#####</value>
</property>
<property>
<name>portNumber</name>
<value>#####</value>
</property>
<property>
<name>SID</name>
<value>######</value>
</property>
<property>
<name>serverName</name>
<value>hostname</value>
</property>
</properties>
<password-encrypted>##########</password-encrypted>
<use-xa-data-source-interface>false</use-xa-data-source-interface>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>75</max-capacity>
<capacity-increment>5</capacity-increment>
<shrink-frequency-seconds>900</shrink-frequency-seconds>
<highest-num-waiters>2147483647</highest-num-waiters>
<connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds>
<connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
<test-frequency-seconds>60</test-frequency-seconds>
<test-connections-on-reserve>true</test-connections-on-reserve>
<profile-harvest-frequency-seconds>300</profile-harvest-frequency-seconds>
<ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
<inactive-connection-timeout-seconds>0</inactive-connection-timeout-seconds>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<login-delay-seconds>0</login-delay-seconds>
<statement-cache-size>10</statement-cache-size>
<statement-cache-type>LRU</statement-cache-type>
<remove-infected-connections>true</remove-infected-connections>
<seconds-to-trust-an-idle-pool-connection>10</seconds-to-trust-an-idle-pool-connection>
<statement-timeout>-1</statement-timeout>
<profile-type>0</profile-type>
<pinned-to-thread>false</pinned-to-thread>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>##########</jndi-name>
</jdbc-data-source-params>
</jdbc-data-source>

are you using any front end web server or hardware load balancer ? verify your load balancing if it's happening or not properly between your clustered managed servers.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com/

HttpClusterServlet Load Balancing Problem

          Hi,
          I have a problem with LoadBalancing and HttpClusterServlet.
          I have 2 boxes, with a clustered application, deployed on 2 managed servers
          box 1 with adminServer and and a managed server (managed1)
          box 2 with second managed server (managed2)
          on box 1 I have another managed server, which hosts the HttpClusterServlet application
          The cluster is made up of managed1 & managed2, and httpClusterServlet is configured
          to send requests to boths the managed servers in the cluster.
          When I run some tests against the httpClusterServlet web application to see how
          it load-balances requests, I can see that all the requests are redirected just
          to managed1,
          on the same machine.
          If I stop managed1, and run some tests, I can see that httpCluster every time
          tries to contact managed1 first, and since it's down, sends the requests to managed2(handles
          failover correctly).
          If I move the httpClusterServlet application to another box, let's call it box
          3, and re run the tests, it will load-balances the requests between managed1 (box1)
          and managed2(box2) correctly.
          I would like to know if httpClusterServlet has some kind of "server affinity"
          logic (?) or I'm missing something in the cluster configuration (even if I can't
          see clearly how the cluster configuration could affect things, since HttpServlet,
          which is not in the cluster, just should route
          requests to the specified servers in round-robin fashion, I guess)
          Someone in previous posts pointed out http session issues, is it true? and so,
          why?
          Sorry for the far too long post,
          thanks in advance,
          Thomas


Only from load balancing point of view cluster is not really needed.
apart from session replication and failover capabilities, few more benefits are there with clustering only if you are using a web server also.
Stuck threads can be due to lot's of problems like application issues, load issues etc, So first make sure you are getting stuck thread on both servers or only on one, if on one, then in this case your load balancing not working properly and sending more load to that server, and if you are getting stuck threads on both then try to add one more managed server.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com

WebCache load balancing problem

I am having a problem with Web Cache distributing load to 4 origin servers. It turns out that one Origin server received 24 times less requests than another, despite the fact that they configured the same way.
here is my configuration of production site:
Radware load balancer ( LB) with cyclic algoritm received requests from users.
LB distrubuted request to 4 dedicated webcache servers running as a one clusted with the same number for capacity for each server.
This cluster in turn forward missed requests to 4 application servers (Oracle HTTP and OC4j running J2EE apps). Those 4 servers connected in 2 clusters with 2 servers each. Session failover is disabled.
The problem is that one server has 60 session and another only 1.
Here is some statistics I collected from WebCache admin pages:
Request served to origin servers:
     cache1     cache2     cache3     cache4     total
serv5     1095     704     1102     8206     11107
serv6     2190     9414     9829     3404     24837
serv7     58     481     465     92     1096
serv8     10113     1145     1102     934     13294
as you may see serv7 does not get his share of requests.
Does anybody experienced the same problem or have any idea where to look for answer?
thanks

Does your application require session binding?
You may want to contact Oracle Support to review your configuration setttings.

CUCM Load Balancing Problem

Hi All, I have two CUCM 6.1.3 ( I Pub & 1 Sub). All phones registers with sub and all phones use pub for tftp. I am trying to force some phones to register with pub but have no success even new CM group created has pub as first choice & sub as second choice. For your information during Failover in the past phones used to register with publisher and currently there are some ATA devices registered with pub for some reason. Any Ideas ???

Hi Mike,
Hope all is well my friend!
Just a note here, did you change the reference to the CCM Group in the Device Pool that phones in question are using? After changing the reference you will reset all the phones to push them over to the Pub
You should keep in mind that in the SRND for CUCM the recommendation is that IP Phones are not registered on the Publisher. The Publisher should be kept for dB processing etc. It is a "best practice" to have at least 3 servers in your cluster (1 Pub and 2 Subs). When you define your Calmanager Groups you might setup Group 1 as;
Sub-1 (Primary)
Pub
And Group 2 as;
Pub (Primary)
Sub-1
In Group 1 the Pimary Callmanager is Sub-1 and in Group 2 the Primary Callmanager is the Pub. This is in reference to the phones registered with each Callmanager Group (with the highest one listed being the Primary or "First choice")
**This is not related to the Publisher (Primary Node) and its functionality in any way The wording can be a tad confusing at times.
This relationship is built via the Callmanager Group and Device Pool that the phones belong to.
You can specify where a phone registers by assigning it to a specific Device Pool this in turn will look at a Callmanager Group that lists a Primary, Secondary and Tertiary Callmanager server.
Here is some related info;
Cisco Unified CallManager groups and device pools represent logical groupings of devices that you can arrange in any way that you want. For ease of administration, make sure that all the devices in a group or pool share a common and easily identified characteristic, such as their physical location on the network.
You can also use Cisco Unified CallManager groups to establish redundancy (backup call processors) for the primary Cisco Unified CallManager in the group. A Cisco Unified CallManager group comprises an ordered list of up to three Cisco Unified CallManager servers. During normal operation, the first (primary) Cisco Unified CallManager in the group controls all device pools and devices that are assigned to that group. If the primary Cisco Unified CallManager in a group fails, control of the device pools and devices that are registered with the primary Cisco Unified CallManager transfers to the next Cisco Unified CallManager in the group list.
Cisco Unified CallManager Groups
A Cisco Unified CallManager group comprises a prioritized list of up to three Cisco Unified CallManagers. The first Cisco Unified CallManager in the list serves as the primary Cisco Unified CallManager for that group, and the other members of the group serve as secondary (backup) Cisco Unified CallManagers.
Cisco Unified CallManager groups associate with devices through device pools. Each device belongs to a device pool, and each device pool specifies the Cisco Unified CallManager group for all of its devices.
Cisco Unified CallManager Groups:
Call processing load balancing You can configure device pools and Cisco Unified CallManager groups to distribute the control of devices across multiple Cisco Unified CallManagers. These should be Subscriber servers
Device Pools
Device pools provide a convenient way to define a set of common characteristics that can be assigned to devices.
Hope this helps!
Rob

RV320, load balancing problem

Hi,
How do I force the router to use WAN1 till it's saturated, and ther switch to WAN2 when needed. I've already configured the bandwidth correctly for each WAN, but it seems that some clients use WAN1, others use WAN2, disregarding the fact that they should use WAN1 as primary and the bandwidth it's not saturated by any other client.

Only from load balancing point of view cluster is not really needed.
apart from session replication and failover capabilities, few more benefits are there with clustering only if you are using a web server also.
Stuck threads can be due to lot's of problems like application issues, load issues etc, So first make sure you are getting stuck thread on both servers or only on one, if on one, then in this case your load balancing not working properly and sending more load to that server, and if you are getting stuck threads on both then try to add one more managed server.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com

Load Balancing Problem with WLS6.1

          Hi,
          I have 4 Instances of Weblogic servers two instance per box with Clustered. The
          admin server is running in the first box. While stress testing it seems all the
          loads are going to one instance and other instances are almost idle.
          In the Secondary Group, i have given the name of the other instance on the same
          server. I'm running weblogic in Solaris with SP3.
          Can anyone suggest why loadbalancing doesn't work.


Typically, load balancing will work unless there is a problem with the
          clusters seeing each other. Therefore first make sure that the managed
          server has joined the cluster.
          Other things to look at are the __WebLogicBridgeConfig (see WLS plugin
          documents) to confirm that there is a primary and secondary.
          The above assumes Servlet load balancing, for objects check the
          deployment descriptors.
          Diwan Mohideen wrote:
          >
          > Hi,
          >
          > I have 4 Instances of Weblogic servers two instance per box with Clustered. The
          > admin server is running in the first box. While stress testing it seems all the
          > loads are going to one instance and other instances are almost idle.
          >
          > In the Secondary Group, i have given the name of the other instance on the same
          > server. I'm running weblogic in Solaris with SP3.
          >
          > Can anyone suggest why loadbalancing doesn't work.

Wgate Load Balancing Problem

Hi Folks,
We have ITS 6.20 Patch level 33 installed which connects to our R/3 system. We are trying to add multiple Agate servers (not multiple Agate processes) to one Wgate. We installed agates on two hosts, host1 and host2. We then installed wgate on host1 which we connected during the time of installation to agate on host2. It connected fine and we were able to get the webgui and also able to login to R/3 system. At that time we had problem in going to native ADM instance as we were getting http 500 error (we had re-installed ADM instance on both the hosts after the whole exercise of installating agate and wgate). Hoping that we can solve native ADM problem later, we added the the second agate which is on hosts1(the same host on which wgate is) by adding the entry for agate 2 in the wgate registry xml file.
<key name="Agates">
      <key name="Agate1">
       <value name="Host" type="text">host2</value>
       <value name="PortAGate" type="text">sapavw00_******</value>
       <value name="PortMManager" type="text">sapavwmm_******</value>
       <value name="Type" type="text">1</value>
       <value name="SncNameAGate" type="text"/>
       <value name="SncNameWGate" type="text"/>
       <value name="MultiProcess" type="text">no</value>
       <value name="Available" type="text">yes</value>
      </key>
      <key name="Agate2">
       <value name="Host" type="text">host1</value>
       <value name="PortAGate" type="text">sapavw00_******</value>
       <value name="PortMManager" type="text">sapavwmm_******</value>
       <value name="Type" type="text">1</value>
       <value name="SncNameAGate" type="text"/>
       <value name="SncNameWGate" type="text"/>
       <value name="MultiProcess" type="text">no</value>
       <value name="Available" type="text">yes</value>
      </key>
The second agate added fine and is doing load balancing as well as we can see requests getting routed to both the agate in the load balancing screen. However we are not able to access the global.srvc file under configuration->Performance->global services->All settings as we are getting the following message:
Error loading service file "global.srvc"!
Also when we go to services under configuration, we are getting a message "error accessing services directory!"
In default R/3 system also all the fields are empty although we had given the application server details while installing both the agates.
We are getting the below messages in diagnostics.log file:
2010-11-22T12:30:04.401 --- log opened -
A 2010-11-23T13:55:53.346 [agate,sapdiag ] 00, s00000000061DB140, CsRead returned rd=-100
2010-11-23T14:17:06.863 --- log closed -
2010-11-23T14:17:07.753 --- log opened -
A 2010-11-23T14:30:48.618 [agate,sapdiag ] 00, s00000000061DB220, Cannot handle request from login
A 2010-11-23T14:38:45.615 [agate,        ] 00, s0000000000000000, WorkDoGetReq: ContReceiveContainer() failed, rc=0xffffffff
A 2010-11-23T14:38:45.615 [agate,        ] 00, s0000000000000000, WorkDoWork: WorkDoGetReq() failed, rc=0xffffffff
A 2010-11-23T14:38:45.677 [agate,sapxgdk ] 00, s0000000000000000, ContSendContainer: FAILED, send length is 0
A 2010-11-23T14:38:50.958 [agate,        ] 00, s0000000000000000, WorkDoGetReq: ContReceiveContainer() failed, rc=0xffffffff
A 2010-11-23T14:38:50.958 [agate,        ] 00, s0000000000000000, WorkDoWork: WorkDoGetReq() failed, rc=0xffffffff
A 2010-11-23T14:38:50.974 [agate,sapxgdk ] 00, s0000000000000000, ContSendContainer: FAILED, send length is 0
Please let me know if this procedure of adding the agate was wrong or there are some parameter settings that we may have missed. Would it have been better to go for a single host wgate+agate installation on host1 and then add agate2 on host2?

Hi Edgar,
Thanks for the reply. I had re-installed ADM instance on both the hosts after the whole exercise of installing agate and wgate.
Anyways, Now we have uninstalled the earlier instances on both hosts and installed wgate+agate on host1 as a single host installation and agate2 on host2. Then we added agate2 to wgate1 and load balancing is working fine. Now the issue of not being able to access the service file and directories, etc has also been resolved. The only problem that remains is that we are not able to go into the native ADM. We get a http 500 error, although the redirect URL is correct. Is the any additional setting required for that to happen?

ACE Load Balancing Problem

Hi,
I have ACE 4701 with c4710ace-mz.A3_2_2.bin image. In the current setup ACE is located in the center of network where all the WAN, Intenret and LAN is connected and ACE has default towards Internet and All other segment has default route towards ACE appliance. ACe is only redirecting the port 80 traffic to my Proxy server and bypass my lan subnet on port 80.
Internet
i
i
i
i
i
ACE--------------------------------WAN
i
i
i
i
LAN
I want to use ACE for the load balancing of two servers. Today I did the load balancing configuration but as soon as I applied the policy map on the interface vlan 200 and 300, my complete network reachability went down. When I remove the policy my network came back to normal.
192.168.200.66 FAX Server-1
192.1168.200.67 FAX Server-2
192.168.200.65   Virtual IP address
Attached is the configuration that I did on ACE for the load balancing and below is the current configuration of the ACE appliance.
access-list acl-in remark ACCESS LIST FOR ACE-INSIDE
access-list acl-in line 1 extended permit ip any any
access-list acl-out remark ACCESS LIST FOR ACE-OUTSIDE
access-list acl-out line 1 extended permit ip any any
access-list acl-proxy remark ACCESS LIST FOR PROXY SEGMENT
access-list acl-proxy line 1 extended permit ip any any
access-list acl-wan remark ACCESS LIST FOR WAN SEGMENT
access-list acl-wan line 1 extended permit ip any any
probe tcp PROBE_5050
port 5050
interval 15
passdetect interval 60
open 1
probe tcp PROBE_5101
port 5101
interval 15
passdetect interval 60
open 1
probe tcp PROBE_TCP
port 80
interval 15
passdetect interval 60
open 1
parameter-map type http PARAMAP_CASE
case-insensitive
no persistence-rebalance
rserver host RS_BCPR01
ip address 192.168.0.103
inservice
rserver host RS_BCPR02
ip address 192.168.0.104
inservice
rserver host RT_fax1
description Right Fax Server-1
ip address 192.168.200.66
rserver host RT_fax2
description Right Fax Server-2
ip address 192.168.200.67
serverfarm host SF_BCPR
transparent
probe PROBE_5050
probe PROBE_5101
probe PROBE_TCP
rserver RS_BCPR01
inservice
rserver RS_BCPR02
inservice
serverfarm host SF_RT_fax
rserver RT_fax1
rserver RT_fax2
sticky ip-netmask 255.255.255.255 address source STICKY-SOURCE
replicate sticky
serverfarm SF_BCPR
sticky ip-netmask 255.255.255.255 address source FAX-STICKY
replicate sticky
serverfarm SF_RT_fax
class-map type management match-any CM_ALL
2 match protocol snmp any
3 match protocol http any
4 match protocol https any
5 match protocol icmp any
6 match protocol telnet any
class-map match-any CM_BYPASS_FOR_LAN
3 match virtual-address 100.1.1.0 255.255.255.0 tcp eq www
8 match virtual-address 10.0.0.0 255.0.0.0 tcp eq www
9 match virtual-address 172.16.0.0 255.255.0.0 tcp eq www
10 match virtual-address 192.168.0.0 255.255.0.0 tcp eq www
class-map match-any CM_BYPASS_SUBNET
9 match virtual-address 100.0.0.0 255.0.0.0 tcp eq www
13 match virtual-address 10.0.0.0 255.0.0.0 tcp eq www
14 match virtual-address 172.16.0.0 255.255.0.0 tcp eq www
15 match virtual-address 192.168.0.0 255.255.0.0 tcp eq www
class-map match-any CM_IM
2 match virtual-address 0.0.0.0 0.0.0.0 tcp eq 5050
3 match virtual-address 0.0.0.0 0.0.0.0 tcp eq 1080
4 match virtual-address 0.0.0.0 0.0.0.0 tcp eq 5101
class-map match-all CM_SF_BCPR
255 match virtual-address 0.0.0.0 0.0.0.0 tcp eq www
class-map match-any RT_FAX
2 match virtual-address 192.168.200.65 0.0.0.0 any
policy-map type management first-match PM_ALL
class CM_ALL
permit
policy-map type loadbalance http first-match PM_L7_BYPASS_FOR_LAN_HTTP
class class-default
forward
policy-map type loadbalance http first-match PM_L7_BYPASS_HTTP
class class-default
forward
policy-map type loadbalance first-match PM_LB_RT_FAX
class class-default
sticky-serverfarm FAX-STICKY
policy-map type loadbalance http first-match PM_LB_SF_BCPROXY
class class-default
sticky-serverfarm STICKY-SOURCE
policy-map multi-match PM_BYPASS_FOR_LAN_HTTP
class CM_BYPASS_FOR_LAN
loadbalance vip inservice
loadbalance policy PM_L7_BYPASS_FOR_LAN_HTTP
policy-map multi-match PM_BYPASS_HTTP
class CM_BYPASS_SUBNET
loadbalance vip inservice
loadbalance policy PM_L7_BYPASS_HTTP
policy-map multi-match PM_MAIN_BCPROXY
class CM_SF_BCPR
loadbalance vip inservice
loadbalance policy PM_LB_SF_BCPROXY
loadbalance vip icmp-reply active
appl-parameter http advanced-options PARAMAP_CASE
class CM_IM
loadbalance vip inservice
loadbalance policy PM_LB_SF_BCPROXY
policy-map multi-match PM_RT_FAX
class RT_FAX
loadbalance vip inservice
loadbalance policy PM_LB_RT_FAX
service-policy input PM_ALL
interface vlan 100
description FW-INSIDE CONTEXT RACK1
ip address 192.168.0.5 255.255.255.224
alias 192.168.0.11 255.255.255.224
peer ip address 192.168.0.6 255.255.255.224
mac-address autogenerate
no icmp-guard
access-group input acl-out
no shutdown
interface vlan 200
description WAN-VLAN CONTEXT RACK1
ip address 192.168.0.33 255.255.255.224
alias 192.168.0.43 255.255.255.224
peer ip address 192.168.0.34 255.255.255.224
mac-address autogenerate
access-group input acl-wan
service-policy input PM_BYPASS_HTTP
service-policy input PM_MAIN_BCPROXY
no shutdown
interface vlan 300
description ACE-INSIDE CONTEXT RACK1
ip address 192.168.0.65 255.255.255.224
alias 192.168.0.73 255.255.255.224
peer ip address 192.168.0.66 255.255.255.224
mac-address autogenerate
access-group input acl-in
service-policy input PM_BYPASS_FOR_LAN_HTTP
service-policy input PM_BYPASS_HTTP
service-policy input PM_MAIN_BCPROXY
no shutdown
interface vlan 301
description BC-VLAN CONTEXT RACK1
ip address 192.168.0.97 255.255.255.224
alias 192.168.0.107 255.255.255.224
peer ip address 192.168.0.98 255.255.255.224
mac-address autogenerate
access-group input acl-proxy
no shutdown
ft track interface TRACKING_FOR_FT_VLAN
track-interface vlan 300
peer track-interface vlan 300
priority 255
peer priority 255
ip route 0.0.0.0 0.0.0.0 192.168.0.1
Please help me out what i am missing. Is there any limitation on policy map or my bypass subnet list is creating problem.

I did these changes this time nothing disconnected but I am not able to do the Remote desktop on the virtual IP address. Real IP has Remote desktop enabled even VIP is not ping able for me.
rserver host RT_fax1
description Right Fax Server-1
ip address 192.168.200.66
inservice
rserver host RT_fax2
description Right Fax Server-2
ip address 192.168.200.67
inservice
serverfarm host SF_RT_fax
rserver RT_fax1
    inservice
rserver RT_fax2
    inservice
policy-map type loadbalance rdp first-match PM_LB_RT_FAX
class class-default
    serverfarm SF_RT_fax
policy-map multi-match PM_RT_FAX
class RT_FAX
    loadbalance vip inservice
    loadbalance policy PM_LB_RT_FAX
    loadbalance vip icmp-reply active
interface vlan 200
description WAN-VLAN CONTEXT RACK1
ip address 192.168.0.33 255.255.255.224
alias 192.168.0.43 255.255.255.224
peer ip address 192.168.0.34 255.255.255.224
mac-address autogenerate
access-group input acl-wan
service-policy input PM_BYPASS_HTTP
service-policy input PM_MAIN_BCPROXY
service-policy input PM_RT_FAX
no shutdown
interface vlan 300
description ACE-INSIDE CONTEXT RACK1
ip address 192.168.0.65 255.255.255.224
alias 192.168.0.73 255.255.255.224
peer ip address 192.168.0.66 255.255.255.224
mac-address autogenerate
access-group input acl-in
service-policy input PM_BYPASS_FOR_LAN_HTTP
service-policy input PM_BYPASS_HTTP
service-policy input PM_MAIN_BCPROXY
service-policy input PM_RT_FAX
no shutdown
But nothing is working for me. Please help me out. This time i didnt configure the sticky. But in real I will go with sticky and complete IP protocol will be use a VIP. Please help me out.

Load Balance Problem in Oracle RAC 10.2.0.4 (two nodes with CRS)

Hi all,
I have an Oracle RAC 10.2.0.4 with two nodes and I'm having problems with sessions load balance.
The problem is that all connections are going to the node which is enabled as 'master' in RAC, the node who has located .db resource in CRS.
If .db resource is located in node1 all connections are made in node1. In the same way, all connections are made in node2 when .db resource from CRS stack is located in node2.
The connections are made by a pool in Tomcat 6 using RAC service for made the connections.
Any idea?
Thanks in advance.
Here is an example of my net configuration:
listener.ora in node1:
LISTENER_RAC_NODE1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1_vip)(PORT = 1525)(IP = FIRST))
(ADDRESS = (PROTOCOL = TCP)(HOST = node1)(PORT = 1525)(IP = FIRST))
tnsnames in node1:
LISTENERS_RAC =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1_vip)(PORT = 1525))
(ADDRESS = (PROTOCOL = TCP)(HOST = node2_vip)(PORT = 1525))
NODE1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1_vip)(PORT = 1525))
(ADDRESS = (PROTOCOL = TCP)(HOST = node1)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = rac)
(INSTANCE_NAME = rac1)
RAC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1_vip)(PORT = 1525))
(ADDRESS = (PROTOCOL = TCP)(HOST = node2_vip)(PORT = 1525))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = rac)
********************************************************

It is my fault.
It was the connection service. I had one one with preferred option and one without it. Now is working well.

CSS load balancing problem

Hi,
I have two CSS that I use to load balance RDP connections to two WTS servers. I dont have switch behind CSS so they are connected back-to-back via cable. All server facing ports (including back-to-back ports) are in the same VLAN.
CSS1 is primary for the VIP address and for redundant interface address, and CSS2 is standby.
So, when I connect WTS-1 to CSS-1 and WTS-2 to CSS-2, CSS1 sees both services as active and everything seems fine. If WTS-2 is disconnected, WTS2 service on CSS1 is down etc.
In sticky table, I can see that CSS1 is load balancing request to both servers, but the problem is that only RDP connections to WTS-1(server directly connected to CSS1) work fine , and connections that are load balanced to WTS-2 are dropped??? Direct RDP connection to WTS-2 IP works fine.
If I connect WTS-2 to CSS1, so both WTS servers are connected to CSS1 everything works fine.
Can anyone tell what can be wrong?
Configurations are in the attachment.
Thanks for help.
Regards,
Branimir

try the command 'ip uncond' on both CSS.
It will guarantees that the response from WTS-2 comes back to CSS1.
Gilles.

Oracle RAC - Load Balancing Problem

Our J2EE application transactions (Container-managed) are using MULTIPLE database connections to complete one business transaction.
Recently we swiched to below Oracle RAC configuration, and it is creating problems.
BEA 8.1 SP5 Multi Pools
Oracle 9i RAC (2 instances) : Active - Active
Algorithm : Load Balancing
Driver (JDBC) : Oracle 10g Release 1 Thin Driver
non-XA transactions
Looks like when LB algorithm is chosen, the load balacing is only **connection-aware** and NOT **transaction-aware**. Because of this, the application gets one connection from one RAC instance, and other from other instance is creating problems.
Is there any work-around exist for this problem?
If we chose, HIGH_AVAILABILTY algorithm, everything is fine. But we would like to make use of both instances.

Srinivas Chintala wrote:
Hello Joe,
Here is the configuration:
<JDBCConnectionPool DriverName="oracle.jdbc.OracleDriver"
InitialCapacity="10" MaxCapacity="30" Name="rac_node1"
PasswordEncrypted="{3DES}5M6WvgV8GsA=" Properties="user=apps"
StatementCacheSize="20" Targets="app_cluster"
TestConnectionsOnCreate="true" TestConnectionsOnRelease="true"
TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@usplgmnvmdb001.iweb.com:1521:prod_1"/>
<JDBCConnectionPool DriverName="oracle.jdbc.OracleDriver"
InitialCapacity="10" MaxCapacity="30" Name="rac_node2"
PasswordEncrypted="{3DES}5M6WvgV8GsA=" Properties="user=apps"
StatementCacheSize="20" Targets="app_cluster"
TestConnectionsOnCreate="true" TestConnectionsOnRelease="true"
TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@usplgmnvmdb002.iweb.com:1521:prod_2"/>
<JDBCMultiPool AlgorithmType="Load-Balancing" Name="appmutlipool"
PoolList="rac_node1,rac_node2" Targets="app_cluster"/>
<JDBCDataSource JNDIName="appdatasource" Name="AppDatasource"
PoolName="appmutlipool" Targets="app_cluster"/>
ChintalaHi, OK, that looks fine, except:
1 - I would define the initial and max capacity = 30, for performance and stability.
2 - For more performance, turn off test-on-release. It's a waste of cycles.
3 - You can change your TestTableName to "SQL BEGIN NULL; END;" which goes
even faster than "select 1 from dual".
And the main problem is:
4 - Your JDBCDataSource doesn't seem to be a transactional one, so any
application code that gets connections from that, will get independent
connections each time, and their work will not be included in any WLS
controlled transactions. You want to make/use a JDBCTxDataSource.
Joe

Bpel cluster, soap adress in wsdl, soapSeverUrl, load balance - problem

Similar Messages

Maybe you are looking for