Actually, I think the checkbox name is: ```reques...
# lucee
c
Actually, I think the checkbox name is:
Copy code
requestExclusive
z
thread plz
c
@bdw429s I actually saw this property in: https://github.com/Ortus-Solutions/commandbox-cfconfig/blob/master/commands/cfconfig/datasource/save.cfc
Copy code
requestExclusive
So, I presumed it was connected?
Thanks. I can see that it will available in Lucee 6 🙂
Are there any plans to add it to 5.4?
z
nope
👍 1
which ticket in jira?
z
that's what i thought
c
😂
Sorry
Hmmm. Well, when I try and add it using the method version of
Copy code
<cfadmin action="updateDatasource" />
Like:
Copy code
variables.adm = new Administrator("server", variables.adminpassword);

variables.adm.updateDatasource(
    type=variables.datasource.dbdriver, 
    name=variables.key,
    newName=variables.key,
    host=variables.datasource.host,
    port=variables.datasource.port,
    database=variables.datasource.database,
    username=variables.datasource.username,
    password=variables.datasource.password,
    requestExclusive=true
 );
It doesn't change the value to true?
z
wanna submit a patch, administraor.cfc is cfml
c
Sorry, do you want me to submit a patch?
I don't think I have ever submitted a patch? And to be honest, it looks like an issue with the Java, not the CFML?
OK. I can now see that:
Copy code
requestExclusive
Is missing from:
Copy code
public void function updateDatasource(){}
Apologies. It is a CFML issue. 🙂
If I create a ticket for this, can we add this to 5.4? We have tested the fix and it works...
z
sure
👍 1
c
Should I make a FORK of: https://github.com/lucee/Lucee/tree/5.4 And then: Create a feature branch/ticket and send you a PR?
Or can I just clone: https://github.com/lucee/Lucee.git And create a branch/ticket/PR
c
I have got some weird check errors on: https://github.com/lucee/Lucee/pull/2163
z
yeah know issues, @pothys-mitrahsoft is looking into the http ones
👍 2
c
Hi Zack Do you know roughly how many concurrent datasource connections, Lucee can handle? My team want to switch this setting on, but I am concerned that it will limit how many DSNs our system will be able to handle. We have 600 DSNs
Copy code
Exclusive connections for request

If set to true, the connections of this datasource are exclusive to one request, guaranteeing that you always have the same connection to the datasource for the request. Keep in mind that this limits the maximum possible concurrent requests to the maximum possible datasource connections and can cause a lot more open connections. Only use the requestExclusive setting when it is absolutely necessary to always have the same connection within a request, for example when your connection has set a specific state.
z
No idea but I would avoid so many DSNs myself, seems like you're asking for trouble and that setting will just exacerbate it
Load test to find your answer
👍 1