Session Stickiness

Can anyone advise if I can do this with Vshield? I am getting thins from a developer hosting on some servers in our data center.
We need to maintain session stickiness for users as they switch back and forth between http and https. Is it possible to do this with a method other than IP hash? We would like to avoid IP hash because of concerns of it not working for companies with multiple gateways/proxies and/or mobile users who may switch networks during a session.
Thank you in advance
Todd

Hello,
If they are talking about a web server session, then that is entirely up to the web server unless you are using vCNS load balancing, then I do not think so. Session stickiness between protocols I do not think is supported but this is something you will have to test. The best thing to do in this case is attempt it, and see if things work as the developer expected. If in the webserver, that is a webserver issue, in the LB, then a vCNS issue.
Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009-2015
Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.
Virtualization and Cloud Security Analyst: The Virtualization Practice, LLC -- vSphere Upgrade Saga -- Virtualization Security Round Table Podcast

Similar Messages

Session Stickiness Issue

Hi All,
I am facing session stickiness issue where we have four webserver instances and six weblogic instances.
If you see in the failure logs the JVM ID generated by the cookie is 1872775671 but the plugin is routing the request to 923706867.Please find below
Please find the success and failure logs below
Proxy Error Log :
================New Request: [amserver/UI/Login] =================
Wed Mar 20 15:01:10 2013 <202911363806070191> Uri as read from rq (request) data structure /amserver/UI/Login
Wed Mar 20 15:01:10 2013 <202911363806070191> Uri after pathTrim /amserver/UI/Login
Wed Mar 20 15:01:10 2013 <202911363806070191> Uri resolved to /amserver/UI/Login?module=GMACLoginModule&org=branch
Wed Mar 20 15:01:10 2013 <202911363806070191> resolveRequest return code is [0]
Wed Mar 20 15:01:10 2013 <202911363806070191> URI=[amserver/UI/Login?module=GMACLoginModule&org=branch]
Wed Mar 20 15:01:10 2013 <202911363806070191> INFO: SSL is not configured
Wed Mar 20 15:01:10 2013 <202911363806070191> Found cookie from cookie header: JSESSIONID=RKHWGqJvmJGWgZ9YdqywsXBLRd7QtMGX1Qr1yTmNTn0Kcdq0M0xq!-1872775671
Wed Mar 20 15:01:10 2013 <202911363806070191> Parsing cookie JSESSIONID=RKHWGqJvmJGWgZ9YdqywsXBLRd7QtMGX1Qr1yTmNTn0Kcdq0M0xq!-1872775671
Wed Mar 20 15:01:10 2013 <202911363806070191> getpreferredServersFromCookie: [-1872775671]
Wed Mar 20 15:01:10 2013 <202911363806070191> primaryJVMID: [-1872775671]
secondaryJVMID: []
Wed Mar 20 15:01:10 2013 <202911363806070191> No of JVMIDs found in cookie: 1
Wed Mar 20 15:01:10 2013 <202911363806070191> Trying to locate Primary or Secondary using SrvrInfo with JVMID: 923706867
Wed Mar 20 15:01:10 2013 <202911363806070191> getPreferredFromCookie: Start Position is 0, listLen is 1
Wed Mar 20 15:01:10 2013 <202911363806070191> getPreferredFromCookie: Either JVMIDs not set or they are stale. Will try to get JVMIDs from WLS
Wed Mar 20 15:01:10 2013 <202911363806070191> initJVMID: Iterating SrvrList from position 0
Wed Mar 20 15:01:10 2013 <202911363806070191> ======internal request /bea_wls_internal/WLDummyInitJVMIDs======
initJVMID: Trying Host[10.13.52.81] Port[7005] SecurePort[7006] useSSL [0] ioTimeout [30] socketTimeout [10]
Wed Mar 20 15:01:10 2013 <202911363806070191> INFO: New NON-SSL URL
Wed Mar 20 15:01:10 2013 <202911363806070191> Connect returns -1, and error no set to 245, msg 'Operation now in progress'
Wed Mar 20 15:01:10 2013 <202911363806070191> EINPROGRESS in connect() - selecting
Wed Mar 20 15:01:10 2013 <202911363806070191> Local Port of the socket is 63476
Wed Mar 20 15:01:10 2013 <202911363806070191> Remote Host 10.13.52.81 Remote Port 7005
Wed Mar 20 15:01:10 2013 <202911363806070191> URL::sendHeaders(): meth='HEAD' file='/bea_wls_internal/WLDummyInitJVMIDs' protocol='HTTP/1.0'
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[Connection]=[Close]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Wed Mar 20 15:01:10 2013 <202911363806070191> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 400 Bad Request]
Wed Mar 20 15:01:10 2013 <202911363806070191> URL::parseHeaders: StatusLine set to [400 Bad Request]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[Date]=[Wed, 20 Mar 2013 19:01:10 GMT]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[Content-Length]=[897]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[Content-Type]=[text/html]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[X-WebLogic-Cluster-Hash]=[7GHstOoW2dPEsRHcWrZe05SfKAc]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[X-WebLogic-Cluster-List]=[923706867!168637521!7005!7006]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from WLS:[Connection]=[Close]
Wed Mar 20 15:01:10 2013 <202911363806070191> parsed all headers OK
Wed Mar 20 15:01:10 2013 <202911363806070191> initJVMID: Received the same cluster-list. Returning with no preferred servers found.
Wed Mar 20 15:01:10 2013 <202911363806070191> .....internal request /bea_wls_internal/WLDummyInitJVMIDs.....processed
Wed Mar 20 15:01:10 2013 <202911363806070191> getPreferredFromCookie: Found 0 servers
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[accept]=[image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */*]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[referer]=[https://capacity.dealerservices.ally.com/userprovisioning/jsp/autoSubmit.jsp?lang=en-us&source=MigratedLoginWidget&userType=branch&process=login]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[accept-language]=[en-US]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[user-agent]=[Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; BTRS99959; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8; .NET4.0C; InfoPath.3)]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[accept-encoding]=[gzip, deflate]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[host]=[gdpcapacity.gmacbranch.gmac.gm.com]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[cache-control]=[no-cache]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[cookie]=[s_pers=%20s_ts%3D%255B%255B%2527BRA0006T%2527%252C%25271362265430952%2527%255D%252C%255B%2527BRA0005T%2527%252C%25271363804235955%2527%255D%255D%7C1521570635955%3B%20s_nr%3D1363805063050-Repeat%7C1366397063050%3B; Locale=en-us; MasterCookie=MasterCookie; GDP_screenHeight=768; GDP_screenWidth=1366; GDP_browserType=Microsoft%20Internet%20Explorer; GDP_browserVersion=4.0%20%28compatible%3B%20MSIE%208.0%3B%20Windows%20NT%206.1%3B%20Trident/4.0%3B%20BTRS99959%3B%20SLCC2%3B%20.NET%20CLR%202.0.50727%3B%20.NET%20CLR%203.5.30729%3B%20.NET%20CLR%203.0.30729%3B%20Media%20Center%20PC%206.0%3B%20MS-RTC%20LM%208%3B%20.NET4.0C%3B%20InfoPath.3%29; GDP_operatingSystem=Win32; GDP_userAgent=Mozilla/4.0%20%28compatible%3B%20MSIE%208.0%3B%20Windows%20NT%206.1%3B%20Trident/4.0%3B%20BTRS99959%3B%20SLCC2%3B%20.NET%20CLR%202.0.50727%3B%20.NET%20CLR%203.5.30729%3B%20.NET%20CLR%203.0.30729%3B%20Media%20Center%20PC%206.0%3B%20MS-RTC%20LM%208%3B%20.NET4.0C%3B%20InfoPath.3%29; JSESSIONID=RKHWGqJvmJGWgZ9YdqywsXBLRd7QtMGX1Qr1yTmNTn0Kcdq0M0xq!-1872775671; ObSSOCookie=tKGxD0YS6sUw8kyVwfVBNujGihNvtG5GlUrYljs%2F3fngJbUm4%2B1bA6FpLn3LEESIpQsqwhjMDZODuautF%2B7zHKXypTkT%2Fn8DwdGn%2FYZOJK49wBTU511DfkqBmqBMsGjSM42jobA5gSQ672vUQskytWaJc4tZQC7MDLOGPEJf%2Bwc%2BVtXRi1%2FRGI4ql8jQpyWSJP6ImkHwt6QNig3Vlyt9BLZws6vvgHulULaxuA%2BXfUZ4fkVaVwN35tAmWorUa1ODiORCWhVSrZybMhTk53NsjT%2FdOaXFLZM4wcj6PKVkeG1UtZVfoNuVw8LBBVd5ave0]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[gmacdealer_groups]=[smartcash:scsupervisor:branch:us:en-us:EOAdminUS:]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[HTTP_OBLIX_UID]=[cbrus16]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs from Client:[HTTP_OBLIX_UID]=[cbrus16]
Wed Mar 20 15:01:10 2013 <202911363806070191> attempt #0 out of a max of 5
Wed Mar 20 15:01:10 2013 <202911363806070191> Server details are ''/0/0
Preferred server not set or was marked bad, checking next preferred server
Wed Mar 20 15:01:10 2013 <202911363806070191> Server details are ''/0/0
Preferred server not set or was marked bad, checking next preferred server
Wed Mar 20 15:01:10 2013 <202911363806070191> Trying a pooled connection for '10.13.52.81/7005/7006'
Wed Mar 20 15:01:10 2013 <202911363806070191> getPooledConn: No more connections in the pool for Host[10.13.52.81] Port[7005] SecurePort[7006]
Wed Mar 20 15:01:10 2013 <202911363806070191> general list: trying connect to '10.13.52.81'/7005/7006 at line 1676 for '/amserver/UI/Login?module=GMACLoginModule&org=branch'
Wed Mar 20 15:01:10 2013 <202911363806070191> INFO: New NON-SSL URL
Wed Mar 20 15:01:10 2013 <202911363806070191> Connect returns -1, and error no set to 245, msg 'Operation now in progress'
Wed Mar 20 15:01:10 2013 <202911363806070191> EINPROGRESS in connect() - selecting
Wed Mar 20 15:01:10 2013 <202911363806070191> Local Port of the socket is 63477
Wed Mar 20 15:01:10 2013 <202911363806070191> Remote Host 10.13.52.81 Remote Port 7005
Wed Mar 20 15:01:10 2013 <202911363806070191> general list: created a new connection to '10.13.52.81'/7005 for '/amserver/UI/Login?module=GMACLoginModule&org=branch', Local port: 63477
Wed Mar 20 15:01:10 2013 <202911363806070191> WLS info : 10.13.52.81:7005 recycled? 0
Wed Mar 20 15:01:10 2013 <202911363806070191> URL::sendHeaders(): meth='GET' file='/amserver/UI/Login?module=GMACLoginModule&org=branch' protocol='HTTP/1.1'
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[accept]=[image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */*]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[referer]=[https://capacity.dealerservices.ally.com/userprovisioning/jsp/autoSubmit.jsp?lang=en-us&source=MigratedLoginWidget&userType=branch&process=login]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[accept-language]=[en-US]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[user-agent]=[Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; BTRS99959; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8; .NET4.0C; InfoPath.3)]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[accept-encoding]=[gzip, deflate]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[host]=[gdpcapacity.gmacbranch.gmac.gm.com]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[cache-control]=[no-cache]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[cookie]=[s_pers=%20s_ts%3D%255B%255B%2527BRA0006T%2527%252C%25271362265430952%2527%255D%252C%255B%2527BRA0005T%2527%252C%25271363804235955%2527%255D%255D%7C1521570635955%3B%20s_nr%3D1363805063050-Repeat%7C1366397063050%3B; Locale=en-us; MasterCookie=MasterCookie; GDP_screenHeight=768; GDP_screenWidth=1366; GDP_browserType=Microsoft%20Internet%20Explorer; GDP_browserVersion=4.0%20%28compatible%3B%20MSIE%208.0%3B%20Windows%20NT%206.1%3B%20Trident/4.0%3B%20BTRS99959%3B%20SLCC2%3B%20.NET%20CLR%202.0.50727%3B%20.NET%20CLR%203.5.30729%3B%20.NET%20CLR%203.0.30729%3B%20Media%20Center%20PC%206.0%3B%20MS-RTC%20LM%208%3B%20.NET4.0C%3B%20InfoPath.3%29; GDP_operatingSystem=Win32; GDP_userAgent=Mozilla/4.0%20%28compatible%3B%20MSIE%208.0%3B%20Windows%20NT%206.1%3B%20Trident/4.0%3B%20BTRS99959%3B%20SLCC2%3B%20.NET%20CLR%202.0.50727%3B%20.NET%20CLR%203.5.30729%3B%20.NET%20CLR%203.0.30729%3B%20Media%20Center%20PC%206.0%3B%20MS-RTC%20LM%208%3B%20.NET4.0C%3B%20InfoPath.3%29; JSESSIONID=RKHWGqJvmJGWgZ9YdqywsXBLRd7QtMGX1Qr1yTmNTn0Kcdq0M0xq!-1872775671; ObSSOCookie=tKGxD0YS6sUw8kyVwfVBNujGihNvtG5GlUrYljs%2F3fngJbUm4%2B1bA6FpLn3LEESIpQsqwhjMDZODuautF%2B7zHKXypTkT%2Fn8DwdGn%2FYZOJK49wBTU511DfkqBmqBMsGjSM42jobA5gSQ672vUQskytWaJc4tZQC7MDLOGPEJf%2Bwc%2BVtXRi1%2FRGI4ql8jQpyWSJP6ImkHwt6QNig3Vlyt9BLZws6vvgHulULaxuA%2BXfUZ4fkVaVwN35tAmWorUa1ODiORCWhVSrZybMhTk53NsjT%2FdOaXFLZM4wcj6PKVkeG1UtZVfoNuVw8LBBVd5ave0]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[gmacdealer_groups]=[smartcash:scsupervisor:branch:us:en-us:EOAdminUS:]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[HTTP_OBLIX_UID]=[cbrus16]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[HTTP_OBLIX_UID]=[cbrus16]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[Proxy-Path-Translated]=[u001/webserver/docs/gdp-capacity-backend-sec/amserver/UI/Login]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[Proxy-Path-Translated-Base]=[u001/webserver/docs/gdp-capacity-backend-sec]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[WL-Proxy-Client-Keysize]=[128]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[WL-Proxy-Client-Secretkeysize]=[128]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[WL-Proxy-Client-IP]=[129.41.252.30]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[WL-Proxy-SSL]=[true]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[Proxy-Client-IP]=[129.41.252.30]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-Forwarded-For]=[129.41.252.30]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[Connection]=[Keep-Alive]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]
Wed Mar 20 15:01:10 2013 <202911363806070191> Hdrs to WLS:[x-weblogic-cluster-hash]=[7GHstOoW2dPEsRHcWrZe05SfKAc]
Wed Mar 20 15:01:11 2013 <202911363806070191> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 302 Moved Temporarily]
Wed Mar 20 15:01:11 2013 <202911363806070191> URL::parseHeaders: StatusLine set to [302 Moved Temporarily]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Date]=[Wed, 20 Mar 2013 19:01:10 GMT]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Pragma]=[no-cache]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Location]=[https://gdpcapacity.gmacbranch.gmac.gm.com/portal/dt?action=process&provider=PortletWindowProcessChannel&windowProvider.targetPortletChannel=GMACDataProvider&containerName=GMACBranchHomeContainer&windowProvider.currentChannelMode=VIEW&window.portletAction=ACTION]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Content-Type]=[text/html]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Expires]=[0]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Set-Cookie]=[JSESSIONID=RKHW4QzDhbJpcQJJpXJ21CV3lxY2lbhNJYmtJCYGGK2BC71JTqGr!923706867; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Set-Cookie]=[iPlanetDirectoryPro=AQIC5wM2LY4Sfcwgaa%2Bz8dzyN5AAXxW2GEBHoRwWjfYUb9M%3D%40AAJTSQACMDI%3D%23; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Set-Cookie]=[AMAuthCookie=LOGOUT; expires=Thursday, 01-Jan-1970 01:00:00 GMT; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[X-AuthErrorCode]=[0]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[X-DSAMEVersion]=[6 2005Q1]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Transfer-Encoding]=[chunked]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs from WLS:[Cache-Control]=[private]
Wed Mar 20 15:01:11 2013 <202911363806070191> parsed all headers OK
Wed Mar 20 15:01:11 2013 <202911363806070191> sendResponse() : uref_p->getStatus() = '302'
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[date]=[Wed, 20 Mar 2013 19:01:10 GMT]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Pragma]=[no-cache]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Location]=[https://gdpcapacity.gmacbranch.gmac.gm.com/portal/dt?action=process&provider=PortletWindowProcessChannel&windowProvider.targetPortletChannel=GMACDataProvider&containerName=GMACBranchHomeContainer&windowProvider.currentChannelMode=VIEW&window.portletAction=ACTION]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[content-type]=[text/html]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Expires]=[0]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Set-Cookie]=[JSESSIONID=RKHW4QzDhbJpcQJJpXJ21CV3lxY2lbhNJYmtJCYGGK2BC71JTqGr!923706867; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Set-Cookie]=[iPlanetDirectoryPro=AQIC5wM2LY4Sfcwgaa%2Bz8dzyN5AAXxW2GEBHoRwWjfYUb9M%3D%40AAJTSQACMDI%3D%23; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Set-Cookie]=[AMAuthCookie=LOGOUT; expires=Thursday, 01-Jan-1970 01:00:00 GMT; path=/]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[X-AuthErrorCode]=[0]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[X-DSAMEVersion]=[6 2005Q1]
Wed Mar 20 15:01:11 2013 <202911363806070191> Hdrs to client (add):[Cache-Control]=[private]
Wed Mar 20 15:01:11 2013 <202911363806070191> canRecycle: conn=1 status=302 isKA=1 clen=-1 isCTE=1
Wed Mar 20 15:01:11 2013 <202911363806070191> closeConn: pooling for '10.13.52.81/7005'
Wed Mar 20 15:01:11 2013 <202911363806070191> request [amserver/UI/Login?module=GMACLoginModule&org=branch] processed successfully..................
Could some one let me know how to maintain the session stickiness and please do let me know why the JVM ID is getting changed.
Note : We are using cookie based replication in our environment.
Thanks & Regards
Arun

the CSS does not have the possibility to dynamically learn cookie.
So, you have to setup manually the value sent by each server.
According to your setup, the jsessionid would have a fix value after the first 33 bytes and the value will be 2 bytes long.
Is that correct ?
If yes, try to increase the string range.
Finally, it might be easier to use arrowpoint cookies.
Gilles.

How to do http session stickiness based on URL patterns?

Is there a feature within the WL plugin for Apache that would allow me to emulate the "jvmroute" session stickiness behaviour as provided by Tomcat and its plugin. I would like to have the control to tie requests from http clients to particular WLS servers in a cluster depending on the URL. For example http://foo.com/web01 requests would be forwarded to an appsererver app01 and so on. For all other requests (e.g http://foo.com/web), the WL plugin would do its normal load balancing ignoring the stickiness. From my understanding the WLS inbuilt http session stickiness is based on JSessionIDs which are exchanged using cookies - which is something i cannot use in my case since i want the stickiness based on URL patterns.
I am using WLS 10.0 with Apache 2.2.4 on Linux.
Thanks
Ramdas

Session is not replicated across all the servers in the Cluster.
Apache knows which server to go using the JSession ID.
There is a concept of primary and secondary, secondary is selected based on the replication groups there are configured in the cluster.
you can configure the cluster so that /web01 requests go to different cluster, and /web requests go to different cluster.
but you can get all the funtiionalities from the single cluster.
Do you have any java caching that you are not able to replicate across the cluster ?(I know this can be done too).
let me know what you are actually trying to solve by doing the behavior you explained.

Hardware load balancing with session stickiness

Hello,
          We are looking for a hardware based solution to load balance 4
          unclustered weblogic servers. These servers are software replicas of
          each other and share a common database. We need a solution that
          provides session level server stickiness based on jsessionid as both a
          cookie and url rewrite. Currently we have Cisco load balancers which
          do not handle the url rewrite due to the fact the the load balancer
          only "sees" what is after the question mark in the url and the
          jsessionid is before the question mark. Example:
          http://somehost.com/some/url.jsp;jsessionid=26D5C566075663ABD8E17AD255974323?parm=value
          I'm sure we are not the only ones trying to do this. Any suggestions
          would be greatly appreciated.
          Thanks,
          Alan George


          Having worked on Cisco load balancer and WLS clustered, you would loose sessions
          when the requests are failed over.
          S
          "Shawn Kircher" <[email protected]> wrote:
          >
          >Has anyone got this type of scenario working where you load balance sticky
          >sessions
          >from a Cisco load balancer between non-clustered weblogic servers?
          >
          >Thanks,
          >
          >Shawn
          >
          >"Aravind Krishnasamy" <[email protected]> wrote:
          >>F5 or BigIp provides hardware level load balancing and it injects date
          >>inside weblogic cookie and maintains server affinity.
          >>Thanks
          >>Aravind
          >>"ageorge" <[email protected]> wrote in message
          >>news:[email protected]...
          >>> Hello,
          >>>
          >>> We are looking for a hardware based solution to load balance 4
          >>> unclustered weblogic servers. These servers are software replicas
          >>of
          >>> each other and share a common database. We need a solution that
          >>> provides session level server stickiness based on jsessionid as both
          >>a
          >>> cookie and url rewrite. Currently we have Cisco load balancers which
          >>> do not handle the url rewrite due to the fact the the load balancer
          >>> only "sees" what is after the question mark in the url and the
          >>> jsessionid is before the question mark. Example:
          >>>
          >>>
          >>http://somehost.com/some/url.jsp;jsessionid=26D5C566075663ABD8E17AD255974323
          >>?parm=value
          >>>
          >>> I'm sure we are not the only ones trying to do this. Any suggestions
          >>> would be greatly appreciated.
          >>>
          >>> Thanks,
          >>>
          >>> Alan George
          >>
          >>
          >

Sticky using session variables

Hello
I was wondering if it is possible to stick a session to a server using session variables (such as username) Currently I am using cookies to keep the session sticky but i also need to use the session variables.
Thanks
Donagh

Donagh,
there is absolutely no reason to use both.
If the name is more important, than use the name.
If the cookie is more important, than use the cookie.
If one is not more important than the other, then keep using the cookie.
Another way to see it is :
if the name and the cookie refer to the same server, it does not matter which one you use.
But if they point to different servers.
What do you do ?
Which information do you use to select the server ?
The name or the cookie ?
As I said, there is no reason to use both.
Unless if one is missing.
But the problem is then to make sure it is always there.
Is there any stickyness issue currently ?
Gilles.

How to make IIS plug-in do STICKY load balancing

There are two classes of scalable services: pure and sticky. A pure service
is one where any instance of the application can respond to client requests.
A sticky service is one where a client sends its requests to the same
instance; those requests are not redirected to other instances.
It seems to me that weblogic IIS proxy plug-in does not support the sticky
load balancing.
Could someone give me some information on how to make the proxy sticky?
Is there configuration parameters for this?
Thanks,
-Lei

I set the cluster.
It seems to me that there is some problem with the Set-Cookie mechanism of
the plug-in.
Sometime it set the cookie in my browser, sometime it is not.
Even from the wlproxy.log, I could set something like
Fri Aug 03 17:56:12 2001 Hdrs to
client:[Set-Cookie]=[AribaNode=O2tII92qHlP2tpZjUV0m5ued1s6X028cUPu24QcGj1Q25
AE5VXOd!1782877802312707887!ltang.ariba.com!8001!7002; domain=ariba.com;
path=/]
But the cookie is not set in my browser, what might be wrong here?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I do believe that this will not work since if clustering is not enabled, a
cookie will not be set on the browser that contains the primary and
secondary server.
You are specifying two different ports in your servers. You need to use
clustering in order to get this functionality with the plugin.Furthermore,
you will achieve fail-over.
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
Here is what I did for the examples under the bea sample directory.
I put the following in test1/WEB-INF/weblogic.xml
<session-descriptor>
<session-param>
<param-name> CookieDomain </param-name>
<param-value> *.ariba.com </param-value>
</session-param>
<session-param>
<param-name> CookieName </param-name>
<param-value> AribaNode </param-value>
</session-param>
<session-param>
<param-name> CookiePath </param-name>
<param-value> /test1 </param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
I add the following in iisproxy.ini
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=ltang.ariba.com:8001,achu.ariba.com:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test1
DynamicServerList=OFF
CookieName=AribaNode
I use SesssionServlet.java as an example
When I involk http://proxy/test1/SessionServlet, I always get 1
if I use
http://proxy/test1/SessionServlet:AribaNode=................................
I could see the session becomes sticky.
If I do not want to use URL rewriting, what should I do in order to makethe
session STICKY
for this example.
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
If you leave the CookieName untouched on the WebLogic side, then there
should be no reason to make the change in the plug-in.
But yes, you need to make sure the cookie names are the same.
Regards,
Eric
"Mark Vaughn" <[email protected]> wrote in message
news:[email protected]...
Actually, you also need to make sure you set the "CookieName" in theplugin.
That let's the plugin read the cookie set by WebLogic to determine
who
the
primary and secondary servers are for that session. Otherwise, theplugin
has no
way of knowing if you are establishing a new session or returning to
an
existing
one. The cookie will tell it if you have a current session and who
it
should
send you to for continuing that session, or failing that session
over.
>>>>
Eric Gross wrote:
Without having clustering enabled, you will not get Sticky load
balancing.
You need to have clustering so that a cookie is sent back to the
client
that
contains information about where it's session is located.
Otherwise,
you
are just going to get round-robin each time.
You can refer to the following page for more information:
http://e-docs.beasys.com/wls/docs61/cluster/servlet.html
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
WebLogicCluster=machine1:7001,machine2:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test,/test1
DynamicServerList=OFF
I run two standone (Admin server) weblogic servers on machine1
machine2.
Then I deploy application test.war on machine1 first, then onmachine2.
Should I make machine2 as a managed server and machine1 as an
admi
n
server?
Will this make the session sticky?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
It would help us to know how you have iisproxy.ini configured.
Sticky
load
balancing should work fine if you have the plug-in and
WebLogic
Server
setup
correctly.
How have you setup the plug-in?
Thanks,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
There are two classes of scalable services: pure and sticky.
A
pure
service
is one where any instance of the application can respond to
client
requests.
A sticky service is one where a client sends its requests to
the
same
instance; those requests are not redirected to other
instances.
It seems to me that weblogic IIS proxy plug-in does notsupport
the
sticky
load balancing.
Could someone give me some information on how to make the
proxy
sticky?
Is there configuration parameters for this?
Thanks,
-Lei
.-. Mark Vaughn
/V\ 7024 Corona Dr.
// \\ North Richland Hills, TX 76180
/( )\ [email protected]
^^-^^
"Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks."
Ben Woodbridge

HTTP sticky timeout issue in ACE .

Hi All ,
We are facing the dis connectivity issue in the the http session ( sticky configuration )
As per the customer requirement we configured the http sticky with the connection time out 60 min ( one hour ) .
But as per the test with the tool cookie manager , they identified as the http sessions are getting timed out in 20 to 30 minuits .
Please find the sticky configuration
sticky http-cookie FRONT_SESSION_ID TEST_FRONT
cookie insert
timeout 60
replicate sticky
serverfarm TEST_FRONT
We also did the http persistence as below .
parameter-map type http HTTP_Persistence_Rebalance
persistence-rebalance
Parameter-map : HTTP_Persistence_Rebalance
Description : -
Type : http
    server-side connection reuse       : disabled
    case-insensitive parsing           : disabled
    persistence-rebalance              : enabled
    header modify per-request          : disabled
    cookie-error-ignore                : disabled
    header-maxparse-length             : 4096
    content-maxparse-length            : 4096
    parse length-exceed action         : drop
    urlcookie-delimiters               : /&#+
    urlcookie-start                    : ?
We have also tested the session directly with the Rserver .But it is not getting disconnected ( As we doubt is it any server related issue )
Also please find the below resource allocation .
resource-class TEST-FRONT
limit-resource all minimum 0.00 maximum unlimited
limit-resource buffer syslog minimum 0.50 maximum equal-to-min
limit-resource sticky minimum 2.00 maximum unlimited
So can any one please suggest me is there any configuration mistakes here .
If the configuration is ok please suggest me what more I have to do for making the stickiness around 60 min .
Regards ,
Sinjish.K

Sinjish-
Can you use the capture utiliy on ACE to gather a trace of the entire session - then filter out the traffic to just the client IP or the server IP and attach it to this thread? A showtech would also be useful to see if there are any anomolies.
Regards,
Chris Higgins

Session Stickness problem on weblogic load balancer

Hello All
I having trouble related to session stickiness for weblogic load balancing, am using httpclusterservlet on a proxy server that forward requests to 3 managed server that are members of the same cluster.
I tried to search for a solution to this problem and I found two links that are talking about the same problem but there are still not answered!!.
Here are the links:
https://forums.oracle.com/message/11158966#11158966
https://forums.oracle.com/message/11158964#11158964
Based on oracle link Using Sessions and Session Persistence, the documentation says under the "HTTP Session Properties" section that there is a change in how the sessions are formatted and this might cause a problem
for some load balancers (the documentation did not say if weblogic httpclusterservlet is one of them), I tried to do the suggested workaround and I got "java.lang.IllegalStateException: Response already committed" error same as what happens with the user in link https://forums.oracle.com/message/11158966#11158966.
Does anyone knows how to fix this??, I search for a very long time on this problem and with no luck, please help!

Hi,
Can you please give me some more information about your setup ...
Something like ...
F5/LB --> Apache or OHS --> WebLogic Cluster..
If you are using F5/OHS directly to WebLogic cluster you can try enabling the session persistence and this problem should go away..
If you are using plain Apache or OHS try putting "DynamicServerList" off.
Let me know something more about setup so that i can contribute to help ..thanks.

Sticky behavior

Hi,
I am planning to make a implement LB design with URI based load balalncing with 2 Serverfarms. Like if http://urla it goes to Serverfarm A and if URI is http://urlb then it goes Serverfarm B.
1) This URI will not be displayed in address bar, this will be HTTP GET requests - Will it work if we place Layer 7 policeis, i hope so?
2) this URI will be genrated whenever user selects some model in drop down box , means depending on the selection it has to go to Serverfarm A or B- But we do have IP Sticky (as Application requires IP sticky) - So now the question would be , How ACE will work in this design, Like If User goes to Serverfarm A and made sticky and if he selects soemthing else which needs to goto Serverfarm B- WIll ACE break the session?

