search

TIBCOSoftware / be-contribution

This repository is to add various contributions across different modules within TIBCO BusinessEvents. It will include contributions by TIBCO BusinessEvents team as well external users/customers/fields teams.
BSD 3-Clause "New" or "Revised" License
0 stars 9 forks source link

BE-6.3.0||Cassandra Channel || Message is not getting consumed and reflecting back during restarting of engine #92

Closed praagraw-tibco closed 1 year ago

praagraw-tibco commented 1 year ago

Version Information

Software Version(s)
BusinessEvents 6.3.0
OS Type?
OS Version?

There are 2 issues being observed:

MSG Counter variable is incrementing for data topic whenever BE-Engine is restarted Message is not getting consumed and reflecting back during engine restart.

What is the expected behavior?

What is the actual behavior?

MSG Counter variable is incrementing for data topic whenever BE-Engine is restarted Message is not getting consumed and reflecting back during engine restart.

Other notes on how to reproduce the issue?

Steps to reproduce: Cassandra server should be up and running. Pulsar should be up and running Deploy pulsar connector NAR file in the Pulsar cluster with required configuration. Insert a record into Cassandra database. Start the BE-Engine. (During this msgIn counter and msgOut Counter variables for data topic will display as '1' and msg will display in engine logs ) Close the BE-Engine and restart. (Msgout counter variable value changed to '2' and msg will display in engine logs)

Please provide log files.

BE-31626.zip

rakulkar-tibco commented 1 year ago

There is an issue with the pulsar channel implementation. Able to reproduce scenario with standalone pulsar channel consumer.

praagraw-tibco commented 1 year ago

Logged issue in JIRA: https://jira.tibco.com/browse/BE-31651

rakulkar-tibco commented 1 year ago

Pulsar guarantees at least once delivery of messages. User can change initial position using destination property ( set it to Latest) so that the start consuming position will be the last message.