AW: Timeout problem with long running queries

[Blumreiter, Fa. Westernacher, IIPS, B]

Hi Joe,

thanks for your advice. Actually, I was trying to avoid client-demarcated transaction 
as proposed by sun. 
Is there a chance to set this timeout within container transactions?



-----Urspr�ngliche Nachricht-----
Von: Joe Gittings [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 24. Oktober 2000 19:11
An: 'Blumreiter, Fa. Westernacher, IIPS, B'; '[EMAIL PROTECTED]'
Betreff: RE: Timeout problem with long running queries


One solution is to run your query within a client-demarcated transaction, 
and set a long timeout on it. E.g.

      UserTransaction utx = 
(UserTransaction)ctx.lookup("javax.transaction.UserTransaction");
      utx.setTransactionTimeout(10*60); // A 10 minute txn
      utx.begin();
      Enumeration results = home.findAll();
      utx.commit();

Joe

-----Original Message-----
From:   Blumreiter, Fa. Westernacher, IIPS, B 
[SMTP:[EMAIL PROTECTED]]
Sent:   Tuesday, October 24, 2000 5:53 PM
To:     '[EMAIL PROTECTED]'
Subject:        Timeout problem with long running queries

Hi,

I have got a serious problem: when long-running queries are being executed 
I get strange error message from jonas:

XAResource ---> rollback: XA START without XA END
WARNING: Connection not closed by caller
Force a physical close to avoid reusing it in another transaction
Cannot resolve XAC => PoolItem
Cannot set transaction as rollback only

After that a SQLException is thrown:

java.sql.SQLException: Must be logged on to server

java.sql.SQLException: Must be logged on to server
        at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:456)
        at oracle.jdbc.ttc7.TTC7Protocol.closeQuery(TTC7Protocol.java:378)
        at 
oracle.jdbc.driver.OracleResultSet.internal_close(OracleResultSet.java:145)
        at oracle.jdbc.driver.OracleResultSet.next(OracleResultSet.java:81)
        at 
dpag.ass.application.dispatcher.DispatcherBean.dispatch(DispatcherBean.j  
ava:218)
        at 
dpag.ass.application.dispatcher.JOnASdispatcherRemote.dispatch(classes\d  
pag\ass\application\dispatcher\JOnASdispatcherRemote.java:55)
        at 
dpag.ass.application.dispatcher.JOnASdispatcherRemote_Skel.dispatch(clas  
ses\dpag\ass\application\dispatcher\JOnASdispatcherRemote_Skel.java:47)
        at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:319)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:187)
        at sun.rmi.transport.Transport$1.run(Transport.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
        at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)
        at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja  
va:643)
        at java.lang.Thread.run(Thread.java:484)
doPostInvoke: Rolling back transaction

Obviously, the query hasn't finished yet when the connection is 
destroyed...

Are there any timeout parameters to configure?
Or does it look like a bug?


Thanks a lot

Torsten


----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".