WebLogic's High-Performance XML parser

I understand that 6.1's high performance XML parser is the replacement of 6.0's
custom generated parser. Per the documentation, I need to set SAXParserFactory
to weblogic.xml.babel.jaxp.SAXParserFactoryImpl, but I couldn't find weblogic/xml/babel/jaxp/SAXParserFactoryImpl
in either weblogic.jar or xmlx.jar. There are bunch of weblogicx/xml/babel/* in
xmlx.jar.
When I call JAXP code, I got this error:
javax.xml.parsers.FactoryConfigurationError: Failed to find SAXParserFactory.
weblogic.xml.babel.jaxp.SAXParserFactoryImpl
javax.xml.parsers.FactoryConfigurationError: Failed to find SAXParserFactory.
weblogic.xml.babel.jaxp.SAXParserFactoryImpl
Am I missing something, or the 6.1 beta download forget to include the *.babel.jaxp.*
stuff?
Jim Zhou.

Jim,
Please don't use System.setProperty() in any server code. This was intended
as an example only. I think the XMLReaderFactory is not specified in
JAXP1.1.
Thanks,
Chris
"Chris Fry" <[email protected]> wrote in message
news:[email protected]...
Jim,
Here is a code fragment to acess the parser:
System.setProperty("javax.xml.parsers.SAXParserFactory","weblogic.xml.babel.
jaxp.SAXParserFactoryImpl");
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
parser.parse("yourfile.xml",defaultHandler);
"Jim Zhou" <[email protected]> wrote in message
news:[email protected]...
I just found out that XML Registry setting on SAXParserFactory does notapply to
XMLReaderFactory() and XMLReader:
XMLReader parser = XMLReaderFactory.createXMLReader();
I have to use SAXParserFactory to get High Performance Parser kicked in:
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
Is this the right behavior? Thanks for the help.
Jim Zhou.
"Jim Zhou" <[email protected]> wrote:
Chris,
Thanks for the reply. It still doesn't work. I think the problem is
that weblogic.jar
and xmlx.jar both does not have eihter
"weblogicx.xml.babel.jaxp.SAXParserFactoryImpl"
or "weblogic.xml.babel.jaxp.SAXParserFactoryImpl". So the current Beta
download
forgot to include the above classes. I might try download Beta again
to see if
any difference.
Regards,
Jim Zhou.
"Chris Fry" <[email protected]> wrote:
Jim,
This is a mismatch between our beta and the final place that the
parser
will
live in the release, you should be able to get the parser by setting
the
SAXParserFactory to weblogicx.xml.babel.jaxp.SAXParserFactoryImpl (it
will
be weblogic.xml.babel.jaxp.SAXParserFactoryImpl in the final release).
A couple notes:
The parser only handles standalone documents, with no entityreferences
and
is optimized for small to midsize documents (IE soap and wsdl type
documents).
Pleas let me know if you can get it to work.
Chris
"Jim Zhou" <[email protected]> wrote in message
news:[email protected]...
I understand that 6.1's high performance XML parser is the
replacement
of
6.0's
custom generated parser. Per the documentation, I need to setSAXParserFactory
to weblogic.xml.babel.jaxp.SAXParserFactoryImpl, but I couldn't findweblogic/xml/babel/jaxp/SAXParserFactoryImpl
in either weblogic.jar or xmlx.jar. There are bunch ofweblogicx/xml/babel/* in
xmlx.jar.
When I call JAXP code, I got this error:
javax.xml.parsers.FactoryConfigurationError: Failed to findSAXParserFactory.
weblogic.xml.babel.jaxp.SAXParserFactoryImpl
javax.xml.parsers.FactoryConfigurationError: Failed to findSAXParserFactory.
weblogic.xml.babel.jaxp.SAXParserFactoryImpl
Am I missing something, or the 6.1 beta download forget to includethe
*.babel.jaxp.*
stuff?
Jim Zhou.

Similar Messages

  • High Volumn XML Parser

    We have more than 4000+ XML file, and we would like to generate the index pages (a-z) and date index pages (2008/Jan, 2008/Feb/ ... )
    we use Xml beans to parse the xml,
    it works , but the performance which is not that good
    it took at least 5-10 minutes to complete the generation.
    Can someone advise any better XML parser or better methodology ?
    Thanks
    Calvin

    We have more than 4000+ XML file, and we would like to generate the index pages (a-z) and date index pages (2008/Jan, 2008/Feb/ ... )
    we use Xml beans to parse the xml,
    it works , but the performance which is not that good
    it took at least 5-10 minutes to complete the generation.
    Can someone advise any better XML parser or better methodology ?
    Thanks
    Calvin

  • Weblogic 6.1 and xml parser empty elements

    FYI, It looks like Weblogic changed there xml parser in the transition from
    6.0sp2 to 6.1. Example : The empty Extra Info Class produced and error,
    because it is empty. Where in 6.0sp2 it did not produce and error:
    <taglib>
    <tag>
    <name>indexProperty</name>
    <info>
    some info..
    </info>
    <tagclass>com.pssg.jsp.tags.IndexPropertyTag</tagclass>
    <teiclass></teiclass>
    </tag>
    </taglib>
    ####<Aug 20, 2001 12:20:52 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101047>
    <[WebAppServletContext(7008653,cam,/cam)] resolved taglib uri '/pssglibtags'
    to taglib-location /WEB-INF/tlds/pssgtaglib.tld:>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101160> <Deployment
    descriptor is malformed, check against the DTD:
    org.xml.sax.SAXParseException: The content of element type "tag" must match
    "(name,tagclass,teiclass?,bodycontent?,info?,attribute*)"..>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Error> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101020>
    <[WebAppServletContext(7008653,cam,/cam)] Servlet failed with Exception>
    weblogic.servlet.jsp.JspException: (line 1): Error in using tag library
    uri='/pssglibtags' prefix='pssglibtag': For tag 'indexProperty', cannot load
    extra info class ''
    at
    weblogic.servlet.jsp.StandardTagLib.tld_jspException(StandardTagLib.java:901
    -Scot

    hi,
    there are two versions of ldap supported in wls6.1 , ldapv1 and ldavp2
    ldap v1 only has the functionality of listing groups.
    but where ldapv2 doesn't have that functionality,
    by looking at your config , it seems you are using ldap v2..
    if u need that functionality u can use ldapv1.
    thanks
    kiran
    "Bert Cliche" <[email protected]> wrote in message
    news:[email protected]..
    Per a proof of concept, I am having trouble getting WL6.1 to see
    group members as defined in iPlanet LDAP. I can see the groups,
    but modifies to create groups only create them in the local DB.
    Created users also only get placed in the local DB. I can bind
    for searches as Directory Manager via ldapsearch and run queries,
    and the DS gateway works fine. I can dump the LDIF file and the
    entries look fine.
    I copied and modified the template for the Netscape server and
    have the realm setup per the GUI.
    For sanity, everything is very generic as:
    the Root DN is "o=test.org"
    and my "Configuration" part from the config.xml looks like:
    server.authprotocol=simple;
    server.host=localhost;
    membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));
    server.port=390;
    group.dn=o=test.org;
    group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
    server.principal=cn=Directory Manager;
    user.dn=o=test.org;
    server.groupiscontext=false;
    user.filter=(&(uid=%u))
    I added the "authprotocol" as a guess. Note that the server is
    running on port 390, this is not a typo.
    Any ideas what is going wrong?

  • Which XML Parser gives best performance? Please respond!!

    Hi,
    I am trying to figure out what is the best performing XML parser. I know that SAX implementation is good for XML reading and DOM is good when building XML documents.
    Now, I want to know which parser (JAXP? JDOM? Piccolo?) I understand that JAXP underneath uses Xerces and SAX2. Is it right?
    Is it a good practice to have a single application using a SAX parser for reading xml docs and a DOM parser to build xml parser?
    We are also planning to migrate from Apache Soap to Apache Axis. Do you have any recommendations?

    I think JAXP is an API, not a parser. It uses an underlying parser called Crimson by default. If you want it to use other parsers you can configure it to do so. I can't tell you which parser is more fastest.
    The easiest way of reading and writing XML documents is to use an XML data binding library such as JAXB or castor. It's much nicer than implementing the SAX callback methods or building document trees. The steps involve are...
    1. Write an XML Schema
    2. Tell the XML data binding tool to generate the source code to marshall / unmarshall XML documents to and from java objects
    3. Compile the source code
    4. Package the classes into a library
    5. Use the library in your application
    Steps 2-4 can be added into your build script.
    It may take you a couple of days to become familiar with the tools, but will save you weeks of maintenance & debugging.

  • Memory Utilization during XML Parsing - Response time is high

    Slow response time while xml parsing is done.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes

    "Kris" <[email protected]> wrote in message news:40f2fcda$1@mktnews1...
    Sorry, I overlooked it.
    yes we do have 8 GB RAM. And as far as xml usage, we are parsing the xml to DOM
    (including validation) and then applying transformation. But its the parsing stuff
    which is eating the memory.1. Can you run JProbe to find out real CPU utilization/bottlenecks?
    2. Apache Xerses implementation that is used in weblogic has a design
    flaw that results in serialization of memory allocation by the transformer,
    that makes it impossible to use for intense multithreaded transformations.
    Consider using other transformers.
    Regards,
    Slava Imeshev
    >
    >
    "Slava Imeshev" <[email protected]> wrote:
    Please answer my questions.
    Regards,
    Slava Imeshev
    "Krisna" <[email protected]> wrote in message news:40f299ae$1@mktnews1...
    Thanks Slava for youe response. Coming back to response time, thisprocess is part
    of a big task. So i cant really tell what response time i can allocatejust for
    this piece alone. Might be, roughly it should be less than 0.4 seconds.what the
    major concenr is the memory utilization by these packages. So whatmakes it to
    use this kind of memory and whether its a known issue ?
    "Slava Imeshev" <[email protected]> wrote:
    "kris" <[email protected]> wrote in message news:40eaddce$1@mktnews1...
    Slow response time while xml parsing is done.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently thatgarbage collection
    is occurring multiple times per minute, impacting performance. In
    order
    to better
    understand the source of the memory usage issue, we used JProbe
    Memory
    Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determinewhich classes
    were using the most total or aggregate memory (the sum of the memoryrequired
    to instantiate not just a given object, but all the objects it uses.)The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap
    of
    121MB. In
    additional tests, the larger the heap, the greater these percentageswere.
    Large heap means longer garbage collections. Anyway, DOM is very heavy
    on memory and you can not escape it. What's is your usage patternfor
    XML
    processing? Do you use XSL?
    This results in slow response time.What do you consider as acceptable/inacceptable responce time?
    The following are the details of software and Hardware configurationsused:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 MegabytesDoes this mean you got 8GB RAM on 150Mhz box?
    Regards,
    Slava Imeshev

  • XML Parsing in Weblogic

    Hi all,
    Am releatively new to weblogic and am migrating my web app from the tomcat container to weblogic 9.2
    I use a XerxesImpl jar to parse my XML using a DOMParser and I dont want to use any libraries provided by weblogic atleast now!!
    It always gives the SAXParserException, but the same bit of code works fine with the tomcat container.
    I have also checked for the well-formedness of the xml and the xml and the dtd looks fine.
    Any inputs on this would help!
    Thnx
    Cyrus

    The solution to this being that ---
    1. Whenever using the local jar file for any XML parsing such as XerxesImpl.jar the weblogic provided services may try to override it and hence must be added on to the classpath before the ap[plication is deployed.
    2.Also that somtimes the pageContext.getServletContext() returns a null and hence some other means mustbe found to find the corresponding xml file.(probably loading it as an initparam)
    3. Also make sure that your xml matches the dtd declarations since atomcat container doesnt validate this but the weblogic container.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • NullPointerException is weblogic xml parser

    We are using weblogic server 8.1 SP4 on HP Tru64.
    A NullPointerException is happening when parsing documents. I tried to find the source code however could not match the source version with the line numbers. Is this a problem in the message? Or a bug in the parser?
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:notificationOfApprovalResponse xmlns:ns0="http://www.auspost.com.au/elms/xml/notificationofapproval/response" elmsMailingStatementId="775507" pricingStatementNumber="0070922517">
    <notificationOfApprovalStatus>
    <code>S</code>
    <extendedCode>233</extendedCode>
    <description>ORDER_HEADER_IN has been processed successfully VBAKKOM </description>
    </notificationOfApprovalStatus>
    </ns0:notificationOfApprovalResponse>
    java.lang.NullPointerException
    at weblogic.apache.xerces.util.XMLAttributesImpl.getName(XMLAttributesImpl.java:261)
    at weblogic.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:428)
    at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:877)
    at weblogic.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:569)
    at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:727)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:759)
    at weblogic.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:957)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1544)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
    at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
    at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
    at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
    at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
    at com.bea.xbean.store.Root$SaxLoader.load(Root.java:776)
    at com.bea.xbean.store.Root.loadXml(Root.java:1077)
    at com.bea.xbean.store.Root.loadXml(Root.java:1069)
    at com.bea.xbean.store.Root.loadXml(Root.java:1089)
    at com.bea.xbean.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:241)
    at au.com.auspost.elms.xml.notificationofapproval.response.NotificationOfApprovalResponseDocument$Factory.parse(Unknown Source)

    WLS 6.1 is not yet certifed with JDK 1.4.
    Venki wrote:
    Hi,
    Does weblogic ships it's own XML parser.
    We tried parsing an XML document using JDK1.4(default XML parser) it all worked
    well, but after deploying in weblogic container, the document didn't parse correctly.
    We are using Weblogic 6.1 sp2.
    Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
    i guess.
    Any comments , help thanx !
    Venki--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • XML parser performance

    Hello,
    I was wondering if anybody had any experience in regards to the relative performance (i.e., speed) of the different Java XML parsers out there. Specifically,
    javax.xml.parsers.DocumentBuilder.parse() vs. any others.
    My goal is to reduce the amount of time needed to parse ~1000 XML files (avg size 3kb) and I have done some tests that lead me to conclude that the rate-limiting step is not the file i/o (surprisingly).
    Is there any particular XML parser that people favor?
    Thanks,
    ckl

    I have created a parser with interesting performance result with
    files < 100 Ko at http://www.japisoft.com/fastparser
    Regards,
    A.Brillant

  • Weblogic  XML Parser ?

    Hi,
    Does weblogic ships it's own XML parser.
    We tried parsing an XML document using JDK1.4(default XML parser) it all worked
    well, but after deploying in weblogic container, the document didn't parse correctly.
    We are using Weblogic 6.1 sp2.
    Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
    i guess.
    Any comments , help thanx !
    Venki

    WLS 6.1 is not yet certifed with JDK 1.4.
    Venki wrote:
    Hi,
    Does weblogic ships it's own XML parser.
    We tried parsing an XML document using JDK1.4(default XML parser) it all worked
    well, but after deploying in weblogic container, the document didn't parse correctly.
    We are using Weblogic 6.1 sp2.
    Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
    i guess.
    Any comments , help thanx !
    Venki--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • XML Parser Exception in Install of AIA 11.1.1.5 on SOA 11.1.1.5

    I am attempting to install AIA Foundation Pack on a SOA domain and continually encounter an XML parsing exception error as the installer is attempting to install WSM security policies. Here are the key details:
    AIA version = 11.1.1.5
    SOA Suite = 11.1.1.5
    WebLogic = 10.3.5
    Operating System = Fedora14 (a home lab machine but I don't think this is an OS issue)
    The error is encountered about 17 minutes into the lengthy process. Just before the error appears in the installation log, the following message appears indicating roughly what step is being performed:
    [zip] Building zip: /opt/oraclemw/aia11115/aia_instances/dev1/tmp/aia_security_policies.zip
    The core error messages are:
    [exec] SEVERE: WSM-01605 XML parser exception
    [exec] oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
    [exec] at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
    The python modules being executed by the WLST scripting tool at the time of the failure are:
    [exec] Problem invoking WLST - Traceback (innermost last):
    [exec] File "/opt/oraclemw/aia11115/Infrastructure/Install/AID/lib/py/importpolicy.py", line 29, in ?
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/wsmManage.py", line 719, in importRepository
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/lib/ora_util.py", line 51, in raiseScriptingException
    [exec] OracleScriptingException: None
    Finally, the outer XML files being used as input for the deployer that seems to be running at the time are:
    /opt/oraclemw/aia11115/Infrastructure/Install/AID/AIAExecuteDriver.xml
    with references to lines 221 and 64.
    The problem occurs whether I try to use Java JDK 16.0.20 or JRockit R28.2.0 as the JRE when running the AIA installer. (The WebLogic domain is configured to use JRockit).
    Any suggestions? Is there a library conflict being picked up between different releases of XercesImpl? I would hope there isn't actually a bad XML file in the AIA artifacts or WSM (Web Service Management) policies being deployed.

    HI
    How this issue was resolved? Please explain in detail. I am facing the same issue.
    Regards
    Arun

  • XML Parsing in a Schedule Job (OIM 11g R1)

    Hi,
    I am writing a lookup recon - schedule task in OIM 11g R1 to connect to a webservice and get the lookup attribute values. Now, I am able to fetch the values in a xml format. I am facing an issue while trying to parse the xml values (tried both as a string and from a file).
    I have tried using both the SAX and the DOM parser. PFA the snippet for the DOM Parser:
                        DocumentBuilderFactory builderFactory =
                            DocumentBuilderFactory.newInstance();
                        DocumentBuilder builder = null;
                        try {
                            builder = builderFactory.newDocumentBuilder();
                        } catch (ParserConfigurationException e) {
                            e.printStackTrace();
                        org.w3c.dom.Document doc =
                            (org.w3c.dom.Document)builder.parse(file);
                        System.out.println("Parsed the xml");
                        org.w3c.dom.NodeList nodes =
                            doc.getElementsByTagName("entry");
                        System.out.println("Total Profiles fetched:: " +
                                           nodes.getLength());
    This is giving the nodes.getLength() as 0. Though the code runs fine in the Java Client (directly from eclipse)
    The snippet for the SAX method is :
                SAXParserFactory factory = SAXParserFactory.newInstance();
                SAXParser saxParser = factory.newSAXParser();
                DefaultHandler handler = new DefaultHandler() {
                    boolean bfname = false;
                    boolean blname = false;
                    boolean bnname = false;
                    boolean bsalary = false;
                    public void startElement(String uri, String localName,
                                             String qName,
                                             Attributes attributes) throws SAXException {
                        //   System.out.println("Start Element :" + qName);
                        if (qName.equalsIgnoreCase("d:Name")) {
                            blname = true;
                    public void endElement(String uri, String localName,
                                           String qName) throws SAXException {
                        //     System.out.println("End Element :" + qName);
                    public void characters(char[] ch, int start,
                                           int length) throws SAXException {
                        if (blname) {
                            System.out.println("d:Name : " +
                                               new String(ch, start, length));
                            blname = false;
                           saxParser.parse("home/oracle/UserProfiles.xml", handler);
    This is throwing a java.net.malformedurlexception: no protocol: /home/oracle/userprofiles.xml exception. I tried to pass it as "file://home/oracle/UserProfiles.xml" but then is gives a
    java.net.ConnectException: Connection refused Even this code is running fine in the Java Client when ran directly. It seems there is some weblogic configurations I am missing for the XML parsing?
    Please do help, if anyone has faced any issues parsing an xml in a Schedule job. Will highly appreciate your inputs.
    Thanks,
    Anuj.  

    Hi,
    I am writing a lookup recon - schedule task in OIM 11g R1 to connect to a webservice and get the lookup attribute values. Now, I am able to fetch the values in a xml format. I am facing an issue while trying to parse the xml values (tried both as a string and from a file).
    I have tried using both the SAX and the DOM parser. PFA the snippet for the DOM Parser:
                        DocumentBuilderFactory builderFactory =
                            DocumentBuilderFactory.newInstance();
                        DocumentBuilder builder = null;
                        try {
                            builder = builderFactory.newDocumentBuilder();
                        } catch (ParserConfigurationException e) {
                            e.printStackTrace();
                        org.w3c.dom.Document doc =
                            (org.w3c.dom.Document)builder.parse(file);
                        System.out.println("Parsed the xml");
                        org.w3c.dom.NodeList nodes =
                            doc.getElementsByTagName("entry");
                        System.out.println("Total Profiles fetched:: " +
                                           nodes.getLength());
    This is giving the nodes.getLength() as 0. Though the code runs fine in the Java Client (directly from eclipse)
    The snippet for the SAX method is :
                SAXParserFactory factory = SAXParserFactory.newInstance();
                SAXParser saxParser = factory.newSAXParser();
                DefaultHandler handler = new DefaultHandler() {
                    boolean bfname = false;
                    boolean blname = false;
                    boolean bnname = false;
                    boolean bsalary = false;
                    public void startElement(String uri, String localName,
                                             String qName,
                                             Attributes attributes) throws SAXException {
                        //   System.out.println("Start Element :" + qName);
                        if (qName.equalsIgnoreCase("d:Name")) {
                            blname = true;
                    public void endElement(String uri, String localName,
                                           String qName) throws SAXException {
                        //     System.out.println("End Element :" + qName);
                    public void characters(char[] ch, int start,
                                           int length) throws SAXException {
                        if (blname) {
                            System.out.println("d:Name : " +
                                               new String(ch, start, length));
                            blname = false;
                           saxParser.parse("home/oracle/UserProfiles.xml", handler);
    This is throwing a java.net.malformedurlexception: no protocol: /home/oracle/userprofiles.xml exception. I tried to pass it as "file://home/oracle/UserProfiles.xml" but then is gives a
    java.net.ConnectException: Connection refused Even this code is running fine in the Java Client when ran directly. It seems there is some weblogic configurations I am missing for the XML parsing?
    Please do help, if anyone has faced any issues parsing an xml in a Schedule job. Will highly appreciate your inputs.
    Thanks,
    Anuj.  

  • Memory Utilization during XML Parsing

    We have a slow response time during XML Parsing.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes
    Please let me know if there is any work around or patches available.

    We have a slow response time during XML Parsing.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes
    Please let me know if there is any work around or patches available.

  • How can I use a 3rd party XML parser such as xerces with OC4J ?

    Hi all tech experts,
    I am using Oracle Application Server 10g Release 2 (10.1.2) and i have
    installed Portal and Wireless and OracleAS Infrastructure on the same
    computer.
    i tried all the solutions on this thread
    Use of Xerces Parser in out application with Oracle App Server 9.0.4
    but still fighting.
    I have also posted this query on OTN on following thread
    How can I use a 3rd party XML parser such as xerces with OC4J?
    but no reply....
    Please help me on this issue.
    Since OC4J is preconfigured to use the Oracle XML parser which is xmlparserv2.jar.
    i have read the following article which states that
    OC4J is preconfigured to use the Oracle XML parser. The Oracle XML parser is fully JAXP 1.1 compatible and will serve the needs of applications which require JAXP functionality. This approach does not require the download, installation, and configuration of additional XML parsers.
    The Oracle XML parser (xmlparserv2.jar) is configured to load as a system level library of OC4J through it's inclusion as an entry in the Class-Path entry of the oc4j.jar Manifest.mf file. This results in the Oracle XML parser being used for all common deployment and packaging situations. You are not permitted to modify the Manifest.mf file of oc4j.jar.
    It must be noted that configuring OC4J to run with any additional XML parser or JDBC library is not a supported configuration. We do know customers who have managed to successfully replace the system level XML parser and the Oracle JDBC drivers that ship with the product, but we do not support this type of configuration due to the possibility of unexpected system behavior and system errors that might occur from replacing the tested and certified libraries.
    If you absolutely must use an additional XML parser such as xerces, then you have to start OC4J such that the xerces.jar file is loaded at a level above the OC4J system classpath. This can be accomplished using the -Xbootclasspath flag of the JRE.
    i have also run the following command
    java -Xbootclasspath/a:d:\xerces\xerces.jar -jar oc4j.jar
    but no success.
    How could i utilize my jar's like xerces.jar and xalan.jar for parsing instead of OC4J in-built parser ?
    All reply will be highly appreciated.
    Thnx in advance to all.
    Neeraj Sidhaye
    try_catch_finally @ Y !

    Hi Neeraj Sidhaye,
    I am trying to deploy a sample xform application to the Oracle Application Server (10.1.3). However, I encountered the class loader issue that is similar to your stuation. I tried all the three solutions but the application is still use the Oracle xml paser class. I am wondering if you have any insight about this?
    Thanks for your help.
    Xingsheng Qian
    iPass Inc.
    Here is the error message I got.
    Message:
    java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
    Stack Trace:
    org.chiba.xml.xforms.exception.XFormsException: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
         at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
         at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
         at org.chiba.xml.xforms.Container.initModels(Unknown Source)
         at org.chiba.xml.xforms.Container.init(Unknown Source)
         at org.chiba.xml.xforms.ChibaBean.init(Unknown Source)
         at org.chiba.adapter.servlet.ServletAdapter.init(ServletAdapter.java:153)
         at org.chiba.adapter.servlet.ChibaServlet.doGet(ChibaServlet.java:303)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
         at org.chiba.xml.xforms.Instance.iterateModelItems(Unknown Source)
         at org.chiba.xml.xforms.Bind.initializeModelItems(Unknown Source)
         at org.chiba.xml.xforms.Bind.init(Unknown Source)
         at org.chiba.xml.xforms.Initializer.initializeBindElements(Unknown Source)
         at org.chiba.xml.xforms.Model.modelConstruct(Unknown Source)
         at org.chiba.xml.xforms.Model.performDefault(Unknown Source)
         at org.chiba.xml.xforms.XFormsDocument.performDefault(Unknown Source)
         at org.chiba.xml.xforms.XFormsDocument.dispatchEvent(Unknown Source)
         at org.apache.xerces.dom.NodeImpl.dispatchEvent(Unknown Source)
         ... 18 more

  • XML publisher : Error oracle.xml.parser.v2.XMLParseException: Expected ';'

    I am trying to output a customer list containing customer number and customer name using 11i ( 11.5.10 CU2) with latest XML publisher patches on.
    How do I debug the following error in OPP log:
    [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    The XML ouput file is generated fine but get the following error in the log file.
    | Starting concurrent program execution...
    +-----------------------------
    Spawned Process 13471
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 1088898 on node O11IDEV at 03-APR-2006 13:57:35.
    Post-processing of request 1088898 failed at 03-APR-2006 13:57:37 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    ------------- 2) PRINT   -------------
    Finished executing request completion options.
    The OPP service log messge is :
    [4/3/06 6:02:53 AM] [main] Starting GSF service with concurrent process id = 72156.
    [4/3/06 6:02:53 AM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
    [4/3/06 6:02:53 AM] [Thread-12] Service thread starting up.
    [4/3/06 6:02:53 AM] [Thread-13] Service thread starting up.
    [4/3/06 1:16:08 PM] [OPPServiceThread0] Post-processing request 1088889.
    [4/3/06 1:16:08 PM] [72156:RT1088889] Executing post-processing actions for request 1088889.
    [4/3/06 1:16:09 PM] [72156:RT1088889] Starting XML Publisher post-processing action.
    [4/3/06 1:16:09 PM] [72156:RT1088889]
    Template code: COCXDOTEST
    Template app: COC
    Language: en
    Territory: US
    Output type: PDF
    [040306_011610131][][EXCEPTION] [DEBUG] ------- Preferences defined PreferenceStore -------
    [040306_011610132][][EXCEPTION] [DEBUG] ------- Environment variables stored in EnvironmentStore -------
    [040306_011610133][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610134][][EXCEPTION] [DEBUG] [USER_ID]:[-1]
    [040306_011610134][][EXCEPTION] [DEBUG] [FND_JDBC_PLSQL_RESET]:[false]
    [040306_011610135][][EXCEPTION] [DEBUG] [NLS_TERRITORY]:[AMERICA]
    [040306_011610135][][EXCEPTION] [DEBUG] [RESP_APPL_ID]:[-1]
    [040306_011610136][][EXCEPTION] [DEBUG] [FND_MAX_JDBC_CONNECTIONS]:[500]
    [040306_011610136][][EXCEPTION] [DEBUG] [NLS_SORT]:[BINARY]
    [040306_011610137][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.LOW]:[-1]
    [040306_011610138][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610138][][EXCEPTION] [DEBUG] [RESP_ID]:[-1]
    [040306_011610139][][EXCEPTION] [DEBUG] [NLS_NUMERIC_CHARACTERS]:[.,]
    [040306_011610139][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_SIZE]:[5]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_LANGUAGE]:[AMERICAN]
    [040306_011610140][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.HIGH]:[-1]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_DATE_LANGUAGE]:[AMERICAN]
    [040306_011610141][][EXCEPTION] [DEBUG] [LOGIN_ID]:[-1]
    [040306_011610141][][EXCEPTION] [DEBUG] [NLS_DATE_FORMAT]:[DD-MON-RR]
    [040306_011610142][][EXCEPTION] [DEBUG] [APPS_JDBC_URL]:[jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS
    =(PROTOCOL=tcp)(HOST=O11IDEV.concentra.com)(PORT=9200)))(CONNECT_DATA=(SID=DEV1)))]
    [040306_011610143][][EXCEPTION] [DEBUG] [SECURITY_GROUP_ID]:[0]
    [040306_011610144][][EXCEPTION] [DEBUG] [NLS_CHARACTERSET]:[US7ASCII]
    [040306_011610144][][EXCEPTION] [DEBUG] [FND_JDBC_CONTEXT_CHECK]:[true]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_INTERVAL]:[300]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_USABLE_CHECK]:[false]
    [040306_011610147][][EXCEPTION] [DEBUG] ------- Properties stored in Java System Properties -------
    [040306_011610148][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610149][][EXCEPTION] [DEBUG] [sun.cpu.isalist]:[pa2.0 pa1.2 pa1.1 pa1.0]
    [040306_011610149][][EXCEPTION] [DEBUG] [java.version]:[1.3.1.09]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.awt.graphicsenv]:[sun.awt.X11GraphicsEnvironment]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610151][][EXCEPTION] [DEBUG] [sun.io.unicode.encoding]:[UnicodeBig]
    [040306_011610151][][EXCEPTION] [DEBUG] [JTFDBCFILE]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610152][][EXCEPTION] [DEBUG] [java.runtime.name]:[Java(TM) 2 Runtime Environment, Standard Edition]
    [040306_011610153][][EXCEPTION] [DEBUG] [user.home]:[u02/app/dev1app]
    [040306_011610153][][EXCEPTION] [DEBUG] [java.specification.version]:[1.3]
    [040306_011610154][][EXCEPTION] [DEBUG] [java.vm.info]:[mixed mode]
    [040306_011610154][][EXCEPTION] [DEBUG] [user.dir]:[u02/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.io.tmpdir]:[var/tmp/]
    [040306_011610155][][EXCEPTION] [DEBUG] [LONG_RUNNING_JVM]:[true]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.ext.dirs]:[opt/java1.3/jre/lib/ext]
    [040306_011610156][][EXCEPTION] [DEBUG] [dbcfile]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610156][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.awt.fonts]:[]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.class.version]:[47.0]
    [040306_011610158][][EXCEPTION] [DEBUG] [OVERRIDE_DBC]:[true]
    [040306_011610158][][EXCEPTION] [DEBUG] [sun.cpu.endian]:[big]
    [040306_011610159][][EXCEPTION] [DEBUG] [java.class.path]:[/opt/java1.3/lib/rt.jar:/opt/java1.3/lib/tools.jar:/opt/java1.3/jre/lib/rt.jar:/opt
    /java1.3/jre/lib/i18n.jar:/oracle/app/dev1app/dev1comn/java/appsborg.zip:/oracle/app/dev1app/dev1ora/8.0.6.9/forms60/java:/oracle/app/dev1app/d
    ev1comn/java]
    [040306_011610160][][EXCEPTION] [DEBUG] [os.name]:[HP-UX]
    [040306_011610160][][EXCEPTION] [DEBUG] [sun.boot.class.path]:[/opt/java1.3/jre/lib/rt.jar:/opt/java1.3/jre/lib/i18n.jar:/opt/java1.3/jre/lib/
    sunrsasign.jar:/opt/java1.3/jre/classes]
    [040306_011610161][][EXCEPTION] [DEBUG] [java.vendor.url.bug]:[http://www.hp.com/go/Java]
    [040306_011610161][][EXCEPTION] [DEBUG] [user.timezone]:[America/Chicago]
    [040306_011610162][][EXCEPTION] [DEBUG] [java.vm.name]:[Java HotSpot(TM) Server VM]
    [040306_011610163][][EXCEPTION] [DEBUG] [CACHEMODE]:[DISTRIBUTED]
    [040306_011610164][][EXCEPTION] [DEBUG] [cpid]:[72156]
    [040306_011610164][][EXCEPTION] [DEBUG] [java.vm.specification.name]:[Java Virtual Machine Specification]
    [040306_011610165][][EXCEPTION] [DEBUG] [java.vm.vendor]:[Hewlett-Packard Company]
    [040306_011610165][][EXCEPTION] [DEBUG] [user.language]:[en]
    [040306_011610166][][EXCEPTION] [DEBUG] [java.library.path]:[/opt/java1.3/bin/../jre/lib/PA_RISC2.0/native_threads:/opt/java1.3/bin/../jre/lib
    /PA_RISC2.0/server:/opt/java1.3/bin/../jre/lib/PA_RISC2.0:/oracle/app/dev1app/dev1ora/iAS_1.0.2/lib:/oracle/app/dev1app/dev1ora/8.0.6.9/network
    /jre11/lib/PA_RISC/native_threads:/oracle/app/dev1app/dev1appl/cz/11.5.0/bin::/oracle/app/dev1app/dev1ora/8.0.6.9/lib:/usr/lib:/usr/lib]
    [040306_011610167][][EXCEPTION] [DEBUG] [path.separator]:[:]
    [040306_011610167][][EXCEPTION] [DEBUG] [java.vm.specification.version]:[1.0]
    [040306_011610168][][EXCEPTION] [DEBUG] [java.awt.printerjob]:[sun.awt.motif.PSPrinterJob]
    [040306_011610168][][EXCEPTION] [DEBUG] [file.separator]:[]
    [040306_011610169][][EXCEPTION] [DEBUG] [java.runtime.version]:[1.3.1.09-030418-12:59]
    [040306_011610170][][EXCEPTION] [DEBUG] [java.vm.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610171][][EXCEPTION] [DEBUG] [java.vendor]:[Hewlett-Packard Co.]
    [040306_011610172][][EXCEPTION] [DEBUG] [file.encoding.pkg]:[sun.io]
    [040306_011610172][][EXCEPTION] [DEBUG] [java.vendor.url]:[http://www.hp.com/go/Java]
    [040306_011610173][][EXCEPTION] [DEBUG] [logfile]:[oracle/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev/FNDOPP72156.txt]
    040306_011610174][][EXCEPTION] [DEBUG] [os.arch]:[PA_RISC2.0]
    [040306_011610174][][EXCEPTION] [DEBUG] [os.version]:[B.11.11]
    [040306_011610174][][EXCEPTION] [DEBUG] [java.home]:[opt/java1.3/jre]
    [040306_011610175][][EXCEPTION] [DEBUG] [java.specification.name]:[Java Platform API Specification]
    [040306_011610175][][EXCEPTION] [DEBUG] [sun.boot.library.path]:[opt/java1.3/jre/lib/PA_RISC2.0]
    [040306_011610176][][EXCEPTION] [DEBUG] [line.separator]:[
    [040306_011610176][][EXCEPTION] [DEBUG] [file.encoding]:[8859_1]
    [040306_011610177][][EXCEPTION] [DEBUG] [user.name]:[oradev]
    [040306_011610177][][EXCEPTION] [DEBUG] [java.vm.version]:[1.3.1 1.3.1.09-_18_apr_2003_14_01 PA2.0]
    [4/3/06 1:16:13 PM] [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
    at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1001)
    at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1677)
    at oracle.xml.parser.v2.XMLReader.getEntity(XMLReader.java:1928)
    at oracle.xml.parser.v2.NonValidatingParser.parseContentEntityRef(NonValidatingParser.java:1575)
    at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1202)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
    at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:172)
    at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:160)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1015)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
    at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
    at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5975)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3555)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3614)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)

    I was able to correct the error. The data contained an '&' sign and that was causing the xml parser to fail with the above error. If the & is replaced by a different character other than & then this error does not occur.
    Ashok

  • XML Parsing Error: no element found Location:Line Number 1, Column 1:

    Hi,
    i have a servlet code in which i am using bouncy castle encryption algorithm , if i tried to run that servlet on embeded weblogic server than my servlet works fine without error.
    but if i deploy same Servlet code on SOA domain console than i get following error.
    XML Parsing Error: no element found
    Location: http://localhost:7001/Encryption-PGPEncrypt-context-root/pgpservlet
    Line Number 1, Column 1:
    Please help me friends...

    Hi Chandra,
    Based on my research, the error message is only generated by FireFox when the render page is blank in Internet. For some reason, .NET generates a response type of "application/xml" when it creates an empty page. Firefox parses the file as XML and finding
    no root element, spits out the error message.
    Also, based on your description, the other sites are opened correctly, the issue only happened in Central Administration(CA). This means the SharePoint services are working fine.
    Since this issue only occurred in the CA, it might be due the application pool for the CA is corrupted. Please try to restart the application pool for the CA to resove the issue:
    1. Open Internet Information Service(IIS)
    2. List the application pools
    3. Select the application pool used for the CA
    4. Stop it, and then start it again.
    Note, if the application pool is running in Classic mode, please change it to be Integrated mode.
    Additionally, I found a similar thread, which may help you too:
    http://social.msdn.microsoft.com/Forums/en/sharepoint2010general/thread/824d7dda-db03-452b-99c4-531c5c576396
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT

Maybe you are looking for

  • New printer software for Win 8.1 dont work - J4580

    Hi, help please.  My all in one printer worked fine in windows 8 but since upgradeing to 8.1 it doesn't.  I have unistalled the software and run the "Scrubber". Installed new version software OJ_AIO_J4500_Full_Win_WW_140_404. but it fails at the fina

  • Planned delivery cost payed before GR

    Hi all experts, We are analyzing to use transportation for planned delivery costs and freight. We will have multiple legs (steps) in a route and let's say that the end to end transport will take approximately 30 days to complete but we would like to

  • Anonymous block

    I am receiving the following error: Why? ORA-06550: line 11, column 29: PL/SQL: ORA-00905: missing keyword ORA-06550: line 8, column 5: PL/SQL: SQL Statement ignored DECLARE v_end_date_high DATE; v_item_date_high DATE; v_end_date_high DATE; v_item_da

  • Read user groups from realm. Admin rights to each user ??

    Greetings to ALL, I am reading users, groups from realm. If I give the user admin priviliges I am able to get the information else I get the error weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[ruser1, B10AP

  • Dynamic filters print (pdf)

    Hi In our print web template we have an information field that shows us dynamic filters including key figures and structures. Is it possible NOT to show the key figures and structures, but everything else ? Kind Regards Steffen