Hi,
I'm using ws 6.0.2.
On an application on a profile a recieved this error.
.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180008
Looking at websphere manual it seems related to "connection pooling".
Is there a way to "clean" connection pooling without restarting the profile? I restarted the single application that has the problem but it didn't solve the problem.
From ws manual:
You might have a connection leak if your application receives exceptions such as
com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException or
com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException when attempting
to access a data source or JCA-compliant resource adapter, respectively.
In Example 6-10, the application receives a ConnectionWaitTimeoutException
after waiting for 1800030 milliseconds for a connection, but no free connection
from the pool is available. If the connection pool has a high value for the
connection timeout (for example, 1800 seconds), you might not see the
ConnectionWaitTimeOutException immediately.
Example 6-10 ConnectionWaitTimeoutException
[7/12/05 14:04:58:328 AST] 3ad6086e ConnectionMan E J2CA0020E: The
Connection Pool Manager could not allocate a Managed Connection:
com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection
not available, Timed out waiting for 1800030
Is there some command that resets connection pooling?
Thanks in advance.
I'm using ws 6.0.2.
On an application on a profile a recieved this error.
.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180008
Looking at websphere manual it seems related to "connection pooling".
Is there a way to "clean" connection pooling without restarting the profile? I restarted the single application that has the problem but it didn't solve the problem.
From ws manual:
You might have a connection leak if your application receives exceptions such as
com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException or
com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException when attempting
to access a data source or JCA-compliant resource adapter, respectively.
In Example 6-10, the application receives a ConnectionWaitTimeoutException
after waiting for 1800030 milliseconds for a connection, but no free connection
from the pool is available. If the connection pool has a high value for the
connection timeout (for example, 1800 seconds), you might not see the
ConnectionWaitTimeOutException immediately.
Example 6-10 ConnectionWaitTimeoutException
[7/12/05 14:04:58:328 AST] 3ad6086e ConnectionMan E J2CA0020E: The
Connection Pool Manager could not allocate a Managed Connection:
com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection
not available, Timed out waiting for 1800030
Is there some command that resets connection pooling?
Thanks in advance.
