[ 
https://issues.apache.org/jira/browse/CONNECTORS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794444#comment-13794444
 ] 

Karl Wright commented on CONNECTORS-785:
----------------------------------------

The following page:
http://wiki.apache.org/ws/FrontPage/Axis/DealingWithCommonExceptions

...tells us that we need to do this:

{code}
log4j.logger.org.apache.axis.ConfigurationException = INFO
{code}

... or the equivalent in code.  The reason is stated as follows:

"This is logged because this code in AxisEngine (line 308 in Axis 1.x):

    public SOAPService getService(String name) throws AxisFault
    {
        try {
            return config.getService(new QName(null, name));
        } catch (ConfigurationException e) {
            try {
                return config.getServiceByNamespaceURI(name);
            } catch (ConfigurationException e1) {
                throw new AxisFault(e);
            }
        }
    }

depends on an exception being thrown on the first attempt (line 311) to then 
try a different method of finding the service (which succeeds if you see no log 
of the AxisFault on line 316). The log entry is created because a 
ConfigurationException logs itself (at DEBUG level) on creation (questionable 
practice, imho). "

So I will experiment with forcing off the configuration exception logging, and 
see if that helps.


> SharePoint connector: Figure out why Axis tries to read the namespace URL and 
> get it to stop doing that
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-785
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-785
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: SharePoint connector
>    Affects Versions: ManifoldCF 1.3
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Minor
>             Fix For: ManifoldCF 1.4
>
>
> This generates noise in the logs which confuses users, e.g.:
> {code}
> org.apache.axis.ConfigurationException: No service named 
> http://microsoft.com/sharepoint/webpartpages/GetListItems is available
>         at 
> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper$ResourceProvider.getService(SPSProxyHelper.java:2974)
>         at org.apache.axis.AxisEngine.getService(AxisEngine.java:311)
>         at 
> org.apache.axis.MessageContext.setTargetService(MessageContext.java:756)
>         at 
> org.apache.axis.transport.http.HTTPTransport.setupMessageContextImpl(HTTPTransport.java:89)
>         at 
> org.apache.axis.client.Transport.setupMessageContext(Transport.java:46)
>         at org.apache.axis.client.Call.invoke(Call.java:2738)
>         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.microsoft.sharepoint.webpartpages.PermissionsSoapStub.getListItems(PermissionsSoapStub.java:234)
>         at 
> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:606)
>         at 
> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1285)
>         at 
> org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to