Skip to main content

Problem:

  • Product Name: Borland Enterprise Server
  • Product Version: 6.5 and above
  • Product Component: Partition Interceptor
  • Platform/OS version: All
  • JDK/Compiler version: JDK 1.4.2 and above

This article describes why the partition throws an error "Class Not Found" error while starting the partition even though the Partition Interceptors dependancy jar (application jar) file is copied to a new sub-folder under "lib" folder.

Resolution:

Firstly, the partition will not be aware of any sub-folders created under <BES_ROOT>\\var\\domains\\base\\configurations\\<config_name>\\mos\\<partition_name>\\lib, as it can recognize only the sub-folders "app", "shared", and "system".

Secondly, as the Partition Interceptor always looks for classes at the system level, so any files copied under "app" and "shared" are not visible to the Partition Interceptor.

So any dependency jar file should be copied to the <BES_ROOT>\\var\\domains\\base\\configurations\\<config_name>\\mos\\<partition_name>\\lib\\system folder so that the Partition Interceptor can find the class successfully and thus overcoming the "Class Not Found" error.


#VisiBroker
#Security
#partition
#classnotfoundexception
#AppServer
#PartitionInterceptor