|
Problem |
The WebSphere® Application Server classloader API throws a
ClassNotFoundException or returns null when loading an application classes
or resources, respectively, where the absolute path lengths of the classes
or resources exceed 260 characters. Classes or resource might exist in a
JAR or in directory, |
|
Cause |
Microsoft® Windows has a maximal path length of 260
characters. The SDK file API on Microsoft Windows does not recognize files
whose path length exceeds 260 characters (See related URL, below for
details). When executing load operations, this restriction causes
WebSphere Application Server classloaders to not find classes and
resources having path lengths exceeding 260 characters, and ultimately
causes these operations to unexpectedly throw ClassNotFoundException or
return null. |
|
Solution |
Reduce the absolute path lengths of the offending
application classes or resources. Here are some suggestions:
- Shorten length of the install_root path when installing
WebSphere Application Server.
- Shorten the length package names of application classes.
- Shorted the lengths of directory names within paths containing
application resources.
- Shorted the names of application classes and resource files.
|
|
|