User bio
404 bio not found
Member since Aug 26, 2022
Replies:
Colin Brough · 12 hr ago go to post

Looks compliant - and was running fine for a month or so before the 10th of June. Looks suspiciously like a crash of some description (whether Iris specifically, or the laptop more generally that impacted the running Iris).

*** Recovery started at Mon Jun 22 15:43:29 2026 
     Current default directory: c:\intersystems\irishealth\mgr 
     Log file directory: .\ 
     WIJ file spec: c:\intersystems\irishealth\mgr\IRIS.WIJ 
Recovering local (c:\intersystems\irishealth\mgr\IRIS.WIJ) image journal file... 
Starting WIJ recovery for 'c:\intersystems\irishealth\mgr\IRIS.WIJ'. 
  0 blocks pending in this WIJ. 
Exiting with status 3 (Success) 
06/22/26-15:43:30:375 (26160) 0 [Generic.Event] Global buffer setting requires attention.  Auto-selected 25% of total memory. 
06/22/26-15:43:31:101 (26160) 2 [Generic.Event] Failed to allocate 9938MB shared memory using large pages.  Switching to small pages. 
06/22/26-15:43:31:103 (26160) 0 [Generic.Event] Allocated 9938MB shared memory 
06/22/26-15:43:31:105 (26160) 0 [Generic.Event] 8107MB global buffers, 810MB routine buffers, 64MB journal buffers, 633MB buffer descriptors, 300MB heap, 5MB ECP, 18MB miscellaneous 
06/22/26-15:43:31:109 (26160) 0 [Crypto.IntelSandyBridgeAESNI] Intel Sandy Bridge or AMD x8 AES-NI instructions detected. 
06/22/26-15:43:31:110 (26160) 0 [SIMD] SIMD optimization level: DEFAULT 
06/22/26-15:43:31:214 (26160) 2 [Generic.Event] c:\intersystems\irishealth\mgr is locked from 
06/22/26-15:43:31:215 (26160) 2 [Generic.Event] WIJ directory locked - System not started 
06/22/26-15:43:36:234 (26160) 0 [Generic.Event] Unknown job type exited due to normal termination 
06/22/26-15:43:36:718 (34856) 3 irisctl.dll (error during startup):(289) IRIS failed to start.  IRIS Control Process terminated abnormally (exit code = 0).

This is the content of C:\InterSystems\IRISHealth\mgr\messages.log from when I started from command line.

Thanks for those that took the time to reply. Summary of where we've got to:

  • "structural" support for what we are trying to do isn't there in Ensemble 2018; another piece of ammunition to use when kicking our management into upgrading to Iris 😁
  • we had a further think, and also had a conversation with someone from WRC where were able to go into a bit more detail about our application, which resulted in a (very promising looking) solution. We already have a table whose contents includes the MessageBodyId, so we when we come to process a message for a LabReportId we can see whether there is an entry in the table for that LabReportId, and if there is compare the MessageBodyId in the table with that from the current message to ensure they are processed correctly.
Certifications & Credly badges:
Followers:
Following:
Colin has not followed anybody yet.