Hi Syakshanulla,
You can use L7 sticky parameters for session persistence like header, http content etc. This is basically to look for a string or a value in HTTP header for session stickiness. I would recommend going through ACE user guide in section "configuring stickiness" for further details. You will get details about different ways you can get session persistence using information in L7.
If src sticky is applied to a serverfarm and once LB has happened, the session will always stick to the same server as long as the entry is there in sticky table and ACE will not look further into HTTP header.
But by using L7 parameters for session persistence, your requirement can be met. Of course you will need to test it. A simple example is below. This is from user guide.
sticky http-header MSISDN HEADER-GROUP1
timeout 30
serverfarm SFARM1
sticky http-header TestHeader HEADER-GROUP2
header offset 15 length 7
timeout 30
serverfarm SFARM2
class-map match-all L4STICKY-HEADER_129:80_CLASS
2 match virtual-address 192.168.120.129 tcp eq www
class-map type http loadbalance match-all L7MSISDN_CLASS
2 match http header MSISDN header-value ".*"
class-map type http loadbalance match-all L7TESTHEADER_CLASS
2 match http header TestHeader header-value ".*"
policy-map type loadbalance first-match L7PLBSF_STICKY-HEADER_POLICY
class L7MSISDN_CLASS
sticky-serverfarm HEADER-GROUP1
class L7TESTHEADER_CLASS
sticky-serverfarm HEADER-GROUP2
class class-default
serverfarm DEFAULT
The above example is using parameter HTTP header. You can use HTTP Content as well.
Regards,
Kanwal

