Posted by: peteinman | July 23, 2008

Deploying WebLogic 8.1 Application on WebLogic 10MP1

Amongst other things, I’m currently evaluating what’s required to move our WLS 8.1 application to WLS 10.

My first deployment with WLST resulted in the stack trace below where the important part is highlighted in red. I thought it’d stick this on a blog as there aren’t many references to the actual solution.

<03-Jul-2008 21:55:42 o’clock BST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID
‘1215118541927’ for task ‘7’. Error is: ‘weblogic.management.DeploymentException: ‘
weblogic.management.DeploymentException:
        at weblogic.application.internal.BaseDeployment.throwAppException(BaseDeployment.java:86)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:193)
        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java

Technorati Tags: ,,

:61)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCal
lbackDeliverer.java:157)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDe
liverer.java:12)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliver
er.java:45)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.lang.IllegalArgumentException: dom4j-core,jdom,xml-apis,xerces,junit-Extension-Name
        at java.util.jar.Attributes$Name.<init>(Attributes.java:440)
        at java.util.jar.Attributes.getValue(Attributes.java:99)
        at weblogic.application.library.LibraryReferenceFactory.getOptPackReference(LibraryReferenceFactory.java:135)
        at weblogic.application.internal.OptionalPackageProviderImpl.getOptionalPackages(OptionalPackageProviderImpl.java:44)
        at weblogic.utils.classloaders.ClassFinderUtils.getOptionalPackages(ClassFinderUtils.java:140)
        at weblogic.utils.classloaders.ClassFinderUtils.getManifestClassPath(ClassFinderUtils.java:121)
        at weblogic.utils.classloaders.ClassFinderUtils.getManifestFinder(ClassFinderUtils.java:94)
        at weblogic.utils.classloaders.ClassFinderUtils.getManifestFinder(ClassFinderUtils.java:77)
        at weblogic.utils.classloaders.JarClassFinder.<init>(JarClassFinder.java:36)
        at weblogic.utils.classloaders.JarClassFinder.<init>(JarClassFinder.java:25)
        at weblogic.utils.classloaders.ClasspathClassFinder2.getClassFinder(ClasspathClassFinder2.java:87)
        at weblogic.utils.classloaders.ClasspathClassFinder2.setClasspath(ClasspathClassFinder2.java:80)
        at weblogic.utils.classloaders.ClasspathClassFinder2.<init>(ClasspathClassFinder2.java:54)
        at weblogic.utils.classloaders.ClasspathClassFinder2.<init>(ClasspathClassFinder2.java:45)

It was obviously a problem with part of something XML related. After some digging, and googling I found the following post;

the MANIFEST file of the jaxen-1.1-beta-2.jar distributed with 
xml-beans contains problematic extension entries (see end of email). 
these entries do not follow the conventions specified by sun (in 
particular, they must be separated by spaces rather than commas) and 
cause problems when installed in some containers (for example, some 
versions of tomcat 4).

the easiest way to fix this problem seems to be to remove all the 
offending lines from the MANIFEST. i wonder whether the jar in CVS 
should be amended or whether a FAQ entry would be sufficient.

http://mail-archives.apache.org/mod_mbox/xml-xmlbeans-dev/200407.mbox/%3CA1A06E52-E253-11D8-965E-003065DC754C@apache.org%3E

So, changing the “Extension-List” entry in the manifest file to have spaces rather than comma’s cured the problem for me. The correct line can be seen below.

Extension-List: dom4j-core jdom xml-apis xerces junit

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: