Connection pooling + WebObjects

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 ef

Re: Connection pooling + WebObjects

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 + Jav

Re: Connection pooling + WebObjects

Okay. Thanks Kieran. I will check that. 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

Re: Connection pooling + WebObjects

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 configu

Re: Connection pooling + WebObjects

On May 11, 2008, at 8:45 PM, 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, no

Re: Connection pooling + WebObjects

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 WOAp

Re: Connection pooling + WebObjects

Personally, I would only use connection pooling in combination with multiple instances. Chuck and I disagree here :) In retrospect, I don't disagree ... I think I see what Chuck is saying, which is I think basically what I'm saying, too. Connection pool gives you scale without resilience.

Re: Connection pooling + WebObjects

On May 12, 2008, at 10:13 AM, Mike Schrag wrote: Personally, I would only use connection pooling in combination with multiple instances. Chuck and I disagree here :) In retrospect, I don't disagree ... I think I see what Chuck is saying, which is I think basically what I'm saying, too. Con

Re: Connection pooling + WebObjects

On May 12, 2008, at 10:11 AM, Mike Schrag wrote: 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 t

Re: Connection pooling + WebObjects

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 (tog

Re: Connection pooling + WebObjects

I am not sure what you mean by "the complications of being in multiple instances". Stack / instance synchronization or not, you still have to handle optimistic locking errors. You have to handle them less frequently if you are synchronizing, but they still have to be handles (or ignored b

Re: Connection pooling + WebObjects

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 (), so I have to run some critical parts of my code with t

Re: Connection pooling + WebObjects

Hi! On 2008/05/12, at 21:16, Mike Schrag wrote: For the vast majority of apps, I don't believe people will notice the brokenness, but I do agree that it is broken. The fix, unfortunately may be worse than the brokenness. Concurrency issues are bad, uhhkeey? They must be fixed, uhhke

Re: Connection pooling + WebObjects

On May 12, 2008, at 1:30 PM, Miguel Arroz wrote: I'm not even sure if the core of twitter is Rails or not. But as you say, it doesn't matter. Scaling is a nightmare. Makes me nervous (as almost everything, including concurrency issues, that must be fixed!). Makes goat herding look qu

Re: Connection pooling + WebObjects

Hello Mike; Is this implemented through "object store coordinator pooling"? I was wondering about that recently. cheers. So anyway, if you're having scaling problems and you want the fastest way to a solution with the least amount of trouble, adding stacks is probably it. If you want f

Re: Connection pooling + WebObjects

Is this implemented through "object store coordinator pooling"? I was wondering about that recently. Yep ... It's actually the same plumbing as multiple instance synchronization, to shuffle the data around with the exception that in local syncing, it can actually inject the snapshots directl

Re: Connection pooling + WebObjects

So if I have Wonder OSC synchronization going on inside a single app and I lock an OSC (in a background long running thread for example), how does that affect the synchronization between it and other OSCs while it is locked? How are snapshots affected in the locked OSC during the lock perio

Re: Connection pooling + WebObjects

So if I have Wonder OSC synchronization going on inside a single app and I lock an OSC (in a background long running thread for example), how does that affect the synchronization between it and other OSCs while it is locked? How are snapshots affected in the locked OSC during the lock perio

Re: Connection pooling + WebObjects

Am 12.05.2008 um 19:11 schrieb Mike Schrag: Where multiple instances is really a win is 1) if you DO have a problem in your app instance, you don't bring down the entire app. So multiple instances gives you VM isolation (like an OutOfMemoryError, for instance). Which you are also pretty

Re: Connection pooling + WebObjects

Its very nice to hear your advises and discussions. Thanks for all your inputs. We have 3 app servers of which 2 act as webservers as well and 1 separate database server, all are of Solaris 9 OS. We do NOT have Project Wonder integrated to our app. Currently we have 100's of instances config