15 + years Solutions-oriented Integration Interface Specialist with notable success directing a broad range of corporate IT initiatives while participating in planning and implementation of Integrated solutions in direct support of business objectives. Specialties: Design/Development of MS and Oracle SQL Databases, HL7 Ancillary Solutions, and Intersystem Ensemble Solutions. Integrating it all together to create a more robust environment.
While working with Intersystems Ensemble and now IRIS, I have greatly expanded my knowledge of Ensemble and Cache Object Script by asking questions and watching the Developer Community. I tend to ask questions, then figure out the answers on my own or with a little help from others.
Before Intersystems Ensemble, I spent many years as an eGate developer. Specializing in DART, JDBC, and other out of the normal odds and ends.
interesting theory to try, someone on my team changed it to cover it to stream, and put it back into the message before this answer. the Physician memory usage went down, the virtual memory usage went up. However, the error seemed more at the Routing than the DTL. It may have something to do with Locking and trying to send to multiple locations in a single send.
With the way that we built our namespaces, I had to create a smaller namespace that included all of our nuances that we do like... BPL making JDBC MS SQL Stored Procedure calls, making internal cache calls, making linked table/store procedure calls.
Larger namespaces will cause the comparison run to take longer to run.
So, my mini namespace is used to test new versions of HealthShare Health Connect.
The rule was just routing the message through a DTL and sending it to two places in the same line.
The message size was 12661.
My team member just ended up splitting up the send line into multiple send lines instead of a single send line with two destinations.