#Worldwide Response Center (WRC)

I am using the below code in my REST service and it throws the error "java.lang.NoClassDefFoundError: com/intersys/jdbc/CacheDataSource] with root cause
java.lang.ClassNotFoundException: com.intersys.jdbc.CacheDataSource
"

Surprisingly when i am using the same code in a static main method its running perfectly.

package webapps.services.datamgmt.webapps;

import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

I am currently working on an Upgrade to HealthShare 2019.1.1. As described in the steps once the upgrade was complete to run $system.OBJ.Upgrade(). When I run $system.OBJ.Upgrade() , it is not finding any classes to update. However I am getting an Error 5116 on one of my Productions...

InterSystems has corrected several critical defects that can result in data integrity issues. These defects were identified and corrected within a short time, so InterSystems has simplified the upgrade process by consolidating them into a single package. The effects of encountering these defects may not always be visible.

InterSystems has corrected a defect that could lead to invalid backups on Windows platforms. The defect causes upgrades to disable the EnableVSSBackup setting. By default, EnableVSSBackup is enabled (value set to 1) and the upgrade sets its value to 0. Windows VSS backups taken with this setting disabled may contain invalid CACHE.DAT files.

This problem is limited to Windows platforms on the following versions:

• Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare 2019.1 (Unified Care Record, Patient Index, Health Insight, Personal Community, and Provider Directory) on Core version 2018.1.2
• HealthShare 2018.1 (Information Exchange, Patient Index, Health Insight, and Personal Community) on Core versions 2018.1.1 or 2018.1.0

The defect only occurs if you are upgrading to a version listed above. Once you have upgraded to an affected version, you must manually enable the setting; otherwise, it will be disabled on future upgrades, even when upgrading to versions containing the correction.

For customers using Windows VSS backups, InterSystems recommends enabling this setting on any 2018.1 instances of Caché or Ensemble. Once you have enabled the setting, future upgrades (including to affected versions) will preserve its value.

InterSystems has corrected a memory leak in applications that pass by reference to a formal parameter that accepts a variable number of arguments.

I'm looking to see there is a way to create a holding queue in Ensemble. I have a ORM message that is coming into the Engine. I want to convert that message into a ADT^A04. Then send the ADT first and the Original ORM message behind it. How can I hold the Original ORM before I send the ADT message before it?

I have a cache client trying to call a web service using SOAP version 1.2. We receive a SOAP error with the following text:

COD>w ##class(DBMS.Tools).DecomposeError(%objlasterror)

ERROR #6248: SOAP response is a SOAP fault: <Fault><Code><Value>s:Sender</Value>