The MANIFEST.MF filename... Oh My!

In the last month I worked a Service Request along with my colleague Ernani Mattos, where on WebLogic 10.3.4, when attempting to deploy Coherance*Web, the following error occurs on RedHat, but not on Windows or Debian:
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
Comments:

Thanks for this. It saved me a few hours...

Posted by Janbo on October 18, 2011 at 05:35 AM CLST #

Post a Comment:
  • HTML Syntax: NOT allowed
About


Principal Technical Support Engineer in the Exalogic Enterprise Support Team (EEST).

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today