Hi Raimund,
I will definitely try to touch SESSION_TIMOUT.
The problem is reproducible each time. So it is no sporadically. I am running some short time running tests.
One idea is that this is related with the commit of the transaction. In this case after the first commit the problem occurs. If I use only one transaction the PreparedStatement-s are not closed.
userTran.begin(); //start transaction
removeProcessInstances();
userTran.commit(); //commit transaction
and no separate transaction for each process
//userTran.begin(); //start
transaction
deleteResources(id, transctionId,
state);
//userTran.commit(); //commit transaction
But if use only one transaction it may timeout if there is lots of process to
remove. (I think that XATimeout was 30 seconds). The strangest think is that
the connection itself is not closed.
P.S. Thanks for the interest.
Best Regards, Zhivko.
Raimund Jacob wrote:
Zhivko Mitrev wrote:
hi!
I am using MaxDB with JBoss 3.2.6. I have a problem; suddenly my
PreparedStatements are being closed. (SAP DBTech JDBC: Object is
closed.). Here is detailed information.
i cannot say anything about the specific code you pasted but i would
suspect an abnormality only if your error happens reproducably.
if it happens sporadically only, I can say from my experience that
long-running applications on long-running maxdb instances get a hickup
from time to time and lose a connection in the way you described.
one reason may be a session timeout on the maxdb side (parameter
SESSION_TIMEOUT or something) - the db closes a connection after
minutes/hours of inactivity. in my installations i usually disable this
timeout completely since inactivity is handled by the connection pool.
good luck solving this,
Raimund
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
