Admin Help


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	e-docs \| Site Map \| Search \| Contact \| Glossary \| WebLogic Server Documentation

Admin Help: Table of contents; Connections; Events; JDBC info; Licenses; Properties; Realms; Security; Threads; Versions; Workspaces
WebLogic Administration: WebLogic Server Administrators Guide

Workspace help

The Workspace page displays information about the current T3Client workspaces in the WebLogic Server. Each T3Client has its own workspace that it can use to store and fetch arbitrary objects. A T3Client workspace and the objects in it are destroyed according to the interval set in the hard or soft disconnect timeout; setting the interval to non-zero will cause the WebLogic Server to wait that many minutes before cleaning up the T3Client's resources on the WebLogic Server. Setting the timeouts to "never" means that the T3Client's resources, including its workspace, are never destroyed.

The WebLogic Server itself has a system workspace. T3Client workspaces are contained within the system workspace.

Workspace ID

The client workspace ID is the unique ID that identifies the T3Client's workspace. It is assigned by the WebLogic Server when the workspace is created.

T3User

Each T3Client gets access to the WebLogic Server as a T3User. A T3User has a username and password. The default T3User is Guest (which does not require a password).

Connection context

The connection between a T3Client and the WebLogic Server belongs to a single T3Client, and is uniquely identified by its connection context information. There is more information available about each connection, including port and address information.

A connection context can be reused by another T3Client as soon as it is released. The connection context is identified by the ID of the connection and its number of reuses, separated by a colon. For example, connection 14 on its 276th reuse will appear as "14:276".

Time of last work

Time of last work shows the date and time of the last client operation carried out over this connection.

Hard/Soft/Idle disconnect timeouts

Three disconnect timeouts are shown:

Timeout for hard disconnect indicates how long the WebLogic Server will wait to disconnect a T3Client and return its resources, including its connection and its workspace, to the connection pool after the WebLogic Server notices that the socket between the T3Client and the WebLogic Server has been closed. The default for this disconnect timeout is immediately. Setting the timeout to non-zero means that the WebLogic Server will wait that many minutes before cleaning up after the T3Client disconnects; setting the timeout to never means that the T3Client's resources will remain on the WebLogic Server for the life of the server.
Timeout for soft disconnect indicates how long the WebLogic Server will wait to disconnect a T3Client after the client issues a disconnect request (with the T3Client.disconnect() method). The default for this disconnect timeout is immediately. Setting the timeout to non-zero means that the WebLogic Server will wait that many minutes before cleaning up after the T3Client disconnects; setting the timeout to never means that the T3Client's resources will remain on the WebLogic Server for the life of the server.
Timeout for idle disconnects indicates how long the WebLogic Server will wait to disconnect a T3Client after the WebLogic Server notices that the client is idle. The default for this disconnect timeout is never.

Workspace contents

You can examine the contents of each client's workspace in the second row of each client's entry. This two-column table shows information that is specific to the client. For example, information that displays for a WebLogic/JDBC client is value for the connection environment, which includes the number of statements and result sets, and the name of the JDBC driver in use.

Note that you can't -- for security reasons -- see the contents of any workspaces scoped to the system level.

Back to the Admin Help Summary