Correct the numerous FOSSology Portlet Exceptions

[maierthomas]

Issue by mcjaeger
Thursday Mar 29, 2018 at 13:12 GMT
Originally opened as sw360/sw360portal#801

---

In the log, there is too much output like:

2018-03-28 12:28:53,913 ERROR FossologyAwarePortlet:168 - Could not get release from request
 2018-03-28 12:28:53,914 ERROR FossologyAwarePortlet:136 - no response from backend!

This is apparently, if the request does not have a release id: then, this log message rises. Maybe this is coming from the project portlet which doe snot hold releases and then the logic pulled in from the FOSSology portlet via the inheritance hierarchy is triggered with this error.

[maierthomas]

Comment by alexbrdn
Tuesday Apr 03, 2018 at 07:43 GMT

---

If I am not mistaken, this is caused by JS function utils/includes/fossologyClearing.initialize(), which is invoked when a page has just been loaded, but no release has been selected yet.

[mcjaeger]

just tested and also did not see this for a while: solved.