AXL Error Code 0

Version 1
    This document was generated from CDN thread

    Created by: HOLGER SIMON on 15-02-2013 09:05:01 AM
    Hello, i had lan axl error (see below), seams to be an internal error. The AXL interface did not work anymore. A reboot did the fix of that problem, my Question is: How can i prevent from that in the future ? Kind regards, Holger Simon   SOAP-ENV:ClientMax]http://schemas.xmlsoap.org/soap/envelope/">SOAP-ENV:ClientMax connections for dbaxlweb at jdbcurl exceed. Connection not allowed0Max]http://www.cisco.com/AXL/API/7.1">0Max connections for dbaxlweb at jdbcurl exceed. Connection not allowedexecuteSQLQuery

    Subject: RE: AXL Error Code 0
    Replied by: David Staudt on 15-02-2013 10:15:11 AM
    Can you provide some more details?

    - UCM version
    - AXL request/response
    - An idea of system performance at the time: lots of rapid/large AXL requests? 
    For in-depth analysis of the issue, strongly suggest you open a support case with CDN Developer Support: http://developer.cisco.com/web/memberservices/support

    Subject: RE: AXL Error Code 0
    Replied by: HOLGER SIMON on 13-03-2013 04:52:37 AM
    Hello David,
    the CUCM Version is: 9.0.1.11017-1.
    Meanwhile we have identified a suboptimal executesql, which takes 1 minute for execution, we send that request automated > 1000 times.
    This error from the cucm seemed to be: that there are nor more free jdbc connections for the axl interface, because all of them are in used by the slow sql.
    We could make a sql optimization, the execution takes now below 1 second, the result of that is currently pending.
    Is that assumption right?
    How is the jdbc pool limit for this cucm version ?
    Kind regards,
    Holger

    Subject: RE: AXL Error Code 0, poor AXL Perfomance
    Replied by: HOLGER SIMON on 20-03-2013 05:08:24 AM
    Hello,
    now I have that error again with the attached AXL update user request.
    If I send more than 4 Request/second over one minute duration, than I wil get an error for each following AXL request.
    From this situation on I cannot use the AXL interface anymore, until I restart either the "A Cisco DB" Service or the CUCM.
    This violates the performance values, given in the XML Developers Guide(Table 2-15 AXL Query Limits) , I send only approximately 300 Requests/minute, while the Developers Guide stated about 1500 Requests per minute.   The AXL error we get now is:
     '<axlError>
      <axlcode>0</axlcode>
      <axlmessage>Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed</axlmessage>
      <request>executeSQLQuery</request>
    </axlError>'
    The CUCM Version is: 9.0.1.11017-1. How can I handle this error? What ist the limit for that update User Request ? Kind regards, Holger

    Subject: RE: AXL Error Code 0, poor AXL Perfomance
    Replied by: Gangadhar Tunugunta on 26-09-2013 02:23:16 AM
    Hi,

    We are receiving the same error message from CUCM (System version: 9.1.1.20000-5).
    Before this everything was working normal with no errors.

    Did you find any solution for this?

    Below are the trace logs generated in CUCM. 

      12013-09-26 10:13:10,148 INFO  [http-bio-443-exec-8752] servletRouters.AXLFilter - Received request 1380176878870 from XMLServiceUser at IP 10.102.8.62
      22013-09-26 10:13:10,149 DEBUG [http-bio-443-exec-8752] servletRouters.RequestWrapper - : changeNamespace - nameSpac_9_0
      32013-09-26 10:13:10,150 DEBUG [http-bio-443-exec-8752] servletRouters.RequestWrapper - : setNameSpaceFlag - New nameSpace:9.0
      42013-09-26 10:13:10,150 INFO  [http-bio-443-exec-8752] servletRouters.AXLFilter - AXL REQUEST :
      5
      6 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body> <axl:executeSQLQuery xmlns:axl="http://www.cisco.com/AXL/API/9.0"  xsi:schemaLocation="http://www.cisco.com/AXL/9.0 https://www.cisco.com/schema/axlsoap.xsd" sequence="1234"> <sql>SELECT DEVICE.PKID, DEVICE.NAME  FROM DEVICE WHERE DEVICE.NAME LIKE 'SEP%'  </sql></axl:executeSQLQuery></SOAP-ENV:Body> </SOAP-ENV:Envelope>
      7
      82013-09-26 10:13:10,154 DEBUG [http-bio-443-exec-8752] servletRouters.AXLFilter - sequence value: 1234
      92013-09-26 10:13:10,154 DEBUG [http-bio-443-exec-8752] servletRouters.AXLFilter - Request is not a write request
     102013-09-26 10:13:10,154 DEBUG [http-bio-443-exec-8752] servletRouters.AXLFilter - Successfully set the value of counter: 4 value: 0
     112013-09-26 10:13:10,154 DEBUG [http-bio-443-exec-8752] servletRouters.AXLFilter - --------------- Version matched ----------------
     122013-09-26 10:13:10,154 INFO  [http-bio-443-exec-8752] servletRouters.AXLAlpha - SOAPAction : "CUCM:DB ver=9.0"
     132013-09-26 10:13:10,173 DEBUG [http-bio-443-exec-8752] servletRouters.AXLAlpha - addToCache("XMLServiceUser")
     142013-09-26 10:13:10,174 INFO  [http-bio-443-exec-8752] servletRouters.AXLAlpha - Going to axis--->
     152013-09-26 10:13:10,200 DEBUG [http-bio-443-exec-8752] axlapiservice.AXLAPIServiceSkeleton - In ExecuteSQLQueryResponseDocument
     162013-09-26 10:13:10,200 DEBUG [http-bio-443-exec-8752] axlapiservice.ExecuteSqlHandler - SELECT DEVICE.PKID, DEVICE.NAME  FROM DEVICE WHERE DEVICE.NAME LIKE 'SEP%' 
     172013-09-26 10:13:10,204 WARN  [http-bio-443-exec-8752] axlapiservice.ExecuteSqlHandler - java.sql.SQLException: Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed
     182013-09-26 10:13:10,205 ERROR [http-bio-443-exec-8752] axlapiservice.AXLAPIServiceSkeleton - SQL EXCEPTION has occurred, will be sending you the exact error Info
     192013-09-26 10:13:10,205 DEBUG [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - In AXL CAll Flow
     202013-09-26 10:13:10,206 DEBUG [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - In AXL CAll Flow errorCodeStringMax connections for dbaxlweb at jdbcurl exceed. Connection not allowed
     212013-09-26 10:13:10,207 INFO  [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - sqlString is : select name from typedberrors where enum=Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed
     222013-09-26 10:13:10,207 INFO  [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - errorCodeString is : Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed
     232013-09-26 10:13:10,212 ERROR [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - com.cisco.www.axlapiservice.AXLAPIServiceSkeleton@1542da0
     24java.sql.SQLException: Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed
     25        at com.cisco.ccm.dbl.ConnectionManager$ConnectionManagerEntry.getConnection(ConnectionManager.java:94)
     26        at com.cisco.ccm.dbl.ConnectionManager$ConnectionManagerEntry.getConnection(ConnectionManager.java:88)
     27        at com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry.getConnection(ConnectionPool.java:306)
     28        at com.cisco.ccm.dbl.ConnectionPool.getConnection(ConnectionPool.java:86)
     29        at com.cisco.ccm.dbl.Connector.getConn(Connector.java:745)
     30        at com.cisco.ccm.dbl.Connector.connect(Connector.java:697)
     31        at com.cisco.ccm.dbl.Connector.connect(Connector.java:639)
     32        at com.cisco.ccm.dbl.Connector.createStatement(Connector.java:865)
     33        at com.cisco.ccm.dbl.Connector.createStatement(Connector.java:852)
     34        at com.cisco.ccm.dbl.Connector.executeQuery(Connector.java:1029)
     35        at com.cisco.www.axlapiservice.AXLCallFlow.getSOAPError(AXLCallFlow.java:137)
     36        at com.cisco.www.axlapiservice.AXLAPIServiceSkeleton.executeSQLQuery(AXLAPIServiceSkeleton.java:19167)
     37        at com.cisco.www.axlapiservice.AXLAPIServiceMessageReceiverInOut.invokeBusinessLogic(AXLAPIServiceMessageReceiverInOut.java:7017)
     38        at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
     39        at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
     40        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
     41        at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
     42        at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)
     43        at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
     44        at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
     45        at sun.reflect.GeneratedMethodAccessor28156.invoke(Unknown Source)
     46        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     47        at java.lang.reflect.Method.invoke(Method.java:597)
     48        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:274)
     49        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:271)
     50        at java.security.AccessController.doPrivileged(Native Method)
     51        at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     52        at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:306)
     53        at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:166)
     54        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:299)
     55        at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:57)
     56        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:193)
     57        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
     58        at java.security.AccessController.doPrivileged(Native Method)
     59        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
     60        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
     61        at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471)
     62        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
     63        at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:67)
     64        at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:102)
     65        at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:89)
     66        at java.security.AccessController.doPrivileged(Native Method)
     67        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:321)
     68        at com.cisco.www.servletRouters.AXLAlpha.doPost(Unknown Source)
     69        at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
     70        at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
     71        at sun.reflect.GeneratedMethodAccessor28156.invoke(Unknown Source)
     72        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     73        at java.lang.reflect.Method.invoke(Method.java:597)
     74        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:274)
     75        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:271)
     76        at java.security.AccessController.doPrivileged(Native Method)
     77        at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     78        at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:306)
     79        at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:166)
     80        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:299)
     81        at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:57)
     82        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:193)
     83        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
     84        at java.security.AccessController.doPrivileged(Native Method)
     85        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
     86        at com.cisco.www.servletRouters.AXLFilter.doFilter(Unknown Source)
     87        at sun.reflect.GeneratedMethodAccessor28171.invoke(Unknown Source)
     88        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     89        at java.lang.reflect.Method.invoke(Method.java:597)
     90        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:274)
     91        at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:271)
     92        at java.security.AccessController.doPrivileged(Native Method)
     93        at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     94        at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:306)
     95        at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:246)
     96        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
     97        at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:57)
     98        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:193)
     99        at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
    100        at java.security.AccessController.doPrivileged(Native Method)
    101        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    102        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
    103        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
    104        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
    105        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
    106        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
    107        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
    108        at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:309)
    109        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    110        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
    111        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
    112        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
    113        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:307)
    114        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    115        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    116        at java.lang.Thread.run(Thread.java:662)
    1172013-09-26 10:13:10,212 INFO  [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - Exception occured while  querying the database : java.sql.SQLException: Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed
    1182013-09-26 10:13:10,213 DEBUG [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - Setting soap fault
    1192013-09-26 10:13:10,213 DEBUG [http-bio-443-exec-8752] axlapiservice.AXLCallFlow - Setting soap fault2
    1202013-09-26 10:13:10,214 INFO  [http-bio-443-exec-8752] servletRouters.AXLAlpha - Request processed by AXIS
    1212013-09-26 10:13:10,214 DEBUG [http-bio-443-exec-8752] servletRouters.AXLFilter - ---------------AXLFiler > responseString ----------------  : <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed</faultstring><detail><axlError><axlcode>0</axlcode><axlmessage>Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed</axlmessage><request>executeSQLQuery</request></axlError></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    1222013-09-26 10:13:10,214 INFO  [http-bio-443-exec-8752] servletRouters.AXLFilter - <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed</faultstring><detail><axlError><axlcode>0</axlcode><axlmessage>Max connections for dbaxlweb at jdbcurl exceed. Connection not allowed</axlmessage><request>executeSQLQuery</request></axlError></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    1232013-09-26 10:13:10,215 INFO  [http-bio-443-exec-8752] servletRouters.AXLFilter - Request 1380176878870 was process in 67ms


    Best regards,
    Gangadhar.

    Subject: RE: AXL Error Code 0, poor AXL Perfomance
    Replied by: David Staudt on 03-10-2013 03:52:18 PM
    If you are not using/re-using the AXL Tomcat session cookies when doing multiple requests, pls take a look at this thread:

    http://developer.cisco.com/web/axl-developer/forums/-/message_boards/message/16215816