08-25-2014 07:15 AM
Hi guys,
Can someone point me to a right direction regarding DB element exceptions and error from the perspective of
DB not available or link is broken?
How can you setup my script to override that problem? To let's say point to another DB?
Cheers Thanx
V
Solved! Go to Solution.
08-25-2014 07:52 PM
Unfortunately, the Studio Database element has no error handling. If the
DB is down (or any other DB exception occurs) it throws a Java
exception. The app will error back to whoever invoked it (ICM in most
cases).
Really, you should either write your own DB element or 'extend' the
Studio DB element to execute the runtime code within a try/catch. Or
upgrade to Studio 10.5 which lets you catch Java events.
If you don't know how to 'extend' the Studio DB element, I can send you
a precompiled element you can use. What version of Studio/CVP do you have?
08-25-2014 07:52 PM
Unfortunately, the Studio Database element has no error handling. If the
DB is down (or any other DB exception occurs) it throws a Java
exception. The app will error back to whoever invoked it (ICM in most
cases).
Really, you should either write your own DB element or 'extend' the
Studio DB element to execute the runtime code within a try/catch. Or
upgrade to Studio 10.5 which lets you catch Java events.
If you don't know how to 'extend' the Studio DB element, I can send you
a precompiled element you can use. What version of Studio/CVP do you have?
08-26-2014 08:41 AM
08-26-2014 08:48 AM
One weird thing is (or not),
That whenever I make a change in studio and deploy it to vxml server, communication between vxml and MySQL server gets broken, and after 2-3 calls it gets back
And this is what I put in context:
Resource name="jdbc/cisco"
auth="Container"
type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="user"
password="pass"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://myserverhostname:3306/cisco?autoReconnect=true"/>
Any help on that one!?
Thanx!
V
08-26-2014 09:08 AM
Hi,
I don't it's that your changing the app.
I think that whenever VXML Server (Tomcat) finds a stale socket
connection, it throws an exception and frees the socket. Which will then
be fine for the next caller. If this coincides with your Studio app
change, it's probably just coincidence.
You can try adding a few extra attributes to the context.xml file (look
them up under Apache Tomcat JNDI)
I "think" it avoids the exception on a stale socket.
<Resource
name="jdbc/jndi_name"
type="javax.sql.DataSource"
password="pwd"
username="user"
driverClassName=". . ."
url="jdbc:mysql://IP_address:port/db_name"
minIdle="5" **
maxIdle="10" **
maxActive="25" **
initialSize="1" **
maxWait="10000" **
removeAbandoned="true" **
removeAbandonedTimeout="10"**
logAbandoned="true" **
minEvictableIdleTimeMillis="10000" **
timeBetweenEvictionRunsMillis="5000"/>*
08-28-2014 01:11 PM
Thanx Janine!
That's it!
V
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: