1 Reply Latest reply: Apr 16, 2013 1:28 PM by 989618 RSS

    Singleton Service results in schema exception

    989618
      All -

      I am attempting to manually deploy a Singleton Service to one of our clusters via the weblogic console. I am using weblogic 10.3.6.

      After specifying a class that is in the classpath for each server via the Server Start->Classpath, choosing a preferred server and clicking finish. I get the following errors:

      -----

      <Schema validation errors while parsing config/config.xml - Invalid xsi:type qname: 'ext:crl-cert-path-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>

      ####<Mar 5, 2013 9:22:53 PM UTC> <Error> <Management> <server46> <ESB_2_MS> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ef5e150ce7dd5139:-288dd589:13d37459ac5:-8000-000000000000c93b> <1362518573283> <WL-141244> <Schema validation errors while parsing config/config.xml - /home/test/slot0/WLSDomains/slot0/<unknown>:53:9: error: failed to load java type corresponding to t=crl-cert-path-providerType@http://xmlns.oracle.com/weblogic/security/extension>

      ####<Mar 5, 2013 9:22:53 PM UTC> <Warning> <Management> <aurusdl-eis46> <SOM_ESB_EMS_2_MS> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ef5e150ce7dd5139:-288dd589:13d37459ac5:-8000-000000000000c93b> <1362518573283> <WL-141191> <The prepare phase of the configuration update failed with an exception:
      java.io.IOException: [Management:141245]Schema Validation Error in config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false
           at weblogic.management.provider.internal.EditAccessImpl.checkErrors(EditAccessImpl.java:2340)


      -----

      Any ideas?

      I checked the config.xml and it appears correct, simply adding in the <singleton-service> element. The error message it spits out is inconsistent in what it complains about. Sometimes it will say crl-cert-path-providerType and other times it will complain about the singleton service being unexpected... I have no idea how this is happening when interacting directly with the console. I also get the same error if I don't specify any class name for the service, so I know it's not a class path type issue.

      --S