The MANIFEST.MF filename... Oh My!
By Csoto-Oracle on Sep 01, 2011
weblogic.application.ModuleException: Missing Coherence jar or WebLogic Coherence Integration jar
The customer was following the Caching Sessions with Coherence and WebLogic Server documentation.
Taking a look at the ModuleException, the coherence.jar is part of the counter.war application, and the Weblogic.coherence.integration.jar is declared with the active-cache-1.0.jar lib which is referenced by the MANIFEST.MF of the counter application.
The entire issue was that MANIFEST.MF on the counter.war was named as "manifest.mf"; Therefore RedHat Linux could not recognize it simply due to the naming issues. So make sure that manifest file name is "MANIFEST.MF" and declares to active-cache-1.0.jar which should be deployed as a lib on the servers.
This was solved by executing the following steps:
1. Explode the counter.war application
2. Goto counter/META-INF/ directory
3. Rename the manifest.mf to MANIFEST.MF
4. Deploy as open directory or compact back to war file and deploy