06-05-2018 12:27 AM
HI ,
We have an application developed using Call studio 11.6. We see application resulting in below exception:
The error was: A built-in element encountered an exception of type com.audium.server.AudiumException. Connection reset by peer: socket write error The root cause was: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
So to handle this, we have modified application check for this exception in code ie..in start of call, we have added Java Exception type with value as "com.microsoft.sqlserver.jdbc.SQLServerException" and exit state is set to CVP subdialog return .
We even included in vxml events on start
We are able to reproduce the issue but exception is not being handled as defined in application instead playing "TD" from CVP and then call drops.
Is it not the right way of handing this exception or is there anything missing here? How do we handle this?
Also, is there a way we can set application to handle all\any exception instead of specifying a particular exception?
Thank you..
06-05-2018 01:00 AM
Rajani,
I would look at the error logs to confirm exactly which error is been triggered and see if you can catch that specific one.
But by using the catch all error approach - which you have also asked for - it might likely fix your issue.
This is easy to do - and I would recommend configuring it on all Call Studio Apps.
Catch All Errors
Add a dedicated CVP Subdialog Return". Right Click it and select "Error Element -> Yes"
This is your "catch all" element.
Set the return elements values in sub dialog Return as required so you can handle the call gracefully - via your ICM script.
Gerry
06-05-2018 04:33 AM
Rajani,
You can catch your Java exception in an events tab in Start of Call element or in the dB element by specifying the event:
com.audium.server.AudiumException
To catch all java exceptions in the events tab, specify type java exceptions, event list : *. *
To catch all VXML exceptions in the events tab, specify type vxml event, event list : *. *
You can also create an error element as previously mentioned, however the events tab provides more flexibility.
Sent from my Verizon 4G LTE smartphone
06-05-2018 06:37 AM
Yes Janine,
We have set java exception list under events of startofcall as com.audium.server.AudiumException,com.microsoft.sqlserver.jdbc.SQLServerException but this didn't work as per the exit state defined in code.
06-05-2018 06:52 AM
That's odd - sometimes if you have a blank space ANYWHERE within the event list it won't match the exception.
You could try just catching com.audium.server.AudiumException
But if you're still having problems, just use *.* (and again, ensure there are no blank spaces at the beginning or end of the string)
06-05-2018 06:57 AM
Will try having *.* for the list and check.
06-13-2018 12:01 PM
Hi Rajini,
Have you resolved this problem? We do have similar problem after 11.6 upgrade.If so please share the solution.
06-05-2018 06:56 AM
Thank you..will try this and see how it goes.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide