Thanks a lot.
Le 5 sept. 2013 17:08, "Karl Wright" <[email protected]> a écrit :

> Hi Yann,
>
> I've opened CONNECTORS-770 to track this issue.
>
> It appears that in Java1.7, the Java class loader knows the difference
> between an interface and a class, and enforces that.  So when we went to
> Java 1.7 in the last release, some of our stub classes, which were coded as
> interfaces for convenience, no longer load.
>
> But luckily this is trivial to fix.  I will be committing fixes to trunk
> for your particular problem shortly.
>
> Karl
>
>
>
> On Thu, Sep 5, 2013 at 10:59 AM, Yann Barraud <[email protected]>wrote:
>
>> Karl,
>>
>> This is 4.5.2.
>>
>> Hope it will work though.
>>
>> Yann
>> Le 5 sept. 2013 16:55, "Karl Wright" <[email protected]> a écrit :
>>
>> Hi Yann,
>>>
>>> The problem is that the code is built against a stub, and the stub's
>>> class structure does not agree with the actual class structure in the
>>> FileNet API version you are using.  The actual error you are getting is:
>>>
>>> "Error occurred in server thread; nested exception is:
>>>                 java.lang.IncompatibleClassChangeError: Found class
>>> com.filenet.api.constants.AccessType, but interface was expected"
>>>
>>>
>>> This could be because I messed up creating the stubs, or it could be
>>> that you are using a later version of FileNet API than I was working with.
>>> What FileNet API version do you have?
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>>
>>> On Thu, Sep 5, 2013 at 10:49 AM, Yann Barraud <[email protected]>wrote:
>>>
>>>> Hi,
>>>>
>>>> W're getting a working connection. It's just rejecting the docs
>>>> apparently.
>>>>
>>>> ERROR 2013-09-05 16:36:22,909 (Worker thread '10') - Exception tossed:
>>>> Repeated service interruptions - failure getting document version
>>>> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated
>>>> service interruptions - failure getting document version
>>>>                 at
>>>> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:343)
>>>> WARN 2013-09-05 16:36:23,119 (Worker thread '17') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:23,370 (Worker thread '13') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:23,460 (Worker thread '11') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:25,212 (Worker thread '12') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:25,463 (Worker thread '18') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:25,463 (Worker thread '15') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:25,513 (Worker thread '16') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:25,573 (Worker thread '14') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>> WARN 2013-09-05 16:36:26,704 (Worker thread '1') - Pre-ingest service
>>>> interruption reported for job 1378388244044 connection 'FN_45_INT':
>>>> Transient error connecting to filenet service: Error occurred in server
>>>> thread; nested exception is:
>>>>                 java.lang.IncompatibleClassChangeError: Found class
>>>> com.filenet.api.constants.AccessType, but interface was expected
>>>>
>>>>
>>>>
>>>>
>>>> Cordialement,
>>>> Yann Barraud
>>>>
>>>>
>>>> 2013/9/5 Karl Wright <[email protected]>
>>>>
>>>>> Hi Yann,
>>>>>
>>>>> First, you are clearly doing a crawl.  But did you get "Connection
>>>>> working" when you view your FileNet connection?
>>>>>
>>>>> If you did, please have a look at the ManifoldCF log output.  There
>>>>> should be exceptions in there that would help us figure out what the issue
>>>>> may be.
>>>>>
>>>>> Thanks,
>>>>> Karl
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 5, 2013 at 10:08 AM, Yann Barraud 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> Hi Karl,
>>>>>>
>>>>>> It just works, thanks.
>>>>>>
>>>>>> Now getting "failure getting document version". Any tip ? We did not
>>>>>> choose the Version metadata. Might be somewhere in the confirguration ?
>>>>>>
>>>>>>
>>>>>> Cordialement,
>>>>>> Yann Barraud
>>>>>>
>>>>>>
>>>>>> 2013/9/5 Karl Wright <[email protected]>
>>>>>>
>>>>>>> Hi Yann,
>>>>>>>
>>>>>>> First, the FileNet connector is one that requires a secondary
>>>>>>> connector-specific process to run.  Please read the
>>>>>>> "how-to-build-and-deploy" page to familiarize yourself with the process.
>>>>>>> The FileNet API jars do NOT get copied to connector-lib or
>>>>>>> connector-lib-proprietary; they instead get copied into the
>>>>>>> filenet-server-process/lib-proprietary area.  Read the README.TXT file 
>>>>>>> in
>>>>>>> that area for details.  You will need to copy ALL the jars that the 
>>>>>>> filenet
>>>>>>> API requires into that place before the filenet server process can be
>>>>>>> started.
>>>>>>>
>>>>>>> Karl
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 5, 2013 at 6:04 AM, Yann Barraud <[email protected]
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I just deployed binary distribution of ManifoldCF on a local VM &
>>>>>>>> trying to have it running.
>>>>>>>>
>>>>>>>> I'm facing 3 issues right now :
>>>>>>>> 1. "java.lang.NoClassDefFoundError: org/apache/log4j/Priority"
>>>>>>>> 2. "java.lang.NoClassDefFoundError: Could not initialize class
>>>>>>>> com.filenet.api.util.ConfigurationParameters"
>>>>>>>> 3. "java.util.MissingResourceException: Can't find bundle for base
>>>>>>>> name org.apache.manifoldcf.ui.i18n.common, locale fr" (which is a
>>>>>>>> minor warning I guess)
>>>>>>>>
>>>>>>>> Which are the jars I should deploy & where ? I have Jace.jar placed
>>>>>>>> in
>>>>>>>> - connector-lib-proprietary
>>>>>>>> - filenet-server-process
>>>>>>>>
>>>>>>>> What do I miss ?
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Yann Barraud
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>

Reply via email to