IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Storeexception in long queries

  • 1.  Storeexception in long queries

    Posted Tue July 16, 2002 09:56 AM

    Hello,
    I sometimes get this exception when I iterate between documents in the cursor. I have same problem in my other queries too the problem is not specific to this schema. My code is something like this :

    BusinessDocumentWorkspace ws = new BusinessDocumentWorkspace(store);
    RegisterDocType(“oc_icd”);
    QueryContainer query = new QueryContainer(“oc_icd”);
    query.add(new QueryElement(“.”, “*”, “~=”));
    Cursor docCursor = ws.query(“qryoc_icd”, query);//msa
    System.out.println("cursor size : "+docCursor.count());
    while (docCursor.hasNext()) {
    BusinessDocument bicd = (BusinessDocument) docCursor.next(); }

    In this code I get the exception at line docCursor.next and each time in a different record.

    The exception message is like this :

    StoreException: null

    ?Problem during retrieval of previous query cursor content.
    com.softwareag.tamino.db.API.response.TXMLObjectFetchingIterator.fetchBlockAt(TXMLObjectFetchingIterator.java:303)
    com.softwareag.tamino.db.API.response.TXMLObjectFetchingIterator.fetchBlockWith(TXMLObjectFetchingIterator.java:281)
    com.softwareag.tamino.db.API.response.TXMLObjectFetchingIterator.next(TXMLObjectFetchingIterator.java:115)
    com.softwareag.xtools.xapplication.store.TaminoElementIterator.next(TaminoElementIterator.java:141)
    com.softwareag.xtools.xapplication.businessdocument.BusinessDocumentCursor.next(BusinessDocumentCursor.java:303)
    hitit.Hiti…


    #webMethods
    #Tamino
    #API-Management


  • 2.  RE: Storeexception in long queries

    Posted Tue July 16, 2002 04:25 PM

    Hello,

    is it possible to get your schema and a set of test data and the Java code?

    It could be a problem of the underlying Tamino API for Java. But it’s only a guess.

    We have to reproduce the error on one of our machine to analyze the problem.

    A few questions:
    - which Tamino version are you using
    - which JSDK
    - how many documents do you expect as result of your query.

    Thank you,
    bye Christian.


    #API-Management
    #Tamino
    #webMethods