ViewNotify service is not parsing XML from View Drop folder

Hi,
The view drop folder has now 2200 odd XML files which were not parsed from sometime now. We took a backup of this folder and started processing files one by one.
We had to restart the Service after sometime , the processing time is  not uniform it ranges from 10 sec to 600 sec for one file. When parsing in bulk , sometime parsing 5 in batch is successful whereas at times it does not parse in batches.
Any suggestion on the available utility to automate the process where one file is parsed and then service is restarted.
Regards,
Siddharth

Hi Siddharth,
This post is specific for Project Server questions and answer. Please re post your query in corresponding forum.
Thanks and let me know in case have any doubts or I am wrong in my understanding.
Sachin Vashishth MCTS

Similar Messages

  • Parsing XML from Socket input stream

    I create a sax parser to which I send the InputStream from the socket
    But my HandlerBase never gets the events. I get startDocument
    but that is it, I never get any other event.
    The code I have works just like expected when I make the InputStream
    come from a file. The only differeence I see is that when I file is used the
    InputStream is fully consumed while with the socket the InputStream
    is kept open (I MUST KEEP THE SOCKET OPEN ALL THE TIME). If the parser
    does not generate the events unless the InputStream is fully consumed,
    isn't that against the whole idea of SAX (sax event driven) .
    Has anyone been succesfull parsing XML from the InputStream of a socket?
    if yes how?
    I am using JAXP 1.0.1 but I can upgrade to JAXP 1.1.0
    which uses SAX 2.0
    Does anybody know if my needs can be met by JAXP 1.1.0?
    Thanks

    I did the same with client/server model.
    I have client program with SAX parser. Please try if you can make the server side. I was be able to write the program with help from this forum. Please search to see if you can get the forum from which I got help for this program.
    // JAXP packages
    import javax.xml.parsers.*;
    import org.xml.sax.*;
    import org.xml.sax.helpers.*;
    // JAVA packages
    import java.util.*;
    import java.io.*;
    import java.net.*;
    public class XMLSocketClient {
    final private static int buffSize = 1024*10;
    final private static int PORTNUM = 8888;
         final private static int threadSleepValue = 1000;
    private static void usage() {
    System.err.println("Usage: XMLSocketClient [-v] serverAddr");
    System.err.println(" -v = validation");
    System.exit(1);
    public static void main(String[] args) {
    String address = null;
    boolean validation = false;
    Socket socket = null;
    InputStreamReader isr_socket = null;
    BufferedReader br_socket = null;
    CharArrayReader car = null;
    BufferedReader br_car = null;
    char[] charBuff = new char[buffSize];
    int in_buff = 0;
    * Parse arguments of command options
    for (int i = 0; i < args.length; i++) {
    if (args.equals("-v")) {
    validation = true;
    } else {
    address = args[i];
    // Must be last arg
    if (i != args.length - 1) {
    usage();
    // Initialize the socket and streams
    try {
    socket = new Socket(address, PORTNUM);
    isr_socket = new InputStreamReader(socket.getInputStream());
    br_socket = new BufferedReader(isr_socket, buffSize);
    catch (IOException e) {
    System.err.println("Exception: couldn't create stream socket "
    + e.getMessage());
    System.exit(1);
    * Check whether the buffer has input.
    try {
    while (br_socket.ready() != true) {
                   try {
                        Thread.currentThread().sleep(threadSleepValue);     
                   catch (InterruptedException ie) {
              System.err.println("Interrupted error for sleep: "+ ie.getMessage());
                   System.exit(1);
    catch (IOException e) {
    System.err.println("I/O error for in.read(): "+ e.getMessage());
    System.exit(1);
    try {
    in_buff = br_socket.read(charBuff, 0, buffSize);
    System.out.println("in_buff = " + in_buff);
    System.out.println("charBuff length: " + charBuff.length);
    if (in_buff != -1) {
    System.out.println("End of file");
    } catch (IOException e) {
    System.out.println("Exception: " + e.getMessage());
    System.exit(1);
    System.out.println("reading XML file:");
    StringBuffer display = new StringBuffer();
    display.append(charBuff, 0, in_buff);
    System.out.println(display.toString());
    * Create BufferedReader from the charBuff
    * in order to put into XML parser.
    car = new CharArrayReader(charBuff, 0, in_buff); // these two lines have to be here.
    br_car = new BufferedReader(car);
    * Create a JAXP SAXParserFactory and configure it
    * This section is standard handling of XML document by SAX XML parser.
    SAXParserFactory spf = SAXParserFactory.newInstance();
    spf.setValidating(validation);
    XMLReader xmlReader = null;
    try {
    // Create a JAXP SAXParser
    SAXParser saxParser = spf.newSAXParser();
    // Get the encapsulated SAX XMLReader
    xmlReader = saxParser.getXMLReader();
    } catch (Exception ex) {
    System.err.println(ex);
    System.exit(1);
    // Set the ContentHandler of the XMLReader
    xmlReader.setContentHandler(new MyXMLHandler());
    // Set an ErrorHandler before parsing
    xmlReader.setErrorHandler(new MyErrorHandler(System.err));
    try {
    * Tell the XMLReader to parse the XML document
    xmlReader.parse(new InputSource(br_car));
    } catch (SAXException se) {
    System.err.println(se.getMessage());
    System.exit(1);
    } catch (IOException ioe) {
    System.err.println(ioe);
    System.exit(1);
    * Clearance of i/o functions after parsing.
    try {
    br_socket.close();
    } catch (IOException e) {
    System.out.println("Exception: " + e.getMessage());
    try {
    socket.close();
    } catch (IOException e) {
    System.out.println("Exception: " + e.getMessage());
    try {
    br_car.close();
    } catch (IOException e) {
    System.out.println("Exception: " + e.getMessage());
    * The XML handler used by this program
    class MyXMLHandler extends DefaultHandler {
    // A Hashtable with tag names as keys and Integers as values
    private Hashtable tags;
    // Parser calls this once at the beginning of a document
    public void startDocument() throws SAXException {
    System.out.println("startDocument()");
    tags = new Hashtable();
    // Parser calls this for each element in a document
    public void startElement(String namespaceURI, String localName,
    String rawName, Attributes atts)
    throws SAXException
    String key = localName;
    Object value = tags.get(key);
    System.out.println("startElement()");
    System.out.println("namespaceURI: " + namespaceURI);
    System.out.println("localName: " + localName);
    System.out.println("rawName: " + rawName);
    if (value == null) {
    // Add a new entry
    tags.put(key, new Integer(1));
    } else {
    // Get the current count and increment it
    int count = ((Integer)value).intValue();
    count++;
    tags.put(key, new Integer(count));
    // Parser calls this once after parsing a document
    public void endDocument() throws SAXException {
    Enumeration e = tags.keys();
    System.out.println("endDocument()");
    while (e.hasMoreElements()) {
    String tag = (String)e.nextElement();
    int count = ((Integer)tags.get(tag)).intValue();
    System.out.println("Tag <" + tag + "> occurs " + count
    + " times");
    * Error handler of XML parser to report errors and warnings
    * This is standard handling.
    class MyErrorHandler implements ErrorHandler {
    /** Error handler output goes here */
    private PrintStream out;
    MyErrorHandler(PrintStream out) {
    this.out = out;
    * Returns a string describing parse exception details
    private String getParseExceptionInfo(SAXParseException spe) {
    String systemId = spe.getSystemId();
    if (systemId == null) {
    systemId = "null";
    String info = "URI=" + systemId +
    " Line=" + spe.getLineNumber() +
    ": " + spe.getMessage();
    return info;
    * The following methods are standard SAX ErrorHandler methods.
    * See SAX documentation for more info.
    public void warning(SAXParseException spe) throws SAXException {
    out.println("Warning: " + getParseExceptionInfo(spe));
    public void error(SAXParseException spe) throws SAXException {
    String message = "Error: " + getParseExceptionInfo(spe);
    throw new SAXException(message);
    public void fatalError(SAXParseException spe) throws SAXException {
    String message = "Fatal Error: " + getParseExceptionInfo(spe);
    throw new SAXException(message);

  • Can not construct xml from relative xpath expression: //FormVar

    In version 7.0, it was possible to access Form Variables with the (valid) XPath Expression "//FormVariable".
    In 7.2.2, using this XPath Expression leads to a stalled action, with message: "can not construct xml from relative xpath expression: //FormVar". (see full stack trace below)
    What's wrong? How can I fix this?
    Use of relative expression is very very useful during the development phase!
    Best Regards,
    com.adobe.workflow.WorkflowRuntimeException: can not construct xml from relative xpath expression: //FormVar
    at com.adobe.workflow.pat.service.PATExecutionContextImpl.createNodesForXPathExpression(PATE xecutionContextImpl.java:854)
    at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionCo ntextImpl.java:707)
    at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataWithExpression(PATEx ecutionContextImpl.java:429)
    at com.adobe.workflow.qpac.set_value.SetValueService.execute(SetValueService.java:72)
    at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:184)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2371)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:512)
    at sun.reflect.GeneratedMethodAccessor709.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:683)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:185)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
    at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 44)
    at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62)
    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:72)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:120)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:122)
    at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331 )
    at org.jboss.ejb.Container.invoke(Container.java:723)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:359)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:83)
    at $Proxy285.asyncInvokeProcessCommand(Unknown Source)
    at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandController Bean.java:127)
    at sun.reflect.GeneratedMethodAccessor641.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.j ava:458)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:185)
    at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterc eptor.java:62)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:315)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:148)
    at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:90)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
    at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:372)
    at org.jboss.ejb.Container.invoke(Container.java:723)
    at org.jboss.ejb.plugins.jms.JMSCont

    Sorry, i just read my own message in the discussion forum and
    discovered all spaces for formating the XML tags where gone.
    It should look like this:
    [-----xml_type---]
    <doc>
    __<role>
    ____actor
    ____<first>
    ______john
    ____</first>
    ____<last>
    ______bond
    ____</last>
    __</role>
    __<role>
    ____actor
    ____<first>
    ______james
    ______</first>
    ____<last>
    ______smith
    ____</last>
    __</role>
    </doc>
    semantic:
    There are two actors: "john bond" and "james smith"
    Querying for "john bond" succeedes which is correct
    Querying for "james smith" succeedes which is correct
    Querying for "james bond" fails which is correct
    Querying for "john smith" succeedes which is an ERROR!
    contains(xdata, 'actor INPATH(//role[./first = "john" and ./last
    = "smith"])' (= 100 ---> ERROR!)
    bye,
    feri

  • Can't parse xml from applet using dom on linux on Netscape 7 using jre 1.4.

    Hi,
    I can't seem to parse xml from an applet on linux on Netscape 7 using the JRE 1.4.
    My code looks like the following:
    StringBufferInputStream is = new StringBufferInputStream("<foo></foo>");
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = null;
    try
      builder = factory.newDocumentBuilder();
      domDocument = builder.parse(is); // this line creates an exception
    catch (Exception e)
      System.out.println(e);
    This code works fine from an applet on windows. On linux, the error message is:
    java.security.AccessControlException: access denied (java.util.PropertyPermission entityExpansionLimit read)
    I've tried both JRE 1.4.0_04 and 1.4.1_03
    Thanks!
    Q

    There's another posting about this same problem (platform unspecified), but the same error message. I was also having this problem (Windows 1.4.03) and swithced back to 1.4.01 and the problem went away. In the future, I may sign my applets to get a more generous security policy. But, I'm sure it'll be a lot of work (vs. a line of code somewhere).

  • Parse XML from CLOB field

    How can I parse XML from CLOB field? I need to replace or delete the node from XML document and update the database with new XML. I am using Oracle 9i release 2.
    Here is the XML. In this XML if section1 and section2 exists then I need to delete the section1 node. If section2 doesn't exist, replace section1 with section2 node.
    <Document ID='2' TypeID='2'>
    <Body>
    <Page Name='Page1'>
    <Sec ID='section1' Title='Section 1' GroupID='' />
    <Sec ID='section2' Title='Section 2' GroupID='' />
    </Page>
    </Body>
    </Document>
    Please help.. Thank you..

    In 9.2, you are limited into your options. Have a look into, among others, updateXML. Updating tp 10gR2 will give you more options to succeed.

  • Could not parse xml on Weblogic!

    Hello
    My ear file have aldready deployed successfull on Oracle Appllication Server. And now I try deploy on weblogic but I reiceive the error could not parse xml file. I think It may be the problem with security in weblogic.
    # java.lang.NullPointerException
    # at org.apache.commons.digester.Digester.createSAXException(Digester.java:3181)
    # at org.apache.commons.digester.Digester.createSAXException(Digester.java:3207)
    # at org.apache.commons.digester.Digester.endElement(Digester.java:1225)
    # at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
    # at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1550)
    # at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1809)
    # at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1182)
    # at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
    # at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
    # at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:153)
    # at org.apache.commons.digester.Digester.parse(Digester.java:1785)
    # at com.toranto.cmsserver.util.TorantorevisorUtil.createOrganizationOrgEntityIdXml(TorantorevisorUtil.java:3636)
    # at jsp_servlet.__test._jspService(__test.java:119)
    If any one have the same error on weblogic, please help me.
    Thanks in advance.

    Because this ear is ok in oracle apllication server.
    the code here:
    Digester digester = DigesterLoader.createDigester(rulesURL);
    Object rootElement = null;
    InputStream is = null;
    try {
    is = initURL.openStream();
    //3. parse initialization file
    try {
    rootElement = digester.parse(is);
    } catch (SAXException e) {
    String msg = "Digester parse error! Message: " + e.getMessage();
    log.error(msg, e);
    throw e;
    The error cause by rootElement = digester.parse(is);
    So I think in weblogic not accept common-digester.jar to parse xml
    Do you have any idea for this problem.
    Thanks in advance.
    Tang Chow

  • After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

    Hi,
    We have an issue with our OWA page.  We are currently publishing OWA via UAG.
    We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7.  Since the upgrade, we are keep getting the following error after entering our credentials on the login page.  I've tried with every possible browser. 
    You do not have permissions to view this folder or page
    Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues.  I can see this on the Active Sessions screen
    on Web Monitor. 
    I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running. 
    No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer. 
    Any insight would be helpful?  I'm assuming something changed on the Exchange side after the upgrade.
    Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
    UAG > SP4
    TMG > SP2 Rollup 5

    I've found a solution; UAG requires Basic Authentication over OWA.  For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
    http://technet.microsoft.com/en-us/library/ee921443.aspx
    Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue.  Though beware, you
    have do this on all your Client Access servers.  

  • Having a problem parsing XML from web service & dropdown list

    I have 2 data connections that are programmatically invoked via exit event on different fields in form.  Both have identical code with only difference is that one populates a multiselect list box and one populates a drop down list.  The one that populates the listbox works fine.  Everytime Field A changes, it is fired and the results parsed then listblox updated.  The one with the drop down list is not working at all.  The form is used in Workspace.  When I use the javascript debugger, I see the correct node values output to the console window.  The problem is that the value is not successfully added to the drop down list existingFileNumber.  Anyone have any great ideas?  Like I said, this works perfectly in the same form for a different web service and a listbox.
    Here is the code for firing and parsing the dropdown list data:
    Form.sRoutingTransmittalSlip.sPreparer.existingFileNumber.clearItems();
    Form.sRoutingTransmittalSlip.phaseHidden.rawValue="PI";
    xfa.connectionSet.getInfo.execute(0);
    var pls2=xfa.datasets.createNode("dataGroup","pls2");
    pls2.loadXML(Form.sRoutingTransmittalSlip.fileNumbersHidden.rawValue,false,true);
    xfa.datasets.data.nodes.append(pls2);
    var dataGroup=xfa.resolveNode("xfa.data.pls2.Matters");
    var dataGroupLength=dataGroup.nodes.length;
    if (dataGroupLength==0) {}
    else {
      for (var i=0;i<dataGroupLengthl;i++){
         console.println(dataGroup.nodes.item(i).nodes.item(0).value);
         Form.sRoutingTransmittalSlip.sPreparer.existingFileNumber.addItem(dataGroup.nodes.item(i ).nodes.item(0).value);

    Do this instead
    [Bindable]
    var xlTopics:XMLListCollection;
    private function LoadResults(event:ResultEvent):void{
    var xmlResult = XML(event.result); //only use lastResult in
    binding expressions
    trace(xmlResult.toXMLString()); //to be sure of what you have
    xlTopics = new XMLListCollection(xmlResult .children());
    //all the child nodes of the root
    Tracy

  • Xerces - Parse XML from String

    I am trying to parse an xml string using Xerces.
    I have the following code:
    String xml = <segments meters="8643" seconds="538" distance="5.4 mi" time="8 mins"><segment id="seg0"  pointIndex="0" meters="122" seconds="11"  distance="0.1 mi"  time="11 secs">Head  <b>southwest</b> from <b>B Ave NE</b>
    </segment>
    <segment id="seg1" pointIndex="2" meters="239" seconds="22" distance="0.1 mi" time="21 secs">Turn <b>left</b> at <b>19th St NE</b></segment>
    <segment id="seg2" pointIndex="5" meters="2985" seconds="192" distance="1.9 mi" time="3 mins">Turn <b>right</b> at <b>1st Ave NE</b></segment>
    <segment id="seg3" pointIndex="43" meters="3280" seconds="211" distance="2.0 mi" time="3 mins">Continue on <b>1st Ave SW/1st Ave NW</b></segment>
    <segment id="seg4" pointIndex="96" meters="158" seconds="10" distance="0.1 mi" time="10 secs">Bear <b>right</b> at <b>US-151-BR S</b></segment>
    <segment id="seg5" pointIndex="102" meters="1859" seconds="93" distance="1.2 mi" time="1 min">Turn <b>right</b> at <b>16th Ave SW</b></segment>;
    XMLReader reader = new SAXParser();
    reader.setContentHandler(new Handler());
    reader.parse(xml);I am getting the followoing error:
    org.xml.sax.SAXParseException: File "<segments meters="8643" seconds="538" distance="5.4 mi" time="8 mins"><segment id="seg0" pointIndex="0" meters="122" seconds="11" distance="0.1 mi" time="11 secs">Head  <b>southwest</b> from <b>B Ave NE</b></segment><segment id="seg1" pointIndex="2" meters="239" seconds="22" distance="0.1 mi" time="21 secs">Turn <b>left</b> at <b>19th St NE</b></segment><segment id="seg2" pointIndex="5" meters="2985" seconds="192" distance="1.9 mi" time="3 mins">Turn <b>right</b> at <b>1st Ave NE</b></segment><segment id="seg3" pointIndex="43" meters="3280" seconds="211" distance="2.0 mi" time="3 mins">Continue on <b>1st Ave SW/1st Ave NW</b></segment><segment id="seg4" pointIndex="96" meters="158" seconds="10" distance="0.1 mi" time="10 secs">Bear <b>right</b> at <b>US-151-BR S</b></segment><segment id="seg5" pointIndex="102" meters="1859" seconds="93" distance="1.2 mi" time="1 min">Turn <b>right</b> at <b>16th Ave SW</b></segment></segments>" not found.
         at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1219)
         at org.apache.xerces.readers.DefaultEntityHandler.startReadingFromDocument(DefaultEntityHandler.java:501)
         at org.apache.xerces.framework.XMLParser.parseSomeSetup(XMLParser.java:314)
         at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1097)
         at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1139)
         at com.shiftyeyes.xmlTest.main(xmlTest.java:34)
    Exception in thread "main" anyone know how I can fix this? Thanks!!

    reader.parse(new InputSource(new StringReader(xml)));

  • Parsing XML from a session bean

    Hi,
    I am trying to use a Sax parser for parsing xml received from a back end
    legacy system. The code is executed from a Session bean.
    Debugging learned me that the parse() method on the parser hangs the
    container without any error or exception trace. The code works fine outside
    a container.
    All help will be highly appreciated.
    Kurt

    I found out that the InputStream implementation used parsing source inside
    the container is different
    then from the one outside (other type of VM of course!). The Weblogic
    implementation blocks at the end of
    the stream, while the normal SUN JDK 1.3 returns. This is not a bug, the bug
    I found is in my proxy that allows
    the connection to the backend. This proxy allows HTTP connections, and I
    parse the XML received over HTTP.
    Regards,
    Kurt
    "Todd Karakashian" <[email protected]> wrote in message
    news:[email protected]..
    That's seems odd. Perhaps there is something going on in your document
    handler code that triggers a hang in the environment of the server.
    When you see the hang, instruct the VM to give you a thread dump (type
    control-<break> on Windows, <control>-\ (backslash) on UNIX in the
    window in which the server is running; the results are dumped to
    stderr). That will show what every thread in the server is doing. If you
    email or post the thread dump, I will take a look at it and see if I can
    see what is going on. Also, let us know which platform, VM, parser, and
    WebLogic version you are using.
    Regards,
    -Todd
    Kurt Quirijnen wrote:
    Hi,
    I am trying to use a Sax parser for parsing xml received from a back end
    legacy system. The code is executed from a Session bean.
    Debugging learned me that the parse() method on the parser hangs the
    container without any error or exception trace. The code works fine
    outside
    a container.
    All help will be highly appreciated.
    Kurt--
    Todd Karakashian
    BEA Systems, Inc.
    [email protected]

  • Why i can not  parse xml in client jar successfully?

    If the length of xml is short in 300bytes(maybe another amount),i can read the string of xml from the file in java web start client jar and can parse it exactly. But if length is more than the amount, the xml string will be cut off so that i can not parse it.
    is this a bug of java web start? or my fault?
    display my function below:
    className :FileUtils
    private static byte[] getData(String fileName) throws IOException
    byte[] data = null;
    File file = null;
    try
    file = new File(fileName);
    }catch(Exception ex)
    ex.printStackTrace();
    InputStream in = null;
    if (file.exists() && file != null)
    in = new FileInputStream(file);
    data = new byte[in.available()];
    if (in.available() > 0)
    in.read(data);
    in.close();
    else
    in = FileUtil.class.getClassLoader().getParent()
    .getResourceAsStream(fileName);
    if (in == null)
    in = FileUtil.class.getClassLoader() .
    getResourceAsStream(fileName);
    if (in == null)
    throw new IOException("Can not read the file in
    classpath"+ fileName);
    else
    data = new byte[in.available()];
    if (in.available() > 0)
    in.read(data);
    in.close();
    else
    data = new byte[in.available()];
    if (in.available() > 0)
    in.read(data);
    in.close();
    return data;
    please help me,thank you.
    best regards!

    in = new FileInputStream(file);
    data = new byte[in.available()];available tells how many bytes are available at the moment in the buffer. For smaller files fitting into the buffer it might be okay but for longer ones it is definitively not.
    Use a ByteArrayOutputStream to store the data in and return its toByteArray().
    Or ask the for the file length and allocate a buffer of that size and read into it in one operation: read(byte[] b).

  • How to use DOMParser from an Applet / Or, how to parse XML from an Applet?

    Hey,
    As stating in the subject line, I wonder how to do it without getting an �Access Denied� error.
    I would like to parse a XML file that has external DTD pointing to a SYSTEM location. Yes, I can change it to a public location. However, in either way, I have problems to use DOMBuilder to parse the xml file. The application always throws the security exception.
    I tried to use the DOMParser from org.apache.xerces.parsers to parse the xml file. I set the DOMParser to ignore parsing the external DTD, and use the DOMParser.parse(InputSource) to parse the xml file from a giving URL. However, I get null of the result document.
    Does anyone know how to parse the XML from an Applet? Or, does anyone know how to use the DOMParser from an Applet?
    Thank you very much,

    If the document resides on the local filesystem, you will need to sign a CAB or JAR for the applet to circumvent the sandbox's security restrictions. There are dozens of posts on how to do this. Basically, that will turn the applet into an application, from a Java security perspective.
    - Saish
    "My karma ran over your dogma." - Anon

  • "DFS Replication service is not installed" but event viewer is showing 4202 and 4204 for the server

    There are two servers replicating file information, sending member is Server 2008 R2 Datacenter, the receiving member is Server 2003 R2 Standard. There have been no serious problems with this replication set previously.
    Running a health report shows an error against the 2008 server, stating that the DFS Replication service is not installed, though the service is running on the server, and has been restarted today.
    Running dfsrdiag backlog on either server shows "Failed to connect to WMI services on computer %2008 server%"
    Event logs on the receiving server show events 4202 and 4204 (high watermark for staging area) for these two servers?
    Can someone help; is replication occurring, or is it broken? Where else can I look for information?
    TIA

    Just had a very similar instance to this but with a 2008 R2 server replicating to a NAS running Windows Storage Server 2012. 
    I have health reports running as scheduled tasks, twice daily, and a few days ago the morning report for this particular server was fine but on the afternoon's report advised that the replication service was not installed, yet DFSR events are still being
    logged and replication to the target is still working normally - go figure!!
    Have yet to reboot the server as it is live but have found nothing in any of its logs to indicate a problem and/or DFSR is not running when it clearly is!!
    The DFS management option has gone from the Administrative Tools panel, though, and is showing as 'Not Installed' under the File Services role.
    The health report shows a status of 'Indeterminate' and in its 'Suggested Action'
    ...ensure Windows 2003 R2 is installed on this server and that the DFS replication service was installed....
    (guessing a default message given the server in error is 2008 )
    Will be interesting to see if the other 2008 R2 servers start losing the plot!

  • Service center not getting approval from Sony India

    Dear Samuel, First of all thank you for your concern about my issue. The problem is still unresolved. Today also i contacted the service centre but again the  same replay " your work is rejected by the sony". This is the 5th sony mobile am using and now I am planning to approach consumer court. That is the last thing I can do for this genuine case. Thank you

    I have purchased Zperia Z1 on exchange basis from Sony authorized service
    center (Madonna Electronics,MG Road,Cochin) on 04/03/2015. Previously I had
    Zperia ZL and due to mic complaints service center suggested upgrade. But
    after purchasing  Z1 and using 3 months I noticed  mic problem in Zperia Z1
    too (person on other side couldn't hear me).
    So I submitted the device on 25.06.2015 for service and till now it is not
    repaired.
    From the service center they told me that your work is not approved because
    whenever they try to create job it is automatically showing out of
    warranty. That is eventhough the mobile is in warranty,site showing out
    warranty. Service center has explained this issue to SONY INDIA but not
    getting reply from SONY INDIA.  So from their side they are unable to do
    anything unless they get permission from Sony India.
    So today (28.07.2015 at 11 AM) I contacted toll free number and talked with
    customer care executive and we had conference mode with Mr. Jefrin from
    modonna electronices.
    Later getting enough information from Mr. Jefrin customer care executive
    directed the call to one of the Manager in Sony India and I raised the
    issue to him. Later the Manager called the Madonna electronics and one Mr.
    Ajmal explained the technical issues to the Manager.
    Finally the Manager told me to write a mail regarding the issue. I forwarded the same letter hope they will solve it

  • Spry can not  parse xml string

    while designind an mvc architecutre in php I found display
    data on site was slow so I generate a xml sheet an used spry Data
    loading was fast an dproduced and I also performed many operations
    like sorting ,galeery making ..etc... but main thing is that I can
    not parse a xml string using spry only a xml file can be parsed
    my application required to parse xml string

    I'm not sure if this is valid in your situation, but OC4J comes with Oracle XMLParser.
    Simply use the JAXP API to parse/build/modify XML and the Oracle XMLParser implementation will be used behind the scenes.
    If you must use xerces/xalan, try putting the jars in OC4J_HOME/j2ee/home/lib instead.
    HTH //Anders

Maybe you are looking for