Hello, today we had a situation with one of our client. His licenses server wasn't giving licenses. We inspected the flexnets.log file of the service and found that it was quite full of lines with "JSON error response.com.flexnet.lm.FlxException".
Here a little sample of it:
04:49:51,543 WARN No mapping found for HTTP request with URI [/rails_info/properties] in DispatcherServlet with name 'dispatcherServletRegistration'
04:49:51,543 INFO JSON error response.com.flexnet.lm.FlxException: No such REST API and METHOD combination supported: uri=/rails_info/properties with GET for user (unknown)
04:49:51,590 WARN No mapping found for HTTP request with URI [/] in DispatcherServlet with name 'dispatcherServletRegistration'
04:49:51,590 INFO JSON error response.com.flexnet.lm.FlxException: No such REST API and METHOD combination supported: uri=/ with GET for user (unknown)
04:49:51,606 WARN No mapping found for HTTP request with URI [/cgi-bin/comments.php] in DispatcherServlet with name 'dispatcherServletRegistration'
04:49:51,606 INFO JSON error response.com.flexnet.lm.FlxException: No such REST API and METHOD combination supported: uri=/cgi-bin/comments.php with GET for user (unknown)
04:49:51,606 WARN No mapping found for HTTP request with URI [/scripts/comments.php] in DispatcherServlet with name 'dispatcherServletRegistration'
04:49:51,606 INFO JSON error response.com.flexnet.lm.FlxException: No such REST API and METHOD combination supported: uri=/scripts/comments.php with GET for user (unknown)
04:49:51,606 WARN No mapping found for HTTP request with URI [/comments.php] in DispatcherServlet with name 'dispatcherServletRegistration'
04:49:51,606 INFO JSON error response.com.flexnet.lm.FlxException: No such REST API and METHOD combination supported: uri=/comments.php with GET for user (unknown)
We had to stop and start the flexnetls service. After the restart everything went normal. But we would like to avoid this in the future.
Version used of Flexnet Embedded: FlexNet License Server 2018.09 (build 237146)
Unfortunately, there isn't enough information to provide a meaningful suggestion on how to prevent this issue. We will likely need reproduction steps to troubleshoot further. If there are steps or more details you can provide, I would suggest opening a support case as well so that our support team can take a further look at it.
At the very least, I can suggest upgrading to the latest version of the FNE License Server as a precautionary measure, as it may contain changes that could have already fixed the issue.
Unfortunately, there isn't enough information to provide a meaningful suggestion on how to prevent this issue. We will likely need reproduction steps to troubleshoot further. If there are steps or more details you can provide, I would suggest opening a support case as well so that our support team can take a further look at it.
At the very least, I can suggest upgrading to the latest version of the FNE License Server as a precautionary measure, as it may contain changes that could have already fixed the issue.
