If an object fails to serialize, it does not get serialized with circular references allowed if it does not implement Serializable
Database connections do not get serialized to XML when storing in the database or sent to the client
Exceptions still do get serialized to XML
What is the issue: Unexpected value of DBconnection stored in Global Map causing performance issue, see attachment
OS(s) /JREs Used: virtual Window 7 with JRE version 1.8.0_173
Issue found /exists in Version(s)/Build(s): MC 3.6.0, 3.6.1
Is the Issue Consistent (list details):
Not an issue in 3.5.1, the following GlobalMap value is found instead
Acceptance Criteria:
What is the issue: Unexpected value of DBconnection stored in Global Map causing performance issue, see attachment OS(s) /JREs Used: virtual Window 7 with JRE version 1.8.0_173 Issue found /exists in Version(s)/Build(s): MC 3.6.0, 3.6.1 Is the Issue Consistent (list details):
Not an issue in 3.5.1, the following GlobalMap value is found instead
com.mirth.connect.server.userutil.DatabaseConnection@1a211e45Unexpected value observed with "Derby" mirthdb only
Slow performance observed mainly on Window
Steps to Reproduce:
Install and launch MC
Import attached channel (using JS to create DBconnection and store in GlobalMap)
Update script with available db host connection
Deploy channel
View dashboard > Global Maps
Imported Issue. Original Details: Jira Issue Key: MIRTH-4354 Reporter: narupley Created: 2018-12-14T07:32:32.000-0800