search

oracle / docker-images

Official source of container configurations, images, and examples for Oracle products and projects
https://developer.oracle.com/use-cases/#containers
Universal Permissive License v1.0
6.59k stars 5.44k forks source link

FMW em PathLengthException #1626

Open aboncok opened 4 years ago

aboncok commented 4 years ago

When starting the AdminServer, the em (Enterprise Manager) application fails to start.

weblogic.application.ModuleException: Error: Unresolved Webapp Library references for "WebAppModule(em:/em)", defined in weblogic.xml [Extension-Name: emcore, exact-match: false], [Extension-Name: emas, exact-match: false]

Underlying problem is this:

weblogic.application.library.LibraryDeploymentException: [J2EE:160141]Could not initialize the library Extension-Name: emas. Ensure that the deployment unit is a valid library type (WAR, EJB, EAR, plain JAR). weblogic.application.library.LibraryProcessingException: weblogic.utils.jars.JarFileUtils$PathLengthException: /u01/oracle/user_projects/domains/fmwDomain/servers/AdminServer/tmp/_WL_user/emas/58iq7a/as/policymgr/images/cross.gif (File exists)::Probably the string length of the path of the file being extracted was too long or failed to overwrite the file

Tried deleting the tmp folder, it didn't help. The server recreated the tmp files and still threw the exception, so it shouldn't be an access right problem. Files are not open, checked with lsof. I don't know, why's the path length exception, never seen that before on Weblogic. I'm running it on Docker Desktop 2.3.0.2 (45183)

aboncok commented 4 years ago

After doing some research, it happens if the domain folder is mounted to the (Windows) host. Windows has a MAX_PATH setting of 260 characters, which causes the issue. Running the container without a mount causes no problems, but it'd be nice to be able to persist the domain files on the host.

One recommended solution is to set the LongPathsEnabled registry entry to 1. However, I already had that one set, so that doesn't help here. I wonder if this issue belongs to Docker Desktop itself. If so, this issue should be closed here.