Always set up a default transaction timeout.
总是设置默认事务超时。
Set the Component transaction timeout integer to 30.
将组件事务超时时间设置为30。
Double click on the specific bean to set the transaction timeout.
双击具体的bean来设置事务超时时间。
WebSphere Application Server offers two ways to set the transaction timeout.
WebSphereApplicationServer提供了两种设置事务超时时间的方式。
If this is not the case, then you should set the transaction timeout for each bean.
如果不是这种情况，则应该对每个bean都设置事务超时时间。
Find the timestamp of the transaction timeout in the application server SystemOut.log file.
在应用服务器SystemOut . log文件中找到事务超时的时间戳。
Option 2: You can set the transaction timeout in the deployment descriptor for the beans. To do that.
选项2：可以在部署描述符中为bean设置事务超时时间。
Changing the transaction timeout for all beans will impact all applications running in that container.
更改所有bean的事务超时时间会影响在容器中运行的所有应用程序。
Multiple gaps like this could cause a transaction to last longer than 120 seconds, resulting in a transaction timeout.
多个这样的差距可能会导致事务的执行时间超过120秒，从而导致事务超时。
Other information like DCE security level and transaction timeout can also be specified using this class. For example.
其它的信息(如dce安全级别及事务超时)也会通过使用该类来指定。
However, it must be taken into account what the database can handle without a transaction timeout or a transaction log full failure.
但是，必须考虑到在不出现事务超时或事务日志写满的情况下数据库能够处理的操作量。
When tracing that includes the Transaction=all trace string is enabled, it is possible to determine the cause of a transaction timeout.
当启用了包括Transaction=all跟踪字符串的跟踪时，就可以确定事务超时的原因了。
Transaction timeout defaults to the default timeout of the underlying transaction system, or to none if time outs are not supported.
事务默认超时时间取决于事务系统，也有可能没有，如果事务系统不支持。
Note that Transaction timeout is set up on the DE-Light gateway and there are no callbacks from the gateway back into the application server.
注意到事务timeout是建立在DE - Light网关中的，并且没有从网关到应用程序服务器的反向调用。
A typical timeout used with WebSphere Application Server is the default transaction timeout, which defines how long a transaction can run before it is automatically rolled back.
WebSphereApplicationServer使用的一种典型的超时就是默认事务处理超时，它定义了在自动回滚之前一次事务处理最长可运行多长时间。
Option 1: If all of the beans set the transaction timeout to the same value, then you can set the maximum transaction timeout in the WebSphere transaction service using the admin console.
选项1：如果所有bean都将事务超时时间设置为相同的值，则可以使用管理控制台来设置WebSphere事务服务中的最大事务超时时间。
This is because a transaction will time out after it has been active for 120 seconds by default, meaning that you need to have at least 120 seconds of trace data prior to the transaction timeout.
这是因为在缺省情况下事务将会在处于活动状态120秒后超时，这意味着您至少需要在事务超时前120秒钟的跟踪数据。
For example, it's interesting to separate a TIMEOUT event from a SERVER_SHUTDOWN event, for logging purposes or to investigate the need for transaction rollbacks.
例如，为了记录日志或调查事务回滚的需求，将TIMEOUT事件从SERVER_SHUTDOWN事件分离出来是很有意义的。
If the application has set a timeout for several seconds, it exits in a given amount of time, unlocks the application, then asks you to return later to finish your transaction.
如果应用程序将超时设置为数秒钟，则会在给定时间内退出，取消锁定应用程序，然后要求您稍后返回以完成事务。
Set Total transaction lifetime timeout to 30.
将整个事务生命周期的超时时间设置为30。
It shields application developers from the complexity of transaction error and timeout handling related to remote Web services invocation.
应用程序开发人员通过它避免了与远程Web服务调用相关的复杂事务错误和超时处理。
Under the heading List of Inactive SQL statements from current UOW, you see all the SQL statements that were executed in the lock owner's transaction prior to the occurrence of the lock timeout.
在标题Listof InactiveSQLStatementsfromcurrent UOW下边，可以看到在发生锁定超时之前锁持有者的事务执行的所有sql语句。
To force a lock timeout error, establish a first database connection and execute some SQL statements simulating a real transaction on the table employee.
为了促使一个锁定超时错误发生，我们首先建立一个数据库连接，并执行一些sql语句来模拟表employee上的真实事务。
Timeout: the timeout attribute specifies how long the transaction may run before timing out (and automatically being rolled back by the underlying transaction infrastructure).
timeout： timeout属性指定在超时(以及被底层事务基础设施自动回滚)之前事务可以运行多长时间。
Due to the design of the application server, JMS connections can be closed because the Aged timeout has elapsed, even if JMS sessions created from that connection are involved in a transaction.
由于应用服务器设计的原因，JMS连接可能会因为超过过时超时而关闭，即使从该连接创建的JMS会话涉及一个事务也是如此。
In these circumstances the operation fails due to the expired timeout and the transaction aborts appropriately.
在这些情况下，将会因为超时过期而导致操作失败，事务也将随之中止。
If transaction flow is enabled on the binding or the channel, the operation may take longer to execute than the specified timeout.
如果对绑定或通道启用了事务流，执行操作所需的时间可能会比指定的超时时间长。
If transaction flow is enabled on the binding or the channel, the operation may take longer to execute than the specified timeout.
如果对绑定或通道启用了事务流，执行操作所需的时间可能会比指定的超时时间长。
应用推荐