Uploaded image for project: 'Talend Component Kit'
  1. Talend Component Kit
  2. TCOMP-1370

ImageM2Mojo does not set timestamp in the docker image leading to component-server having a wrong lastUpdated value

Details

    • Hide

      I noticed this issue when I tested some corner cases by stopping the pipeline-remote-engine_component-server of a on-premise Remote Engine :

      • any requests did not fail when tcomp was down
      • any requests continued to fail when tcomp was restarted
      Show
      I noticed this issue when I tested some corner cases by stopping the pipeline-remote-engine_component-server of a on-premise Remote Engine : any requests did not fail when tcomp was down any requests continued to fail when tcomp was restarted
    • All
    • Small

    Description

      It seems that environment.getLastUpdated() returns always the date January 1st 1970, consequently, the cache is never cleared.

      org.talend.sdk.component.runtime.server.vault.proxy.service.jcache.VaultProxyCacheResolver:

          private void updateIfNeeded() {
              final Environment environment =
                      client.path("environment").request(APPLICATION_JSON_TYPE).get(Environment.class);
              // assumes time are synch-ed but not a high assumption
              if (lastUpdated < environment.getLastUpdated().getTime()) {
                  clearCaches();
                  lastUpdated = System.currentTimeMillis();
              }
          }
       

      See the attached screenshot.

      Attachments

        Activity

          People

            rmannibucau Romain Manni-Bucau
            amaumont Axel Maumont
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: