ppawel commented on PR #30218: URL: https://github.com/apache/beam/pull/30218#issuecomment-2037429676
@Abacn I just upgraded to Beam 2.55.0 in my project and my streaming pipeline that uses JmsIO gets stuck during consuming messages, it was working fine with Beam 2.53.0 and earlier. I tracked this down to changes in this PR related to managing JMS resources (consumers, sessions etc.) I have a test case in my project that simply publishes around 60 messages to a queue and then a Beam pipeline is executed to consume and process those messages. This test case was passing before but now it works like this: 1. 60 messages are published to a queue in Solace (message broker we use). 2. Pipeline is started, first consumer is created in JmsIO and it fetches all 60 messages into the internal buffer of the consumer. 3. Beam pipeline consumes 10 messages (`advance` is called 10 times in JmsIO). 4. 10 messages are acked, checkpoint is made and `recreateSession` is called in JmsIO (this is the new code introduced in this PR). 5. New consumer is created, old one is closed. 6. New consumer does not get the messages anymore - the broker seems to think that the first consumer is just late with acknowledging the remaining 50 messages. 7. Pipeline hangs forever, `advance` is called all the time but brings no new messages. 50 messages remain sitting in the queue not consumed. Does this scenario make sense or do I miss something in how JmsIO should work? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
