ResourceRefExtension

ResourceRefExtension

This type is a class for model objects.

An optional extension to a resource ref which allows specifying IBM isolation level support at a resource ref level. @since WAS5.0
Package: commonext

Classifier ID:  -1
Instance class name:  * Unspecified *
Instance class:  * Unspecified *

Collection attributes having this type:
  EnterpriseBeanExtension.resourceRefExtensions
  PortletApplicationExtension.resourceRefExt
  WebAppExtension.resourceRefExtensions

Attributes Summary

isolationLevel : IsolationLevelKind * No description is available *

connectionManagementPolicy : ConnectionManagementPolicyKind This resource ref extension can be used for specifying the connection management policy on WebSphere platforms which support this option (such as zOS). Connection Starvation Connection starvation occurs when the number of connections being held by applications reaches the maxium number of connections set during configuration. If connections aren't being returned to the pool fast enough, or not at all, then new requests for connections will not be able to be serviced. Connection starvation due to users not closing connections is one of the main issues this design wants to address. Poorly written applications often have one or two places where they forget to close connections (sometimes in error paths). If nothing is done, it does not take long before the connection pool is completely and indefinitely out of connections. This type of starvation, which is permanent, is different from that where connections are closed when the user is done with them, but because of high usage the pool is temporarily exhausted. Reducing Connection Starvation Shareable Connections For shareable connections, the ManagedConnection will always be returned to the pool when the UOW ends. Since all connections will always run in a UOW this means that it won't be possible for users to "leak" connections because they forgot to close them. It also means that the connection handles will be "parked" on a dummy connection and reassociated to a new connection on the next preinvoke. Unshareable Connections For unshareable connections we'll have two options for the user to choose from to police users who don't close their connection handles in a timely maner. Aggressive | Normal Aggressive - under this option, connection handles a component has in use will be tracked. Handshaking between the Container and the ConnectionHandleManager during passivation time will force all handles to be closed and the component instance to be removed. Normal - similar to aggressive except that the connection handles will be closed and the bean removed during ejbRemove. (default action) Note: This behavior is consistent with that of Websphere z/OS and their descriptor.

commitPriority : EInt * No description is available *

resourceRef : ResourceRef @ * No description is available *

Attribute Details

isolationLevel  -  * No description is available *
    Data Type: IsolationLevelKind
    Default value:  unspecified
    Allowed values:
        0 - TRANSACTION_NONE
        1 - TRANSACTION_READ_UNCOMMITTED
        2 - TRANSACTION_READ_COMMITTED
        4 - TRANSACTION_REPEATABLE_READ
        8 - TRANSACTION_SERIALIZABLE
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

connectionManagementPolicy  -  This resource ref extension can be used for specifying the connection management policy on WebSphere platforms which support this option (such as zOS). Connection Starvation Connection starvation occurs when the number of connections being held by applications reaches the maxium number of connections set during configuration. If connections aren't being returned to the pool fast enough, or not at all, then new requests for connections will not be able to be serviced. Connection starvation due to users not closing connections is one of the main issues this design wants to address. Poorly written applications often have one or two places where they forget to close connections (sometimes in error paths). If nothing is done, it does not take long before the connection pool is completely and indefinitely out of connections. This type of starvation, which is permanent, is different from that where connections are closed when the user is done with them, but because of high usage the pool is temporarily exhausted. Reducing Connection Starvation Shareable Connections For shareable connections, the ManagedConnection will always be returned to the pool when the UOW ends. Since all connections will always run in a UOW this means that it won't be possible for users to "leak" connections because they forgot to close them. It also means that the connection handles will be "parked" on a dummy connection and reassociated to a new connection on the next preinvoke. Unshareable Connections For unshareable connections we'll have two options for the user to choose from to police users who don't close their connection handles in a timely maner. Aggressive | Normal Aggressive - under this option, connection handles a component has in use will be tracked. Handshaking between the Container and the ConnectionHandleManager during passivation time will force all handles to be closed and the component instance to be removed. Normal - similar to aggressive except that the connection handles will be closed and the bean removed during ejbRemove. (default action) Note: This behavior is consistent with that of Websphere z/OS and their descriptor.
    Data Type: ConnectionManagementPolicyKind
    Default value:  unspecified
    Allowed values:
        0 - Default
        1 - Aggressive
        2 - Normal
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

commitPriority  -  * No description is available *
    Data Type: EInt
    Default value:  unspecified
    Required:  false
    Changeable:  true
    Unsettable:  true
    Many:  false
    Ordered:  true
    Lower bound:  0
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

resourceRef  -  * No description is available *
    Reference Type: ResourceRef @
    Containment:  false
    Container:  false
    Required:  true
    Changeable:  true
    Unsettable:  false
    Many:  false
    Ordered:  true
    Lower bound:  1
    Upper bound:  1
    Unique:  true
    Derived:  false
    Transient:  false
    Volatile:  false

(C) COPYRIGHT International Business Machines Corp. 1996-2006

Attributes Summary
isolationLevel : IsolationLevelKind	* No description is available *
connectionManagementPolicy : ConnectionManagementPolicyKind	This resource ref extension can be used for specifying the connection management policy on WebSphere platforms which support this option (such as zOS). Connection Starvation Connection starvation occurs when the number of connections being held by applications reaches the maxium number of connections set during configuration. If connections aren't being returned to the pool fast enough, or not at all, then new requests for connections will not be able to be serviced. Connection starvation due to users not closing connections is one of the main issues this design wants to address. Poorly written applications often have one or two places where they forget to close connections (sometimes in error paths). If nothing is done, it does not take long before the connection pool is completely and indefinitely out of connections. This type of starvation, which is permanent, is different from that where connections are closed when the user is done with them, but because of high usage the pool is temporarily exhausted. Reducing Connection Starvation Shareable Connections For shareable connections, the ManagedConnection will always be returned to the pool when the UOW ends. Since all connections will always run in a UOW this means that it won't be possible for users to "leak" connections because they forgot to close them. It also means that the connection handles will be "parked" on a dummy connection and reassociated to a new connection on the next preinvoke. Unshareable Connections For unshareable connections we'll have two options for the user to choose from to police users who don't close their connection handles in a timely maner. Aggressive \| Normal Aggressive - under this option, connection handles a component has in use will be tracked. Handshaking between the Container and the ConnectionHandleManager during passivation time will force all handles to be closed and the component instance to be removed. Normal - similar to aggressive except that the connection handles will be closed and the bean removed during ejbRemove. (default action) Note: This behavior is consistent with that of Websphere z/OS and their descriptor.
commitPriority : EInt	* No description is available *
resourceRef : ResourceRef @	* No description is available *