Error: Class not found: DemoLambdaV2

[mwl387]

Describe the bug When ingesting a document in the web UI, job completes. But when I try to see the results in the solution, nothing comes up. Errors show that the searchable.pdf file that should be created is not found. Digging into the Lambdas, I found that "DUSStack-dusstackpdfgenerator" had an error in the CloudWatch logs.

Class not found: DemoLambdaV2: java.lang.ClassNotFoundException java.lang.ClassNotFoundException: DemoLambdaV2 at java.net.URLClassLoader.findClass(URLClassLoader.java:387) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348)

To Reproduce

1. Deploy following "Development Deployment" section
2. After deployment successfully completes, log into solution
3. "Upload your own documents"
4. Add Management Report example
5. Wait for pipeline to complete
6. Click on "management" in document list

Expected behavior Expect to see the document to show up and rest of the metadata/interface.

Please complete the following information about the solution:

• [v1.0.3 ] Version: [e.g. v1.0.0]
• [us-east-1 ] Region: [e.g. us-east-1]
• [Y ] Was the solution modified from the version published on this repository?
• [Y ] If the answer to the previous question was yes, are the changes available on GitHub? **Included updates mentioned in older Issues to enable solution to deploy
• [Y ] Have you checked your service quotas for the sevices this solution uses?
• [Y ] Were there any errors in the CloudWatch Logs?

Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context Add any other context about the problem here.

[knihit]

@mwl387 , I deployed the v1.0.3 of the solution, added management reports and then clicked on 'management' in the document list and I am able to see the document and download the document as a searchable pdf. Please let me know if I am missing any steps here. If you have modified the original source, it is difficult for our team to troubleshoot the issue.

[mwl387]

@knihit , thanks for taking a look. The code modifications I made were related to Bug #205. So nothing that should have affected the pipeline. Maybe I'll try taking the stack down and deploying again.

[mwl387]

Turns out it had something to do with a token expiring on the Cloud9 instance I was working on. When I generated a new token and ran bash ../deployment/custom-deployment/bin/update-pdf-lambda-code.sh, the searchable-pdf jar file gets updated and the pipeline starts working properly.