PatrykWitkowski commented on issue #10483: URL: https://github.com/apache/pulsar/issues/10483#issuecomment-833293066
If you invoke `reader.hasMessageAvailable()` before `reader.readNext()` then it works as expected. It looks like in that case during searching if there're any messages available a message id for the last message is found and the reader pointer is set for it. Logs: ``` 17:14:42.290 [] [pulsar-client-io-1-1] INFO Get topic last message Id 17:14:42.290 [] [pulsar-client-io-1-1] INFO Successfully getLastMessageId 150:0 17:14:42.293 [] [pulsar-client-io-1-1] INFO Seek subscription to message id 150:0:-1 17:14:42.308 [] [pulsar-client-io-1-1] INFO Successfully reset subscription to message id 150:0:-1 ``` You can use it as a **workaround**, but still this issue should be fixed. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
