Ok, just got this fix checked in. The syntax is as follows:
Default keep-alive of "SELECT 1":
<pool-controller {attributes}/>
Custom keep-alive query:
<pool-controller {attributes}>
<keep-alive>SELECT 2</keep-alive>
</pool-controller>
Disable keep-alive:
<pool-controller {attributes}>
<keep-alive disable="true"/>
</pool-controller>
or
<pool-controller {attributes}>
<keep-alive disable="true">SELECT 2</keep-alive>
</pool-controller>
It works for me, but give this a try and make sure that it does for you
as well.
Cheers,
Leif
Peter Royal wrote:
> On Friday 25 January 2002 10:02 am, Berin Loritsch wrote:
>
>>This is for backwards compatibility. Let's add an attribute to the
>>keep-alive element to disable it, like this:
>>
>><keep-alive disabled=""/>
>>
>>The existence of that attribute--wether filled or not will mark it for
>>being disabled.
>>
>
> That's confusing. How about:
>
> <keep-alive disabled="true"/>
>
> You can then do a simple
> configuration.getChild("keep-alive").getAttributeAsBoolean("disabled", false);
>
> to have it default to on.
> -pete
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
