I'm also facing similar error with 11.1 version, did you find any solution to this Dave.
Does restarting tideway services resolved your issue..? or how did you manage with it..?
Did you find a solution to this problem?
I'm experiencing the same problem on 220.127.116.11
Does anyone find solution for this?
What is reported in the eca engine logs?
2 of 2 people found this helpful
I was able to resolve a very similar error. Here is my specific error:
Traceback (most recent call last):
File "./transactional_server.py", line 245, in processEvent
File "./localtransaction.py", line 170, in commit
TRANSACTION_ROLLEDBACK: CORBA.TRANSACTION_ROLLEDBACK(0x0, CORBA.COMPLETED_NO)
For me, this started after completing several application mappings via SAAM. I noticed there were a few BAI created that had a significant number of hosts (approx 44 - several more than expected from what I could see in the model definition). I unpublished the model, scanned, still an error. I exported the model, deleted model, imported model definition - same error. Deleted and recreated model from scratch. Working okay now. If you have Application mappings via SAAM, you may want to inspect the model definitions last update and when the scan errors started.
What was the error reported causing the rollback? This should be present in the ECA engine logs.
Thanks for response. I will check with my customer