CVPv11 DB Element Fails For Long Digits

I have created a new test app ‘FaisalTest’. In it the caller enters a dnis and the DB dip is made using the entered digits.. if a 6 digit number like 444444 is entered everything succeeds.

But if I enter a longer number string >=8 digits, the app ***** itself on the lookup, here is the output for dnis 111111111111 failing on the DB element:

xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:28.638,Subdialog Start_01,enter,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:29.638,Subdialog Start_01,exit,done
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:29.638,Digits_01,enter,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:29.638,Digits_01,interaction,audio_group,initial_audio_group
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:47.959,Digits_01,interaction,utterance,111111111111
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:47.959,Digits_01,interaction,inputmode,dtmf
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:47.959,Digits_01,interaction,interpretation,111111111111
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:47.959,Digits_01,interaction,confidence,1
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,value,111111111111
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,confidence,1
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,value_confidence,1
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,nbestConfidence1,1
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,nbestUtterance1,111111111111
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,nbestInputmode1,dtmf
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,nbestInterpretation1,111111111111
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,data,nbestLength,1
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Digits_01,exit,done
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Database_01,enter,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,Database_01,exit,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,,element,error,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,ERROR ELEMENT,enter,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,ERROR ELEMENT,exit,
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,,end,how,app_session_complete
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,,end,result,normal
xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029,,end,duration,19

The error log shows the following, which looks like a type mismatch between the number 111111111111 and string ‘111111111111’:

xxx.xxx.xxxx.xx1470925708638.66.FaisalTest,08/11/2016 15:28:48.029, The error was: A built-in element encountered an exception of type java.lang.NumberFormatException. The root cause was: java.lang.NumberFormatException: For input string: "111111111111"
com.audium.server.AudiumException: A built-in element encountered an exception of type java.lang.NumberFormatException.
       at com.audium.server.voiceElement.ActionElementBase.service(ActionElementBase.java:416)
       at com.audium.server.controller.Controller.goToAction(Controller.java:3981)
       at com.audium.server.controller.Controller.goToElement(Controller.java:3617)
       at com.audium.server.controller.Controller.continueCall(Controller.java:3312)
       at com.audium.server.controller.Controller.doPost(Controller.java:898)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
       at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
       at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
       at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
       at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
       at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.NumberFormatException: For input string: "111111111111"
       at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
       at java.lang.Integer.parseInt(Integer.java:495)
       at java.lang.Integer.valueOf(Integer.java:582)

I’ve tried a lot of things to force both the CED and variables to numbers and/or string, eg, by using Digits_01.value in the SQL, converting it to a string element variable or session variable first , but the error above persists... any ideas what I need to do differently - I was not having this problem in CVP 9..? Attached is a screenshot of the app also.. thanks in advance..

Chances are that you're hitting defect CSCuy80951.  It was fixed in CVP11.0(1)_ES15 so raise a case and ask the TAC for that or a more recent roll-up.

Paul

Thanks Paul - the symptoms appear to be similar although not exactly the same the error text is identical though so this looks promising as a fix! I'll post the outcome of the ES once applied. Thanks again!

Defects are often worded based on the specific conditions which first exposed them so I think this one has wider impact than described. When I investigated the problem and tried to workaround it, it was something that happened wherever variable substitution was being used with numeric data from digit collection as this was being accessed as a number rather than a numeric digit string, hence the overflow.  There's a simple element here you can try that moves the data to another variable first (CopyElementData.java  src - Box), and you'd then use that instead for substitution.

Thanks Paul - thanks for the element also but the link to it fails.. please can you re post it?

we have a number of complex scripts imported from v9 so the ES is the way to go for our scenario, but your element would be a handy workaround if the ES is going to take time for us to apply..

Link seems to be open for public access but source is attached if you need as last resort.

thanks!

ES15 installed and did the trick - thanks again Paul