« Back to CVP - All Versions

AS/400 query from Call Studio

Combination View Flat View Tree View
Threads [ Previous | Next ]
AS/400 query from Call Studio
vxml server cvp 8.5 call studio jndi
Answer
7/19/12 12:45 PM
Hi all,
 
We are currently deploying a Cisco Contact Center solution
based on UCCE and CVP (both version 8.5).
It includes a number of Call Studio applications that
require querying business data in an AS/400 system.
 
We configured the VXML Tomcat server with the jt400.jar
library and the following JNDI data source:
 
    <Resource auth="Container"
                               
name="jdbc/as400test"
                               
url="jdbc:as400://<server ip>/ALPHAMB"
                               
driverClassName="com.ibm.as400.access.AS400JDBCDriver"
                               
type="javax.sql.DataSource"
                               
username="<omitted>"
                               
password="<omitted>"
                               
maxActive="4"
                               
maxIdle="2"
                               
maxWait="5000"
                               
removeAbandoned="true"
                               
removeAbandonedTimeout="300"
                               
validationQuery="SELECT 1 FROM SYSIBM.SYSDUMMY1"
                               
validationQueryTimeout="5"
                               
testOnBorrow="true"
                               
testWhileIdle="true"
                               
/>
 
The problem:
Every morning (and after every long period of inactivity)
our first call always times out on the database connection.
The actual timeout we experience is a VXML fetch timeout
(after 20 seconds). Meaning the VXML server is still busy trying to query the
data.
The second calls always goes through successfully (and very
fast).

 

So although we configured the parameters to have a
connection pool available, the underlying system does not seem to maintain it.

 
Anyone with experience on this particular situation?
Any recommendations on how to further debug this?
 
Thx!
Koen

It turned out our config was missing a few important parameters to start the Evictor thread in DBCP.
See http://commons.apache.org/dbcp/configuration.html

timeBetweenEvictionRunsMillis should be a positive value (-1 by default) to make the evictor thread run.
It's the evictor thread that will run the validation query and remove invalid connections from the pool.

K.