Java Classpath Inconsistency

[Paul Glezen]

I have an outbound node implemented as a Java UPoC in site2.  The Java class file resides in the master site (site1) under site1/java_uccs.  This configuration works in my TEST environment.  When I promoted the code to my PROD environment, I encountered class-not-found errors.  I couldn’t determine the difference between the two configurations.  But when I moved the Java class file from site1/java_uccs to site2/java_uccs, the class loader found it.

Now I’m left wondering why it works in TEST.  I looked for a setting in site2 that says something like “add master site to classpath”.  I didn’t find it; but I don’t have access to an admin console.  So I may be missing something.  I couldn’t find anything in the siteInfo file that seemed pertinent.

Has anyone else observed this discrepancy?

Topic