Thanks a lot, Philippe. But you forgot to tell me that this parameter on only available in the most recent version of jonas 2.1.1. In found that out by myself afterwards... -----Ursprüngliche Nachricht----- Von: Philippe Durieux [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 26. Oktober 2000 13:27 An: Blumreiter, Fa. Westernacher, IIPS, B Cc: '[EMAIL PROTECTED]' Betreff: Re: Timeout problem with long running queries "Blumreiter, Fa. Westernacher, IIPS, B" wrote: > > 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.java:218) > at >dpag.ass.application.dispatcher.JOnASdispatcherRemote.dispatch(classes\dpag\ass\application\dispatcher\JOnASdispatcherRemote.java:55) > at >dpag.ass.application.dispatcher.JOnASdispatcherRemote_Skel.dispatch(classes\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.java: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 You can configure transaction timeout with a property in jonas.properties: jonas.tm.timeout 300 for example, if you want 5mn instead of 1 mn. By the way, there is a little bug in JOnAS: if the timeout expires, the client is not aware of this, if the transaction was started by the EJBServer. You can only see an error message printed by EJBServer. I'll change this for next version. -- Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bull - 1 rue de Provence - 38432 Echirolles Cedex France [EMAIL PROTECTED] -> Download our EJBServer at http://www.evidian.com/ejb <- ---- 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".
AW: Timeout problem with long running queries
Blumreiter, Fa. Westernacher, IIPS, B Thu, 26 Oct 2000 04:30:47 -0700
- AW: Timeout problem with long runnin... Blumreiter, Fa. Westernacher, IIPS, B
- Blumreiter, Fa. Westernacher, IIPS, B