EJB Transaction timeout and Statement Query Timeout

I am looking for some details on how statement query timeout is set when statement execution is part of the session bean transaction. I have done some test in webshere 6.1. and JBoss 5.0 and not getting the desired behavior. My understanding is following
- DB is Oracle 11g
- EJB transaction is set to 5 mins.
- Query time out setting is set to default vaule (not sure what is the default value)
- Session bean is updating say customer record using PreparedStatement
- Prior to calling session bean method I am locking the customer record using external/db tool and holding the lock.
- Call session bean method. Method waits endlessly for the lock to be acquired. No transaction rollback after 5 mins.
- After 10 minutes commit the transaction in the external db tool
- Session bean methods throws transaction rollback.
My understanding was that query timeout is set based on transaction "time to live". Please share out thoughts.
Edited by: hdjava on Jun 18, 2010 1:06 PM
Edited by: hdjava on Jun 18, 2010 1:07 PM

The following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout.

Similar Messages

JTA transaction timeout vs. EJB transaction timeout

Hi,
can anybody tell me if the JTA transaction timeout, e.g. <JTA
Name="myServer" TimeoutSeconds="60"/> works for EJBs as default transaction
timeout if none is given in the deployment descriptor.
I assumed that this is correct, and tried to test this by setting the
JTA-timeout value to 1 (second). However I experienced no timeout exceptions
in our logfile with this setting.
Regards
Andi
+49 69 263-87303, [email protected]

Thanks, Rob
"Rob Woollen" <[email protected]> schrieb im Newsbeitrag
news:[email protected]..
This should work fine in 6.1 and 7.0. I believe it was broken in 6.0
-- Rob
Andreas Bittorf wrote:
Hi,
can anybody tell me if the JTA transaction timeout, e.g. <JTA
Name="myServer" TimeoutSeconds="60"/> works for EJBs as default
transaction
timeout if none is given in the deployment descriptor.
I assumed that this is correct, and tried to test this by setting the
JTA-timeout value to 1 (second). However I experienced no timeoutexceptions
in our logfile with this setting.
Regards
Andi
+49 69 263-87303, [email protected]

Impost a EJB transaction timeout

          Hello...
          I have a problem....I need to impost a transaction timeout on a stateless ejb
          call
          without generate the transaction but only with a new Context and the successive
          lookup.
          This for return the ejb called in case witch this then called another another
          remote ejb but this not give response......so that I can make finish the transaction
          first that the second ejb goes in timeout...
          Is this possible with the stateless ejb also setting some weblogic parameter?
          I work with an J2EE 2.0 application under WLS6.1 SP5 .
          thanks.


          This isn't really possible. If your second bean throws an exception if it doesn't
          respond then you can always catch this and call setRollbackOnly() (or let the
          container do this for you); if however the second bean doesn't respond and blocks
          for a long time, then the transaction timeout won't help. WebLogic implements
          the transaction timeout on another thread so it can keep good time, but can only
          signal your bean when it tries to do something transactional - and if it's blocked
          in another method this might not happen.
          simon.
          "rion" <[email protected]> wrote:
          >
          >Hello...
          >I have a problem....I need to impost a transaction timeout on a stateless
          >ejb
          >call
          >without generate the transaction but only with a new Context and the
          >successive
          >lookup.
          >This for return the ejb called in case witch this then called another
          >another
          >remote ejb but this not give response......so that I can make finish
          >the transaction
          >first that the second ejb goes in timeout...
          >Is this possible with the stateless ejb also setting some weblogic parameter?
          >I work with an J2EE 2.0 application under WLS6.1 SP5 .
          >thanks.
          >

Monitor EJB transaction timeout value

Hi,
I try to create a test case to monitor transaction timeout and rollback value
(not 0) from weblogic 6.1 console. By adding the timeout value to the weblogic-ejb-jar.xml
and rebuild the beanManaged example, I successfully create the scenario by seeing
the timeout and transaction rollback exception from the server. However, from
console the timeout value and rollback value of EJB monitoring still show "0"
not any number I expected. Any bug from Weblogic?
Thanks, Cathy

The following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout.

Ocj4 ejb transaction-timeout

I've got the following in my orion-ejb-jar.xml:
<session-deployment name="..." transaction-timeout="900"/>
OC4J appears to ignore it. For one, I get transaction timeouts with operations lasting less than 900 seconds. For two, I see in the EM MBean browser that the transaction timeout for the stateless session bean has a value of "-1".
Am I doing something wrong, or is OC4J broken?

