Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Creating a data source sets weird connectionLimit

Description

After creating a new data source it’s not really clear what the connection Limit setup is.

Recreate:

1. Setup new DS. Don’t change anything re timeouts or connection limits, just leave defaults. connectionLimit sits on inf (-1). Save.

2. Check lucee-server.xml - there’s no connectionLimit property set in the XML for the new data source, indicating it’s using whatever the default is (I’d expect that to be inf/-1 --- see above).

3. Open data source edit screen for the new data source: UI shows there’s a limit of 100 now set for connectionLimit.

4. Be more confused when looking at the code shown at the bottom of the page:

this.datasources["test1-savedwithoutchange"] = { class: 'com.microsoft.sqlserver.jdbc.SQLServerDriver' , bundleName: 'org.lucee.mssql' , bundleVersion: '7.4.1.jre8' , connectionString: 'jdbc:sqlserver://localhost:1433;DatabaseName=test1;sendStringParametersAsUnicode=true;SelectMethod=direct' , username: '' , password: "" // optional settings , connectionLimit:100 // default:-1 , liveTimeout:15 // default: -1; unit: minutes , validate:false // default: false };

 

So, where’s the 100 coming from after the initial creation of the data source? Is 100 the real default and not -1 as shown above and on the initial creation screen?

And what IS really being set now? 100? If so - it’s not reflected in lucee-server.xml for me. Is there another place/default where the 100 is being retrieved from?

When I set it to - say: 200 - and update/save the data source → connectionLimit is correctly set in lucee-server.xml.

I’m unsure if this is a UI issue (initial creation default of “inf” should be 100 and the code samples are wrong) or if there’s something else murky with this setting in lucee-server.xml.



Environment

5.3.9.160
MSFT SQLServer JDBC drive 7.4.1 (prob a general JDBC/data source issue though)

Attachments

1
  • 19 Sept 2022, 05:43 am

Activity

Show:

Pothys - MitrahSoft 19 September 2022 at 14:17

Already has a ticket for this issue https://luceeserver.atlassian.net/browse/LDEV-1445 and this issue was fixed in the lucee 6.0, now I reopened the ticket and added a PR for 5.3.

So I closed the ticket as duplicate

Duplicate

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 19 September 2022 at 05:40
Updated 19 September 2022 at 14:21
Resolved 19 September 2022 at 14:18

Flag notifications