• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Connection pooling + WebObjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Connection pooling + WebObjects


  • Subject: Re: Connection pooling + WebObjects
  • From: Miguel Arroz <email@hidden>
  • Date: Mon, 12 May 2008 19:37:55 +0100

Hi!

For all the reasons other people presented, I believe the way to scalability is, in most cases, multiple instances. That doesn't mean you shouldn't use connection pooling: I think both techniques complement each other, they are not mutually exclusive.

I use connection pooling (together with multiple instances) mainly to avoid problems in the way EOF works (as in, locking everything). Optimistic locking in EOF is, IMO, broken by design (<http://terminalapp.net/dr-optimistic-locking/ >), so I have to run some critical parts of my code with the entire EOF stack locked. That means during that processing, no user of that instance will be able to do whatever he tries to that needs EOF access. So, connection pooling will help, because if you have N connections, instead of locking all your users of that instance, you lock an average of all the users / N.

Note that connection pooling should be used with resource usage in mind. Not only memory for the snapshots, but you'll also consume database connections. That may force you to reconfigure your database server, or, in some cases like PostgreSQL, you may even be forced to change some low level kernel configuration values to handle all the shared semaphores PostgreSQL needs to handle all the simultaneous connections. This is even more serious if you connect to more that one DB on your app. If you connect to two different databases running on the same server, and create a pool of 5 connections, a single instance of the application will be using 10 connections.

  Yours

Miguel Arroz

On 2008/05/12, at 04:45, Shravan Kumar.M wrote:

Hello Group,

Can any one advise me what is the difference between :
* Deploying Multiple Instances of a WebObjects application from deploying a WebObjects application with Connection pooling configured.
i.e., I have a WebObjects app, now I will deploy this app with 5 instances (or) I configure my WOApp with Connection pooling having max 5 connections and deploy it.
Thank You
Shravan Kumar. M
effigent India Pvt., Ltd.,
----------------------------------------------------------



Kieran Kelleher wrote:

Project Wonder has connection pooling.... see ERXObjectStoreCoordinatorPool




On May 8, 2008, at 10:14 AM, Shravan Kumar.M wrote:

Hello Group,

Can anyone advise me best methodologies/ any open source frameworks that help me implement connection pooling in one of my WebObjects 5.2.4 + Java 1.4.2.* + Oracle 9i application.

Also advise pros n cons of Connection Pooling.

Thanks in advance.
--
Thank You
Shravan Kumar. M
effigent India Pvt., Ltd.,
----------------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

Miguel Arroz http://www.terminalapp.net http://www.ipragma.com



Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Connection pooling + WebObjects
      • From: Mike Schrag <email@hidden>
References: 
 >Connection pooling + WebObjects (From: "Shravan Kumar.M" <email@hidden>)
 >Re: Connection pooling + WebObjects (From: Kieran Kelleher <email@hidden>)
 >Re: Connection pooling + WebObjects (From: "Shravan Kumar.M" <email@hidden>)

  • Prev by Date: Re: [OT] Frontbase Export/Dump
  • Next by Date: Re: Inner Classes & EOF
  • Previous by thread: Re: Connection pooling + WebObjects
  • Next by thread: Re: Connection pooling + WebObjects
  • Index(es):
    • Date
    • Thread