Wednesday, December 22, 2010

WebSphere - Exported EAR (Enhance EAR) could not started after deployed on WPS7

On WPS7, an exported EAR file from one WebSphere environment could mot started after deployed on another WebSphere environment. When you start the deployed module, you may see the following error in the log:

[12/21/10 16:56:31:809 EST] 0000002c FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted
on /IBM2/wpsProfiles/tx1Node01/logs/ffdc/uat01Cell.AppTarget.tx1Node01.0_6a306a30_10.12.21_16.56.31.6896290038486030221913.txt com.i
bm.ws.metadata.bindings.EJBModuleHelper.processBindingsFile 199
[12/21/10 16:56:31:818 EST] 0000002c EJBModuleHelp E   CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the MA
_RSDChangeTicketEJB.jar module has a configuration error at line number: 5, column number: 131.
[12/21/10 16:56:34:348 EST] 0000002c FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted
on /IBM2/wpsProfiles/tx1Node01/logs/ffdc/uat01Cell.AppTarget.tx1Node01.0_6a306a30_10.12.21_16.56.31.8253759099213016881532.txt com.i
bm.ws.runtime.component.EJBContainerImpl.createMetaData 3439
[12/21/10 16:56:34:356 EST] 0000002c EJBContainerI E   WSVR0039E: Unable to start EJB jar, MA_RSDChangeTicketEJB.jar: CNTR0146E: The
META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the MA_RSDChangeTicketEJB.jar module has a configuration error at line numb
er: 5, column number: 131.
[12/21/10 16:56:34:359 EST] 0000002c DeployedAppli W   WSVR0206E: Module, MA_RSDChangeTicketEJB.jar, of application, MA_RSDChangeTic
ketApp.ear/deployments/MA_RSDChangeTicketApp, failed to start

Solution:

IBM provided a workaround for this issue:

1) Open Export EAR using any compression software (Ex. 7-Zip)
2) Navigate to "META-INF" folder. (Ex. MA_RSDChangeTicketApp.ear\META-INF\)
3) Open "MANIFEST.MF"
4) Add following line in "MANIFEST.MF"
GeneratedVersion: 7.0.0.0
5) Save "MANIFEST.MF"

this workaround works.

IBM are working on the ifix to solve this issue. will let you know when I get it.

 

No comments:

Post a Comment