Anybody out there?
I'm sure I can't be the only one trying to do this...

EJB Transaction Timeout

Hi,
we have set the following in bc4j.xcfg for our AppicationModule which is deployed as EJB with BMT:
<jbo.ejb.txntimeout>0</jbo.ejb.txntimeout>
With jbo.debugoutput=console we get the following lines
including "Transaction timeout set to 0 secs"
[298] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[299] Loading from /de/materna/heimabrechnung/common/logging/logging.xml file
[300] Loading from indvidual XML files
[301] Loading the Containees for the Package 'de.materna.heimabrechnung.common.logging.logging'.
[302] Loading from /de/materna/heimabrechnung/common/logging/LoggingModule.xml file
[303] Loading from /de/materna/heimabrechnung/common/logging/LogEintragView.xml file
[304] Loading from /de/materna/heimabrechnung/common/logging/LogEintrag.xml file
[305] Loading from /de/materna/heimabrechnung/common/logging/LogStacktraceView.xml file
[306] Loading from /de/materna/heimabrechnung/common/logging/LogStacktrace.xml file
[307] mUsePersColl is false
[308] ViewObjectImpl.mDefaultMaxRowsPerNode is 70
[309] ViewObjectImpl.mDefaultMaxActiveNodes is 30
[310] Transaction timeout set to 0 secs
[311] Created root application module: 'de.materna.heimabrechnung.common.logging.LoggingModule'
[312] Locale is: 'en'
[313] Transaction timeout set to 0 secs
[314] Trying connection: DataSource='com.evermind.sql.OrionCMTDataSource/heimabrechnung/jdbc/HeimabrechnungDS'...
[315] Successfully logged in
But after a while not using the ApplicationModule on the client the server throws the following exception:
java.lang.NullPointerException
at oracle.jbo.server.remote.ejb.EJBApplicationModuleImpl.resumeTransaction(EJBApplicationModuleImpl.java:635)
at de.materna.heimabrechnung.common.logging.server.ejb.beanmanaged.LoggingModuleServer.logDebug(LoggingModuleServer.java:6
0)
at RemoteLoggingModule_StatefulSessionBeanWrapper20.logDebug(RemoteLoggingModule_StatefulSessionBeanWrapper20.java:1383)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:802)
at java.lang.Thread.run(Thread.java:484)
Any ideas ?
What we need are EJB's without any timeout!

The following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout.

EJB Transaction-Timeout Effects

Hi,
We have a long running process, well, longer than the 60 seconds of the default transaction time-out set in the server.xml. I was going to lengthen it but thought I better ask as changing it to a larger amount of time might cause some effects that are undesired.
So a couple of question:
1) Why was it defaulted to 60 seconds, is there something unique about 60 seconds or is just a number to start with.
2) What are the effects of making it larger (e.g. degraded performance, memory usage, connection pool?
3) How does the transaction-timeout property affect the JDBC connection(s) that are contained within the scope of the transaction?
4) Does the transaction timeout affect the time sql queries can take? Or is that the inactivity-timeout?
I greatly appreciate any feedback I can get.
Thanks,
Donovan

The following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout.

Urgent: EJB Transaction mechanism and Database Transaction mechanism

Anybody please clarify me how EJB transaction mechanism use the underlying database transaction mechanism? Here my concern is that in the context EJB transaction, how much reponsibilities are performed by EJB container and how much responsibilities are performed by underlying database server. I will deem it a great favor if you kindly explain the whole story with example(s).

Actually the ejb container is managing the persistence.
It will be like this.
if u r using entity beans or statefull beans
while creating entity bean class you have to specify in the
deployment descriptor, which table in the database this bean is representing .
On the runtime , when you are creating an instance of a entity bean ,that instance will be corresponds to a row in the mapped table.
what all changes you have made to that instance's attributes ie;
columns in that row that all will be avilable in the session
When you commit this particular session .this changes will be written to disk.
that's how the change is managed ...
assume if one user is modifying the particular row and another user is deleting it ..which ever transaction commits first will be get effected.
if modification is committing first and then delete the row will be deleted last.but if first delete and then modify while commiting modifycation..
you should get an error saying that particular row is missing from storage
this how ejb container is manging the persistence
in all cases even in case of synchronus acess
i think u r cleard with this much

Default EJB transaction timeout

