Sorry for not replying to the other email. The links did not address my issue. The one related to SIGTERM was for Lima 3.x and Im using 2.10. The other explaining the consumers explained the consumers but did not address why 2 documents are being pulled from the broker input queue which is the main issue.
I’m strapped for time and Im implementing a db solution to tract the documents so I can determine which ones are being lost so I can resubmit. Would you know what the suggested replacement for Uima-AS is? Thanks for responding. Daniel Cosio dcco...@gmail.com > On Jun 3, 2024, at 11:10 PM, Pablo Duboue <pablo.dub...@gmail.com> wrote: > > Hi Daniel, > > On Monday, June 3, 2024, Daniel Cosio <dcco...@gmail.com > <mailto:dcco...@gmail.com>> wrote: > > Here is the scenario > > > > This is related to another email I sent last week. But I assumed it was the > > (what appears to be) extra consumer.. We have 3 consumers, 1 for meta, 1 > > for messages and apparently there is another one that I don’t know what > > it’s purpose is but is not related to the consumer pulling multiple records > > off the queue. > > I know. I sent you an email with a link from the mailing list archives > discussing the consumers and mentioning they were unlikely to be related to > your problem. You didn't replied to that information. Nor the other link in > my email about the shutdown hook. It's hard to help you if we talk past each > other. (Are you subscribed to the mailing list? I cc: you above just to make > sure.) > > The project no longer has people with UIMA-AS expertise and it has thus been > retired. UIMAv3 does not officially support UIMA-AS as far as I understand it. > > At this stage I suggest you open an issue for this and post a minimal code > setup to reproduce the bug. Then document the steps you have taken so far to > fix it. Over that stream of work we can pool brains and try to help. > > P >
