I found that the unable to setup data connection errors (in the past) were
related to the Tomcat MaxHeader size being too small..it defaults to
something like 8K.with the SSO we are using our header size can get huge, so
we have it set to something like 128.

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Chowdhury, Tauf
Sent: Tuesday, April 26, 2011 9:14 AM
To: [email protected]
Subject: Re: 7.6.04 - mid tier load balancing settings

 

** 

Thanks LJ, have you noticed that your users are getting any RPC or errors
that say "Unable to setup Data connection" errors?  We are getting that and
I'm not sure if this is due to the app load balancer or the front end web. 

 

Tauf Chowdhury | Forest Laboratories, Inc.

Analyst, Service Management

Mobile:646.483.2779

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of LJ LongWing
Sent: Tuesday, April 26, 2011 10:54 AM
To: [email protected]
Subject: Re: 7.6.04 - mid tier load balancing settings

 

Tauf,

I truly wish I could give you some sage advice from a seasoned master, but I
fear that you and I are groping around in the same darkness trying to put
together a 1000 piece puzzle.  I have the same docs that you have and am
planning on assuming (yes, very dangerous, I know) that the 'defaults' are a
good starting point, and make modifications as monitoring goes on as we
reach production mid next month.

 

Regarding the #'s you provided below..I think the settings you have below
look reasonable.  Obviously the default of unchecked lifespan and a lifespan
of 0 won't balance.   Ironically we have also taken the Max Connections per
server from the default of 80 to 200 as well because of problems we were
experiencing with them being exhausted.  I don't see any reason I wouldn't
be able to use the ones you outlined below.ours is a 4 Mid-Tier/2 App server
setup.

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Chowdhury, Tauf
Sent: Tuesday, April 26, 2011 4:14 AM
To: [email protected]
Subject: 7.6.04 - mid tier loadbalancing settings

 

** 

All (LJ),

For those of you have gone through the load balancing exercise, can someone
give a breakdown of the fields in the Connections section of the new mid
tier? 

Yes, I've looked through the guide but it doesn't clearly state what the
ramifications of setting a number too high or too low means for something
like, "Lifespan connection" or "Connection timeout." Do these need to be
greater or lower than what is set on the hardware load balancer? Has anyone
found some settings that work better for them than others based on # of
users or type of requests? 

Interestingly, BMC could not give me ANY recommendations or best practice
guidance. so me and the network guys set the configs to what we thought made
sense with a lot of assumptions on the settings below. The load balancer
(between mid tier and app servers) is set to distribute based on Least
Connection, with no persistency set. 

 

In my environment here are the settings:

Enable Lifespan - Checked

Connection Lifespan (minutes) = 60

 

Connection pool settings:

Max connections per server = 200

Connection Timeout (minutes) = 30

Idle Connections per server = 5

 

 

Tauf Chowdhury | Forest Laboratories, Inc.

Analyst, Service Management

Informatics-Infrastructure

Office: 631.858.7765

Mobile:646.483.2779

 

 

  _____  

This e-mail and its attachments may contain Forest Laboratories, Inc.
proprietary information that is privileged, confidential or subject to
copyright belonging to Forest Laboratories, Inc. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If
you are not the intended recipient of this e-mail, or the employee or agent
responsible for delivering this e-mail to the intended recipient, you are
hereby notified that any dissemination, distribution, copying or action
taken in relation to the contents of and attachments to this e-mail is
strictly prohibited and may be unlawful. If you have received this e-mail in
error, please notify the sender immediately and permanently delete the
original and any copy of this e-mail and any printout.

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

  _____  

This e-mail and its attachments may contain Forest Laboratories, Inc.
proprietary information that is privileged, confidential or subject to
copyright belonging to Forest Laboratories, Inc. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If
you are not the intended recipient of this e-mail, or the employee or agent
responsible for delivering this e-mail to the intended recipient, you are
hereby notified that any dissemination, distribution, copying or action
taken in relation to the contents of and attachments to this e-mail is
strictly prohibited and may be unlawful. If you have received this e-mail in
error, please notify the sender immediately and permanently delete the
original and any copy of this e-mail and any printout.

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend
WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to