The catalog database uses a JDBC data source implementation, which means that you can configure the connection pool settings in the WebSphere® Application Server.
The data source details for the catalog database depend on whether you are using the original embedded Derby database or if you have migrated to a different database.
Table 1. Data source details for the catalog database
|Database name||JNDI name|
|Data source for embedded Derby database||hubdb ||jdbc/MashupHub/hubdb |
|Data source for migrated database||migdb ||jdbc/MashupHub/migdb|
You can modify the connection pool settings for the MashupHub data source for your application requirements. See the following web sites for information about changing the connection pool settings through the WebSphere Application Server administrative console:
Connection pool settings:
Following are the key options for MashupHub data sources:
Specifies the maximum number of physical connections that you can create in the pool. The default value is 50 for the MashupHub data source. If you have a highly concurrent application, and if you see connection timeout errors in the javamashuphub.log or in the server's SystemOut.log, increase the maximum connections.Connection timeout
Specifies the interval, in seconds, after which a connection request times out and a ConnectionWaitTimeoutException exception is thrown. The default connection timeout for the MashupHub data source is set to 5 minutes (300 seconds).
Troubleshooting problems with the MashupHub data source:
Database Connection timeouts
System stops responding
For example, a ConnectionWaitTimeoutException
message in the javamashuphub.log
, like the following code:
2009-09-20 19:25:54,052 (WebContainer : 23) ERROR
[com.ibm.mashuphub.data.WASDataSrc] Error creating connection,
if persists, try restarting database. Error:
not available, Timed out waiting for 299998
Workaround: Increase the maximum connections for the connection pool for the MashupHub data source.
A small connection pool size and a high connection timeout value can make the server appear to be not responding because threads are waiting for a connection in the time specified in the Connection timeout
setting. You might see warning messages in the WebSphere Application Server SystemOut.log
file like this message:
ThreadMonitor W WSVR0605W: Thread "WebContainer : 43" (0000003f)
has been active for 670186 milliseconds and may be hung.
There is/are 40 thread(s) in total in the server that may be hung.
Workaround: Check the maximum connections and the connection timeout values used for the MashupHub data source. Increase the maximum connections and if the connection timeout was incorrectly set to a higher value, reset it to the default value of 300 seconds.
Parent topic: Troubleshooting problems: imc3