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
  • 1.  Tamino access failure

    Posted Wed April 30, 2003 02:24 PM

    I Guess I am posting too many issues in the past 2 or three days. Any help in fixing these issues would be highly appreciated.

    My Email id : rchamarthy@cellexchange.com

    Well, this is one in the Queue of issues.
    Application configuration : Contains EJBs(mainly MDBs) deployed on OC4J, using JDK 1.4 with Tamino 4.1.1.
    Follwoing is the error when I run my application for concurrency loads.

    SEVERE :Apr 30 17:19:45 [DataColle~] In handleException() Exception Occured :Nes
    tedException:Tamino access failure (INOXYE9155, The requested document(s) could
    not be locked, Locking of doctype SharpStatementData failed.)
    com.pl.exception.TaminoConnectionException: NestedException:Tamino acces
    s failure (INOXYE9155, The requested document(s) could not be locked, Locking of
    doctype SharpStatementData failed.)
    at com.pl.dao.tamino.TaminoBaseDAO.queryXML(Unknown Source)
    at com.pl.dao.tamino.StatementDAOImpl.updateStatementData(Unknown Source
    )
    at com.cx.ssc.datacollection.ejb.DataCollectorMessageBean.onMessage(Unkn
    own Source)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDriven
    BeanInvocation.java:141)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:66)
    com.cx.ssc.exception.StatementException
    at com.pl.dao.tamino.StatementDAOImpl.updateStatementData(Unknown Source
    )
    at com.cx.ssc.datacollection.ejb.DataCollectorMessageBean.onMessage(Unkn
    own Source)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDriven
    BeanInvocation.java:141)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:66)


    #API-Management
    #webMethods
    #webMethods-Tamino-XML-Server-APIs


  • 2.  RE: Tamino access failure

    Posted Mon May 05, 2003 01:17 PM

    two scenarios are possible:

    1. An _XQL request was issued with _LOCKWAIT=no and _ISOLATION=shared/protected. At least one of the requested documents was locked by another user, therefore the lock could not be granted immediately.

    In this case you have to check the architecture of your application for concurrency loads.

    2. If your application shares connections between EJBeans and the connection sharing daoes not work properly.

    Please contact the Tamino Support. We’ll need more information:
    1. the architecture of your application.
    2. Deeper stacktrace
    3. The trace output of the Tamino Connector

    Josef Haiduk


    #API-Management
    #webMethods
    #webMethods-Tamino-XML-Server-APIs