Previous Topic  Next Topic

Configuring the Connection Pool

This topic describes how you can configure a connection pool using the ConnectionPoolConfig.properties file and view cached connections on the Server Console.

If you have used SQL statements or other similar tools to connect to a database and act on data, you probably know that getting the connection and signing in is the part that takes the most time. It takes several seconds every time a program needs to establish a connection. To improve performance, you can cache connections in the connection pool. Logi Report Server can then use a cached connection each time the same user accesses the same database table, free from having to create the connection to the database, which saves much time.

You can configure a connection pool using the ConnectionPoolConfig.properties file in the <install_root>\bin directory. The following example shows the contents in the file and describes the properties in the file:

# jdbcpool configure information
URL1=jdbc:hsqldb:JRDemo1400
Expire_URL1=0
IdleExpire_URL1=1
MaxCount_URL1=15
MaxShare_URL1=1
Attempt_URL1=100
Interval_URL1=1000

• URL1
  JDBC URL that can establish a connection to your database. The URL contents are case sensitive.

  You need this property to enable the connection pool. You should give a value that matches exactly with the URL used in Logi Report Designer to establish a connection to the database. The other six properties are optional. If you do not set values to them, Server uses the default values.

  "URL1" is an example of naming the URL. The name should start with the uppercase "URL". If you change the name "URL1" to "URLxY", you should also update the "URL1" in the other property names to "URLxY", for example, change "Expire_URL1" to "Expire_URLxY".

• Expire_URL1
  You can define how long in seconds it takes for an active connection to expire. The value for this property by default is 0, which means that the active connection will not expire.
• IdleExpire_URL1
  You can define how long a free connection can be idle before Server closes it. Server does not release the connection until the defined time is up. The value for this property by default is 1, which means that Server releases the connection after it is idle for one second. If the value is 0, Server closes the connection right after it starts idling.
• MaxCount_URL1
  The maximum number of connections based on the URL. The value for this property by default is 50. Once the number of the connections reaches the maximum, Server blocks any new connections until a free connection becomes available. The fewer the connections, the better the performance of Logi Report Server. If you set the value to 0, Server does not limit the number of the connections.
• MaxShare_URL1
  The maximum number of requests in one connection that Server can run simultaneously. Once the number of the requests reaches the maximum, Server creates a new connection to connect to the database. The value for this property by default is 1, which means that Server can run at most one request in one connection simultaneously. The smaller the number of requests, the better the performance of Logi Report Server. If you set the value to 0, Server does not limit the number of requests sharing one connection and runs all the requests in one connection simultaneously.

  Since the properties MaxShare_URL1 and MaxCount_URL1 are incompatible, you should make a balance between them to achieve the best performance of Logi Report Server.

• Attempt_URL1
  This property has a close relation to the property MaxCount_URL1. Once the number of the connections reaches the maximum, Server blocks any new connections until a free connection becomes available. To make the most use of the available connections in the pool, you can use this property to set how many times the engine tries to establish a new connection. The default value for this property is 1, which means that the engine only tries once to create a new connection. A good value for this is 100, and the engine will try 100 times based on the interval you set to the Interval_URL1 property.
• Interval_URL1
  The interval in milliseconds that the engine waits for between attempts to create a new connection if a previous try failed. The default value for this property is 0, which means that the engine starts the next attempt immediately. However, if you set Attempt_URL1 to 1, Server ignores this property is ignored because there will not be a second attempt. A good value for this is 1000 which is one second.

Administrators can view the cached connections: on the system toolbar of the Server Console, navigate to Administration > Connection > Connection Pool. Server displays the Connection Pool page and the cached connections in the connection table with the following information. To cancel a connection from working, it and then select Disconnect.

Previous Topic  Next Topic