Load Balancing with Reverse Proxy Plug-in in SunOne 6.1

Hello
we are configuring our reverse proxy web server SunOn 6.1 for load balancing and we have some conflicting information that we have found on the internet. The options we have found are the following:
1- In one case, it seems that all we need to do is add the destination servers to the servers parameter (quoted, space-delimited). We have read that the proxy server will simply round-robin requests.
2- In another case, we have seen that we have to use an loadbalancer.xml file with the server names and reference the file from both magnus.conf and obj.conf.
I have doubts about the second option because I really think this is configuration in 7.0 not 6.1.
Also, I also need to configure session stickiness but it is not clear how this works. There is an option for sticky cookies that defaults to JSESSIONID if not configured. Does this mean that I will have session stickiness but simply without the use of cookies?
ANY HELP? We need to solve this in the next day.

HI,
This may work for you.
obj.conf
<Object name="passthrough1">
Service fn="service-passthrough" servers="http://localhost:8080"
</Object>
<Object name="default">
AuthTrans fn="match-browser" browser="MSIE" ssl-unclean-shutdown="true"
NameTrans fn="assign-name" from="/idm(|/*)" name="passthrough1"
NameTrans fn="ntrans-j2ee" name="j2ee"
NameTrans fn="pfx2dir" from="/mc-icons" dir="D:/Sun/WebServer6.1/ns-icons" name="es-internal"
NameTrans fn="document-root" root="$docroot"
PathCheck fn="nt-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index" index-names="intro.htm,index.html,home.html,index.jsp"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
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" name="access"
</Object>
<Object name="j2ee">
Service fn="service-j2ee" method="*"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>
============================================
magnus.conf
# The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED.
# They will not be supported in future releases of the Web Server.
NetsiteRoot D:/Sun/WebServer6.1
ServerName abc
ServerID https-www.abc.com
RqThrottle 128
DNS off
Security off
ExtraPath D:/Sun/WebServer6.1/bin/https/bin
Init fn=flex-init access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
Init fn="load-modules" shlib="D:/Sun/WebServer6.1/bin/https/bin/j2eeplugin.dll" shlib_flags="(global|now)"
Init fn="load-modules" shlib="D:/Sun/WebServer6.1/plugins/passthrough/passthrough.dll"

