Troubleshooting
Problem
Modules that have dependent JAR files with long directory paths fail to build successfully when you use the serviceDeploy tool or when you import the project to WebSphere® Integration Developer.
Symptom
The following message is written to the serviceDeploy logs, and the Enterprise Archive (EAR) file does not build correctly:
- ENTRY com.ibm.ws.sca.rapiddeploy.headless 2 0 2008-05-19 14:46:49.899
!MESSAGE Severity: [error]
Description: IWAE0014E An error occurred validating the MANIFEST.MF file
in archive ABC-lib-frg-inst.jar.
Resource: ABC-ent-frg-institusjonsoppholdApp
Manifest-Version: 1.0
Class-Path: copiedjars/xxxxxx-xxxxxxxr-xxxxxxxxxxxxxr-inst-ejb-2.0.3.
D1-client/xxxxxxxxxxxx-fellesregister-inst-ejb-2.0.3.D1-client.jar
abc-lib-provider-fellesregister-inst-ejb-2.0.3.D1-client.jar
sssssss-commons-lib.jar
ServiceLibrary: true
Cause
The problem is caused by a problem in ArchiveManifestImpl in the org.eclipse.jst.j2ee.core.<versionNumber>.jar plug-in.
Bugzilla bug#233801 has been opened to fix the problem
https://bugs.eclipse.org/bugs/show_bug.cgi?id=233801
Environment
The problem has occurred in WebSphere Application Server V6.1.13 and WebSphere Process Server V6.1.0, and in WebSphere Application Server V6.1.1.15 and WebSphere Process Server V6.1.0.1.
The problem does not occur in WebSphere Application Server V6.0 (any version) and WebSphere Process Server V6.0 (any version).
Note: The problem might occur when the projects are migrated to the new version of WebSphere Application Server V6.1 and WebSphere Process Server V6.1.
Resolving The Problem
This local fix resolves the problem.
The manifest file has a size restriction of 72 bytes. Make sure that your class path is less than 60 bytes (72 max - 12 (class-path: ) = 60 ).
Decrease the length of the dependent library and any client names to resolve the problem.
Related Information
Product Synonym
WPS;WID
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21317616