L3 Workshop - Automation - Execute - Unloading of Bluesam KSDS file for compare is failing.

Question

Hi,
I am executing the automation after all the configurations done. The automation run finishes as expected but when it comes to results for Bluesam - some files fail to unload to Outputs folder. This unloading folder is happening randomly for multiple KSDS files. In one test case a particular KSDS is successfully unloaded but the same KSDS is failing in another test case. The error is related to deserialization.

![Bluesam Unload Error](/media/postImages/original/IMM0P6v_UjQruSAd9YUv0Xwg)

[exec] 2024-11-28 15:11:27.860  ERROR --- [             main] Unexpected error while exporint datasets to file system
     [exec] com.netfective.bluage.gapwalk.bluesam.core.metadata.DeserializationException: Expected token: }, read token: persistenceId 
     [exec] 	at com.netfective.bluage.gapwalk.bluesam.core.metadata.Deserializer$a.parse(Unknown Source)

This is common across all unload failures. Note that this does not happen to all the KSDS files. Majority of them have successfully unloaded and processed for comparision.

![Bluesam Unload Successful](/media/postImages/original/IMGgcVlN8kQEeiCPA_f4bpNQ)

aws-bluage-bluesam-export executable is used for the purpose of unloading and not sure if this  executable has something to do it unstable unload of KSDS files.

Any help/directions in resolving this issue will be greatly appreciated.

Thanks.

re:Post Agent · Answer

The issue you're experiencing with the unloading of Bluesam KSDS files during the L3 Workshop automation step appears to be related to a deserialization error. This error is occurring inconsistently across different test cases, which suggests it might be a timing or caching issue rather than a problem with specific files.

To address this problem, you could try the following steps:

1. Ensure that you're using the correct version of the workshop tools and executables. The L3 Workshop is designed to work with specific versions, and using an incompatible version could lead to unexpected errors.

2. Clear any cached data or temporary files that might be interfering with the unloading process. Sometimes, residual data from previous runs can cause issues in subsequent executions.

3. If you're using a local option for loading datasets, try switching to the server option instead. This change in approach has been known to resolve similar issues in the workshop.

4. Double-check that all necessary configurations and ad-hoc modifications have been correctly applied. Sometimes, missing or incorrect configurations can lead to unexpected behavior during the automation process.

5. If the issue persists, you may need to reach out to the AWS BluAge support team or the workshop facilitators for more specific guidance. They might be able to provide a targeted solution based on the exact version and configuration of your workshop environment.

Remember that while these steps may help resolve the issue, the inconsistent nature of the error suggests that it might be related to the workshop environment or tool versions rather than your specific actions.  
**Sources**  
[AWS BluAge L3 Workshop : bac.war causing issues in loading KSDS files to postgres | AWS re:Post](https://repost.aws/questions/QUQwUty_3jThWGzyZjLQodGg/aws-bluage-l3-workshop-bac-war-causing-issues-in-loading-ksds-files-to-postgres)  
[L3 Workshop. CSD does not get properly transformed. | AWS re:Post](https://repost.aws/questions/QUdSute3IVQF6JsrUCLCOHsw/l3-workshop-csd-does-not-get-properly-transformed)

Didier Durand · Answer

Hi,

From your error message `Expected token: }, read token: persistenceld`, it seems that you have a syntax error in the definition of the file.  Please, fix it to move forward.

Best,

Didier

L3 Workshop - Automation - Execute - Unloading of Bluesam KSDS file for compare is failing.

Füge deine Antwort hinzu

Relevanter Inhalt