Hi

Your request class tsRequest has a property DocumentData which I assume has a data type of %String. There is one thing you need to check and to things you can do in the request class:

1) Make sure that the setting for "Support Long Strings" setting in your Cache Instance is set to true. The setting can be found in the Management Portal at System Administration > Configuration > System Configuration > Memory and Startup
 

2) in the class definition for your request class use the following definition for your DocumentData specify the definition as follows:

Property DocumentData as %String(MAXLEN="", TRUNCATE);

Turning on Long Srinngs enables you to store up to 3,641,144 characters.

The Attribute MAXLEN="" says the Maximum Length of the property is the maximum string length supported i.e. 3,641,144 characters. 

The TRUNCATE attribute will chop off any characters that exceed the MAXLEN without throwing a MAXSTRING error

Nigel

Congratulations guys! Very Impressed.

You could also try

quit ##class(Ens.Director).GetCurrProductionSettings(.pSettings)

and then

according to the documentation you should be able to use:

in Ens.Production

classmethod ApplySettings(pProductionName As %String, ByRef pSettings) as %Status

Apply multiple settings to a production pProductionName is the name of the Production to which to apply the settings
pSettings is a local array of settings structured in the following way:
pSettings(<itemName>,<target>,<settingName>)=<settingValue>
Where:
<itemName> is the configuration item name in the production
<target> Is one of:
Item: Means the setting is a property of the item itself, such as PoolSize
Host: Sets a host setting
Adapter: Sets an adapter setting
<settingName> is the setting name
<settingValue> is the desired value of the setting.

and also in Ens.Production to get the production settings use: \

classmethod GetSettingsArray(Output pSettings) as %Status
 

I haven't tried them but thats what the documentation in the class says

Nigel 

Hi

There are a couple of things to note here:

1) You can programmatically update the Production Item settings as well as the settings of the Adapter bound to the Service or Operation. What you won't see are those modified values on the Production Item Settings TAB though if you do a $$$TRACE in your code you will see that the setting value is the value to assigned to the setting.

2) The Production Item has groups of common attributes such as Information, Connection, Alerting, Development. Most of these are common to almost all production items. 

3) If you want to add a custom setting to the Production Item define it as a property. for example:

Property MaxNumberOfLoops As %Integer [ InitialExpression = 200 ]; 

and then if there isn't already a PARAMETER Settings include the following:

Parameter SETTINGS = "MaxNumberOfLoops:Basic";

This will add a field to the Basic section of the Settings TAB and in the OnProcess(), OnProcessInput() or equivalent methods you can access the property value using  normal object instance syntax:

set maxloops=..MaxNumberOfLoops

4) For a more complex example where you might want to include a drop down list of values derived from a class/table in the database you can do the following:

Property Organization As %String;

Property OrganizationId As %String [ Calculated ];

Parameter SETTINGS = "Organization:Basic:selector?context={Nigel.Production.ContextSearch/Organizations}"';

The code for this ContextSearch is specified in a class method called "Organizations" (the name that follows the ContextSearch/Name} in a class that has the following attributes:

This will populate the list with the Organization Name and you will want to maintain an array of "Organization Name" back to Organization Internal Id. You can specify the Caption to introduce spaces and other cosmetic features.

There are also some built in functions that you can make use of for the selector such as a Calendar for Dates/Date&Time, A Directory Selector, File selector, basically the standard Zen custom components which canbe handy.

As a matter of interest what production item doesn't have the Alerting section. If it doesn't, and given that apart from the development and testing section if there isn't an Alerting Section then there is probably a very good reason why alerting is just not appropriate for that item. Even Ens.Alert has an Alerting section. LOL

If you wanted to add some additional field to the Alerting section then define the property but link it to:

PARAMETER Settings="myProperty:Alerting;"

on the other hand:

I once designed an architecture where I had a an abstract device class and a whole lot of abstract adapter classes which I inherited into persistent classes and each persisted device had a unique name and in the OnInit method I would get the production item name and if i could find an entry for that name in my device Index global I would use the values from my device table to populate the production item with specific device or adapter setting values. It is a bit complex to explain here so let me know if you want any more information on how I made it work but I think that Ensemble ultimately added that sort of functionality in later releases. I think i developed my own version for Ensemble 2014 or earlier.

Finally if you are not sure if a Production Item Setting exists use the following code:

Set outputContentType=$GET(pInput.Attributes("Content-Type"),"text/xml")

and if apart from the

PARAMETER Adapter ="......";

property Adapter as EnsLib.......;

you can use something like:

set xyz=$property(..Adapter,{Property_Name}) if the property doesn't exist then it will return a <property does not exist> error if it is not a property of the Adapter class and you can check that by using the code:

