Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Class not present on classpath (invalid class name)

Updated on September 10, 2021

The Class not present on classpath (invalid class name) exception appears if a custom stream processing configuration is incorrect for a File data set.

Example message text

com.pega.bigdata.dataset.file.repository.streamprocessing.CustomStreamProcessingInvalidException:
Class com.pega.bigdata.dataset.fidf configured for stream processing was not found on classpath

Next steps

Troubleshoot the settings:

  • Verify that the class name that is configured in the File data set matches the class name that you implement in the .jar file.
  • Ensure that your class definition is available on the classpath on every server node.
  • If you upload your .jar file (codeset) into the Pega-EngineCode codeset, use the codeset version that the release supports.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us