Uploaded image for project: 'CloverETL'
  1. CloverETL
  2. CLO-9875

Server Temp Space setting not being used after restart

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: rel-4-2-0, rel-4-3-0, rel-4-3-1
    • Fix Version/s: rel-4-4-0
    • Component/s: Server
    • Security Level: Users (General product issues)
    • Branch:
    • QA Testing:
      UNDECIDED
    • QA Test Identification:
      com.cloveretl.server.test.tempmgr.TempSpacesTest; com.cloveretl.server.test.config.ExportImportTest.testImportExportTempSpaces()
    • OTRS_Ticket_ID:
      2016111610000311
    • Sprint:
      BRQ Sprint 26, BRQ Sprint 27

      Description

      A customer found an issue when configuring a temp space on Server. After adding a temp space location and restarting the Server, that temp space is not active or visible in the Console. If you try to create the temp space it fails with Temp space already exists. It also seems the ${java.io.tmpdir}/clover_temp_{number}, creates a new default temp space every time the CloverETL Server is restarted. The customer is using Linux and PostgreSQL as his DB, but I test it out with Windows and MySQL and it behaves the same way

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                reichmanf Filip Reichman
                Reporter:
                vazquezrosariop Pedro Vazquez
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: