Can't set Session Storage to use a Datasource name / Lucee 5.1.0.34

[Michael Vornkahl]

Hi,

I have some strange findings if I try to active session/client storage in a database:

I have setup a datasource 'efactum_clientscope' in server administrator:

<data-source allow="511" blob="true" class="com.microsoft.sqlserver.jdbc.SQLServerDriver" clob="true" connectionLimit="-1" connectionTimeout="1" custom="DATABASENAME=efactum_clientscope&amp;sendStringParametersAsUnicode=true&amp;SelectMethod=direct" database="efactum_clientscope" dbdriver="MSSQL" dsn="jdbc:sqlserver://{host}:{port}" host="valid ip" metaCacheTimeout="60000" name="efactum_clientscope" param-delimiter="&amp;" param-leading-delimiter="?" param-separator="=" password="encrypted:secret:-)" port="1433" storage="true" username="secret:-)" validate="true"/>

Under Lucee 5.1.0.34 it is possible to set the Client Storage in server administrator to efactum_clientscope. But when I tried to set the Session Storage to 'efactum_clientscope' I got the error: Datasource is not setup for storage. But it is and Client Storage worked.

Now I tried to enter this via application.cfm:

<cfapplication name="efactum QM-Portal"

setclientcookies="No"

clientmanagement="no"

sessionmanagement="yes" sessionStorage = "efactum_clientscope"

setdomaincookies="No">

Then it is contrary to the definition via Server Administrator. The configuration above produced no error, but also produced no entries in the database. If I set "clientmanagement="yes" clientstorage="efactum_clientscope" lucee tries to setup the database (which already exists) and sends the following message: 

Lucee 5.1.0.34 Error (database)
Message
Detail	Der clob-Datentyp für die Spalte, den Parameter oder die Variable Nr. '4' wurde nicht gefunden.
SQL	CREATE TABLE dbo.cf_client_data (expires varchar(64) NOT NULL, cfid varchar(64) NOT NULL, name varchar(255) NOT NULL, data clob NOT NULL)

I'm using MS SQLServer 11.0.6020.0.

I tried to switch the  datasource typ in lucee: Microsoft SQL Server (JDBC4 - Vendor Microsoft) or jTDS (MSQL and Sybase) = same problem. The datasource typ makes no difference.

Any ideas?

Greetings

Michael

[Michael Vornkahl]

I've created an issue in the issue-tracker:

https://luceeserver.atlassian.net/browse/LDEV-1131

[Simon Goldschmidt]

Hi Michael... I noticed the same thing and raised ticket https://luceeserver.atlassian.net/browse/LDEV-1089

Simon