Skip to content

Conversation

@Pietfried
Copy link
Contributor

@Pietfried Pietfried commented Jul 3, 2024

Describe your changes

Fixed bug that lead to incorrect transaction handling in case StartTransaction.req could not be delivered:

  • StartTransaction.conf handler retrieves a transaction based on the message id of the StartTransaction.req. In case this message is retried, the reference is updated in the message queue but not in the transaction handler
  • This change updates the start_transaction_message_id of the transaction of the transaction_handler and in the database in case of a retry

Issue ticket number and link

Checklist before requesting a review

@Pietfried Pietfried force-pushed the bugfix/update-start-transaction-message-id-on-retry branch from 7494772 to 040e959 Compare July 3, 2024 11:57
…ansaction.req could not be delivered:

* StartTransaction.conf handler retrieves a transaction based on the message id of the StartTransaction.req. In case this message is retried, the reference is updated in the message queue but not in the transaction handler
* This change updates the start_transaction_message_id of the transaction of the transaction_handler and in the database in case of a retry

Signed-off-by: pietfried <pietgoempel@gmail.com>
@Pietfried Pietfried force-pushed the bugfix/update-start-transaction-message-id-on-retry branch from 040e959 to 2d7cdad Compare July 3, 2024 12:06
@Pietfried Pietfried changed the title OCPP1.6: Fix transaction handling in case of StartTransactionr.req retries OCPP1.6: Fix transaction handling in case of StartTransaction.req retries Jul 3, 2024
@Pietfried Pietfried merged commit 6587cd4 into main Jul 3, 2024
@Pietfried Pietfried deleted the bugfix/update-start-transaction-message-id-on-retry branch July 3, 2024 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants