[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [sw360-dev] Long delays on deployment with sw360chores
|
Hello,
thanks for pointing this out! good catch!
Kind regards, Michael
> On 1. Oct 2019, at 18:17, Leo von Klenze <leo.vonklenze@xxxxxxxxxxxxx> wrote:
>
> Signed PGP part
> Hi all,
> some of you reported long delays when starting SW360 with sw360chores and accessing a page afterwards. There was now another hint by @imaykay. He experienced the issue while observing a codescoop exception in the log.
>
> As it turns out, the component portlet checks on every view if codescoop is active by asking the codescoop backend service. However this service is not deployed by default. For some reason this check does not fail immediatley all the time but runs into a thrift timeout (which defaults to 10min). It is not clear why the request is failing immediately after some time SW360 is running. Maybe it depends on the page that is visited first.
> To summarize: you may try to set CODESCOOP_ACTIVE in ComponentPortlet.doView to false and see if the problem persists.
> We should check if we can make a property activate/deactivate codescoop at all so this request is not done all the time (might be good for fossology checkup as well).
> Best
> Leo
> --
> Leo von Klenze
> Geschäftsführer
> +49 176 10072624
>
> <top_supplier.jpg>
> Scansation GmbH
> www.scansation.de
>
> Zielstattstr. 133, 81379 München
> Geschäftsführer: Andreas Klett, Leo von Klenze
> Amtsgericht München, HRB 227036
>
>
>