Steps to create a cookieless domain in Weblogic

Hi,
I want to create a cookieless domain, to serve all the static contents like CSS,JS and images for my site to enhance it's performance. Could someone please let me know steps involved to set up a cookieless domain in Weblogic.
Thanks in advance for yours assistance.
Regards,
NM

Generally session stickiness and failover are two important features provided by application server to manage your sessions effectively.This can be achieved either through cookies or url re-writing.
For individual applications using servlets,you could disable cookies from the deployment descriptors.
However,for your specific case,you may want to disable the cookies on your browser if you wish to access the static file directly.
if you have a jsp or servlet which makes a call to static files ona nother server,then i think what you could do is create a war module with all the static images and disable cookies in the weblogic.xml file by setting cookies-enabled to false.
-Sandeep

HTTP POST with advance balance cookies

Hello
I am trying to keep a session sticky for 20 mins based on cookies. The problem is the application is using HTTP POSTs and the balance method only looks into the HTTP GET. How can I get the CSS to look into the HTTP POST?
Any examples would be great.
Thanks.
Donagh

Hi Gilles
Thanks for your reply. I have obviously been misinformed about the POST and the GET. That is good but now I don't have an answer to my problem!! I am balancing on a cookie called ASP.NET_SessionId=
Here is my config
content Toughbook_PDAs
vip address 10.40.21.28
add service w2k-eolasprd1
add service w2k-eolasprd2
protocol tcp
port 80
string prefix "ASP.NET_SessionId="
sticky-inact-timeout 20
advanced-balance cookies
active
I have attached a trace and I am looking for
ASP.NET_SessionId=1w0cql550wou04albf4jrjfoy45
Hopefully my config is incorrect.
Thank You
Donagh

