ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Custom Java jobs fail after Clarity upgrade with java.lang.NoClassDefFoundError

book

Article ID: 143932

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

After we upgraded, we noticed a couple of our java based jar file related job are not working in the new version whilst they are working fine in the previous version. The error is:

java.lang.NoClassDefFoundError: sun/misc/BASE64Decoder

 

Note: this error may be on any class

Environment

Release : All supported Clarity releases

Resolution

Please note that we do not support custom jobs and any customization like Java jobs are outside of the scope of our support. We recommend checking with the jobs developer to see what may have changed after upgrade as this is not something Broadcom takes the responsibility for. We only ensure the OOTB functionality is working.

This said, the error indicates that there are missing classes: java.lang.NoClassDefFoundError

Please make sure with the custom job developer, that any custom jars that are used have been copied to the correct location on the server.

If you are using any OOTB jar files, please let them know that this is not supported and they must support any missing classes, name change etc. by changing them in their Java code. 

Powered by Wolken Software