Support Article

Connect-Java JAR files not found, runtime exception



During run time, external Java classes are not available and an error is thrown.

Error Messages Unexpected exception caught trying to generate wrapper class 'com.ace.pogo.workforce.types.prpcwrapper.GetWorkforcememberResponse, Compilation failed. See file://runtime:/PRGenJava//objwrapper_1489164361986000.log for details.

Steps to Reproduce

1. Log in to Pega 7.2.2.
2. Allow an activity to call an external class from the JAR file at run time.
3. Observe the error indicating that the class files cannot be found.

Root Cause

A defect or configuration issue in the operating environment

An external class is not available during run time.


Perform the following local-change:
  1. Add the JAR file or Java class file to the run-time classpath.
  2. Verify that the Java class or JAR file is located in Process Commander's classloader hierarchy:
    Do this using SMA, Advanced > ETier Runtime Environment > Search for class and check if it is available.
  3. In Process Commander, from the Rules by Type explorer, click SysAdmin > Dynamic System Settings.
  4. Select either the compiler/defaultClasses setting or the compiler/defaultPaths setting, as appropriate.
  5. If you are using the compiler/defaultClasses setting, enter the fully qualified Java class name.
  6. If you are using the compiler/defaultPaths setting, enter the full path to and the name of the JAR file or the path to and directory name of the unarchived Java classes.
  7. In either case, use semicolons (;) to separate entries from each other in the Value field.
  8. Semicolons (;) are used as the delimiter only. Hence, an ending semicolon is not required and changes will not work if you add the classpath entries with ending semicolon.
  9. If you use compiler/defaultPaths, a value should be file:/opt/dirContainingJar/...
  10. Save the settings.
  11. In the System Management Application (SMA), select Advanced > Class Management.
  12. Click Refresh External Jars to add the class or JAR file to the compile-time classpath.
    If it is already included, it will not get added again.
  13. Restart the server.
  14. Test the activity again and confirm there are no error messages getting thrown.

Published March 31, 2017 - Updated April 28, 2017

0% found this useful

Have a question? Get answers now.

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