Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11507

Changing Insight import object type configuration leads to synchronization failure in JSON Import

XMLWordPrintable

      Issue Summary

      Changing Insight import object type configuration leads to synchronization failure in JSON Import

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create an Import configuration for JSON
      2. Create ObjectType mapping
      3. Synchronize it to import objects to Insight.
      4. Update ObjectType Mapping configurations (Ex: Threshold Type)
      5. Try editing a data locator.
      6. Synchronize again to import the objects.

      Expected Results

      1. It's possible to edit a data locator
      2. Synchronization works fine to import the objects

      Actual Results

      • It's not possible to edit a data locator with an error below pops up on the screen.

        The Jira server was contacted but has returned an error response. We are unsure of the result of this operation.

      • JSON Import fails to synchronize again post configuration changes. Please refer to the screenshot below.

      The below exception is thrown in the insight_import.log file:

      2022-05-11 14:05:54,939 [http-nio-44221-exec-2] | ============ Start import of module type rlabs-import-type-json, importSourceId: 4, number of sequential steps: 6 at time 2022-05-11T08:35:54.939Z
2022-05-11 14:05:54,945 [http-nio-44221-exec-2] | Started import in new thread, importSourceId: 4
2022-05-11 14:05:54,945 [insight-InsightThreadGroup-worker-thread-111] | sample >>> Starting import sample with id 4 of type rlabs-import-type-json with number of workers 12 at time 2022-05-11T14:05:54.945
2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | Deleting missing objects for object type id: 25
2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
2022-05-11 14:05:54,947 [insight-InsightThreadGroup-worker-thread-111] | Group [[ImportSourceOTAttr{id=14, importSourceOTId=9, created=Tue May 10 13:12:45 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=154, dataLocator=[DataLocator [locator=name]], regexp=null, delimiter=n, concatenator=null, externalIdPart=true, referencedObjectIQL=null}], [ImportSourceOTAttr{id=15, importSourceOTId=9, created=Tue May 10 13:12:54 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=157, dataLocator=[DataLocator [locator=Store]], regexp=null, delimiter=n, concatenator=null, externalIdPart=false, referencedObjectIQL=null}]] size: 2
2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | JVM Memory level low. Total JVM memory in system 1.7 GB, you still have 131.5 MB, which is 7.88% of total memory. Consider adding more memory to the JVM (-Xmx)
2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | sample>>> Started reading data for configured object type id 25
2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | Execution exception when reading data java.lang.NullPointerException
2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Fetched all data locators from external source in 1 ms

      Workaround

      Delete the respective ObjectType mapping and creating it again will fix this issue.

        1. JSON_Import_Sync.png
          JSON_Import_Sync.png
          43 kB

          Form Name

            [JSDSERVER-11507] Changing Insight import object type configuration leads to synchronization failure in JSON Import

            Michelle Chin made changes -
            Fix Version/s New: 4.20.12 [ 101992 ]
            Michelle Chin made changes -
            Affects Version/s New: 4.20.10 [ 101093 ]
            Michelle Chin made changes -
            Affects Version/s New: 4.22.2 [ 100193 ]
            Michelle Chin made changes -
            Description Original: h3. Issue Summary

            Changing Insight import object type configuration leads to synchronization failure in JSON Import

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Create an Import configuration for JSON
             # Create ObjectType mapping
             # Synchronize it to import objects to Insight.
             # Update ObjectType Mapping configurations (Ex: Threshold Type)
             # Synchronize again to import the objects.

            h3. Expected Results

             # Synchronization works fine to import the objects

            h3. Actual Results

            JSON Import fails to synchronize again post configuration changes. Please refer to the screenshot below.
            !JSON_Import_Sync.png!

            The below exception is thrown in the insight_import.log file:
            {code:java}
            2022-05-11 14:05:54,939 [http-nio-44221-exec-2] | ============ Start import of module type rlabs-import-type-json, importSourceId: 4, number of sequential steps: 6 at time 2022-05-11T08:35:54.939Z
            2022-05-11 14:05:54,945 [http-nio-44221-exec-2] | Started import in new thread, importSourceId: 4
            2022-05-11 14:05:54,945 [insight-InsightThreadGroup-worker-thread-111] | sample >>> Starting import sample with id 4 of type rlabs-import-type-json with number of workers 12 at time 2022-05-11T14:05:54.945
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | Deleting missing objects for object type id: 25
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
            2022-05-11 14:05:54,947 [insight-InsightThreadGroup-worker-thread-111] | Group [[ImportSourceOTAttr{id=14, importSourceOTId=9, created=Tue May 10 13:12:45 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=154, dataLocator=[DataLocator [locator=name]], regexp=null, delimiter=n, concatenator=null, externalIdPart=true, referencedObjectIQL=null}], [ImportSourceOTAttr{id=15, importSourceOTId=9, created=Tue May 10 13:12:54 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=157, dataLocator=[DataLocator [locator=Store]], regexp=null, delimiter=n, concatenator=null, externalIdPart=false, referencedObjectIQL=null}]] size: 2
            2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | JVM Memory level low. Total JVM memory in system 1.7 GB, you still have 131.5 MB, which is 7.88% of total memory. Consider adding more memory to the JVM (-Xmx)
            2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | sample>>> Started reading data for configured object type id 25
            2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | Execution exception when reading data java.lang.NullPointerException
            2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Fetched all data locators from external source in 1 ms
            {code}
            h3. Workaround

            Delete the respective ObjectType mapping and creating it again will fix this issue.             		New: h3. Issue Summary

            Changing Insight import object type configuration leads to synchronization failure in JSON Import

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Create an Import configuration for JSON
             # Create ObjectType mapping
             # Synchronize it to import objects to Insight.
             # Update ObjectType Mapping configurations (Ex: Threshold Type)
             # Try editing a data locator.
             # Synchronize again to import the objects.

            h3. Expected Results

            # It's possible to edit a data locator
            # Synchronization works fine to import the objects

            h3. Actual Results
            * It's not possible to edit a data locator with an error below pops up on the screen.
            {quote}
            The Jira server was contacted but has returned an error response. We are unsure of the result of this operation.
            {quote}
            * JSON Import fails to synchronize again post configuration changes. Please refer to the screenshot below.
            !JSON_Import_Sync.png!

            The below exception is thrown in the insight_import.log file:
            {code:java}
            2022-05-11 14:05:54,939 [http-nio-44221-exec-2] | ============ Start import of module type rlabs-import-type-json, importSourceId: 4, number of sequential steps: 6 at time 2022-05-11T08:35:54.939Z
            2022-05-11 14:05:54,945 [http-nio-44221-exec-2] | Started import in new thread, importSourceId: 4
            2022-05-11 14:05:54,945 [insight-InsightThreadGroup-worker-thread-111] | sample >>> Starting import sample with id 4 of type rlabs-import-type-json with number of workers 12 at time 2022-05-11T14:05:54.945
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | Deleting missing objects for object type id: 25
            2022-05-11 14:05:54,946 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Number of enabled ImportSourceOTs: 1
            2022-05-11 14:05:54,947 [insight-InsightThreadGroup-worker-thread-111] | Group [[ImportSourceOTAttr{id=14, importSourceOTId=9, created=Tue May 10 13:12:45 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=154, dataLocator=[DataLocator [locator=name]], regexp=null, delimiter=n, concatenator=null, externalIdPart=true, referencedObjectIQL=null}], [ImportSourceOTAttr{id=15, importSourceOTId=9, created=Tue May 10 13:12:54 IST 2022, updated=Tue May 10 13:16:00 IST 2022, description=null, objectTypeAttributeId=157, dataLocator=[DataLocator [locator=Store]], regexp=null, delimiter=n, concatenator=null, externalIdPart=false, referencedObjectIQL=null}]] size: 2
            2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | JVM Memory level low. Total JVM memory in system 1.7 GB, you still have 131.5 MB, which is 7.88% of total memory. Consider adding more memory to the JVM (-Xmx)
            2022-05-11 14:05:54,948 [insight-InsightImportThreadGroup-worker-thread-1] | sample>>> Started reading data for configured object type id 25
            2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | Execution exception when reading data java.lang.NullPointerException
            2022-05-11 14:05:54,948 [insight-InsightThreadGroup-worker-thread-111] | sample>>> Fetched all data locators from external source in 1 ms
            {code}
            h3. Workaround

            Delete the respective ObjectType mapping and creating it again will fix this issue.
            Yinon Negev made changes -
            Fix Version/s New: insight 8.10.5 [ 102099 ]
            Satej Mirpagar made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Alex Cooksey (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 659300 ]
            Satej Mirpagar made changes -
            Fix Version/s New: 5.1.0 [ 101095 ]
            Satej Mirpagar made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Satej Mirpagar made changes -
            Status Original: Gathering Impact [ 12072 ] New: In Progress [ 3 ]

              Unassigned Unassigned
              f75285566e0c Prabhu Subramaniyan
              Affected customers:
              5 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: