Hi, so encounter a pretty sever problem this morning that I think needs addressed and answered to here.
Experienced a problem with the TestRail db that caused some dead-locking that in turn caused the front end to be unresponsive. However, aside from that , experienced a whole other problem with Jira.
With TestRail unresponsive, the plugin kept trying to connect to TestRail (through the apis I presume) to get data to provide to Jira, but because the server was unresponsive this created a looping set of socketConnect that eventually took down Jira with high general traffic on top of the threading connection being created by the TestRail plugin. This is a sever issue and needs to be handled correctly in the plugin.
- Is there a configurable option to the plugin to control connection retires - I do not see anything and there needs to be one?
- Why does the plugin continue to consume many connection threads within the max thread pool if non-responsive in the first place?
Please someone let me know if there is something in place to control this behavior so Jira does not crash due to the plugin when TestRail is unavailable - for whatever reason.