-
-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Foreign key failure with meter values report #61
Comments
in the meter values message, the optional transaction id parameter is set ( steve indeed accepts meter readings that do not belong to a transaction, but in such cases the optional transaction id should not be set. |
Sevket, Perhaps a SOAP fault text of "invalid transaction ID" would be clearer than the raw SQL error text. Not worth a lot of effort, though. |
i agree on both. since the database model already enforces such integrity/constraint checks, we trust it and do not do the same kind of check in application code. for example, there are several messages which might reference transaction and/or reservation ids. before processing these messages, we could do another database round trip just to check whether this transaction/reservation exists and just to respond with a more appropriate error message. i'd argue that the benefit is not worth the extra processing overhead. or we could process the java exception (for example the one you got from db) to find out what the reason was. but we do not do this for reasons explained here. |
Usually i would advise against vendor specific workarounds, but treating an transaction id 0 in the same way as if was ommited seems not too bad. |
@csamsel in wsdl files, transaction id is an over time, steve already became more and more tolerant, since we dialed down its strictness. but this is one case i would be against. |
I have an OCPP1.5 charge point (Delta AC Mini, v02.05.30 firmware) which is configured for periodic meter values reporting. After powering up the charge point, the first meter values report fails.
Without analyzing code, I speculate that perhaps Steve isn't set up to accept meter readings that don't belong to a transaction?
Charge point POST (periodic meter values report):
Central System reply (database error)
The text was updated successfully, but these errors were encountered: