web stats
BUG: Metadata collision whem migrating to v3.5.x - Mirth Community

Go Back   Mirth Community > Mirth Connect > Development

Reply
 
Thread Tools Display Modes
  #1  
Old 02-15-2018, 01:11 AM
odo odo is offline
OBX.3 Kenobi
 
Join Date: Feb 2017
Location: Luxembourg
Posts: 129
odo is on a distinguished road
Exclamation BUG: Metadata collision whem migrating to v3.5.x

Context:
We defined in Mirth v3.4.2 a meta-data for a channel, which is called "CASE" and displays the admission id in the dashboard. When migrating a channel containing this custom meta-data to v3.5.x, this is flawlessly accepted.

Trigger:
However, as soon as the channel is deployed, it remains in the state "deploying", throws an exception and can only be stopped by stopping the service:
Code:
com.mirth.connect.donkey.server.data.DonkeyDaoException: Failed to add meta-data column
[...]
java.sql.SQLSyntaxErrorException: Syntax error: Encountered "CASE" at line 1, column 32.
[...]
 ERROR 42X01: Syntax error: Encountered "CASE" at line 1, column 32.
Finding:
If a custom metadata is named like a reserved SQL command, the adverse behavior occurs.


Workaround:
As soon as the concerned custom metadata column is renamed, the deployment and start of the channel works as intended.

Environment:
  • Mirth 3.5.1
  • Windows Server 2012R2
  • Java 8
  • Derby DB
Attached Images
File Type: jpg MetadataCollisionExceptionChannelConfig.jpg (120.5 KB, 7 views)
Attached Files
File Type: txt MetadataCollisionStackTrace.txt (3.2 KB, 1 views)
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 08:41 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.
Mirth Corporation