Apple

On Tue, Jul 1, 2008 at 10:05 PM, Lon Varscsak <email@hidden> wrote:

This is the connection I assumed wasn't closing, but Klaus would have to chime in. I'm using:

new ERXEC(new ERXObjectStoreCoordinator(true));

in one specific instance and calling dispose() when I'm done (on the OSC) seems to do the trick (closes both connections properly).

I pointed Klause to ERXEOAccessUtilities.closeDatabaseConnections which is what I believe does the trickery (called from OSC's dispose method).

But maybe I misunderstood the problem. :)

Lon

On Tue, Jul 1, 2008 at 9:41 PM, Mike Schrag <email@hidden> wrote:
>>>>
>>>> I would look at Wonder source and see what trickery is being used to implement this fix.
>>>
>>> I don't think we close ... The OSC pool in Wonder is designed to be round-robin'ed across requests and never needs to close.
>>
>> I recall a discussion from a while ago that actually getting EOF to close the connection is difficult / impossible. I have never needed to (see Mike's comment above), so I have never looked into it.
>
> Maybe you're referring to the jdbc2Info connection? It's not impossible, but it is very tricky. I don't THINK this is his problem here, though.
>
> ms
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription: