Highlighted

2016 to 2018 migration with clustered scheduled tasks?

Community Beginner ,
Jun 25, 2019

Copy link to clipboard

Copied

has anyone done this?  We just upgraded one of our nodes and CFIDE is giving us an db incompatibility error.

Windows 2016 Server

MSSQL Server 2017 cu13

CF2016 Enterprise

CF2018 Enterprise

the clustered scheduled tasks was initialized with CF2016

we try to go to CF2018's CFIDE Scheduled Tasks and attach this new node to the existing datasource for the cluster that has existing running schema.

is it possible CF2018's clustered scheduler is not compatible with CF2016's clustered scheduler?

Views

96

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

2016 to 2018 migration with clustered scheduled tasks?

Community Beginner ,
Jun 25, 2019

Copy link to clipboard

Copied

has anyone done this?  We just upgraded one of our nodes and CFIDE is giving us an db incompatibility error.

Windows 2016 Server

MSSQL Server 2017 cu13

CF2016 Enterprise

CF2018 Enterprise

the clustered scheduled tasks was initialized with CF2016

we try to go to CF2018's CFIDE Scheduled Tasks and attach this new node to the existing datasource for the cluster that has existing running schema.

is it possible CF2018's clustered scheduler is not compatible with CF2016's clustered scheduler?

Views

97

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jun 25, 2019 0
Community Beginner ,
Jun 25, 2019

Copy link to clipboard

Copied

just compared the qrtz_* table schemas between 2016's and 2018's.   they're identical..

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 25, 2019 0
Community Beginner ,
Jun 25, 2019

Copy link to clipboard

Copied

i did a tiny bit of CFIDE hacking.

edited \cfusion\wwwroot\CFIDE\administrator\scheduler\scheduleTasks.cfm

line 158 in the try catch block to push the exception message to efrErrorMessage

I get the raw error on the screen :

Couldn't retrieve job because the BLOB couldn't be deserialized: coldfusion.util.CaseInsensitiveMap; local class incompatible: stream classdesc serialVersionUID = -5469900980072247315, local class serialVersionUID = -4876788950396709071

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 25, 2019 0
Community Beginner ,
Jun 25, 2019

Copy link to clipboard

Copied

i have a gut feeling that issue is CF2016 serialized the scheduler data using JRE 8's Serializer class   whereas CF2018 is trying to deserialize that same data using JDK 11.  

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 25, 2019 0