if ##class(%Dictionary.CompiledProperty).%ExistsId("Classname||PropertyName") is true then the property is a property of the Adapter class 

Nigel

Hi

When did this issue start happening and what happened before this error that required the system to be shut down and restarted? Was there a system problem or just a normal restart?

It could also be the URL of the Patient Resource. In the REST Dispatcher XDATA Routing Map Block check the URL syntax:

Normally for FHIR REST Dispatchers you will see the routings will look like this:

In the IRIS for Health, HS.FHIRServer.resthandler the XDATA Block looks like this:

XData UrlMap
{
<Routes> <Route Url="/(.*)"   Method="GET"  Call="processRequest"/>
<Route Url="/(.*)"   Method="POST"  Call="processRequest"/>
<Route Url="/(.*)"   Method="PUT"  Call="processRequest"/>
<Route Url="/(.*)"   Method="DELETE"  Call="processRequest"/>
<Route Url="/(.*)"   Method="PATCH"  Call="processRequest"/>
<Route Url="/(.*)"   Method="HEAD"  Call="processRequest"/>
</Routes>
}

The Process Request will see that it is a Bundle and ultimately calls the class  HS.FHIRServer.DefaultBundleProcessor. The Bundle processor will analyze the entries in the Bundle, it looks at the Entries in the Bundle to check if there are any dependencies for Entries where the request Method is POST.  There is comment in the code that says:

// Transaction Processing:
// 1. Map 'fullUrl' -> entry# for each POST entry
// 2. Visit all references, capture:
// References that are "search urls"
// References the target one of the 'POST' entry fullUrl values
// 3. Resolve the search urls to resource references
// 4. Resolve references for each POST result
// 5. execute other operations and return result.
 

Further on it goes the following code:

