go to post Stefan Schick · Jul 28, 2022 Hello Alexey, thanks for pointing back to the manual! After re-reading this section I found the crucial sentence: ^JRNRESTO restores only to databases whose journal state is Yes at the time of the journal restore. So, if journaling at database level is set to "no", no journal restore will be performed! And as you said: ^JRNRESTO itself provides an option to disable journaling - at the far end of the configuration process. This might be the answer(s) to my initial question.
go to post Stefan Schick · Mar 25, 2022 I think I found the answer to question 1: use the .DeleteProps() method of the search table class and recompile the class
go to post Stefan Schick · Mar 25, 2022 Hi Scott, we had a similar problem with orphaned response messages. They were shown in the visual message trace as type "NULL" instead of request or respose and the MessageBodyClassName in Ens.MessageHeader was empty. We found two reasons for that: 1. business processes or operations where the pResponse parameter of the OnMessage() method was never used, e.g. Method OnMessage(pRequest As Ens.Request, Output pResponse As Ens.Response) As %Status The fix was to add a line of code to instanciate the object: Set pResponse = ##class(Ens.Response).%New() 2. Routing rules that are called synchronous respond with a "NULL" message when the Response From parameter is empty. The fix was to set the Response From parameter e.g. to "*" - the first response received will be the one returned RegardsStefan