Business Objects XI 3.1 load balancing (is not balancing).

We have 2 x Tomcat servers running on 2 seperate Solaris servers. Users access XI via a load balanced URL which hits one or other of these 2 servers. However, this is not happening. What we see is that which ever server the load balancer hits first (after Tomcat server restarts), all subsequent sessions are connected to that Tomcat server. We see no traffic in the other Tomcat's logs. My IP engineers have assured me it's not the CSM (h/w load balancer) and that the sticky bit is correctly set. What ever I try we only get 1 Tomcat server doing any work. If 1 Tomcat is up and the other down, the load balancing works as expected - i.e. all traffic hits the live Tomcat server. It's just when the 2 are up and running it does not behave as expected. We have BO XI configured for Silent Single Sign-On (SSSO) with Windows AD. When the Tomcat servers start up the LDAP + SSSO initialisation can be seen to be successful in both Tomcat logs.
Is there any special session stickiness or cookie settings the h/w load balancer needs to be configured with ?
Is there something that needs to be configured in Tomcat, especially as we have SSSO configured ?
s/w versions:
BO XI 12.1.0
Tomcat 5.5 (standard install deployment)
Any suggestiojns gratefully recieved.
Thanks
Rich

Load balancer as well as Tomcat servers are not part of BOE product, so you do not have a problem with Xi3.1 load balancing.
BOE simply has no play between LB and Tomcats.
If you have 10 DIFFERENT user sessions and all of them or majority of them go to only one of 2 tomcats -- this is a problem with your loadbalancer and has nothing to do with BOE or session persistancy.
If you have ONE user session and all request go to a single tomcat , then your session persistancy is set correctly and everything works as expected.