Within the weblogic-ejb-jar.xml it is possible to set:
<transaction-descriptor>
<trans-timeout-seconds>120</trans-timeout-seconds>
</transaction-descriptor>
which tells the container the maximum period of time an EJB method is allowed to run. Is there some default value that is used if this is not set? Or does leaving this tag out of the XML file completely give the EJB methods infinite time to return?

"Ruben Ambrose" <[email protected]> wrote in message news:22852953.1100634354551.JavaMail.root@jserv5...
Within the weblogic-ejb-jar.xml it is possible to set:
<transaction-descriptor>
<trans-timeout-seconds>120</trans-timeout-seconds>
</transaction-descriptor>
which tells the container the maximum period of time an EJB method is allowed to run. Is there some default value that is used ifthis is not set? Or does leaving this tag out of the XML file completely give the EJB methods infinite time to return?
The default value is 30 seconds. This value can be changed via web ui console of by editing config.xml.
<JTA Name="myServer" TimeoutSeconds="60"/>
Also, even if the timeout is set in the DD, factual timeout is defined by initiator of the TX.
Slava

Ejb Transaction Timeouts

We have a weblogic cluster, we keep getting messages in the logs saying "Transaction timed out after 60 seconds". We have also noticed that if we shutdown one of the servers in the cluster then we do not get these messages in the logs.What could be the reason for this?
Please advise.
Anil

