Observing significant rise in occurrence of axis ConfigurationException when calling AdwordsUser.getService

[cefc]

Hello,

I'm using the (old) Java client library and over the past few weeks have noticed that on first use of a service (also seen in AdgroupAdService, AdgroupCriterionService, CampaignService) an wrapped ConfigurationException: No Named Service is being thrown. 

Is this merely happening because of class loading that's invoked by the first getService() call for a particular service triggering an exception which in turn gets caught somewhere in the client library and then instantiates the relevant constructors?

Christian


2013-02-27 09:12:25 DEBUG ProjectResourceBundle:handleGetObject 72 - org.apache.axis.i18n.resource::handleGetObject(transport00)
2013-02-27 09:12:25 DEBUG Call:setTransport 2119 - Transport is org.apache.axis.transport.http.HTTPTransport@1029f93b
2013-02-27 09:12:25 DEBUG Call:invoke 2351 - Enter: Call::invoke(ns, meth, args)
2013-02-27 09:12:25 DEBUG Call:getParamList 2043 - operation=name:        get
returnQName: {https://adwords.google.com/api/adwords/info/v201209}rval
returnType:  {https://adwords.google.com/api/adwords/info/v201209}ApiUsageInfo
returnClass: class com.google.api.adwords.v201209.info.ApiUsageInfo
elementQName:null
soapAction:  null
style:       wrapped
use:         literal
numInParams: 1
method:null
 ParameterDesc[0]:
  name:       {https://adwords.google.com/api/adwords/info/v201209}selector
  typeEntry:  null
  mode:       IN
  position:   0
  isReturn:   false
  typeQName:  {https://adwords.google.com/api/adwords/info/v201209}InfoSelector
  javaType:   class com.google.api.adwords.v201209.info.InfoSelector
  inHeader:   false
  outHeader:  false

 FaultDesc[0]:
  name: null
  qname: {https://adwords.google.com/api/adwords/info/v201209}ApiExceptionFault
  type: {https://adwords.google.com/api/adwords/cm/v201209}ApiException
  Class: com.google.api.adwords.v201209.cm.ApiException

[axis out lines removed for brevity]
2013-02-27 09:12:25 DEBUG ConfigurationException:logException 110 - Exception:
org.apache.axis.ConfigurationException: No service named InfoServiceInterfacePort is available
org.apache.axis.ConfigurationException: No service named InfoServiceInterfacePort is available
    at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:233)
    at org.apache.axis.AxisEngine.getService(AxisEngine.java:311)
    at org.apache.axis.MessageContext.setTargetService(MessageContext.java:756)
    at org.apache.axis.client.Call.invoke(Call.java:2690)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at com.google.api.adwords.v201209.info.InfoServiceSoapBindingStub.get(InfoServiceSoapBindingStub.java:458)

[Anash P. Oommen (AdWords API Team)]

Hi,

Could you please open a new issue on the library's issue tracker? The library maintainer will follow up directly with you over the issue tracker.

Cheers,

Anash P. Oommen,
AdWords API Advisor.

[Takeshi Hagikura]

Hello cefc,

Also, can you please write the library version you are using?

Thanks,

- Takeshi, AdWords API Team

[cefc]

Anash,

 

Thanks for the tip. I'll raise an issue on the library tracker.

 

 

Takeshi,

 

We were using v201206 from the (old) Java client library adwords-api-8.7.0.jar.  I've also seen similar events in the testing of our migrating to v201209 (adwords-api-8.10.1.jar).