manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Sharepoint
Date Fri, 22 Feb 2013 09:45:12 GMT
Please try checking out, building, and running trunk.  I committed an
explicit CONNECTION_TIMEOUT value of one minute.  Please be aware that
the schema on trunk has changed since 1.1, so just let it use Derby
and don't try to use whatever database you are using for your test.

Thanks,
Karl

On Fri, Feb 22, 2013 at 2:16 AM, Mark Lugert <mlugert@yahoo.com> wrote:
> Tested with 1.6.  Still doesn't work for me.  The solr, Alfresco, and CMIS
> connectors all work fine.
>
> Running 1.1 of manifold.
>
> I'm running using the multiprocessor setup with tomcat 6.
>
> Any ideas how I can further debug this?
>
> thanks,
> mark
>
> From: Mark Lugert <mlugert@yahoo.com>
> To: Karl Wright <daddywri@gmail.com>
> Cc: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
> Sent: Friday, February 22, 2013 1:43 AM
> Subject: Re: Sharepoint
>
> Hi Karl,
>
> Ok, so this is where it's hanging:
>
> public
> ListsWS(String siteUrl, String userName, String password,
> EngineConfiguration configuration, HttpClient httpClient)
> throws java.net.MalformedURLException
> {
> super(configuration);
>
> It never finishes the configuration in the super class.  I don't have the
> code for that, so not sure why.
>
> The server manifold runs on is using Java 1.7.  Could there be an issue with
> Axis and Java 1.7?  Has anyone tried the Sharepoint connector using Java
> 1.7?
>
> thanks,
> Mark
>
> From: Karl Wright <daddywri@gmail.com>
> To: Mark Lugert <mlugert@yahoo.com>
> Cc: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
> Sent: Thursday, February 21, 2013 7:55 PM
> Subject: Re: Sharepoint
>
> This is exactly where I would expect it to be during check.  If it
> hasn't thrown an exception and is just sitting there, there are only
> two real possibilities.  Both involve socket timeouts.  One is the
> connection timeout, the other the socket timeout proper.  Currently we
> don't set the connection timeout, so I bet that is interpreted as
> being "infinite".  The socket timeout we set to 15 minutes - seems
> high  but that seems to be needed for some sharepoint systems out
> there; they are slow.
>
> I'll open a ticket to set the connection timeout to something
> reasonable.  But basically this means your communication with the
> amazon instance is not properly configured; you're either hitting a
> firewall somewhere (Amazon's?) or the instance's IIS is not running on
> port 80.
>
> Karl
>
> On Thu, Feb 21, 2013 at 7:44 PM, Mark Lugert <mlugert@yahoo.com> wrote:
>> Debuggin this, it's hung up on this call:
>>
>> viewconnection.jsp
>> connectionStatus = c.check();
>>
>> This essentially does a:
>>
>> getSession();
>> URL urlServer =
>> new URL( serverUrl );
>> proxy.checkConnection(
>> "/", supportsItemSecurity );
>>
>> There is pretty much no logging in this entire connector.  I'll go in and
>> add some to see which method, and where, it's having issues.
>>
>> Looking at the code I'd guess the proxy.checkConnection.  However, if I
>> use
>> the URL it "should" be using via a browser it works fine.
>>
>> Wondering if Amazon is doing something that is causing issues?  Has anyone
>> tried using a Sharepoint in Amazon before?
>>
>> thanks,
>> mark
>>
>> From: Karl Wright <daddywri@gmail.com>
>> To: Mark Lugert <mlugert@yahoo.com>
>> Cc: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
>> Sent: Thursday, February 21, 2013 6:13 PM
>> Subject: Re: Sharepoint
>>
>> Ok, just confirmed here that SharePoint 2010 selected with the
>> following parameters gives you something back in less than 1 min:
>>
>> Parameters:    serverLocation=
>> serverPort=
>> serverVersion=4.0
>> userName=domain\foo
>> serverProtocol=http
>> serverName=localhost
>> password=********
>> Connection status:    The site at http://localhost did not exist
>>
>> Obviously I didn't try connecting to an Amazon instance with a missing
>> MCPermissions.asmx, but that shouldn't be much different.
>>
>> If the empty response persists, we can assume it's throwing some weird
>> Error and try to catch it in the JSP.  If you are interested in doing
>> that let me know and I'll give you precise instructions.
>>
>> Thanks
>> Karl
>>
>>
>> On Thu, Feb 21, 2013 at 6:02 PM, Mark Lugert <mlugert@yahoo.com> wrote:
>>> I see no exceptions.  Going to install the service tonight or tomorrow
>>> and
>>> retest.
>>>
>>> Never does return which is weird.  I'll keep digging.
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 21, 2013, at 6:00 PM, Karl Wright <daddywri@gmail.com> wrote:
>>>
>>>> For SharePoint 2010 and up, MCPermissions.asmx is required, because
>>>> many of the services that worked previously in SharePoint 2003 and
>>>> 2008 no longer work properly on SharePoint 2010.  As far as I know,
>>>> Amazon does not provide anything other than SharePoint 2010 instances,
>>>> so that is probably going to be an issue for you.
>>>>
>>>> But you *should* get back a connection failure message on the view
>>>> page.  The reason not may be timeout (may take a minute or two), or it
>>>> could be something more serious.  Do you see any exceptions printed in
>>>> either the logs or out to standard out?
>>>>
>>>> Karl
>>>>
>>>> On Thu, Feb 21, 2013 at 5:03 PM, Mark Lugert <mlugert@yahoo.com> wrote:
>>>>> Another note.  I did not install MCPermissions.asmx as I do not need
>>>>> permission information from Sharepoint at this time.  All the docs are
>>>>> basically public.  It's more about what docs are ready for publish.
>>>>>
>>>>> Would this cause the problem I'm seeing below?  The docs make it sound
>>>>> like
>>>>> MCPermissions.asmx is only if you want authority info from the docs.
>>>>>
>>>>> thanks,
>>>>> mark
>>>>>
>>>>>
>>>>> From: Mark Lugert <mlugert@yahoo.com>
>>>>> To: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
>>>>> Sent: Thursday, February 21, 2013 5:00 PM
>>>>> Subject: Sharepoint
>>>>>
>>>>> I'm trying to connect to my sharepoint server, which is on amazon.
>>>>>
>>>>> There are no sites, just a document library.  I can connect via a
>>>>> browser
>>>>> just fine, but when I set up the manifold repos connector and click
>>>>> save
>>>>> I
>>>>> just get a blank screen.  Nothing in the logs and the screen stays
>>>>> blank.
>>>>>
>>>>> It's sharepoint 2010
>>>>> http
>>>>> my amazon ec2-50-16......amzaonaws.com
>>>>> server port: 80
>>>>> Site Path: <blank> since I don't have any sites
>>>>> user name: <host_name>\Administrator  - this is what it shows me
logged
>>>>> in
>>>>> as via the browser
>>>>> Password.
>>>>> No cert.
>>>>>
>>>>> Any idea why there is nothing in the log and why the screen goes blank?
>>>>> I
>>>>> turned on wire level debugging and got nothing.
>>>>>
>>>>> thanks,
>>>>> mark
>>>>>
>>>>>
>>
>>
>
>
>
>

Mime
View raw message