Not Connected Exception during long operation

Question

Hi all. My program does a very long operation - more than an hour. (import records from excel file). I create a thread, the operation runs there, and put af:poll on the page for changing progress indicator. So it's ok. The trouble is that I get
Exception in thread "Thread-90" oracle.jbo.NotConnectedException: JBO-25200: Application module is not connected to a database.
     at oracle.jbo.server.DefaultTxnHandlerImpl.handleRollback(DefaultTxnHandlerImpl.java:145)
     at oracle.jbo.server.DBTransactionImpl.doRollback(DBTransactionImpl.java:4872)
     at oracle.jbo.server.DBTransactionImpl.rollback(DBTransactionImpl.java:2429)
     at kz.kklife.insis.modules.policyImport.ImportRunner.run(ImportRunner.java:124)
     at java.lang.Thread.run(Thread.java:619)
after some time.
With default jbo.ampool.timetolive (3 600 000) it throws exactly in an hour after starting developer server. So I changed it to 7 200 000. But I got an error on a production server in a random time - because I don't restart it just before importing, of course.
So, is there any settings for weblogic not to disconnect transactions? (I get a transaction object through getDBTransaction() method of application module) I tried to uncheck "Ignore In-Use Connections" option, but it didn't help.

Answer 1

Timo Hahn wrote:
As far as I understand the framework, a transaction begins directly after the last commit or rollback.
So I assume that the timeout is reset at this point. I would not make sense doing it otherwise. As you already mentioned if you set the timeout to e.g. 2 hours and you get the am instance from the pool after 1:59,59 of initializing the transaction it would be stale before you had any chance to do something with it.Oh. I'll try to commit new transaction just before import, thanks. Need I do something like
  DBTransaction transaction = ADFFacesUtils.getApplicationModuleForDataControl("ImportAppModuleDataControl").getDBTransaction();
  transaction.commit();
  // -- do long running stuffor you mean some another way to commit?
I would set up a different configuration for this long running transaction (an other AM configuration) where I increase the timeout value to a higher number. Then use an instance from this configuration for the long running stuff only.I use another AM, only for long running stuff. But users can do import simultaneously.