Thanks to your reply
we are using SqlServer200 DB.which uses only row only locking policy.I hope
this wont cause deadlock exception.I want to control timeout period of each
bean.please see my log file.this is the one when JBoss is started.
Please see the lines that marked in red color
1) we
The logs mention a possible transaction timeout on the operation that is being
performed. However, the actual cause might be related to locks on the database
table on which the operation is being carried out. Have you looked at the
database table to check whether the table gets locked as part of
thanks for your reply...
I will try to modify web appl/.timeout issue.
but I need clear idea about JBoss Transaction timeout issues..I am using
default container configuration(Standard)..when my clients trying to delete
particular case, most of the people are getting "Unable to delete case"
me
I dont think that this has got anything to do with the EJB transaction timeout
value. The EJB transaction timeout value will come into picture only when you
have invoked some method on the EJB and its taking a long time to process.
What you are looking for is, i guess, the session timeout on the
Thanks to spend time on my issue.
My requirement is when the application is timedout I hav to notify presentation
tier(ULC) as " Session is timedout please login again "
I still seeing Transaction MBean in jta-service.xml file only...
eventhough timeout is 300 sec...application is still work
anonymous wrote : my application is destroyed after 35 mins only
Please explain as to what you mean by application being destroyed. What is
that you want to have on transaction timeout?
anonymous wrote : I dont find any TransactionManagerService on
jboss-service.xmlwe are using jboss4.0.3