Sorry for the delay:
Here is the stack trace
Error marking transaction for rollback: java.lang.IllegalStateException: Cannot mark the transaction for rollback. xid=23645:9de7ceb8422f21aa, status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 60 seconds Name=[EJB com.nextjet.enterprise.timing.timingmanager.TimingManagerBean.actionFired(flux.RemoteKeyFlowContext)],Xid=23645:9de7ceb8422f21aa(148367394),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,activeThread=Thread[RUNNER: 33273648,5,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@8d7ea8e),SCInfo[exms+enterprise1]=(state=active),SCInfo[exms+routing2]=(state=active),properties=({ISOLATION LEVEL=2, weblogic.transaction.name=[EJB com.nextjet.enterprise.timing.timingmanager.TimingManagerBean.actionFired(flux.RemoteKeyFlowContext)], weblogic.jdbc=t3://myserver.domain.com:3337}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=enterprise1+myserver.domain.com:3337+exms+t3+, Resources={})],CoordinatorURL=enterprise1+myserver.domain.com:3337+exms+t3+)]
Server name: enterprise1
Time: 07:05:00
Date: 07/30/2004

Changing default transaction timeout for 5.1

          Hi
          Does someone know a way to change the default ejb transaction timeout for
          WL5.1?
          The default is 300 secs, which is a bit too long for me.
          I know I can change it in each deployment descriptor but it would be easier
          and quicker if I could just change the default :-)
          Thanks
          Nicolas


There is another way but I think it's more complicated.
After reading the file you can use a java code (java embedded activity) and split the file.
For each part of the split you can PUT by FTP the file with append mode. That way your transaction will run in few cycles with less time.

BMT and transaction timeout

Hello,
Does anybody knows what the behavior should be for a Session EJB with BMT (using JTA) after a transaction timeout? Does the container performs a database rollback for you immediately after the time-out event? I’ve noticed that JBoss does not perform a rollback but Web does. What do the J2EE specs say what should happen?
We are experiencing database locks in an Oracle database caused by ‘hanging’ JTA-transactions which aren’t removed after a timeout. An application server restart will remove them. We are trying to find the cause, there fore I’am posting this message.
Regards,
Marteyn Heijlaerts

          "Laurel Neustadter" <[email protected]> wrote:
          >
          >Hi:
          >
          >The WLS 6.0 documentation states that for a CMT bean, one specifies the
          >transaction
          >timeout in weblogic-ejb-jar.xml, and for a BMT bean, one specifies the
          >transaction
          >timeout via UserTransaction.setTransactionTimeout().
          >
          >You also set a transaction timeout attribute at the domain level. How
          >does the
          >domain level attribute work into all of this? How is it used?
          >
          >For example, if a transaction timeout value is not specified at the bean
          >level,
          >will the domain level value be used?
          >
          >Laurel
          Yes, the domain level timeout is the default.
          It is overridden by any setting at the EJB level. This in turn
          can be overridden by the client calling the EJB, if the client
          starts a transaction and uses
          transactionManager.setTransactionTimeout()

Transaction timeout seconds and suspended trsnactions.

          All,
          Does the <trans-timeout-seconds>10</trans-timeout-seconds> in weblogic-ejb-jar.xml
          apply to transactions that are in a suspended state?
          For E.G
          I have EJB1 (Container Managed/Required) that starts transaction T1 and does some
          work then calls another ejb EJB2 (Container Managed/NotSupported) which makes
          a inter domain T3 call. Since EJB2 is configured with NotSupported transaction
          attribute, transaction T1 is suspended for the time being while the business method
          of EJB2 is executing.
          The question is if I set <trans-timeout-seconds>10</trans-timeout-seconds> for
          transactions started by EJB1, will it work? Looks like once a method on EJB2 is
          invoked, the transaction T1 is suspened and if the EJB2 method takes 30 seconds
          to execute, then transaction T1 waits untill that time despite having a transaction
          time out of 10 seconds.
          How can I exit out of the transaction T1 while its in suspened state if it takes
          more that 10 seconds for EJB2 to complete its work?
          Any suggestions are welcome and thx in advance.
          Regards,
          Dhilip.


          Dhilip,
          I had similar issue but in my case I got timeout exception once the transaction
          of first bean resumed. It seeems the timeout clock keeps on ticking even when
          the transaction is in suspended state.
          Finally I increased the timeout value of first bean to execute the process.
          -Ashish
          "Dhilip" <[email protected]> wrote:
          >
          >All,
          >
          >Does the <trans-timeout-seconds>10</trans-timeout-seconds> in weblogic-ejb-jar.xml
          >apply to transactions that are in a suspended state?
          >
          >For E.G
          >I have EJB1 (Container Managed/Required) that starts transaction T1 and
          >does some
          >work then calls another ejb EJB2 (Container Managed/NotSupported) which
          >makes
          >a inter domain T3 call. Since EJB2 is configured with NotSupported transaction
          >attribute, transaction T1 is suspended for the time being while the business
          >method
          >of EJB2 is executing.
          >
          >The question is if I set <trans-timeout-seconds>10</trans-timeout-seconds>
          >for
          >transactions started by EJB1, will it work? Looks like once a method
          >on EJB2 is
          >invoked, the transaction T1 is suspened and if the EJB2 method takes
          >30 seconds
          >to execute, then transaction T1 waits untill that time despite having
          >a transaction
          >time out of 10 seconds.
          >
          >How can I exit out of the transaction T1 while its in suspened state
          >if it takes
          >more that 10 seconds for EJB2 to complete its work?
          >
          >Any suggestions are welcome and thx in advance.
          >
          >Regards,
          >Dhilip.
          >
          >

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

Transaction timeouts of 242 seconds

Hi All,
I am getting transaction timeouts of 242 seconds. Can somebody help me where
is this timeout value configured and how change it?
Here We are Using Weblogic 8.1
Stateless Session Bean, DAO, Servlets and JSPs
The log file says as
<DEBUG>SQLException: The transaction is no longer active - status: 'Marked rollback.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 242 secon
ds
Name=[EJB com.hartfordlife.gbd.pvev.ejb.participantadmin.ParticipantAdministrationEJB.getPADownloadCaseCoverage(java.util.ArrayList,java.lang.String,java.lang.String)],Xid=BEA1-003
0E44EFCA87F28EDB9(14529255),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=242,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue:
'weblo
gic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTS
XAResourceImpl]=(state=started,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@10c624a),SCInfo[mydomain+myserver]=(state=active),properties=({weblogic.transaction.name=[
EJB com.hartfordlife.gbd.pvev.ejb.participantadmin.ParticipantAdministrationEJB.getPADownloadCaseCoverage(java.util.ArrayList,java.lang.String,java.lang.String)],
weblogic.jdbc=t3:
//157.209.165.64:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+157.209.165.64:7001+mydomain+t3+,
XAResources={},NonXAResources={})],C
oordinatorURL=myserver+157.209.165.64:7001+mydomain+t3+)]'. No further JDBC access
is allowed within this transaction.
<DEBUG>SQLErrorCode: 0
<DEBUG>SQLState: null
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 242 seconds
Thanks in Advance
Sai

Unfortunately, it seems to work different in JBoss7. I created a very simple app and it waits until end of query execution instead of interrupting it.
I'm porting application from weblogic to JBoss7 and it is critical for me to achieve identical behavior.

EJB Transaction timeout and Statement Query Timeout

Similar Messages

Maybe you are looking for