if isTransaction {
if (reqObj.method  = "POST") {
// Grab the UUID if the fullUrl is specified
Set referenceKey = ..ExtractUUID(entryObj.fullUrl)
 

It uses this for the response where it returns the 'Location' and the response Bundle will specify the entry.response.fullURL

In your example you have specified the 'url' as "Patient" 

Despite all of the rest of the code I searched through I could not find any code that checked this for a leading "/"

Ultimately each Post is then dispatched to the FHIRService which will perform the POST (Interaction="Insert") and send back the Response Status that will potentially be converted into an Operation Outcome.

It's just a hunch and I suspect that adding the "/" after R4 might have the same effect but try putting a "/" into the url i.e. "url" : "/Patient"

or you could use the property 'fullUrl' instead of 'url' and see if that makes a difference

Yours

Nigel  

Congratulations Guys, well deserved

Nice piece of work Robert!

Nigel

Hi John

That's a neat solution. Thanks

Nigel

Hi

There are a couple of options. You can install Putty which allows you to connect to IRIS and behaves exactly like terminal but I suspect you will run into similar size constraints.

The other option and the one that I like an use all the time is call Web Terminal and is available in the Open Exchange.

Essentially, once you have downloaded the Web Terminal xml file and imported it into Cache/Ensemble/IRIS (it doesn't matter which namespace) you can then open your browser and type in http://server:port/terminal/ and you will be presented witha login popup where you enter your cache credentials and then you have a fully functional terminal running in your browser, in colour, with intellisense so as you start typing in class names it will auto suggest the rest of the class/property/method names, you can also run an sql shell.

Just one word of advice, if on very rare occasions the browser tab freezes and refreshing the page does not resolve the problem and you end up killing the tab or the browser then it is possible that the process that was created on your cache server for the terminal connection may be left orphaned and I have yet to work out a way of reconnecting to that process id (PID) and you may have to kill the process on the server.

Apart from that it is a great alternative to terminal and I have been using it for some years now and almost never use cache terminal or putty.

Nigel

If you have a Business Service that is acting as a Web Service server then every client connection will result in the server process spawning off a sub-process to deal with the incoming client request. The server will also detect where the request has come from (i.e. the client ip address and other CGI variables) and therefore will be able to detect whether the requests are coming from one client or many. If the requests are coming from one client then you will be able to manipulate %session to a certain extent and that client will be able to have a number of simultaneous connections to the server yet consume one 'License' however if there are multiple clients connecting simultaneously then Cache will treat them as individual 'users' and each 'user' will consume a license and depending on the license key you have installed/purchased may result in you running out of licenses. Even if you were able to successfully kill your %session (where each session is viewed as a 'user') there is a grace period of several minutes before the license is released back into the available license pool. 

The reason the system works like this is to prevent applications from supporting more users than the T&C's of your license agreement with InterSystems allows. If this functionality didn't exist then developers would be able to build applications supporting multiusers with a single user license and that would not be good business practice for ISC who license their software based on the number of users that the application is going to support. 

Nigel

Hi

Dimitry is correct in his reply that this is a memory issue. Every cache connection or ensemble production class as well as all of the system processes run in individual instances of cache.exe or iris.exe (in IRIS). Each of these processes is in effect an operating system process (or job) and when a new user process is created Cache allocates a certain amount of memory to that process. The memory is divided into chucks, there is a chunk of memory where the code being executed is stored, there is a chunk of memory where system variables and other process information is stored and then there is a chunk of memory that is used to store variables that are created by the code being executed. Whether it is a simple variable [variable1="123"] or a complex structure such as an object (which is basically a whole load of variables and arrays that are related together as the attributes of an object instance). If you are using Cache Objects then when you create variables or manipulate objects in a (class)method those variables are killed when the method quits. Another feature of Cache Objects is that if you open an instance of a very large object with lots of properties, some of which are embedded objects, collections, streams and relationships Cache does not load the entire object into memory. it just loads the basic object and then as you reference properties that are serial objects, collections and so on then only then does cache pull that data into your variable memory area. And in normal situations you can generally speaking create a lot of variables and open many objects and still have memory left over. However there are a couple of things that can mess with this memory management and they are:

1) Specifying variables used in a method as PUBLIC which means that once they are created they remain in memory until you either kill them or use the NEW command on them. Secondly, it is possible to write code that gets into a nested loop and within each loop more variables are created and more objects are created or opened and eventually you will run out of memory and a <STORE> error is generated. 

I did a quick check to see where %SYS.BNDSRV is referenced and there is one line of code in the %Library.RegisteredObject class in a method called %BindExport what calls a method in %SYS.BINDSRV. The documentation for %BindExport says the following:

/// This method is used by Language Binding Engine to
/// send the whole object and all objects it referes to
/// to the client.

So my guess is that you have a Java, .Net or some other binding and when %BindExport is called it is trying to pass the contents of your object (and any directly linked objects) to the client and that is filling up your variable memory and generating the store error. 

I also see that the %Atelier class is also referencing %SYS.BINDSRV. 

So to investigate further do you use Atelier and/or are you using class bindings (Java etc....)

If you are then something you are doing with Atelier or in you application is periodically trying to manipulate a lot of objects all at once and killing your process memory. You can increase the amount of memory allocated to cache processes but bear in mind that if you increase the process memory allocation then that setting will be applied to all cache processes. I suspect there may be a way of creating a cache process with a larger memory allocation for just that process but I have no idea if it is possible or how to do it.

It is quite likely that even if you increase the process memory it may not cure the problem in which case I would suggest that you contact WRC and log a call with them.

Nigel

Hi

There is an application DBeaver that will connect to your Cache/Ensemble/IRIS database and will generate a visual representation of your schema. I haven't tried creating tables in DBeaver and see whether it will generate a valid Cache Table/Class Definition. I suspect that it will generate classes in the same way that if you use the SQL Server import utility that will execute an SQL CREATE TABLE script and generate Cache classes/tables. Likewise you can use the SQL Gateway to connect to a SQL database and you can either create class/definitions in Cache that connect to the tables in SQL Server and leave the data in SQL Server or you can opt to create the table definitions in Cache and pull the data from SQL Server into Cache and remove SQL server altogether.

In the System Configuration and in the $system.SQL class you can manipulate how Cache Classes/Tables are created from an SQL Script or through the SQL Gateway. Including how to handle Integers and support for NULL vs Empty String.

I also found a couple of android apps called DB Scheme and Database that supports SQL Script Generation for about 8 common relational database technologies (ISC is not one of them but then we don't really push ourselves as a pure Relational database as we are primarily an Object Orientated Technology with  excellent Relational functionality and Relational Connectivity). The Android app allows you to design tables including relationship and then you select the SQL Database from the list of common Relational technologies and it will generate a SQL CREATE TABLE script. It also supports UPDATE and DELETE. It may support other functionality as well but I basically played with it for 10 minutes, built a simple table, generated the SQL Server SQL Script and then ran it through Ensemble and it created a valid Cache Table/Class. 

There is Cache based UML application that you can find in the Open Exchange tab. Download the zip file and import the classes. The documentation will tell you how to use the application. I like it because it is based on Cache Classes and Tables and therefore gives you a far more realistic view of your Cache Classes/Tables including all those nice weird things like Parent-Child Relationships, Streams, Certain Cache Data Types that we are so accustomed to using in Cache that are just not supported in other Relational classes. The only word of caution is that if your select a schema with loads of tables in it then it can take ages to render the display. I have attached a screen shot of the UML Class Explorer

Nigel