AXL Error when doing a "list" SOAP request

Version 1
    This document was generated from CDN thread

    Created by: roesch yann on 16-07-2009 11:27:58 AM
    Hello everybody,
    I'm new in this forum and I wish that this question wasn't answer in a former post (excuse me if it is the case).
     
    So I explain my problem:
     
    When I try to do a "list" AXL request to my CCM like a "listPhoneTemplateByName" for example with the wildcard caracter "%" for searchstring, I have an axl error 5000 response.
    A 5000 axl reponse code is an unknown error or a problem in the request syntax but I'm sure that my resquest is in correct form, so it is an unknown error.
    So, to know more, I listed the AXL logs via RTMT and I saw the following error log:
     
    com.cisco.ccm.axl.ListHandler@1551d8fjava.util.MissingResourceException:
    Can't find resource for bundle java.util.PropertyResourceBundle, key TypeModel. 
    at java.util.ResourceBundle.getObject(ResourceBundle.java:325) 
    at java.util.ResourceBundle.getString(ResourceBundle.java:285) 
    at com.cisco.ccm.dbl.TypeTables.Utils.getName(Utils.java:127) 
    at com.cisco.ccm.axl.ListHandler.listPhoneTemplateByName(ListHandler.java:767) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... etc
     
    So does anyone knows what is this problem and how I can solve it ??
     
    Thanks,
    Philippe

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: Anitha V on 16-07-2009 11:41:26 AM
    Hi Philippe,
     
    5000 error is a generic AXL error.
     
    Could you please provide the corresponding AXL logs for this issue also the callManager version which you are using?
     
    Thanks and Regards,
    Anitha

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: roesch yann on 16-07-2009 11:58:58 AM

    Thanks for your answer, so the CCM version is 5.1.3.2000-3.
     
    I paste here the complete AXL log found in RTMT for this error.
     
    Date: 2009-07-09 10:50:35,305
    Trace Level: ERROR
    Thread: http-8443-Processor19
    Class Name:  axl.Handler
    Message: 
    com.cisco.ccm.axl.ListHandler@1ae1811java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key TypeProduct. at java.util.ResourceBundle.getObject(ResourceBundle.java:325) at java.util.ResourceBundle.getString(ResourceBundle.java:285) at com.cisco.ccm.dbl.TypeTables.Utils.getName(Utils.java:127) at com.cisco.ccm.axl.ListHandler.listDeviceByNameAndClass(ListHandler.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.cisco.ccm.axl.Handler.execute(Handler.java:407) at com.cisco.ccm.axl.AxlListener.onMessage(AxlListener.java:312) at com.cisco.ccm.axl.AxlListener.doPost(AxlListener.java:218) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at sun.reflect.GeneratedMethodAccessor338.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:239) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:157) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:140) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:136) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:417) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534)

    Hope this will help you.
    Thanks,
    Philippe

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: David Staudt on 16-07-2009 06:15:58 PM
    It seems that the trace is set for ERROR level only.  Can you set this to DEBUG level:
     
    Serviceability pages/Trace/Trace/Configuration/Database and Admin Services/Cisco AXL Web Service (Active)
     
    Check the Debug Trace Level

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: roesch yann on 20-07-2009 08:13:26 AM
    I set the "Debug Trace level" in the Cisco AXL Web Service. There is effectively much more logs but nothing that can help me to knows what is the problem.
    Just a question, could it be that the MaxAXLWritesPerMinute service parameter create this problem?
     

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: Anitha V on 21-07-2009 05:58:47 AM
    Hi Roesch,
     
    This issue is due to the defect CSCsl09338.
     
    This problem is due to a phone type which was added after UCM was installed.
     
    Hope this helps.

    Thanks and Regards,
    Anitha

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: roesch yann on 22-07-2009 09:14:16 AM
    Hi Anitha,
     
    Thanks for your answer, I think this is the correct defect because I recently plug a new device package, with a new phone type definition.
    This bug is only fixed in UCM 6.1 or 7.0. I have a 5.1.3.2000-3. Does it meen that I should upgrade to 6.1 or 7.0 to fix this problem? I planed to upgrade to 5.1.3.7000-5, could this fix this bug?
     
    Thanks and regards,
     
    Philippe

    Subject: RE: AXL Error when doing a "list" SOAP request
    Replied by: Anitha V on 23-07-2009 10:00:22 AM
    Hi Philippe,
     
    Since the bug is fixed in  UCM 6.1 or 7.0, upgrading to  5.1.3.7000-5 won't solve the issue.
     
    You could raise a TAC SR with cisco, to check whether the fix for this defect could be made available in 5.1.3.7000-5. If this is possible then you can get the fix in 5.1.3.7000-5.
     
    Thanks and Regards,
    Anitha