X

@OracleIMC Partner Resources & Training: Discover your Modernization options + Reach new potential through Innovation

Admin Server Startup fails with parsing failure in config.xml

Gokhan Goksu
Technology Consultant

While I was working with one of our partners here at the Oracle Partner Hub Migration Center in Turkey, I faced a problem where I can't restart the Admin Server with an error :

BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: 
failed to find method MethodName{methodName='setCacheInAppDirectory', paramTypes=[boolean]} on class weblogic.management.configuration.AppDeploymentMBeanImpl>".

Apparently Weblogic was not happy with a config.xml file parameter and the config file was corrupted. After digging at the config.xml file we found out that for every deployment, a new <cache-in-app-directory> parameter was added to the config file. Also the recent change made by partner was  rolling back a PSU that was applied to their Weblogic Server. 

After searching for the error on Oracle Support, we saw that whenever you rollback the PSU, config file schema definition changes introduced as part of the PSU were also rolled back. But as for the bug 20852182 , config.xml file still had the <cache-in-app-directory> element which caused parsing errors while starting the servers.

After manually removing <cache-in-app-directory> elements from the config file, inside every <app-deployment> , we were successfully able to start the Admin Server. Another workaround is also to add -Dweblogic.configuration.schemaValidationEnabled=false" to  Server Startup scripts like:

JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.configuration.schemaValidationEnabled=false" 
export JAVA_OPTIONS

I hope this post will help you in case you come across this problem with Weblogic Server. 

Facebook Google+ Twitter LinkedIn Pinterest Delicious Digg Addthis

Join the discussion

Comments ( 5 )
  • guest Friday, March 10, 2017

    Nice article It worked...


  • Don Pate Wednesday, November 29, 2017
    This worked for me too. Tried to roll back PSU as part of our QA testing and ran across this issue. Thanks for sharing. Very clear explanation.
  • Ken P Tuesday, June 19, 2018
    I have been banging my head against a wall for the past week trying to redeploy applications after a PSU rollback... this indeed was the fix that worked for me. Thank you for the clear explanation.
  • Praveen Wednesday, May 1, 2019
    This solution worked for me. Thank you very much.
  • Matthew Uribe Wednesday, May 8, 2019
    Hugely helpful. Thank you Gokhan.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.