I do not see the error stack here. external jar itself should have nothing to do with the temp directory as it is stored in db and it is loaded by engine during earch node startup, did you restart the nodes after importing the jar? How do you use the java classes in the jar?

Can you confirm the version of PRPC here: the newer (6+) versions store Java Classes in a central location (the Database - as Kevin says) : older versions used the more traditional file system approach).

Additionally: you have to reboot the nodes in order to see any newly import JARs .... (as Kevin also says).

Also: you refer to the JAR as 'externalize' - do you mean you have dropped it on the filesystem rather than import the JAR ?

Hi,

PRPC version for our application is 6.3 SP1. We already checked the classes are there pr_engineclasses table.We imported the jar file in one of the node and we restart both the node.But still this is working in only one node from where we imported the jar and not working in other node.

I have attached here the error stack trace with this.

Thanks

Piyali

Have you tried to delete the pega temp dir content for the non-working nodes before restart? Since your jar are shared by all nodes, you should look for differences among nodes, this being the first thing to check.

Yes, We had deleted temp directory for both the nodes before retsart after importing the jar.We checked the the configuration,which are same for both the nodes.Please let me know if we need to do some additinal steps for the other node working.