Closed suseela22 closed 2 months ago
@suseela22 , The jar file which was used is a backup one and was not properly built and deployed which is evident from the screenshot attached below. Kindly check after a proper build and deployment.
Class file from improper jar :
Also from the above screenshot we can notice that the JAR was run in the backup folder and was found missing in the actual deployed location. Kindly re-check once again once the correct JAR is deployed.
@rajesh-jeyaraman / @ashoksri0 , This is a process miss during build generation. CLI build pass was from a old build. Please add this to the checklist and inform Devops team to take care
We are checking the gap in the build process . Will check and update on this.
@kilam005 @rajesh-jeyaraman 192.168.1.218 server is deployed with tag 2024.01.45313_P1 on 11/3/2024. CLI module was not included in the build . This will be added in checklist for any existing or new deployment going forward. I have deployed the CLI module with tag 2024.01.45313_P1 in the server . With the latest version , the reported bug doesn't exist.
@suseela22 Can you check and provide closure for this.
Working as expected
Fix details
Team has taken steps and checklist to use the correct code base for build generation
Server: 192.168.1.218
While running the start-ads-cli.sh script to add custom template, junk characters were there as below.