go to post Oliver Wilms · Jun 13, 2019 My problem was in the Response class definition. I had Property BillingCodes As %Collection.ArrayOfObj; I replaced it with Property BillingCodes As array Of xyz; Everything gets passed along in the Response object from one BPL to the calling one. Thanks!!
go to post Oliver Wilms · Jun 6, 2019 I got the same error occasionally when parsing X12 files. Lock table got filled up when saving a transaction that contains hundreds of objects.
go to post Oliver Wilms · Apr 24, 2019 Hopefully they will tell the provider of the files to NOT send files that way and we do not need to come up with a work-around.
go to post Oliver Wilms · Jan 30, 2019 We understand what happened after we looked at the console log.We failed to acquire locks when there were two actors because the lock table was full.The rollback failed because journaling was off.We will address our configuration.
go to post Oliver Wilms · Oct 16, 2018 Hello Sean,Thank you for your response.We attempted a different approach yesterday using XML Adapter in our persistent class and routing the message to an SQL Outbound Adapter. We were able to insert data into our table. However we see errors logged in our SQL Operation (Business Operation):ERROR <Ens>ErrRequestNotHandled: Request message '13@Test.SubscriberX' not handledDo you know what we need to do to avoid getting these errors?Thank you
