Replies: 1 comment
-
Resolved! I looked at the zep file from version 4 and version 5. As per a security concern that was raised a while back, it was decided to throw an execption instead of commit any uncommited transactions, forcing the developer to make sure they commit the logs, which clears the transaction queue correctly. Thanks. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello All,
I upgraded from v4 to v5 and since the upgrade, I see this exception being thrown on every reply I receive from the server.
There is an active transaction in phalcon/Logger/Adapter/AbstractAdapter.zep on line 64
I am using transaction to log messages using begin() and commit()
To commit:
Comparing the AbstractAdapter.zep files from v4 to v5, I see this exception was added to the __destruct() instead of this->commit()
Any suggestion on how to fix this?
Beta Was this translation helpful? Give feedback.
All reactions