Is a cluster proxy a single-point-of-failure?

Our group is planning on configuring a two machine cluster to host
          servlets/jsp's and a single backend app server to host all EJBs and a
          database.
          IIS is going to be configured on each of the two cluster machines with a
          cluster plugin. IIS is being used to optimize performance of static HTTP
          requests. All servlet/jsp request would be forwarded to the Weblogic
          cluster. Resonate's Central Dispatch is also going to be installed on the
          two cluster machines. Central Dispatch is being used to provide HTTP
          request load-balancing and to provide failover in case one of the IIS
          servers fails (because the IIS process fails or the cluster machine it's on
          fails).
          Will this configuration work? I'm most concerned about the failover of the
          IIS cluster proxy. If one of the proxies is managing a sticky session (X),
          what happens when the machine (the proxy is on) dies and we failover to the
          other proxy? Is that proxy going to have any awareness of session X?
          Probably not. The new proxy is probably going to believe this request is
          new and forward the request to a machine which may not host the existing
          primary session. I believe this is an error?
          Is a cluster proxy a single-point-of-failure? Is there any way to avoid
          this? Does the same problem exist if you use Weblogic's HTTP server (as the
          cluster proxy)?
          Thank you.
          Marko.


We found our entity bean bottlenecks using JProbe Profiler. It's great for
          watching the application and seeing what methods it spends its time in. We
          found an exeedingly high number of calls to ejbLoad were taking a lot of
          time, probably due to the fact that our EBs don't all have bulk-access
          methods.
          We also had to do some low-level method tracing to watch WebLogic thrash EB
          locks, basically it locks the EB instance every time it is accessed in a
          transaction. Our DBA says that Oracle is seeing a LOT of lock/unlock
          activity also. Since much of our EB data is just configuration information
          we don't want to incur the overhead of Java object locks, excess queries,
          and Oracle row locks just to read some config values. Deadlocks were also a
          major issue because many txns would access the same config data.
          Our data is also very normalized, and also very recursive, so using EBs
          makes it tricky to do joins and recursive SQL queries. It's possible that we
          could get good EB performance using bulk-access methods and multi-table EBs
          that use custom recursive SQL queries, but we'd still have the
          lock-thrashing overhead. Your app may differ, you may not run into these
          problems and EBs may be fine for you.
          If you have a cluster proxy you don't need to use sticky sessions with your
          load balancer. We use sticky sessions at the load-balancer level because we
          don't have a cluster proxy. For our purposes we decided that the minimal
          overhead of hardware ip-sticky session load balancing was more tolerable
          than the overhead of a dog-slow cluster proxy on WebLogic. If you do use the
          proxy then your load balancer can do round-robin or any other algorithm
          amongst all the proxies.
          Marko Milicevic <[email protected]> wrote in message
          news:[email protected]...
          > Sorry Grant. I meant to reply to the newsgroup. I am putting this reply
          > back on the group.
          >
          > Thanks for your observations. I will keep them all in mind.
          > Is there any easy way for me to tell if I am getting acceptable
          performance
          > with our configuration? For example, how do I know if my use of Entity
          > beans is slow? Will I have to do 2 implementations? One implementation
          > using entity beans and anther implementation that replaces all entity use
          > with session beans, then compare the performance?
          >
          > One last question about the cluster proxy. You mentioned that you are
          using
          > Load Director with sticky sessions. We too are planning on using sticky
          > sessions with Central Dispatch. But since the cluster proxy is stateless,
          > does it matter if sticky sessions is used by the load balancer? No matter
          > which cluster proxy the request is directed to (by load balancing) the
          > cluster proxy will in turn redirect the request to the correct machine
          (with
          > the primary session). Is this correct? If I do not have to incur the
          cost
          > of sticky sessions (with the load balancer) I would rather avoid it.
          >
          > Thanks again Grant.
          >
          > Marko.
          > .
          >
          > -----Original Message-----
          > From: Grant Kushida [mailto:[email protected]]
          > Sent: Monday, May 01, 2000 5:16 PM
          > To: Marko Milicevic
          > Subject: RE: Is a cluster proxy a single-point-of-failure?
          >
          >
          > We haven't had too many app server VM crashes, although our web server
          > typically needs to be restarted every day or so due to socket strangeness
          or
          > flat out process hanging. Running 2 app server processes on the same box
          > would help with the VM stuff, but remember to get 2 NICs, because all
          > servers on a cluster need to run on the same port with different IP addrs.
          >
          > We use only stateless session beans and entity beans - we have had a
          number
          > of performance problems with entity beans though so we will be migrating
          > away from them shortly, at least for our configuration-oriented tables.
          > Since each entity (unique row in the database) can only be accessed by one
          > transaction at a time, we ran into many deadlocks. There was also a lot of
          > lock thrashing because of this transaction locking. And of course the
          > performance hit of the naive database synching (read/write for each method
          > call). We're using bean-managed persistence in 4.5.1, so no read-only
          beans
          > for us yet.
          >
          > It's not the servlets that are slower, it's the response time due to the
          > funneling of requests through the ClusterProxy servlet running on a
          WebLogic
          > proxy server. You don't have that configuration so you don't really need
          to
          > worry. Although i have heard about performance issues with the cluster
          proxy
          > on IIS/netscape, we found performance to be just fine with the Netscape
          > proxy.
          >
          > We're currently using no session persistence. I have a philosophical issue
          > with going to vendor-specific servlet extensions that tie us to WebLogic.
          We
          > do the session-sticky load balancing with a Cisco localdirector, meanwhile
          > we are investigating alternative servlet engines (Apache/JRun being the
          > frontrunner). We might set up Apache as our proxy server running the
          > Apache-WL proxy plugin once we migrate up to 5.1, though.
          >
          > > -----Original Message-----
          > > From: Marko Milicevic [mailto:[email protected]]
          > > Sent: Monday, May 01, 2000 1:08 PM
          > > To: Grant Kushida
          > > Subject: Re: Is a cluster proxy a single-point-of-failure?
          > >
          > >
          > > Thanks for the info Grant.
          > >
          > > That is good news. I was worried that the proxy maintained
          > > state, but since
          > > it is all in the cookie, then I guess we are ok.
          > >
          > > As for the app server, you are right. It is a single point
          > > of failure, but
          > > the machine is a beast (HP/9000 N-class) with hardware
          > > redundancy up the
          > > yin-yang. We were unsure how much benefit we would get if we
          > > clustered
          > > beans. There seems to be a lot of overhead associated with
          > > clustered entity
          > > beans since every bean read includes a synch with the
          > > database, and there is
          > > no fail over support. Stateful session beans are not load
          > > balanced and do
          > > not support fail over. There seems to be real benefit for
          > > only stateless
          > > beans and read-only entities. Neither of which we have many
          > > of. We felt
          > > that we would probably get better performance by locating all
          > > of our beans
          > > on the same box as the data source. We are considering creating a two
          > > instance cluster within the single app server box to protect
          > > against a VM
          > > crash. What do you think? Do you recommend a different
          > > configuration?
          > >
          > > Thanks for the servlet performance tip. So you are saying
          > > that running
          > > servlets without clustering is 6-7x faster than with
          > > clustering? Are you
          > > using in-memory state replication for the session? Is this
          > > performance
          > > behavior under 4.5, 5.1, or both? We are planning on
          > > implementing under
          > > 5.1.
          > >
          > > Thanks again Grant.
          > >
          > > Marko.
          > > .
          >
          >
          > Grant Kushida <[email protected]> wrote in message
          > news:[email protected]...
          > > Seems like you'll be OK as far as session clustering goes. The Cluster
          > > proxies running on your IIS servers are pretty dumb - they just analyze
          > the
          > > cookie and determine the primary/secondary IP addresses of the WebLogic
          > web
          > > servers that hold the session data for that request. If one goes down
          the
          > > other is perfectly capable of analyzing the cookie too. As long as one
          > proxy
          > > and one of your two clustered WL web servers survives your users will
          have
          > > intact sessions.
          > >
          > > You do, however, have a single point of failure at the app server level,
          > and
          > > at the database server level, compounded by the fact that both are on a
          > > single machine.
          > >
          > > Don't use WebLogic to run the cluster servlet. It's performance is
          > > terrible - we experienced a 6-7x performance degredation, and WL support
          > had
          > > no idea why. They wanted us to run a version of ClusterServlet with
          > timing
          > > code in it so that we could help them debug their code. I don't think
          so.
          > >
          > >
          > > Marko Milicevic <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Our group is planning on configuring a two machine cluster to host
          > > > servlets/jsp's and a single backend app server to host all EJBs and a
          > > > database.
          > > >
          > > > IIS is going to be configured on each of the two cluster machines with
          a
          > > > cluster plugin. IIS is being used to optimize performance of static
          > HTTP
          > > > requests. All servlet/jsp request would be forwarded to the Weblogic
          > > > cluster. Resonate's Central Dispatch is also going to be installed on
          > the
          > > > two cluster machines. Central Dispatch is being used to provide HTTP
          > > > request load-balancing and to provide failover in case one of the IIS
          > > > servers fails (because the IIS process fails or the cluster machine
          it's
          > > on
          > > > fails).
          > > >
          > > > Will this configuration work? I'm most concerned about the failover
          of
          > > the
          > > > IIS cluster proxy. If one of the proxies is managing a sticky session
          > > (X),
          > > > what happens when the machine (the proxy is on) dies and we failover
          to
          > > the
          > > > other proxy? Is that proxy going to have any awareness of session X?
          > > > Probably not. The new proxy is probably going to believe this request
          > is
          > > > new and forward the request to a machine which may not host the
          existing
          > > > primary session. I believe this is an error?
          > > >
          > > > Is a cluster proxy a single-point-of-failure? Is there any way to
          avoid
          > > > this? Does the same problem exist if you use Weblogic's HTTP server
          (as
          > > the
          > > > cluster proxy)?
          > > >
          > > > Thank you.
          > > >
          > > > Marko.
          > > > .
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > >
          > >
          >
          >

Local Director & HTTP Redirection

Hi, just wondering if anyone has successfully implemented HTTP
redirection on Cisco Local Director 416 running ver 4.1.2 Basically I'm
after any pitfalls to look out for. Current implementation utilizes
generic session stickiness however this has problems for clients
trying to access our load balanced servers if they come from behind
multiple proxies via their ISP.
Servers are Private IP addressed (Firewall in front of LD performing NAT static
txlation)
On another point, how does the Cisco CS11000 (Arrowpoint) perform
session persistance/stickiness or what "better" ways does the
Arrowpoint acheive this as compared to Local Director?
Any helpful input would be much appreciated.
Rgds
Adam

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen
If anyone else in the forum has some advice, please reply to this thread.
Thank you for posting.

Session Stickiness

Similar Messages

Maybe you are looking for