Client-Storage in DB not work

Description

I store the session and client-Values in a Database.
since the update from Ver 5.1.3.18 lucee do not store the client-values in the database.
When i degrade to 5.1.3.18 it works fine, without any changes in the configuration.
The session-Values stored allway in the database

Environment

Version: Lucee 5.1.3.18
Versionsname: Velvet
Release Datum: 29.03.2017
Kompatibel zu ColdFusion® Version: 2016.0.03.300357
Betriebssystem: Windows Server 2012 R2 (6.3) 64bit
Remote IP: 127.0.0.1
Host Name: 127.0.0.1
Servlet Container: Apache Tomcat/8.5.6
Java: 1.8.0_112 (Oracle Corporation) 64bit
Architecture: 64bit

Database: MySQL with InnoDB

Activity

Show:

Wilfried Wacker 19 June 2017 at 10:29

Dear Michael,

first i make a new, empty tabel for de client-Data. --> the same mistake
then i install lucce new in the newest stabel Version --> the same mistake and another mistake with the mailserver konfiguration
lucee dont store data in the client-table. the session-table works fine.

so i roll back to e previus, working Version.

Michael Offner 7 June 2017 at 16:46

the format of the storage scope has changed with 5.2 and Lucee fails to load old storage data stored by Lucee 5.1. this is not a big issue with sessions, because session normally have a lifetime under an hour.
client scope lifespan on the other side is by default 90 days (i think).

So poblem with client remains a lot longer than with sessions.

Workaround: change the name of the application by changing

this.name

in application.cfc

Michael Offner 7 June 2017 at 15:22

starting with 5.2.0.0, im getting this:

lucee.runtime.interpreter.InterpreterException: Syntax Error, invalid Expression [struct:{"timecreated":createDateTime(2017,6,7,17,5,37,473,"CEST"),"ldev1320":22,"hitcount":24,"lastvisit":createDateTime(2017,6,7,17,16,32,106,"CEST")}] at lucee.runtime.interpreter.CFMLExpressionInterpreter.interpret(CFMLExpressionInterpreter.java:222) at lucee.runtime.interpreter.CFMLExpressionInterpreter.interpret(CFMLExpressionInterpreter.java:198) at lucee.runtime.PageContextImpl.evaluate(PageContextImpl.java:3034) at lucee.runtime.type.scope.storage.StorageScopeDatasource._loadData(StorageScopeDatasource.java:132) at lucee.runtime.type.scope.client.ClientDatasource.getInstance(ClientDatasource.java:55) at lucee.runtime.type.scope.ScopeContext.getClientScope(ScopeContext.java:244) at lucee.runtime.type.scope.ScopeContext.getClientScopeEL(ScopeContext.java:275) at lucee.runtime.PageContextImpl.clientScopeEL(PageContextImpl.java:1387) at lucee.runtime.type.scope.UndefinedImpl.reinitialize(UndefinedImpl.java:599) at lucee.runtime.PageContextImpl.setApplicationContext(PageContextImpl.java:2881) at lucee.runtime.listener.ModernAppListener.initApplicationContext(ModernAppListener.java:442) at lucee.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:116) at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:43) at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2293) at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2284) at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2252) at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:891) at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:103) at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

there seem to be an issue with the CFML Interpreter

Pothys - MitrahSoft 29 May 2017 at 13:50

I've analyzed this ticket a lot confirmed the issue happened. If I upgrade 5.1.3.18 into 5.2.1.19 client storage is not working but session storage is working as expected. After downgrade into 5.1.3.18 it's working fine.

Fixed

Details

Assignee

Reporter

Priority

Fix versions

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

Sprint

Affects versions

Created 11 May 2017 at 20:36
Updated 19 June 2017 at 10:29
Resolved 8 June 2017 at 13:57

Flag notifications