|
|
The Application Server Options for WebLogic Connectors page of the New / Edit J2EE Session EJB Wizard is application server specific. The configuration options change depending on the application server type you have chosen. Each J2EE application you deploy contains both a connector and EJB.
These options, along with the application server options for the session EJB, are needed for your application server, and are included in the packaging of your enterprise application.
 |
These are WebLogic application server specific options that are set in META-INF\weblogic-ra.xml. Please check your WebLogic application server documentation for suggestions and limitations to use when setting these options. |
WebLogic Options
Each stateful EJB you use keeps a connector allocated (until the EJB is removed). This ensures that the same number of connectors are available. Connector options are set on the previous panel of the wizard.
Initial Capacity: Identifies the initial number of managed connections which the WebLogic Server will attempt to obtain during deployment. The default value is 10.
Max Capacity: Identifies the maximum number of managed connections which the WebLogic Server will allow. Requests for newly allocated managed connections beyond this limit will result in an exception being returned. The default value is 1000.
Capacity Increment: Identifies the number of additional managed connections which the WebLogic Server will attempt to obtain during resizing of the maintained connection pool. The default value is 10.
Shrinking Enabled: Indicates whether or not the Connection Pool should have unused managed connections reclaimed as a means to control system resources. The value can be either True or False. The default value is True.
Shrink Period (in minutes) : Identifies the amount of time the connection pool management will wait between attempts to reclaim unused managed connections. The default value is 15.
Logging Enabled: Indicates whether or not the log writer is set for either the ManagedConnectionFactory or ManagedConnection. If this element is set to True, ouput generated from either the ManagedConnectionFactory or ManagedConnection will be sent to the file specified by the Log Filename. The value can be either True or False. The default value is False.
Log Filename: Specifies the name of the log file where output generated from either the ManagedConnectionFactory or ManagedConnection is sent. The full address of the filename is required.
Connection Profiling Enabled: Indicates whether or not the connection pool should store the call stacks of where each connection is allocated. If enabled, the information can be viewed on active connections through the console and the stacks for Leaked and Idle connections will be available and can help troubleshoot components that fail to close connections. The value can be either True or False. The default value is False.
Connection Max-Idle Time: Identifies the amount of time (in seconds) a connection handle can remain idle. This element prevents leaks when an application may not have closed a connection after completing usage. Idle connections will only be terminated when the connection pool becomes full and because of this, a new connection request is about to fail. The default value is 0.
 |
The pools used by your application server are a subset of the pools used by the Runtime Service. Take care that you have configured enough pools on the Pools Configuration page to handle the pools necessary for your application server. |
The task file and application server names are the names selected on the Task File and Application Server page of the J2EE Session EJB Wizard.
 |
|
 |
Packaging J2EE Session EJBs |
|
Configuring J2EE Session EJBs, Overview |
 |
MCS for Screens Help Links |
 |