Properties on this tab govern the allocation and deallocation of resources required by the component.
Transaction Timeout A component’s Transaction Timeout property specifies the maximum duration of an EJB Server transaction. See Chapter 5, “Understanding Transactions and Component Lifecycles,” for more information on EJB Server transactions.
The timeout period is configured in seconds, with 0 indicating infinity (that is, no timeout). If the component’s Transaction Timeout property is not set, the default is inherited from the server properties. The default for a new server is 0. When specifying timeouts, a resolution of 5 seconds is recommended. EJB Server checks for timeouts after each method returns. Your component will not be deactivated in the middle of an invocation because of a timeout. When a transaction times out, the next method invocation in the client-side ORB throws the CORBA::TRANSACTION_ROLLEDBACK system exception.
To set Transaction Timeout for a server, display the All Properties tab in the Server Properties window. Then set the com.sybase.jaguar.server.tx_timeout property.
Network transport time is included in the measured timeout period. You may need to configure a larger timeout period if clients connect over slow networks.
Instance Timeout Specifies how long, in seconds, an active component instance can remain idle between method calls before the client’s proxy becomes invalid. If the timeout expires, the instance is automatically deactivated. Instance Timeout is useful for ensuring timely deactivation of stateful components. (“Stateful versus stateless components” explains this term.) The setting has no effect for stateless components.
When the timeout period is exceeded, EJB Server deactivates the component and invalidates the client’s object reference. If the client attempts another method invocation, the client-side ORB throws the CORBA::OBJECT_NOT_EXIST exception. At this point, the client must create a new proxy instance for the component.
This property is not set for new components; the component inherits a default value from the server properties. At the server level, configure the instance timeout by displaying the All Properties tab in the Server Properties window. Then set the com.sybase.jaguar.server.timeout property.
The timeout period is configured in seconds, with 0 indicating infinity (that is, no timeout). If the component’s Instance Timeout property is not set, the default is inherited from the server properties. The default for a new server is 0. When specifying timeouts, a resolution of 5 seconds is recommended.
Network transport time is not included in the measured timeout period. You may need to configure a larger timeout period if clients connect over slow networks.
