Re: [VOTE] Release ManifoldCF 2.26, RC0

[Cihad Guzel]

Hi,

+1 from me

Regards,
Cihad Guzel

11 Eki 2023 Çar, saat 15:08 tarihinde Karl Wright  şunu
yazdı:

> Please vote on whether to release Apache ManifoldCF 2.26, RC0.
> This release is the first release that requires at least Java 11, and it
> also includes a new CSV connector along with support for Solr 9.  The
> release artifact can be found at:
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26 ,
> and there is a release tag also at
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.26-RC0 .
>
> Karl
>

Re: [VOTE] Release ManifoldCF 2.25, RC0

[Cihad Guzel]

+1

30 May 2023 Sal, saat 00:08 tarihinde Karl Wright  şunu
yazdı:

> Please vote on whether to release ManifoldCF 2.25, RC0.
>
> This release contains one new feature: the ability to disable hopcount
> tracking entirely, for better performance of the web connector.  The
> attempt to update the Solr connector to release 9.x of Solr did NOT make it
> in because that version of SolrJ depends on a broken version of zookeeper,
> our thread coordination library.
>
> A release artifact can be found here:
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.25
>
> A release tag can also be found at
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.25-RC0 .
>
> Karl
>
-- 
Cihad Güzel

Re: [VOTE] Release Apache ManifoldCF 2.24, RC0

[Cihad Guzel]

Hi,

+1

30 Kas 2022 Çar, saat 15:27 tarihinde Karl Wright  şunu
yazdı:

> Please vote on whether to release Apache ManifoldCF 2.24, RC0.  The release
> artifact can be found at:
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.24 .
> There is also a release tag at
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.24-RC0 .
>
> This release contains a number of fixes for issues found externally, some
> of them high priority.  We have therefore chosen to accelerate the release
> schedule, since it was originally scheduled for the end of December.  You
> can review CHANGES.txt for a partial list of the changes.
>
> Thanks,
> Karl
>
-- 
Cihad Güzel

Re: Tika Service Rmeta Connector Error

[Cihad Guzel]

Hi,

The problem goes away when I increase the socket timeout from the mfc tika
connector edit page. I think "document ingest (Solr)" should not be OK when
there is such a problem.

Regards,
Cihad Güzel


Cihad Guzel , 20 Eki 2022 Per, 02:28 tarihinde şunu
yazdı:

>  Hi Julien,
>
> I ran the tika 2x service using the official tika available on docker hub.
> I am using MFC version 2.3. I activated the tika-service-rmeta connector
> for MFC. I created a job on mfc for a folder with 5 files in it. But OCR
> was not performed on some of the files. When I look at Solr, the content of
> some files seems empty. I also got the error messages found in the
> attachment.
>
> In the second test I made, this time I created 5 separate jobs to include
> each of the 5 files one by one. When I ran these jobs, I did not encounter
> any problems.
>
> When I send these 5 files directly to the tika-service using curl it also
> works correctly.
>
> When I examine the Simple History Report, I see error messages for some
> files as in the attached picture.
>
> Could Tika connector have a bug that will cause an error while sending
> multiple files to tika? Could it have something to do with this issue?
> https://issues.apache.org/jira/browse/CONNECTORS-1733
> [image: Screen Shot 2022-10-20 at 02.08.11.png]
> Regards,
> Cihad Güzel
>

[jira] [Updated] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1699:

Description: 
Tika has released 2.x. . We can support the new version instead of 1.x  . There 
is a migration document here: 
[https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]

Changes can be found from here: 
[https://tika.apache.org/2.4.0/|https://tika.apache.org/2.3.0/]

  was:
Tika has a new version as 2.x . We can support the new version instead of 1.x  
. There is a migration document here: 
[https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]

Tika has released 2.3.0. Changes can be found from here: 
https://tika.apache.org/2.3.0/


> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.21
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 2.x. . We can support the new version instead of 1.x  . 
> There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Changes can be found from here: 
> [https://tika.apache.org/2.4.0/|https://tika.apache.org/2.3.0/]



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Comment Edited] (CONNECTORS-1667) New Tika Service Connector

[Cihad Guzel (Jira)]

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

Cihad Guzel edited comment on CONNECTORS-1667 at 6/3/22 9:44 PM:
-

Hi [~julienFL] 

Does this service support Tika2x?


was (Author: cguzel):
Hi Jullien. 

Does this service support Tika2x?

> New Tika Service Connector
> --
>
> Key: CONNECTORS-1667
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1667
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: Tika service connector
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Fix For: ManifoldCF 2.20
>
>
> The current Tika Service Connector exploits the '/unpack/all' endpoint of a 
> Tika Server. This endpoint is not optimal to only extract document's metadata 
> and content.  We should develop a new connector based on the 'rmeta' endpoint 
> which is more suited for our needs.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (CONNECTORS-1667) New Tika Service Connector

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1667:
-

It looks like some changes are needed. 
https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0

> New Tika Service Connector
> --
>
> Key: CONNECTORS-1667
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1667
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: Tika service connector
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Fix For: ManifoldCF 2.20
>
>
> The current Tika Service Connector exploits the '/unpack/all' endpoint of a 
> Tika Server. This endpoint is not optimal to only extract document's metadata 
> and content.  We should develop a new connector based on the 'rmeta' endpoint 
> which is more suited for our needs.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (CONNECTORS-1667) New Tika Service Connector

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1667:
-

Hi Jullien. 

Does this service support Tika2x?

> New Tika Service Connector
> --
>
> Key: CONNECTORS-1667
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1667
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: Tika service connector
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
> Fix For: ManifoldCF 2.20
>
>
> The current Tika Service Connector exploits the '/unpack/all' endpoint of a 
> Tika Server. This endpoint is not optimal to only extract document's metadata 
> and content.  We should develop a new connector based on the 'rmeta' endpoint 
> which is more suited for our needs.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1699:
-

Maybe any student would like to develop this issue for GSoC 2022

> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.21
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has a new version as 2.x . We can support the new version instead of 1.x 
>  . There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Tika has released 2.3.0. Changes can be found from here: 
> https://tika.apache.org/2.3.0/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1699:

Affects Version/s: ManifoldCF 2.21
   (was: ManifoldCF 2.13)

> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.21
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has a new version as 2.x . We can support the new version instead of 1.x 
>  . There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Tika has released 2.3.0. Changes can be found from here: 
> [http://tika.apache.org/2.3.0/|http://tika.apache.org/1.23/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1699:

Description: 
Tika has a new version as 2.x . We can support the new version instead of 1.x  
. There is a migration document here: 
[https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]

Tika has released 2.3.0. Changes can be found from here: 
https://tika.apache.org/2.3.0/

  was:
Tika has a new version as 2.x . We can support the new version instead of 1.x  
. There is a migration document here: 
[https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]

Tika has released 2.3.0. Changes can be found from here: 
[http://tika.apache.org/2.3.0/|http://tika.apache.org/1.23/]


> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.21
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has a new version as 2.x . We can support the new version instead of 1.x 
>  . There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Tika has released 2.3.0. Changes can be found from here: 
> https://tika.apache.org/2.3.0/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel reassigned CONNECTORS-1699:
---

Assignee: (was: Karl Wright)

> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has a new version as 2.x . We can support the new version instead of 1.x 
>  . There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Tika has released 2.3.0. Changes can be found from here: 
> [http://tika.apache.org/2.3.0/|http://tika.apache.org/1.23/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1699:

Description: 
Tika has a new version as 2.x . We can support the new version instead of 1.x  
. There is a migration document here: 
[https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]

Tika has released 2.3.0. Changes can be found from here: 
[http://tika.apache.org/2.3.0/|http://tika.apache.org/1.23/]

  was:
Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]

 

please see :[TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
CONNECTORS-1683


> Upgrade to Tika 2.x
> ---
>
> Key: CONNECTORS-1699
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has a new version as 2.x . We can support the new version instead of 1.x 
>  . There is a migration document here: 
> [https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0]
> Tika has released 2.3.0. Changes can be found from here: 
> [http://tika.apache.org/2.3.0/|http://tika.apache.org/1.23/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (CONNECTORS-1699) Upgrade to Tika 2.x

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1699:
---

 Summary: Upgrade to Tika 2.x
 Key: CONNECTORS-1699
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1699
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Tika extractor
Affects Versions: ManifoldCF 2.13
Reporter: Cihad Guzel
Assignee: Karl Wright
 Fix For: ManifoldCF next


Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]

 

please see :[TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
CONNECTORS-1683



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.28.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Description: 
Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]

 

please see :[TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
CONNECTORS-1683

  was:
Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]

 

please see :[ TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
[CONNECTORS-1683|https://issues.apache.org/jira/browse/CONNECTORS-1683]


> Upgrade to Tika 1.28.x
> --
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.28.1. Changes can be found from here: 
> [http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]
>  
> please see :[TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
> CONNECTORS-1683



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.28.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Description: 
Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]

 

please see :[ TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
[CONNECTORS-1683|https://issues.apache.org/jira/browse/CONNECTORS-1683]

  was:Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]


> Upgrade to Tika 1.28.x
> --
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.28.1. Changes can be found from here: 
> [http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]
>  
> please see :[ TIKA-3625|https://issues.apache.org/jira/browse/TIKA-3625] and  
> [CONNECTORS-1683|https://issues.apache.org/jira/browse/CONNECTORS-1683]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.28.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Description: Tika has released 1.28.1. Changes can be found from here: 
[http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]  (was: Tika has 
released 1.23. Changes can be found from here: http://tika.apache.org/1.23/)

> Upgrade to Tika 1.28.x
> --
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.28.1. Changes can be found from here: 
> [http://tika.apache.org/1.28.1/|http://tika.apache.org/1.23/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.28.x

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Summary: Upgrade to Tika 1.28.x  (was: Upgrade to Tika 1.23)

> Upgrade to Tika 1.28.x
> --
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.23. Changes can be found from here: 
> http://tika.apache.org/1.23/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [VOTE] Release Apache ManifoldCF 2.20, RC0

[Cihad Guzel]

+1

Cihad Güzel


 adresine sahip kullanıcı 26 Eyl 2021 Paz,
15:06 tarihinde şunu yazdı:

> +1
>
> Julien
>
> -Message d'origine-
> De : Karl Wright 
> Envoyé : samedi 25 septembre 2021 15:24
> À : dev 
> Objet : [VOTE] Release Apache ManifoldCF 2.20, RC0
>
> Please vote on whether to release Apache ManifoldCF 2.20, RC0.
>
> This release has a new connector in it, and a few bug fixes, but is
> otherwise pretty light.  Nevertheless, it's a month behind schedule so I'm
> calling a vote for release, by the end of the month.
>
> The release artifact can be found at:
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.20
>
> There is also a release tag here:
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.20-RC0
>
> Karl
>
>

Re: [VOTE] Release Apache ManifoldCF 2.19, RC0

[Cihad Guzel]

Hi,

+1 from me

Cihad Güzel


 adresine sahip kullanıcı 3 May 2021 Pzt,
16:39 tarihinde şunu yazdı:

> Hi,
>
> On our side, we plan to test this release on Thursday. I'll give my vote
> after the test if it will not be too late
>
> Julien
>
> -Message d'origine-
> De : Karl Wright 
> Envoyé : lundi 3 mai 2021 13:43
> À : dev 
> Objet : Re: [VOTE] Release Apache ManifoldCF 2.19, RC0
>
> Reminder: Voting underway.  Please evaluate and vote.
>
> Ran tests.  +1 from me.
>
> Karl
>
>
> On Wed, Apr 28, 2021 at 7:21 PM Karl Wright  wrote:
>
> > Please vote to release Apache ManifoldCF 2.19, RC0.  The release
> > artifact can be found at:
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.
> > 19
> > .  There is also a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.19-RC0 .
> >
> > This release has a significant update to the Elastic Search connector,
> > to both bring it up to date, and to work around the problem with
> > limited ID length that ES has.
> >
> > Karl
> >
> >
>
>

[jira] [Comment Edited] (CONNECTORS-1633) Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process

[Cihad Guzel (Jira)]

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

Cihad Guzel edited comment on CONNECTORS-1633 at 11/27/20, 1:38 PM:


I have similar logs as follow: 

!Screen Shot 2020-11-27 at 16.33.35.png|width=815,height=91!


was (Author: cguzel):
I have similar logs as follow: 

!Screen Shot 2020-11-27 at 16.33.35.png!

> Exception tossed: Repeated service interruptions - failure processing 
> document: The process cannot access the file because it is being used by 
> another process.
> ---
>
> Key: CONNECTORS-1633
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1633
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: File system connector
>Affects Versions: ManifoldCF 2.13
>Reporter: Michael Cizmar
>Assignee: Karl Wright
>Priority: Major
> Attachments: Screen Shot 2020-11-27 at 16.33.35.png
>
>
> Seeing this error occurring and I'm working to address it.  If it's not a 
> bug, a better message should be generated.
>  
> {code:java}
> crawl job fails with the following error due to document being in use by 
> another user: 
>  WARN 2019-08-25T15:02:27,416 (Worker thread '11') - Service interruption 
> reported for job 1565115290083 connection 'fs_vwoaahvp319': Timeout or other 
> service interruption: The process cannot access the file because it is being 
> used by another process.
> ERROR 2019-08-25T15:02:27,424 (Worker thread '11') - Exception tossed: 
> Repeated service interruptions - failure processing document: The process 
> cannot access the file because it is being used by another process.
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service 
> interruptions - failure processing document: The process cannot access the 
> file because it is being used by another process.
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:489) 
> [mcf-pull-agent.jar:?]
> Caused by: jcifs.smb.SmbException: The process cannot access the file because 
> it is being used by another process.
>         at 
> jcifs.smb.SmbTransportImpl.checkStatus2(SmbTransportImpl.java:1457) ~[?:?]
>         at jcifs.smb.SmbTransportImpl.checkStatus(SmbTransportImpl.java:1568) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.sendrecv(SmbTransportImpl.java:1023) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.send(SmbTransportImpl.java:1539) ~[?:?]
>         at jcifs.smb.SmbSessionImpl.send(SmbSessionImpl.java:409) ~[?:?]
>         at jcifs.smb.SmbTreeImpl.send(SmbTreeImpl.java:472) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send0(SmbTreeConnection.java:401) 
> ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:315) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:295) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:130) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:117) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1741) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1710) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1704) ~[?:?]
>         at jcifs.smb.SmbFile.queryPath(SmbFile.java:770) ~[?:?]
>         at jcifs.smb.SmbFile.exists(SmbFile.java:851) ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.fileExists(SharedDriveConnector.java:2188)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.processDocuments(SharedDriveConnector.java:610)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> ~[mcf-pull-agent.jar:?]
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CONNECTORS-1633) Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process.

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1633:
-

I have similar logs as follow: 

!Screen Shot 2020-11-27 at 16.33.35.png!

> Exception tossed: Repeated service interruptions - failure processing 
> document: The process cannot access the file because it is being used by 
> another process.
> ---
>
> Key: CONNECTORS-1633
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1633
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: File system connector
>Affects Versions: ManifoldCF 2.13
>Reporter: Michael Cizmar
>Assignee: Karl Wright
>Priority: Major
> Attachments: Screen Shot 2020-11-27 at 16.33.35.png
>
>
> Seeing this error occurring and I'm working to address it.  If it's not a 
> bug, a better message should be generated.
>  
> {code:java}
> crawl job fails with the following error due to document being in use by 
> another user: 
>  WARN 2019-08-25T15:02:27,416 (Worker thread '11') - Service interruption 
> reported for job 1565115290083 connection 'fs_vwoaahvp319': Timeout or other 
> service interruption: The process cannot access the file because it is being 
> used by another process.
> ERROR 2019-08-25T15:02:27,424 (Worker thread '11') - Exception tossed: 
> Repeated service interruptions - failure processing document: The process 
> cannot access the file because it is being used by another process.
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service 
> interruptions - failure processing document: The process cannot access the 
> file because it is being used by another process.
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:489) 
> [mcf-pull-agent.jar:?]
> Caused by: jcifs.smb.SmbException: The process cannot access the file because 
> it is being used by another process.
>         at 
> jcifs.smb.SmbTransportImpl.checkStatus2(SmbTransportImpl.java:1457) ~[?:?]
>         at jcifs.smb.SmbTransportImpl.checkStatus(SmbTransportImpl.java:1568) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.sendrecv(SmbTransportImpl.java:1023) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.send(SmbTransportImpl.java:1539) ~[?:?]
>         at jcifs.smb.SmbSessionImpl.send(SmbSessionImpl.java:409) ~[?:?]
>         at jcifs.smb.SmbTreeImpl.send(SmbTreeImpl.java:472) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send0(SmbTreeConnection.java:401) 
> ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:315) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:295) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:130) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:117) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1741) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1710) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1704) ~[?:?]
>         at jcifs.smb.SmbFile.queryPath(SmbFile.java:770) ~[?:?]
>         at jcifs.smb.SmbFile.exists(SmbFile.java:851) ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.fileExists(SharedDriveConnector.java:2188)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.processDocuments(SharedDriveConnector.java:610)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> ~[mcf-pull-agent.jar:?]
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONNECTORS-1633) Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process.

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1633:

Attachment: Screen Shot 2020-11-27 at 16.33.35.png

> Exception tossed: Repeated service interruptions - failure processing 
> document: The process cannot access the file because it is being used by 
> another process.
> ---
>
> Key: CONNECTORS-1633
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1633
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: File system connector
>Affects Versions: ManifoldCF 2.13
>Reporter: Michael Cizmar
>Assignee: Karl Wright
>Priority: Major
> Attachments: Screen Shot 2020-11-27 at 16.33.35.png
>
>
> Seeing this error occurring and I'm working to address it.  If it's not a 
> bug, a better message should be generated.
>  
> {code:java}
> crawl job fails with the following error due to document being in use by 
> another user: 
>  WARN 2019-08-25T15:02:27,416 (Worker thread '11') - Service interruption 
> reported for job 1565115290083 connection 'fs_vwoaahvp319': Timeout or other 
> service interruption: The process cannot access the file because it is being 
> used by another process.
> ERROR 2019-08-25T15:02:27,424 (Worker thread '11') - Exception tossed: 
> Repeated service interruptions - failure processing document: The process 
> cannot access the file because it is being used by another process.
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service 
> interruptions - failure processing document: The process cannot access the 
> file because it is being used by another process.
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:489) 
> [mcf-pull-agent.jar:?]
> Caused by: jcifs.smb.SmbException: The process cannot access the file because 
> it is being used by another process.
>         at 
> jcifs.smb.SmbTransportImpl.checkStatus2(SmbTransportImpl.java:1457) ~[?:?]
>         at jcifs.smb.SmbTransportImpl.checkStatus(SmbTransportImpl.java:1568) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.sendrecv(SmbTransportImpl.java:1023) 
> ~[?:?]
>         at jcifs.smb.SmbTransportImpl.send(SmbTransportImpl.java:1539) ~[?:?]
>         at jcifs.smb.SmbSessionImpl.send(SmbSessionImpl.java:409) ~[?:?]
>         at jcifs.smb.SmbTreeImpl.send(SmbTreeImpl.java:472) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send0(SmbTreeConnection.java:401) 
> ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:315) ~[?:?]
>         at jcifs.smb.SmbTreeConnection.send(SmbTreeConnection.java:295) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:130) ~[?:?]
>         at jcifs.smb.SmbTreeHandleImpl.send(SmbTreeHandleImpl.java:117) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1741) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1710) ~[?:?]
>         at jcifs.smb.SmbFile.withOpen(SmbFile.java:1704) ~[?:?]
>         at jcifs.smb.SmbFile.queryPath(SmbFile.java:770) ~[?:?]
>         at jcifs.smb.SmbFile.exists(SmbFile.java:851) ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.fileExists(SharedDriveConnector.java:2188)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.processDocuments(SharedDriveConnector.java:610)
>  ~[?:?]
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> ~[mcf-pull-agent.jar:?]
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

[Cihad Guzel]

Hi,

+1 from me

Kind Regards


16 Eyl 2020 Çar 02:21 tarihinde Karl Wright  şunu yazdı:

> Hi all,
> This is a vote thread, and RC1 is still waiting for votes.  Still need 2
> more +1s.
>
> Karl
>
>
> On Tue, Sep 15, 2020 at 10:32 AM Cihad Guzel  wrote:
>
> > Hi,
> >
> > I think that we can vote again to release
> >
> > Kınd Regards,
> > Cihad Guzel
> >
> >
> > Michael Cizmar , 15 Eyl 2020 Sal, 14:13
> > tarihinde şunu yazdı:
> >
> > > Karl,
> > >
> > > This occurs on mac and then only on maven.  Both of these are secondary
> > > targets for the build/release process.   I don't know if there's any
> > > difference to doing a follow up RC candidate  because the original
> build
> > > works on the targeted platforms and as you mentioned, this is just a
> path
> > > issue with a test and no code has been modified in this connector.
> > >
> > > M
> > >
> > > On Mon, Sep 14, 2020 at 6:28 AM Karl Wright 
> wrote:
> > >
> > > > I have time this week only to spin a new RC, if that's what the
> > community
> > > > wants, but not to modify the maven build to download ElasticSearch
> and
> > > > unpack it.  Mind you, there's still no difference in production code
> > > > between RC0, RC1, and what's currently on the branch.  We've been
> > fixing
> > > a
> > > > test only.
> > > >
> > > > Please let me know what you feel is necessary for a release to
> succeed.
> > > > Karl
> > > >
> > > >
> > > > On Sun, Sep 13, 2020 at 6:36 AM Karl Wright 
> > wrote:
> > > >
> > > > > Works fine now for Maven (although I had to upgrade the version of
> > > > > failsafe plugin to work with my current version of Maven), provided
> > you
> > > > run
> > > > > the ant make-dependencies first.
> > > > >
> > > > > Karl
> > > > >
> > > > >
> > > > > On Sat, Sep 12, 2020 at 9:28 PM Karl Wright 
> > > wrote:
> > > > >
> > > > >> I used a -D variable that is set differently by maven and ant
> > builds.
> > > > >>
> > > > >> It works fine for ant.  Bandwidth limitations tonight mean I will
> > try
> > > > >> tomorrow morning for maven.
> > > > >>
> > > > >> Karl
> > > > >>
> > > > >>
> > > > >> On Sat, Sep 12, 2020 at 9:26 PM Michael Cizmar <
> > > > mich...@michaelcizmar.com>
> > > > >> wrote:
> > > > >>
> > > > >>> Ok.  What about an environmental variable that is used for the
> > > download
> > > > >>> and
> > > > >>> then is read in the test case?
> > > > >>>
> > > > >>> On Sat, Sep 12, 2020 at 7:14 PM Karl Wright 
> > > > wrote:
> > > > >>>
> > > > >>> > Ok, the path change will break the Ant test.  The maven test
> > seems
> > > to
> > > > >>> have
> > > > >>> > the current directory set connectors/elasticsearch during
> > testing;
> > > > the
> > > > >>> ant
> > > > >>> > test explicitly sets it to one of the build directories below
> > that.
> > > > >>> But in
> > > > >>> > any case I will need to consider how the test can be changed to
> > > use a
> > > > >>> > specific ES source directory; maybe a -D can be pushed into it.
> > > > >>> >
> > > > >>> > Karl
> > > > >>> >
> > > > >>> > On Sat, Sep 12, 2020 at 3:30 PM Michael Cizmar <
> > > > >>> mich...@michaelcizmar.com>
> > > > >>> > wrote:
> > > > >>> >
> > > > >>> > > Two in BaseITHSQLDB's setupElasticSearch method
> > > > >>> > >
> > > > >>> > > First to set the Java_HOME
> > > > >>> > > Map envs = pb.environment();
> > > > >>> > > if (System.getenv("JAVA_HOME")!= null) {
> > > > >>> > > envs.put("JAVA_HOME",System.getenv("JAVA_HOME"));
> > > > >>>

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

[Cihad Guzel]

Michael,

I have log lines repeating like as follow:

---
 T E S T S
---
Running
org.apache.manifoldcf.agents.output.elasticsearch.tests.APISanityHSQLDBIT
Configuration file successfully read
[main] INFO org.eclipse.jetty.util.log - Logging initialized @7246ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.3.v20140905
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started
o.e.j.w.WebAppContext@2ad48653
{/mcf-crawler-ui,file:/private/var/folders/gw/4lgs06cd065d09gnm6ythcp8gn/T/jetty-0.0.0.0-8346-mcf-crawler-ui.war-_mcf-crawler-ui-any-5325495261063795321.dir/webapp/,AVAILABLE}{../dependency/mcf-crawler-ui.war}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started
o.e.j.w.WebAppContext@6bb4dd34
{/mcf-authority-service,file:/private/var/folders/gw/4lgs06cd065d09gnm6ythcp8gn/T/jetty-0.0.0.0-8346-mcf-authority-service.war-_mcf-authority-service-any-1339291969162319913.dir/webapp/,AVAILABLE}{../dependency/mcf-authority-service.war}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started
o.e.j.w.WebAppContext@7d9f158f
{/mcf-api-service,file:/private/var/folders/gw/4lgs06cd065d09gnm6ythcp8gn/T/jetty-0.0.0.0-8346-mcf-api-service.war-_mcf-api-service-any-2172701003493912621.dir/webapp/,AVAILABLE}{../dependency/mcf-api-service.war}
[main] INFO org.eclipse.jetty.server.ServerConnector - Started
ServerConnector@2796aeae{HTTP/1.1}{0.0.0.0:8346}
[main] INFO org.eclipse.jetty.server.Server - Started @10899ms
ES working directory is
'/Users/cguzel/Projects/apache/svn/release-2.17-RC1/connectors/elasticsearch/target/test-output/.'
Unix process
ElasticSearch is starting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...
Didn't reach ES; waiting...

Cihad


Michael Cizmar , 9 Eyl 2020 Çar, 12:40 tarihinde
şunu yazdı:

> Cihad,
>
> What was the error that you received when compiling in maven?
>
> On Wed, Sep 9, 2020 at 3:39 AM Cihad Guzel  wrote:
>
> > Hi Karl,
> >
> > I have successfully compiled using ant build. I tried to compile the
> tag[1]
> > using maven, but the ElasticSearch tests still fail using Mac [2] .
> > <https://issues.apache.org/jira/browse/CONNECTORS-1651>
> >
> > [1] https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.17-RC1
> > [2] https://issues.apache.org/jira/browse/CONNECTORS-1651
> >
> > Regards,
> > Cihad Güzel
> >
> >
> > Karl Wright , 8 Eyl 2020 Sal, 16:32 tarihinde şunu
> > yazdı:
> >
> > > Tests pass.  +1 from me.
> > >
> > > Looking for a few other voters?
> > >
> > > Karl
> > >
> > >
> > > On Sat, Sep 5, 2020 at 6:32 AM Karl Wright  wrote:
> > >
> > > > Please vote on whether to release Apache ManifoldCF 2.17, RC1.  The
> > > > release artifact can be found here:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.17
> > > >
> > > > There is also a release tag at:
> > > >
> > > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.17-RC1
> > > >
> > > > This release does not contain anything major - just a few bug fixes,
> > > > summarized in the CHANGES.txt file.  It does include documentation,
> > > > however, which did not get successfully built for the 2.16 release.
> > > Please
> > > > review carefully with that in mind.
> > > >
> > > > The respin was required because the ElasticSearch test did not
> properly
> > > > work on the Mac.
> > > >
> > > > Thanks!
> > > > Karl
> > > >
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

[Cihad Guzel]

Hi Karl,

I have successfully compiled using ant build. I tried to compile the tag[1]
using maven, but the ElasticSearch tests still fail using Mac [2] .


[1] https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.17-RC1
[2] https://issues.apache.org/jira/browse/CONNECTORS-1651

Regards,
Cihad Güzel


Karl Wright , 8 Eyl 2020 Sal, 16:32 tarihinde şunu
yazdı:

> Tests pass.  +1 from me.
>
> Looking for a few other voters?
>
> Karl
>
>
> On Sat, Sep 5, 2020 at 6:32 AM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.17, RC1.  The
> > release artifact can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.17
> >
> > There is also a release tag at:
> >
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.17-RC1
> >
> > This release does not contain anything major - just a few bug fixes,
> > summarized in the CHANGES.txt file.  It does include documentation,
> > however, which did not get successfully built for the 2.16 release.
> Please
> > review carefully with that in mind.
> >
> > The respin was required because the ElasticSearch test did not properly
> > work on the Mac.
> >
> > Thanks!
> > Karl
> >
> >
> >
>

Re: Release time again

[Cihad Guzel]

Hi Karl,

+1 from me.

Cihad Guzel


Piergiorgio Lucidi , 11 Ağu 2020 Sal, 22:52
tarihinde şunu yazdı:

> Hi Karl,
>
> sure, +1 from me.
>
> PJ
>
>
> Il Mar 11 Ago 2020, 14:44 Karl Wright  ha scritto:
>
> > Hi all,
> > August 31 is our next scheduled release date.  The release should
> probably
> > go out because the documentation in the last release did not properly
> build
> > (since corrected, but no new artifacts have been pushed).  Other than
> that,
> > I can think of nothing that hints at a new release - the mailing lists
> have
> > been quite slow, and there are three issues in the release, that is all.
> >
> > Given that, I propose doing a patch release, not a full release.  Any
> > objections?
> >
> > Karl
> >
>

[jira] [Resolved] (CONNECTORS-1647) Update copyright years

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel resolved CONNECTORS-1647.
-
Resolution: Fixed

> Update copyright years
> --
>
> Key: CONNECTORS-1647
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1647
> Project: ManifoldCF
>  Issue Type: Bug
>Affects Versions: ManifoldCF 2.16
>    Reporter: Cihad Guzel
>    Assignee: Cihad Guzel
>Priority: Minor
> Fix For: ManifoldCF 2.17
>
>
> All copyrights should include 2020
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CONNECTORS-1647) Update copyright years

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1647:
-

r1879520

> Update copyright years
> --
>
> Key: CONNECTORS-1647
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1647
> Project: ManifoldCF
>  Issue Type: Bug
>Affects Versions: ManifoldCF 2.16
>    Reporter: Cihad Guzel
>    Assignee: Cihad Guzel
>Priority: Minor
> Fix For: ManifoldCF 2.17
>
>
> All copyrights should include 2020
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CONNECTORS-1647) Update copyright years

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1647:
---

 Summary: Update copyright years
 Key: CONNECTORS-1647
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1647
 Project: ManifoldCF
  Issue Type: Bug
Affects Versions: ManifoldCF 2.16
Reporter: Cihad Guzel
Assignee: Cihad Guzel
 Fix For: ManifoldCF 2.17


All copyrights should include 2020
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Broken MFC Documentation Link

[Cihad Guzel]

Hi Karl,

ManifoldCF latest version documentation link is broken:
https://manifoldcf.apache.org/release/release-2.16/en_US/index.html

Kind Regards,
Cihad Güzel

Re: [VOTE] Release Apache ManifoldCF 2.16, RC0

[Cihad Guzel]

Hi,

+1 from me.

I have built successfully with JDK 11 via maven. All tests passed
successfully.

Regards,
Cihad Güzel

Furkan KAMACI , 3 May 2020 Paz, 22:27 tarihinde
şunu yazdı:

> Hi,
>
> +1 from me.
>
> I checked:
>
> - LICENSE is fine
> - NOTICE should be updated (minor issue, I can fix it)
> - No unexpected binary files
> - Checked PGP signatures
> - Checked Checksums
> - Apache rat checks are OK
>
>
> PS: I got an error while compiling and testing with Java 11 but seems to
> related with my environment:
>
> [ERROR] Failed to execute goal on project mcf-cmis-connector: Could not
> resolve dependencies for project
> org.apache.manifoldcf:mcf-cmis-connector:jar:2.16: Failed to collect
> dependencies at
> org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:1.1.0 ->
> org.apache.chemistry.opencmis:chemistry-opencmis-client-bindings:jar:1.1.0
> -> org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.12 ->
> org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.12 ->
> org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.12 ->
> com.sun.xml.bind:jaxb-impl:jar:2.1.14: Failed to read artifact descriptor
> for com.sun.xml.bind:jaxb-impl:jar:2.1.14: Could not transfer artifact
> com.sun.xml.bind:jaxb-impl:pom:2.1.14 from/to central (
> https://repo.maven.apache.org/maven2): Transfer failed for
>
> https://repo.maven.apache.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.14/jaxb-impl-2.1.14.pom
> :
> Operation timed out (Read failed)
>
> Kind Regards,
> Furkan KAMACI
>
> On Sun, May 3, 2020 at 9:59 PM Michael Cizmar 
> wrote:
>
> > Great work Karl!  I'm looking forward to trying this out.
> >
> > On Sun, May 3, 2020 at 1:31 PM Karl Wright  wrote:
> >
> > > Please vote on whether to release Apache ManifoldCF 2.16, RC0.  This
> > > release has a new confluence connector as well as preliminary support
> for
> > > Java 11.  The release artifact can be found at:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.16
> > >
> > > There is a release tag at:
> > >
> > > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.16-RC0
> > >
> > > Thanks in advance!
> > > Karl
> > >
> >
>

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1639:
-

I have tested the patch. Connector maven build is successful with JDK 11.

> Upgrade Elastic Search Version
> --
>
> Key: CONNECTORS-1639
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1639
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Elastic Search connector
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.16
>
> Attachments: CONNECTORS-1639.diff, 
> elastic-search-1.0.1-java11-build-error.log
>
>
> Current Elastic Search version is 1.0.1 . According to [this 
> matrix|https://www.elastic.co/support/matrix#matrix_jvm], Java 11 is not 
> supported by any ES version below 6.5.
> Besides, ES 1.x is no longer supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Release schedule

[Cihad Guzel]

Thanks folks for your information.

I reviewed the pom.xml of the  ES connector. It uses an old elastic search
version as dependency. It misled me. On the other hand, you are right. I
agree with your thoughts on this matter. It is best if we can rearrange
them.

Kind regards,
Cihad Guzel


Karl Wright , 18 Nis 2020 Cmt, 17:49 tarihinde şunu
yazdı:

> I can help with Ant tasks but I need information as to how you're supposed
> to start the ES instance.  An ant task snippet would be sufficient I think.
>
>
> On Sat, Apr 18, 2020 at 10:33 AM Michael Cizmar <
> michael.ciz...@mcplusa.com>
> wrote:
>
> > I believe so.  I only modified the Pom in the es connector project and
> > removed the Node references.  I know there is a way to do this in ant as
> > well.  I will look it up but may need some guidance on Ant.
> >
> > Get Outlook for iOS<https://aka.ms/o0ukef>
> > 
> > From: Karl Wright 
> > Sent: Saturday, April 18, 2020 9:15:15 AM
> > To: dev 
> > Subject: Re: Release schedule
> >
> > Hi Michael,
> > This has to run under Ant as well.  Any way to make that happen?
> >
> > Karl
> >
> >
> > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar <
> michael.ciz...@mcplusa.com
> > >
> > wrote:
> >
> > > I've got a fix for this.  I switched to using a Maven plugin that spins
> > up
> > > an Elasticsearch instance.  With this, you need only to remove the Node
> > > code in the integration tests.  Tested with 6.x client and 7.x
> > > elasticsearch.
> > >
> > > There are more things we can do with this output plugin in the future
> > like
> > > moving to the SDK.
> > >
> > > M
> > >
> > > On 4/18/20, 8:32 AM, "Karl Wright"  wrote:
> > >
> > > Thanks for the quick reply.
> > > I agree we don't want to turn off the ES connector itself, but yes
> we
> > > will
> > > need to shut down the tests.  Cihad, would you like to propose a
> > > strategy
> > > for that?  I think for now just marking them with @Ignore should be
> > OK,
> > > since the tests don't have compile time dependencies on missing
> > > classes.
> > > What do you think?
> > >
> > > Upgrading to ES 6.x is obviously the right thing to do but who here
> > > has the
> > > knowledge to do a good job with this?  I am certain there are a
> > number
> > > of
> > > ES users lurking on this list.  Please volunteer if so.
> > >
> > > Karl
> > >
> > >
> > > On Sat, Apr 18, 2020 at 9:15 AM Furkan KAMACI <
> > furkankam...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > There is a compatibility matrix for Elasticsearch. We need to
> > > support at
> > > > least Elasticsearch 6.5.x for Java 11 support. You can check it
> > from
> > > here:
> > > > https://www.elastic.co/de/support/matrix#matrix_jvm
> > > >
> > > > @Cihad
> > > >
> > > > As far as I know, current support is not 2.0.0. It is 5.5.2:
> > > >
> https://github.com/apache/manifoldcf-integration-elasticsearch-5.5
> > > >
> > > > @Karl Wright 
> > > >
> > > > So, such an upgrade from 5.5.2 to 6.5.x may not be so painful.
> > > Committers
> > > > who use ES can comment on this.
> > > >
> > > > My comments:
> > > >
> > > > +1 to temporarily turning those tests off
> > > > -1 to temporarily turning the connector off
> > > >
> > > > Kind Regards,
> > > > Furkan KAMACI
> > > >
> > > > On Sat, Apr 18, 2020 at 3:27 PM Cihad Guzel 
> > > wrote:
> > > >
> > > >> Hi Karl,
> > > >>
> > > >> MFC ES Connector uses the Elastic Search 2.0.0 . It's an ancient
> > > version.
> > > >> The latest version is 7.6.2 . So, I agree with you and I think
> we
> > > can
> > > >> temporarily turn the connector off.
> > > >>
> > > >> +1
> > > >>
> > > >> Kind Regards,
> > > >> Cihad Güzel
> > > >>
> > > >>
> > > >> Karl W

Re: Release schedule

[Cihad Guzel]

Hi Karl,

MFC ES Connector uses the Elastic Search 2.0.0 . It's an ancient version.
The latest version is 7.6.2 . So, I agree with you and I think we can
temporarily turn the connector off.

+1

Kind Regards,
Cihad Güzel


Karl Wright , 18 Nis 2020 Cmt, 11:41 tarihinde şunu
yazdı:

> Hi all,
>
> We're due to release ManifoldCF 2.16 by April 30th.  The major work for
> this release was adoption of Java 11, and that work is incomplete because
> of ElasticSearch incompatibilities.  I'm therefore tempted to hold the
> release until we at least have a plan for dealing with ES going forward.
>
> It's not clear that our ES connector support is affected, but certainly our
> integration tests are, because Java 11 isn't supported in any of the ES
> versions we run for those tests.  So at the least we need to decide to turn
> those off.  And indeed, we really need to have someone with ES experience
> map a strategy for getting our ES support back into compliance with what's
> out in the world at large now.  Cihad Guzel did much work on Java 11 but
> stumbled over the Elastic Search problem.  Any of our committers who know
> ES and are stuck inside at the moment, please speak up.
>
> Thanks in advance,
> Karl
>

[jira] [Comment Edited] (CONNECTORS-1624) Get ManifoldCF to run under Java 11 or higher

[Cihad Guzel (Jira)]

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

Cihad Guzel edited comment on CONNECTORS-1624 at 3/22/20, 1:56 PM:
---

I fixed the connector-common maven build problem for Java 11. On the other 
hand, elastic search connector does not support Java 11. We must upgrade 
elastic search version CONNECTORS-1639 . Please check it: 
[https://www.elastic.co/support/matrix#matrix_jvm]


was (Author: cguzel):
I fixed the connector-common maven build problem for Java 11. On the other 
hand, elastic search connector does not support Java 11. We must upgrade 
elastic search version. Please check it: 
https://www.elastic.co/support/matrix#matrix_jvm

> Get ManifoldCF to run under Java 11 or higher
> -
>
> Key: CONNECTORS-1624
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1624
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Framework core
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> Java 11 doesn't include a number of classes that Java 8 does.  We need to 
> explicitly include jars that provide these classes or ManifoldCF will not 
> function under higher Java revs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1639:

Attachment: elastic-search-1.0.1-java11-build-error.log

> Upgrade Elastic Search Version
> --
>
> Key: CONNECTORS-1639
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1639
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Elastic Search connector
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.16
>
> Attachments: elastic-search-1.0.1-java11-build-error.log
>
>
> Current Elastic Search version is 1.0.1 . According to [this 
> matrix|https://www.elastic.co/support/matrix#matrix_jvm], Java 11 is not 
> supported by any ES version below 6.5.
> Besides, ES 1.x is no longer supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CONNECTORS-1639) Upgrade Elastic Search Version

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1639:
---

 Summary: Upgrade Elastic Search Version
 Key: CONNECTORS-1639
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1639
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Elastic Search connector
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.16


Current Elastic Search version is 1.0.1 . According to [this 
matrix|https://www.elastic.co/support/matrix#matrix_jvm], Java 11 is not 
supported by any ES version below 6.5.

Besides, ES 1.x is no longer supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CONNECTORS-1624) Get ManifoldCF to run under Java 11 or higher

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1624:
-

I fixed the connector-common maven build problem for Java 11. On the other 
hand, elastic search connector does not support Java 11. We must upgrade 
elastic search version. Please check it: 
https://www.elastic.co/support/matrix#matrix_jvm

> Get ManifoldCF to run under Java 11 or higher
> -
>
> Key: CONNECTORS-1624
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1624
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Framework core
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> Java 11 doesn't include a number of classes that Java 8 does.  We need to 
> explicitly include jars that provide these classes or ManifoldCF will not 
> function under higher Java revs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CONNECTORS-1638) JCIFS connector optional hidden files

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1638:
---

 Summary: JCIFS connector optional hidden files
 Key: CONNECTORS-1638
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1638
 Project: ManifoldCF
  Issue Type: Improvement
  Components: JCIFS connector
Affects Versions: ManifoldCF 2.15
Reporter: Cihad Guzel
Assignee: Cihad Guzel
 Fix For: ManifoldCF 2.16


The JCIFS connector should indexes hidden files optionally.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.23

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Description: Tika has released 1.23. Changes can be found from here: 
http://tika.apache.org/1.23/  (was: Tika has released 1.22. Changes can be 
found from here: http://tika.apache.org/1.22/)

> Upgrade to Tika 1.23
> 
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.23. Changes can be found from here: 
> http://tika.apache.org/1.23/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.23

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Summary: Upgrade to Tika 1.23  (was: Upgrade to Tika 1.22)

> Upgrade to Tika 1.23
> 
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.22. Changes can be found from here: 
> http://tika.apache.org/1.22/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONNECTORS-1634) Occured 501 HTTP Error while downloading 'h2' dependency

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1634:

Component/s: Build

> Occured 501 HTTP Error while downloading 'h2' dependency
> 
>
> Key: CONNECTORS-1634
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1634
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: ManifoldCF 2.15
>    Reporter: Cihad Guzel
>Assignee: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> We have to update h2 dependency download  link. I try this command:
> {noformat}
> ant make-core-deps{noformat}
> I have this error:
> {noformat}
> download-h2:
>   [get] Getting: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] To: /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Can't get 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
> /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
> BUILD FAILED
> /Users/cguzel/Projects/apache/svn/mcf-trunk/build.xml:1514: Can't get 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
> /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
> {noformat}
> I tried the request in my browser and got the following response:
> [http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar]
> {noformat}
> 501 HTTPS Required. 
> Use https://repo1.maven.org/maven2/
> More information at https://links.sonatype.com/central/501-https-required
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CONNECTORS-1624) Get ManifoldCF to run under Java 11 or higher

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1624:
-

Sure, I will research it.

> Get ManifoldCF to run under Java 11 or higher
> -
>
> Key: CONNECTORS-1624
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1624
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Framework core
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> Java 11 doesn't include a number of classes that Java 8 does.  We need to 
> explicitly include jars that provide these classes or ManifoldCF will not 
> function under higher Java revs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CONNECTORS-1634) Occured 501 HTTP Error while downloading 'h2' dependency

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1634:
-

new url: https://repo1.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
old url: http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar

> Occured 501 HTTP Error while downloading 'h2' dependency
> 
>
> Key: CONNECTORS-1634
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1634
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.15
>    Reporter: Cihad Guzel
>    Assignee: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> We have to update h2 dependency download  link. I try this command:
> {noformat}
> ant make-core-deps{noformat}
> I have this error:
> {noformat}
> download-h2:
>   [get] Getting: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] To: /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Error opening connection java.io.IOException: Server returned 
> HTTP response code: 501 for URL: 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
>   [get] Can't get 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
> /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
> BUILD FAILED
> /Users/cguzel/Projects/apache/svn/mcf-trunk/build.xml:1514: Can't get 
> http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
> /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
> {noformat}
> I tried the request in my browser and got the following response:
> [http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar]
> {noformat}
> 501 HTTPS Required. 
> Use https://repo1.maven.org/maven2/
> More information at https://links.sonatype.com/central/501-https-required
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CONNECTORS-1634) Occured 501 HTTP Error while downloading 'h2' dependency

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1634:
---

 Summary: Occured 501 HTTP Error while downloading 'h2' dependency
 Key: CONNECTORS-1634
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1634
 Project: ManifoldCF
  Issue Type: Improvement
Affects Versions: ManifoldCF 2.15
Reporter: Cihad Guzel
Assignee: Cihad Guzel
 Fix For: ManifoldCF 2.16


We have to update h2 dependency download  link. I try this command:
{noformat}
ant make-core-deps{noformat}
I have this error:
{noformat}
download-h2:
  [get] Getting: 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
  [get] To: /Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
  [get] Error opening connection java.io.IOException: Server returned HTTP 
response code: 501 for URL: 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
  [get] Error opening connection java.io.IOException: Server returned HTTP 
response code: 501 for URL: 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
  [get] Error opening connection java.io.IOException: Server returned HTTP 
response code: 501 for URL: 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar
  [get] Can't get 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
/Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar

BUILD FAILED
/Users/cguzel/Projects/apache/svn/mcf-trunk/build.xml:1514: Can't get 
http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar to 
/Users/cguzel/Projects/apache/svn/mcf-trunk/lib/h2-1.3.158.jar
{noformat}
I tried the request in my browser and got the following response:
[http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar]
{noformat}
501 HTTPS Required. 
Use https://repo1.maven.org/maven2/
More information at https://links.sonatype.com/central/501-https-required
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Oracle JDBC Job Error

[Cihad Guzel]

Hi,

I have debugged the MFC-2.15 codes and caught the problem.

JDBCConnector.java line:270

Object o = row.getValue(JDBCConstants.idReturnColumnName);

if (o == null)
  throw new ManifoldCFException("Bad seed query; doesn't return
$(IDCOLUMN) column.  Try using quotes around $(IDCOLUMN) variable,
e.g. \"$(IDCOLUMN)\", or, for MySQL, select \"by label\" in your
repository connection.");


The "row" object's value is "LCF__ID" -> this is a uppercase string

"JDBCConstants.idReturnColumnName" is "lcf__id" -> this is a lowercase string

So "o" object is null.

I think that Oracle returns the uppercase column name. It is not a
bug. How can I fix it? Should I update the seed query in the Query
tab? Should we change the code lines?

Regards,
Cihad Guzel


Cihad Guzel , 5 Oca 2020 Paz, 20:14 tarihinde şunu yazdı:

> Hi,
>
> I try JDBC connector with Oracle (version: 11.2.0.4). I added to classpath
> ojdbc6.jar. My seed query as follows:
>
> "SELECT PERSONID AS $(IDCOLUMN) FROM PERSON"
>
> and I have an error as follow:
>
> "Error: Bad seed query; doesn't return $(IDCOLUMN) column. Try using
> quotes around $(IDCOLUMN) variable, e.g. "$(IDCOLUMN)", or, for MySQL,
> select "by label" in your repository connection."
>
> I have tried JDBC connector with MsSQL and Mysql. It has run successfully.
>
> How can I fix it?
>
> Regards,
> Cihad Guzel
>

Re: [VOTE] Release Apache ManifoldCF 2.15, RC0

[Cihad Guzel]

Hi,

+1 from me. Ran all tests.

Regards,
Cihad Guzel


Karl Wright , 24 Ara 2019 Sal, 17:34 tarihinde şunu
yazdı:

> Ran all tests.
>
> +1 from me.
>
> Karl
>
>
> On Sun, Dec 22, 2019 at 7:13 PM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.15, RC0.  The
> > release artifact can be found at:
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.15
> > .  There is also a release tag at:
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.15-RC0 .
> >
> > This release of ManifoldCF ties up some loose ends in the csws connector,
> > and also updates the Solr Connector to the 8.x version of SolrJ.  There
> are
> > also some bug fixes included.
> >
> > Thanks,
> > Karl
> >
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC2

[Cihad Guzel]

Hi Karl,

Sorry for the late reply. I have fixed my problem. I realized that it was
related to my environment.

I checked:
- All tests pass

+1 from me.

Thanks,
Cihad Guzel


Karl Wright , 30 Eyl 2019 Pzt, 11:22 tarihinde şunu
yazdı:

> All tests pass.  +1 from me.
> Can anyone else look at this, especially Cihad?  I'm not expecting this to
> fix his import but it will possibly fix his linkage error.
>
> Karl
>
>
> On Wed, Sep 25, 2019 at 9:28 PM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> >
> > There is a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC2 .
> > There is a release artifact at
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> .
> >
> > Note that this release of ManifoldCF has a new connector -- the Content
> > Services Web Services connector.  In order to integrate this connector,
> > changes to the dependencies for web services had to be made, so I urge
> > those using the Alfresco and CMIS connectors to verify this release if at
> > all possible.  Integration tests pass but there's nothing like an on-site
> > test.
> >
> > RC2 also contains a fix for CONNECTORS-1623.
> >
> > RC2 also removes duplicate jars appearing connector-lib that are also in
> > the root directory.  This could potentially cause runtime link errors.
> >
> > Thanks,
> > Karl
> >
>

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Cihad Guzel]

Hi Karl,

Shortly;
1- I have created a job via ManifoldCF API. There is not any problem, no
error, all is well.
2- Then I try to open the Edit Job page from UI and UI won't display it
properly. There is the 500 error on the popup.

I didn't move my current installation. I have downloaded new ManifoldCF
version and have run in a clean new environment. Then, I have sent the JSON
object to my new ManifoldCF API.

I agree with you on this:
"The actual error you are getting is because of a JSP exception. The JSP
exception is not being handled properly, possibly because of a version
mismatch between the included version of Velocity and Apache Commons
Collections. "

Regards,
Cihad Guzel

Karl Wright , 26 Eyl 2019 Per, 01:31 tarihinde şunu
yazdı:

> The actual error you are getting is because of a JSP exception.  The JSP
> exception is not being handled properly, possibly because of a version
> mismatch between the included version of Velocity and Apache Commons
> Collections.  But if that is real, it's odd because it's occurring when the
> velocity context is being initialized!! That means it should be happening
> on every page load in the UI, and it most certainly does not -- not for me,
> not for anyone who ran the tests.  So I suspect a setup problem of some
> kind, especially if you're trying to move your 2.12 installation to 2.14 in
> place.  Lots of jars moved around and you might have a jar conflict.
>
> Karl
>
> On Wed, Sep 25, 2019 at 6:25 PM Karl Wright  wrote:
>
>> Hi Cihad,
>> Using the API should not ever invoke JSP pages, so I do not think you are
>> actually communicating with the API.  Unless what you are saying is that
>> you create the job, and then the UI won't display it properly?
>>
>> Karl
>>
>>
>> On Wed, Sep 25, 2019 at 6:11 PM Cihad Guzel  wrote:
>>
>>> Hi,
>>>
>>> Firstly, Thanks @Furkan, all tests are passed with Java8 now.
>>>
>>> On the other hand, I test the ManifoldCF API. There are some errors. I
>>> have created a job using ManifoldCF API successfully (versions: 2.12, 2.13,
>>> 2.14). Then I have HTTP 500 error if I click "mcf-crawler-ui/editjob.jsp" .
>>> I get this error when only I use Manifoldcf-2.13 and Manifoldcf-2.14. I
>>> don't have any error when I use Manifoldcf-2.12.
>>>
>>> I sent following JSON object to the manifoldCF API  to create new job.
>>>
>>> {"job":{"children":[{"type":"start_mode","value":"manual"},{"type":"hopcount_mode","value":"accurate"},{"type":"run_mode","value":"continuous"},{"type":"recrawl_interval","value":"8640"},{"type":"reseed_interval","value":"360"},{"type":"description","value":"file_filecrawler2"},{"type":"repository_connection","value":"file_filecrawler2"},{"type":"priority","value":"1"},{"type":"pipelinestage","children":[{"type":"stage_id","value":"0"},{"type":"stage_isoutput","value":"false"},{"type":"stage_connectionname","value":"Allowed
>>>  
>>> Documents"},{"type":"stage_specification","children":[{"type":"extensions","value":"xlsx\r\nrtf\r\ncsv\r\ndocx\r\npptx\r\ntxt\r\npdf\r\nppt\r\nxml\r\ndoc\r\nodp\r\nxls\r\nodt\r\nods"},{"type":"mimetypes","value":"application\/xml\r\napplication\/msword\r\napplication\/pdf\r\napplication\/vnd.ms-powerpoint\r\napplication\/vnd.openxmlformats-officedocument.wordprocessingml.document\r\napplication\/rtf\r\napplication\/vnd.oasis.opendocument.text\r\napplication\/vnd.openxmlformats-officedocument.presentationml.presentation\r\napplication\/vnd.openxmlformats-officedocument.spreadsheetml.sheet\r\ntext\/csv\r\napplication\/vnd.oasis.opendocument.presentation\r\napplication\/vnd.ms-excel\r\napplication\/vnd.oasis.opendocument.spreadsheet\r\ntext\/plain"},{"type":"mindate","value":"","attribute_value":"36593"},{"_type":"minlength","value":"","attribute_value":"1"},{"_type":"maxlength","value":"","attribute_value":"1"}]}]},{"_type":"pipelinestage","children":[{"type":"stage_id","value":"1"},{

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Cihad Guzel]

ttribute_path":"SharedFiles","_value":""}]}]}}


The error message as follow:
HTTP ERROR 500

Problem accessing /mcf-crawler-ui/editjob.jsp. Reason:

Server Error

Caused by:

org.apache.jasper.JasperException: An exception occurred processing
JSP page /editjob.jsp at line 716

713: {
714:   try
715:   {
716: transformationConnector.outputSpecificationHeader(new
org.apache.manifoldcf.ui.jsp.JspWrapper(out,adminprofile),pageContext.getRequest().getLocale(),pipelineSpecifications[j],1+j,tabsArray);
717:   }
718:   finally
719:   {


Stacktrace:
at 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:412)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
at 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.servlet.ServletException:
java.lang.NoClassDefFoundError:
org/apache/commons/collections/ExtendedProperties
at 
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:865)
at 
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:794)
at org.apache.jsp.editjob_jsp._jspService(editjob_jsp.java:3113)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
... 23 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/collections/ExtendedProperties
at 
org.apache.velocity.runtime.RuntimeInstance.(RuntimeInstance.java:183)
at org.apache.velocity.app.VelocityEngine.(VelocityEngine.java:60)
at 
org.apache.manifoldcf.core.i18n.Messages.createVelocityEngine(Messages.java:55)
at 
org.apache.manifoldcf.ui.i18n.Messages.outputResourceWithVelocity(Messages.java:132)
at 
org.apache.manifoldcf.agents.transformation.documentfilter.Messages.outputResourceWithVelocity(Messages.java:136)
at 
org.apache.manifoldcf.agents.transformation.documentfilter.DocumentFilter.outputSpecificationHeader(DocumentFilter.java:288)
at org.apache.jsp.editjob_jsp._jspService(editjob_jsp.java:953)
... 26 more
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.collections.ExtendedProperties
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 33 more


Regards,
Cihad Guzel


Furkan KAMACI , 25 Eyl 2019 Çar, 15:14 tarihinde
şunu yazdı:

> Hi Cihad,
>
> That package is removed at Java 11. It is possible that you compiled the
> project via Java 11 which is not supported at ManifoldCF yet.
>
> Kind Regards,
> Furkan KAMACI
>
> 25 Eyl 2019 Çar, saat 15:00 tarihinde Cihad Guz

[jira] [Commented] (CONNECTORS-1624) Get ManifoldCF to run under Java 11 or higher

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1624:
-

Some packages (ex: 
[JAX-WS|https://en.wikipedia.org/wiki/Java_API_for_XML_Web_Services]) are no 
longer applicable due to the removal of the Java 11 [2]. I try to build using 
maven with Java11 and I have had some errors as follows:
{code:java}
[INFO] -< org.apache.manifoldcf:mcf-connector-common >-
[INFO] Building ManifoldCF - Connector-Common 2.14   [5/63]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
mcf-connector-common ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
mcf-connector-common ---
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
mcf-connector-common ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
mcf-connector-common ---
[INFO] Compiling 59 source files to 
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[60,21]
 error: package javax.xml.soap does not exist
[ERROR] 
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[61,21]
 error: package javax.xml.soap does not exist
[ERROR] 
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[62,21]
 error: package javax.xml.soap does not exist
[INFO] 3 errors
{code}
[1] 
[mail-list|https://lists.apache.org/thread.html/cbad71e2309bd492b18e2cf4ba5731e5144063a32e743210528c3b1d@%3Cdev.manifoldcf.apache.org%3E]

[2] [Java 11 Release 
Notes|https://www.oracle.com/technetwork/java/javase/11-relnote-issues-5012449.html#JDK-8190378]

> Get ManifoldCF to run under Java 11 or higher
> -
>
> Key: CONNECTORS-1624
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1624
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Framework core
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.15
>
>
> Java 11 doesn't include a number of classes that Java 8 does.  We need to 
> explicitly include jars that provide these classes or ManifoldCF will not 
> function under higher Java revs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Release Apache ManifoldCF 2.14, RC1

[Cihad Guzel]

Hi Karl,

I have following errors:

[INFO] -< org.apache.manifoldcf:mcf-connector-common
>-
[INFO] Building ManifoldCF - Connector-Common 2.14
[5/63]
[INFO] [ jar
]-
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
mcf-connector-common ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @
mcf-connector-common ---
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
mcf-connector-common ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
mcf-connector-common ---
[INFO] Compiling 59 source files to
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[60,21]
error: package javax.xml.soap does not exist
[ERROR]
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[61,21]
error: package javax.xml.soap does not exist
[ERROR]
/Users/cguzel/Projects/apache/svn/mcf-tag-2.14-RC1/framework/connector-common/src/main/java/org/apache/manifoldcf/connectorcommon/common/CommonsHTTPSender.java:[62,21]
error: package javax.xml.soap does not exist
[INFO] 3 errors

Regards,
Cihad Guzel


Karl Wright , 25 Eyl 2019 Çar, 02:01 tarihinde şunu
yazdı:

> Ran all tests.
>
> +1 from me.
>
> Karl
>
>
> On Tue, Sep 24, 2019 at 1:29 PM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.14, RC0.
> >
> > There is a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.14-RC1 .
> > There is a release artifact at
> > https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.14
> .
> >
> > Note that this release of ManifoldCF has a new connector -- the Content
> > Services Web Services connector.  In order to integrate this connector,
> > changes to the dependencies for web services had to be made, so I urge
> > those using the Alfresco and CMIS connectors to verify this release if at
> > all possible.  Integration tests pass but there's nothing like an on-site
> > test.
> >
> > RC1 also contains a fix for CONNECTORS-1623.
> >
> > Thanks,
> > Karl
> >
>

[jira] [Updated] (CONNECTORS-1622) Upgrade to Tika 1.22

[Cihad Guzel (Jira)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1622:

Summary: Upgrade to Tika 1.22  (was: Upgrade to Tika 1.22 when available)

> Upgrade to Tika 1.22
> 
>
> Key: CONNECTORS-1622
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Tika extractor
>Affects Versions: ManifoldCF 2.13
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Tika has released 1.22. Changes can be found from here: 
> http://tika.apache.org/1.22/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (CONNECTORS-1622) Upgrade to Tika 1.22 when available

[Cihad Guzel (Jira)]

Cihad Guzel created CONNECTORS-1622:
---

 Summary: Upgrade to Tika 1.22 when available
 Key: CONNECTORS-1622
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1622
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Tika extractor
Affects Versions: ManifoldCF 2.13
Reporter: Cihad Guzel
 Fix For: ManifoldCF next


Tika has released 1.22. Changes can be found from here: 
http://tika.apache.org/1.22/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Comment Edited] (CONNECTORS-1561) Upgrade to Tika 1.20 when available

[Cihad Guzel (Jira)]

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

Cihad Guzel edited comment on CONNECTORS-1561 at 9/1/19 9:18 AM:
-

Tika has released [http://tika.apache.org/1.22/|http://tika.apache.org/1.22/]


was (Author: cguzel):
Tika has released [http://tika.apache.org/1.22/|http://tika.apache.org/1.20/]

> Upgrade to Tika 1.20 when available
> ---
>
> Key: CONNECTORS-1561
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1561
> Project: ManifoldCF
>  Issue Type: Improvement
>Reporter: Tim Allison
>Priority: Major
>
> On TIKA-2776, a ManifoldCF user alerted us to a bad bug in Tika 1.19 and 
> 1.19.1 that causes tika-server to return 503 forever after it hits an OOM.  
> This is bad.  We'll be rolling a fix out in a week or two in Tika 1.20.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (CONNECTORS-1561) Upgrade to Tika 1.20 when available

[Cihad Guzel (Jira)]

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

Cihad Guzel commented on CONNECTORS-1561:
-

Tika has released [http://tika.apache.org/1.22/|http://tika.apache.org/1.20/]

> Upgrade to Tika 1.20 when available
> ---
>
> Key: CONNECTORS-1561
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1561
> Project: ManifoldCF
>  Issue Type: Improvement
>Reporter: Tim Allison
>Priority: Major
>
> On TIKA-2776, a ManifoldCF user alerted us to a bad bug in Tika 1.19 and 
> 1.19.1 that causes tika-server to return 503 forever after it hits an OOM.  
> This is bad.  We'll be rolling a fix out in a week or two in Tika 1.20.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: [ANNOUNCE] Cihad Guzel has joined the ManifoldCF project as a committer

[Cihad Guzel]

Hi All,

I have been committer and PMC in the Apache GORA project for a while. I
also have been contributed various Apache Projects for a while.

I am glad to be on board. I believe I will contribute more.

Kind Regards,
Cihad Guzel


Furkan KAMACI , 17 Ağu 2019 Cmt, 16:57 tarihinde
şunu yazdı:

> Hi,
>
> Congrats Cihad! Welcome on board.
>
> Kind Regards,
> Furkan KAMACI
>
> 17 Ağu 2019 Cmt, saat 16:55 tarihinde Karl Wright 
> şunu
> yazdı:
>
> > Cihad has had a long association with ManifoldCF and also Project Gora.
> > He's now agreed to join us as a committer.  Please welcome him warmly.
> >
> > Karl
> >
>

JDBC Connector Max Connection Size is set as hardcoded

[Cihad Guzel]

Hi Karl,

I create a new jdbc repository connection and I set "max connections "and
"Max avg fetches/min" from throttling tab on mfc-ui. Then, I reviewed
JDBCConnectionFactory.java and I have encountered some hardcoded parameters
as follow:

cp =_pool.addAlias(poolKey, driverClassName, dburl, userName,
password, 30, 30L)

Max connection is set as 30.

Are we sure that the parameters entered from the screen are used?

Regards,
Cihad Guzel

[jira] [Created] (CONNECTORS-1590) Resources should be closed in a finally block

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1590:
---

 Summary: Resources should be closed in a finally block
 Key: CONNECTORS-1590
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1590
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core
Affects Versions: ManifoldCF 2.12
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.13


{code:java}
public class DBInterfaceHSQLDB extends Database implements IDBInterface {
  ...
  try
  {
Connection c = 
DriverManager.getConnection(_localUrl+databaseName,userName,password);
Statement s = c.createStatement();
s.execute("SHUTDOWN");
c.close();
  }
  catch (Exception e)
  {
// Never any exception!
e.printStackTrace();
  }
{code}
Connections that implement the _Closeable_ interface or its super-interface, 
_AutoCloseable_, needs to be closed after use. That close call must be made in 
a *finally* block otherwise an exception could keep the call from being made.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CONNECTORS-1589) lrusize always null

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1589:
---

 Summary: lrusize always null
 Key: CONNECTORS-1589
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1589
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core
Affects Versions: ManifoldCF 2.12
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.13


{code:java}
public int getMaxLRUCount()
   ...
  String x = null; // 
JSKW.getProperty("cache."+objectClassName+".lrusize");
  if (x == null)
   ...
{code}

Change this condition so that it does not always evaluate to "true"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1589) lrusize always null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1589:

Description: 
{code:java}
public abstract class BaseDescription implements ICacheDescription {
...
public int getMaxLRUCount()
   ...
  String x = null; // 
JSKW.getProperty("cache."+objectClassName+".lrusize");
  if (x == null)
   ...
{code}

Change this condition so that it does not always evaluate to "true"

  was:
{code:java}
public int getMaxLRUCount()
   ...
  String x = null; // 
JSKW.getProperty("cache."+objectClassName+".lrusize");
  if (x == null)
   ...
{code}

Change this condition so that it does not always evaluate to "true"


> lrusize always null
> ---
>
> Key: CONNECTORS-1589
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1589
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Framework core
>Affects Versions: ManifoldCF 2.12
>Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
>
> {code:java}
> public abstract class BaseDescription implements ICacheDescription {
> ...
> public int getMaxLRUCount()
>...
>   String x = null; // 
> JSKW.getProperty("cache."+objectClassName+".lrusize");
>   if (x == null)
>...
> {code}
> Change this condition so that it does not always evaluate to "true"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1589) lrusize always null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1589:

Priority: Major  (was: Minor)

> lrusize always null
> ---
>
> Key: CONNECTORS-1589
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1589
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Framework core
>Affects Versions: ManifoldCF 2.12
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
>
> {code:java}
> public int getMaxLRUCount()
>...
>   String x = null; // 
> JSKW.getProperty("cache."+objectClassName+".lrusize");
>   if (x == null)
>...
> {code}
> Change this condition so that it does not always evaluate to "true"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1578) GSOC: Azure Storage Repository Connector

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1578:
-

Hi [~Rajiv],


 * Send a empty email to the appropriate address 
([dev-subscr...@manifoldcf.apache.org|mailto:dev-subscr...@manifoldcf.apache.org])
 ,
 * Ezmlm will send a reply,
 * Reply to the confirmation message to confirmation email address


You can see all manifoldcf mail lists from here: 
[https://manifoldcf.apache.org/en_US/mail.html#ManifoldCF%20Mailing%20Lists]

You can see more detail from: https://apache.org/foundation/mailinglists.html

> GSOC: Azure Storage Repository Connector
> 
>
> Key: CONNECTORS-1578
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1578
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: Azure Storage Repository Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Minor
>  Labels: gsoc2019
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Indexing and Migration capabilities 
> adding Azure Storage as a new repository connector for reading and indexing 
> contents from one or more repositories supported by ManifoldCF. In this way 
> we will help users on indexing and migrating contents from different data 
> sources from Azure Storage.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> You will find a technical description about all the references to the Azure 
> Java SDK on an existing issue on our JIRA:
> https://issues.apache.org/jira/browse/CONNECTORS-1577
>  
> We have a complete documentation on how to implement a Repository Connector:
> [http://manifoldcf.apache.org/release/release-2.12/en_US/writing-repository-connectors.html]
>  
> Take a look at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1588) Custom Jcifs Properties

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1588:

Flags: Patch

> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
> Attachments: CONNECTORS-1588
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1] 
> ; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
> checks the DNS server. In my opinion, the linux server doesn't recognize the 
> DNS server and threads are waiting for every file for access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I 
> have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another 
> example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1588) Custom Jcifs Properties

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1588:

Description: 
In some cases, "jcifs" is running slowly. In order to solve this problem, we 
need to set custom some properties. 
  
 For example; my problem was in my test environment: I have a windows server 
and an ubuntu server in same network in AWS EC2 Service. The windows server has 
Active Directory service, DNS Server and shared folder while the ubuntu server 
has some instance such as manifoldcf, an db instance and solr. 
  
 If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1] ; 
firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
checks the DNS server. In my opinion, the linux server doesn't recognize the 
DNS server and threads are waiting for every file for access to read.
  
 I suppose, WINS is used when accessing hosts on different subnets. So, I have 
set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
  
 Another suggestion for similar problem from [another 
example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
  
 We need to set custom resolveOrder variable.

^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 

  was:
In some cases, "jcifs" is running slowly. In order to solve this problem, we 
need to set custom some properties. 
  
 For example; my problem was in my test environment: I have a windows server 
and an ubuntu server in same network in AWS EC2 Service. The windows server has 
Active Directory service, DNS Server and shared folder while the ubuntu server 
has some instance such as manifoldcf, an db instance and solr. 
  
 If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It 
means^~[1]~^; firstly "jcifs" checks '/etc/hosts' files for linux/unix 
server'', then it checks the DNS server. In my opinion, the linux server 
doesn't recognize the DNS server and threads are waiting for every file for 
access to read.
  
 I suppose, WINS is used when accessing hosts on different subnets. So, I have 
set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
  
 Another suggestion for similar problem from [another 
example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
  
 We need to set custom resolveOrder variable.

^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 


> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>      Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1] 
> ; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
> checks the DNS server. In my opinion, the linux server doesn't recognize the 
> DNS server and threads are waiting for every file for access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I 
> have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another 
> example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1588) Custom Jcifs Properties

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1588:

Description: 
In some cases, "jcifs" is running slowly. In order to solve this problem, we 
need to set custom some properties. 
  
 For example; my problem was in my test environment: I have a windows server 
and an ubuntu server in same network in AWS EC2 Service. The windows server has 
Active Directory service, DNS Server and shared folder while the ubuntu server 
has some instance such as manifoldcf, an db instance and solr. 
  
 If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It 
means^~[1]~^; firstly "jcifs" checks '/etc/hosts' files for linux/unix 
server'', then it checks the DNS server. In my opinion, the linux server 
doesn't recognize the DNS server and threads are waiting for every file for 
access to read.
  
 I suppose, WINS is used when accessing hosts on different subnets. So, I have 
set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
  
 Another suggestion for similar problem from [another 
example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
  
 We need to set custom resolveOrder variable.

^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 

  was:
In some cases, "jcifs" is running slowly. In order to solve this problem, we 
need to set custom some properties. 
 
For example; my problem was in my test environment: I have a windows server and 
an ubuntu server in same network in AWS EC2 Service. The windows server has 
Active Directory service, DNS Server and shared folder while the ubuntu server 
has some instance such as manifoldcf, an db instance and solr. 
 
If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1]; 
firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
checks the DNS server. In my opinion, the linux server doesn't recognize the 
DNS server and threads are waiting for every file for access to read.
 
I suppose, WINS is used when accessing hosts on different subnets. So, I have 
set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
 
Another suggestion for similar problem from [another 
example|[https://stackoverflow.com/a/18837754]]: "-Djcifs.resolveOrder = DNS"
 
We need to set custom resolveOrder variable.


[1] [https://www.jcifs.org/src/docs/resolver.html] 


> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>      Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It 
> means^~[1]~^; firstly "jcifs" checks '/etc/hosts' files for linux/unix 
> server'', then it checks the DNS server. In my opinion, the linux server 
> doesn't recognize the DNS server and threads are waiting for every file for 
> access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I 
> have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another 
> example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1588) Custom Jcifs Properties

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1588:
-

I have a PR : https://github.com/apache/manifoldcf/pull/96

> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>    Reporter: Cihad Guzel
>Priority: Major
> Fix For: ManifoldCF 2.13
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>  
> For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>  
> If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1]; 
> firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
> checks the DNS server. In my opinion, the linux server doesn't recognize the 
> DNS server and threads are waiting for every file for access to read.
>  
> I suppose, WINS is used when accessing hosts on different subnets. So, I have 
> set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>  
> Another suggestion for similar problem from [another 
> example|[https://stackoverflow.com/a/18837754]]: "-Djcifs.resolveOrder = DNS"
>  
> We need to set custom resolveOrder variable.
> [1] [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CONNECTORS-1588) Custom Jcifs Properties

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1588:
---

 Summary: Custom Jcifs Properties
 Key: CONNECTORS-1588
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
 Project: ManifoldCF
  Issue Type: Improvement
  Components: JCIFS connector
Affects Versions: ManifoldCF 2.12
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.13


In some cases, "jcifs" is running slowly. In order to solve this problem, we 
need to set custom some properties. 
 
For example; my problem was in my test environment: I have a windows server and 
an ubuntu server in same network in AWS EC2 Service. The windows server has 
Active Directory service, DNS Server and shared folder while the ubuntu server 
has some instance such as manifoldcf, an db instance and solr. 
 
If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1]; 
firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
checks the DNS server. In my opinion, the linux server doesn't recognize the 
DNS server and threads are waiting for every file for access to read.
 
I suppose, WINS is used when accessing hosts on different subnets. So, I have 
set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
 
Another suggestion for similar problem from [another 
example|[https://stackoverflow.com/a/18837754]]: "-Djcifs.resolveOrder = DNS"
 
We need to set custom resolveOrder variable.


[1] [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: custom jcifs properties

[Cihad Guzel]

Hi Karl,

In some cases, "jcifs" is running slowly. In order to solve this problem,
we need to set custom some properties.

For example; my problem was in my test environment: I have a windows server
and an ubuntu server in same network in AWS EC2 Service. The windows server
has Active Directory service, DNS Server and shared folder while the ubuntu
server has some instance such as manifoldcf, an db instance and solr.

If the DNS settings are not defined on the ubuntu server, jcifs runs
slowly. Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It
means[1]; firstly "jcifs" checks '/etc/hosts' files for linux/unix
server'', then it checks the DNS server. In my opinion, the linux server
doesn't recognize the DNS server and threads are waiting for every file for
access to read.

I suppose, WINS is used when accessing hosts on different subnets. So, I
have set "jcifs.resolveOrder = WINS" and my problem has been FIXED.

I suppose, WINS is used when accessing hosts on different subnets.

Another suggestion for similar problem from another example[2]:
"-Djcifs.resolveOrder = DNS"

Finally; I suggest these changes:

Remove the line
(System.setProperty("jcifs.resolveOrder","LMHOSTS,DNS,WINS"); )  from
SharedDriveConnector.java

Add "-Djcifs.resolveOrder = LMHOSTS,DNS,WINS" to "start-options.env" file.

If you have been convinced about this, I can create a PR.

[1] https://www.jcifs.org/src/docs/resolver.html
[2] https://stackoverflow.com/a/18837754

Regards,
Cihad Guzel

Karl Wright , 24 Şub 2019 Paz, 19:20 tarihinde şunu
yazdı:

> These settings were provided by the developer of jcifs, Michael Allen.
> You have to really understand the protocol well before you should consider
> changing them in any way.
>
> Thanks,
> Karl
>
>
> On Sun, Feb 24, 2019 at 9:53 AM Cihad Guzel  wrote:
>
>> Hi,
>>
>> SharedDriveConnector have some hardcoded system properties as follow:
>>
>> static
>> {
>>   System.setProperty("jcifs.smb.client.soTimeout","15");
>>   System.setProperty("jcifs.smb.client.responseTimeout","12");
>>   System.setProperty("jcifs.resolveOrder","LMHOSTS,DNS,WINS");
>>   System.setProperty("jcifs.smb.client.listCount","20");
>>   System.setProperty("jcifs.smb.client.dfs.strictView","true");
>> }
>>
>> How can I override them when to start manifoldcf?
>>
>> It may be better to define these settings in the start-options.env file.
>>
>> Regards,
>> Cihad Guzel
>>
>

custom jcifs properties

[Cihad Guzel]

Hi,

SharedDriveConnector have some hardcoded system properties as follow:

static
{
  System.setProperty("jcifs.smb.client.soTimeout","15");
  System.setProperty("jcifs.smb.client.responseTimeout","12");
  System.setProperty("jcifs.resolveOrder","LMHOSTS,DNS,WINS");
  System.setProperty("jcifs.smb.client.listCount","20");
  System.setProperty("jcifs.smb.client.dfs.strictView","true");
}

How can I override them when to start manifoldcf?

It may be better to define these settings in the start-options.env file.

Regards,
Cihad Guzel

About publishing in mvn central repository

[Cihad Guzel]

Hi,

There aren't Manifoldcf jar packages in the mvn central repository. Maybe
they can be published in the repository? So we can add mcf-core or other
mfc jar packages to our projects as dependency.

What do you think about that?

[1] https://maven.apache.org/repository/guide-central-repository-upload.html


Regards,
Cihad Güzel

MFC in Mvn Repository

[Cihad Guzel]

Hi,

There isn't manifoldcf in mvn repository [1] . It would be nice to be added
in it ?

[1] https://mvnrepository.com/search?q=apache+manifoldcf
-- 
Cihad Güzel

Re: Exchange Repository Connector

[Cihad Guzel]

Hi dev,

I think so, current email connector does not meet to need. javamail api is
insufficient for exchange server crawl . Should be new connector for
exchange server.


26 May 2017 02:39 tarihinde "Karl Wright"  yazdı:

I have no objection, if you think you can implement such a connector
readily.

Karl


On Thu, May 25, 2017 at 7:21 PM, Furkan KAMACI 
wrote:

> Hi Team,
>
> Currently we have a "Individual Email Repository Connection" which works
on
> IMAP, IMAP-SSL, POP3, or POP3-SSL.
>
> However, I think that we should also have an Exchange Repository Connector
> which works over Exchange Web Services (EWS). Current implementation has
> some limitations and such a connector can overwhelm it.
>
> For example, we should create individual connections for all e-mail
> addresses if we want to index all e-mails within an Exchange Server. Also,
> we should know all passwords of corresponding e-mail addresses. However,
we
> can access to other mailboxes with a user via EWS if that user authorised
> to access it.
>
> So, what do you think about it?
>
> Kind Regards,
> Furkan KAMACI
>

email job is down

[Cihad Guzel]

Hi,

I have created an email job that runs continuously.  I have an error
downing my job for a reason. Because it is a job that needs to be
continuously run, errors should be handled  and the job shouldn't be
downed. Is there anything we can do about it?

 My error as follow:

ERROR 2017-04-25T14:25:44,475 (Seeding thread) - Exception tossed: Error
finding emails: * BYE JavaMail Exception: java.io.IOException: Connection
dropped by server?
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error finding
emails: * BYE JavaMail Exception: java.io.IOException: Connection dropped
by server?
at
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1721)
~[?:?]
at
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.addSeedDocuments(EmailConnector.java:335)
~[?:?]
at
org.apache.manifoldcf.crawler.system.SeedingThread.run(SeedingThread.java:150)
[classes/:?]
Caused by: javax.mail.MessagingException: * BYE JavaMail Exception:
java.io.IOException: Connection dropped by server?
at com.sun.mail.imap.IMAPFolder.open(IMAPFolder.java:961)
~[mail-1.4.5.jar:1.4.5]
at
org.apache.manifoldcf.crawler.connectors.email.EmailSession.openFolder(EmailSession.java:99)
~[?:?]
at
org.apache.manifoldcf.crawler.connectors.email.EmailConnector$OpenFolderThread.run(EmailConnector.java:1981)
~[?:?]
Caused by: com.sun.mail.iap.ConnectionException: * BYE JavaMail Exception:
java.io.IOException: Connection dropped by server?
at com.sun.mail.iap.Protocol.handleResult(Protocol.java:356)
~[mail-1.4.5.jar:1.4.5]
at com.sun.mail.imap.protocol.IMAPProtocol.examine(IMAPProtocol.java:886)
~[mail-1.4.5.jar:1.4.5]
at com.sun.mail.imap.IMAPFolder.open(IMAPFolder.java:925)
~[mail-1.4.5.jar:1.4.5]
at
org.apache.manifoldcf.crawler.connectors.email.EmailSession.openFolder(EmailSession.java:99)
~[?:?]
at
org.apache.manifoldcf.crawler.connectors.email.EmailConnector$OpenFolderThread.run(EmailConnector.java:1981)
~[?:?]

-- 
Cihad Güzel
Regards

[jira] [Created] (CONNECTORS-1420) Incorrect Date Comparison in Email Filtering

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1420:
---

 Summary: Incorrect Date Comparison in Email Filtering
 Key: CONNECTORS-1420
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1420
 Project: ManifoldCF
  Issue Type: Bug
  Components: Email connector
Affects Versions: ManifoldCF 2.7
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.8
 Attachments: CONNECTORS-1420.patch

Email date filtering  doesn't work correctly. 

{code}
  else if (findParameterName.equals(EmailConfig.EMAIL_START_DATE)) {
comparisonTerm = ComparisonTerm.LT;
  } else if (findParameterName.equals(EmailConfig.EMAIL_END_DATE)) {
comparisonTerm = ComparisonTerm.GT;
  }
{code}

It must be as follow: 

{code}
  else if (findParameterName.equals(EmailConfig.EMAIL_START_DATE)) {
comparisonTerm = ComparisonTerm.GT;
  } else if (findParameterName.equals(EmailConfig.EMAIL_END_DATE)) {
comparisonTerm = ComparisonTerm.LT;
  }
{code}

Reference: 
[ComparisonTerm|https://www.gnu.org/software/classpathx/javamail/javadoc/javax/mail/search/ComparisonTerm.html#LT]

{noformat}
ComparisonTerm.GT : The greater than operator.
ComparisonTerm.LT : The less than operator.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1420) Incorrect Date Comparison in Email Filtering

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1420:

Attachment: CONNECTORS-1420.patch

> Incorrect Date Comparison in Email Filtering
> 
>
> Key: CONNECTORS-1420
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1420
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1420.patch
>
>
> Email date filtering  doesn't work correctly. 
> {code}
>   else if (findParameterName.equals(EmailConfig.EMAIL_START_DATE)) {
> comparisonTerm = ComparisonTerm.LT;
>   } else if (findParameterName.equals(EmailConfig.EMAIL_END_DATE)) {
> comparisonTerm = ComparisonTerm.GT;
>   }
> {code}
> It must be as follow: 
> {code}
>   else if (findParameterName.equals(EmailConfig.EMAIL_START_DATE)) {
> comparisonTerm = ComparisonTerm.GT;
>   } else if (findParameterName.equals(EmailConfig.EMAIL_END_DATE)) {
> comparisonTerm = ComparisonTerm.LT;
>   }
> {code}
> Reference: 
> [ComparisonTerm|https://www.gnu.org/software/classpathx/javamail/javadoc/javax/mail/search/ComparisonTerm.html#LT]
> {noformat}
> ComparisonTerm.GT : The greater than operator.
> ComparisonTerm.LT : The less than operator.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1417:
-

Thanks @kwri...@metacarta.com ,
Thanks for suggestions @kamaci . 

> Error processing email: null
> 
>
> Key: CONNECTORS-1417
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1417.patch
>
>
> Email connector should support "multipart/alternative" mimetype.
> {noformat}
> FATAL 2017-04-26T00:37:23,800 (Worker thread '0') - Error tossed: null
> java.lang.NullPointerException
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> DEBUG 2017-04-26T00:37:24,860 (Worker thread '2') - Email: Processing 
> document identifier 
> 'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
> FATAL 2017-04-26T00:37:26,096 (Worker thread '2') - Error tossed: null
> java.lang.NullPointerException
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> DEBUG 2017-04-26T00:37:26,887 (Worker thread '1') - Email: Processing 
> document identifier 
> 'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
> FATAL 2017-04-26T00:37:28,019 (Worker thread '1') - Error tossed: null
> java.lang.NullPointerException
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> DEBUG 2017-04-26T00:37:28,961 (Worker thread '4') - Email: Processing 
> document identifier 
> 'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
> FATAL 2017-04-26T00:37:31,037 (Worker thread '4') - Error tossed: null
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1417:

Description: 
Email connector should support "multipart/alternative" mimetype.

{noformat}
FATAL 2017-04-26T00:37:23,800 (Worker thread '0') - Error tossed: null
java.lang.NullPointerException
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
DEBUG 2017-04-26T00:37:24,860 (Worker thread '2') - Email: Processing document 
identifier 
'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
FATAL 2017-04-26T00:37:26,096 (Worker thread '2') - Error tossed: null
java.lang.NullPointerException
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
DEBUG 2017-04-26T00:37:26,887 (Worker thread '1') - Email: Processing document 
identifier 
'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
FATAL 2017-04-26T00:37:28,019 (Worker thread '1') - Error tossed: null
java.lang.NullPointerException
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
DEBUG 2017-04-26T00:37:28,961 (Worker thread '4') - Email: Processing document 
identifier 
'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
FATAL 2017-04-26T00:37:31,037 (Worker thread '4') - Error tossed: null

{noformat}


  was:
Email connector should support "multipart/alternative" mimetype.

{noformat}
DEBUG 2017-04-24T21:30:31,079 (Seeding thread) - Email: Finding emails where 
'body' = 'test'
ERROR 2017-04-24T21:31:16,625 (Worker thread '23') - Email: Error processing 
email: null
javax.mail.FolderClosedException
at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
~[mail-1.4.5.jar:1.4.5]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
 [mcf-email-connector.jar:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 [mcf-email-connector.jar:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
ERROR 2017-04-24T21:31:16,639 (Worker thread '23') - Exception tossed: Error 
processing email: null
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error processing 
email: null
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1718)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:715)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
Caused by: javax.mail.FolderClosedException
at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
~[mail-1.4.5.jar:1.4.5]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 ~[?:?]
{noformat}



> Error processing email: null
> 
>
> Key: CONNECTORS-1417
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>    Affects Versions: ManifoldCF 2.7
>Reporter: Cihad Guzel
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1417.patch
>
>
> Email connector should support "multipart/alternative" mimetype.
> {noformat}
> FATAL 2017-04-26T00:37:23,800 (Worker thread '0') - Error tossed: null
> java.lang.NullPointerException
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> DEBUG 2017-04-26T00:37:24,860 (Worker thread '2') - Email: Processing 
> document identifier 
> 'test:<CADNgPDgBOLCnK-mobXia_Af-m4Qmc3p4Mr+k=jgy6o3-nb5...@mail.gmail.com>'
> FATAL 2017-04-26T00:37:26,096 (Worker thread '2') - Error tossed: null
> java.lang.NullPointerException
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailC

[jira] [Updated] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1417:

Attachment: CONNECTORS-1417.patch

> Error processing email: null
> 
>
> Key: CONNECTORS-1417
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1417.patch
>
>
> Email connector should support "multipart/alternative" mimetype.
> {noformat}
> DEBUG 2017-04-24T21:30:31,079 (Seeding thread) - Email: Finding emails where 
> 'body' = 'test'
> ERROR 2017-04-24T21:31:16,625 (Worker thread '23') - Email: Error processing 
> email: null
> javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> ERROR 2017-04-24T21:31:16,639 (Worker thread '23') - Exception tossed: Error 
> processing email: null
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error processing 
> email: null
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1718)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:715)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> Caused by: javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1417:

Attachment: (was: CONNECTORS-1417.patch)

> Error processing email: null
> 
>
> Key: CONNECTORS-1417
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
> Fix For: ManifoldCF 2.8
>
>
> Email connector should support "multipart/alternative" mimetype.
> {noformat}
> DEBUG 2017-04-24T21:30:31,079 (Seeding thread) - Email: Finding emails where 
> 'body' = 'test'
> ERROR 2017-04-24T21:31:16,625 (Worker thread '23') - Email: Error processing 
> email: null
> javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> ERROR 2017-04-24T21:31:16,639 (Worker thread '23') - Exception tossed: Error 
> processing email: null
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error processing 
> email: null
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1718)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:715)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> Caused by: javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1417:

Attachment: CONNECTORS-1417.patch

> Error processing email: null
> 
>
> Key: CONNECTORS-1417
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1417.patch
>
>
> Email connector should support "multipart/alternative" mimetype.
> {noformat}
> DEBUG 2017-04-24T21:30:31,079 (Seeding thread) - Email: Finding emails where 
> 'body' = 'test'
> ERROR 2017-04-24T21:31:16,625 (Worker thread '23') - Email: Error processing 
> email: null
> javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  [mcf-email-connector.jar:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> ERROR 2017-04-24T21:31:16,639 (Worker thread '23') - Exception tossed: Error 
> processing email: null
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error processing 
> email: null
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1718)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:715)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
> [classes/:?]
> Caused by: javax.mail.FolderClosedException
>   at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
> ~[mail-1.4.5.jar:1.4.5]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
>  ~[?:?]
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
>  ~[?:?]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CONNECTORS-1417) Error processing email: null

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1417:
---

 Summary: Error processing email: null
 Key: CONNECTORS-1417
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1417
 Project: ManifoldCF
  Issue Type: Bug
  Components: Email connector
Affects Versions: ManifoldCF 2.7
Reporter: Cihad Guzel
 Fix For: ManifoldCF 2.8


Email connector should support "multipart/alternative" mimetype.

{noformat}
DEBUG 2017-04-24T21:30:31,079 (Seeding thread) - Email: Finding emails where 
'body' = 'test'
ERROR 2017-04-24T21:31:16,625 (Worker thread '23') - Email: Error processing 
email: null
javax.mail.FolderClosedException
at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
~[mail-1.4.5.jar:1.4.5]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
 [mcf-email-connector.jar:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 [mcf-email-connector.jar:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
ERROR 2017-04-24T21:31:16,639 (Worker thread '23') - Exception tossed: Error 
processing email: null
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error processing 
email: null
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.handleMessagingException(EmailConnector.java:1718)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:715)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) 
[classes/:?]
Caused by: javax.mail.FolderClosedException
at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:639) 
~[mail-1.4.5.jar:1.4.5]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.extractBodyContent(EmailConnector.java:935)
 ~[?:?]
at 
org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:687)
 ~[?:?]
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1416) Email Filtering Date Format Should Be Changed

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1416:

Attachment: CONNECTORS-1416.patch

> Email Filtering Date Format Should Be Changed
> -
>
> Key: CONNECTORS-1416
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1416
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Email connector
>Affects Versions: ManifoldCF 2.7
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Trivial
> Fix For: ManifoldCF 2.8
>
> Attachments: CONNECTORS-1416.patch
>
>
> {code}
> public static final String EMAIL_FILTERING_DATE_FORMAT = "dd/MM/yy";
> {code}
> Email filtering date format should be changed from "dd/MM/yy" to "dd/MM/"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CONNECTORS-1416) Email Filtering Date Format Should Be Changed

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1416:
---

 Summary: Email Filtering Date Format Should Be Changed
 Key: CONNECTORS-1416
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1416
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Email connector
Affects Versions: ManifoldCF 2.7
Reporter: Cihad Guzel
Priority: Trivial
 Fix For: ManifoldCF 2.8


{code}
public static final String EMAIL_FILTERING_DATE_FORMAT = "dd/MM/yy";
{code}

Email filtering date format should be changed from "dd/MM/yy" to "dd/MM/"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

date format correction

[Cihad Guzel]

Hi Karl,

I had sent a patch[1] for email connector filter. However, I think we
should change date format  to "dd/MM/" from "dd/MM/yy".

-- 
Cihad Güzel

[1] -
https://github.com/apache/manifoldcf/pull/15/commits/d6af83a24c21dfa57e7a6084b7b9f30a94fce446

[jira] [Commented] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1408:
-

Thanks [~kwri...@metacarta.com], it is run succesfully

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.7
>
> Attachments: http-wire2.log, http-wire.log
>
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel edited comment on CONNECTORS-1408 at 4/15/17 7:55 PM:
--

Yes Karl, hasNullStreamName is set true


was (Author: cguzel):
Yes Karl, hasNullStreamName is true

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
> Attachments: http-wire2.log, http-wire.log
>
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1408:
-

Yes Karl, hasNullStreamName is true

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
> Attachments: http-wire2.log, http-wire.log
>
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1408:
-

{code}
boolean isMultipart = ((this.useMultiPartPost && SolrRequest.METHOD.POST == 
request.getMethod())
  || (streams != null && streams.size() > 1)) && !hasNullStreamName;

  LinkedList postOrPutParams = new LinkedList<>();
if (streams == null || isMultipart) {


{code}

"isMultipart" is false for this case. So, run always the else block. 

{code}
...
 else {
String pstr = toQueryString(wparams, false);
HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
request.getMethod() ?
new HttpPost(url + pstr) : new HttpPut(url + pstr);

{code}

The lines you said are in the "if" block.

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
> Attachments: http-wire2.log, http-wire.log
>
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cihad Guzel updated CONNECTORS-1408:

Attachment: http-wire2.log

I've attached new log file

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
> Attachments: http-wire2.log, http-wire.log
>
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel edited comment on CONNECTORS-1408 at 4/13/17 6:45 PM:
--

If I manually set true to "isMultipart" in code lines for testing , I have 
following error : "Error from server at http://localhost:8983/solr/lagomes: 
missing content stream" . 


was (Author: cguzel):
If I set true to "isMultipart" manually, I have following error : "Error from 
server at http://localhost:8983/solr/lagomes: missing content stream"

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>Reporter: Cihad Guzel
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1408:
-

If I set true to "isMultipart" manually, I have following error : "Error from 
server at http://localhost:8983/solr/lagomes: missing content stream"

> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>Reporter: Cihad Guzel
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1408:
-

{code}
boolean isMultipart = ((this.useMultiPartPost && SolrRequest.METHOD.POST == 
request.getMethod())
  || ((streams != null && streams.size() > 1)) && !hasNullStreamName);
{code}

"isMultipart" is "false" because of " !hasNullStreamName " is false.



> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>Reporter: Cihad Guzel
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

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

Cihad Guzel edited comment on CONNECTORS-1408 at 4/13/17 6:40 PM:
--

{code}
boolean isMultipart = ((this.useMultiPartPost && SolrRequest.METHOD.POST == 
request.getMethod())
  || (streams != null && streams.size() > 1)) && !hasNullStreamName;
{code}

"isMultipart" is "false" because of " !hasNullStreamName " is false.




was (Author: cguzel):
{code}
boolean isMultipart = ((this.useMultiPartPost && SolrRequest.METHOD.POST == 
request.getMethod())
  || ((streams != null && streams.size() > 1)) && !hasNullStreamName);
{code}

"isMultipart" is "false" because of " !hasNullStreamName " is false.



> Request-URI Too Long
> 
>
> Key: CONNECTORS-1408
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector, Solr 6.x component
>Affects Versions: ManifoldCF 2.6
>Reporter: Cihad Guzel
>
> I run email connector job and follow "Simple History" from UI. I see an error 
> as follow:
> {code}
> Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
> message:Request-URI Too Long
> {code}
> It is sent by Solr. 
> Solr logs say: 
> {code}
> HttpParser - URI is too large >8192
> {code}
> and 
> {code}
> HttpParser - bad HTTP parsed: 414 for 
> HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null}
>  
> {code}
> ManifoldCF ModifiedHttpSolrClient.java has following code:
> {code}
>  // It is has one stream, it is the post body, put the params in the URL
>   else {
> String pstr = toQueryString(wparams, false);
> HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
> request.getMethod() ?
> new HttpPost(url + pstr) : new HttpPut(url + pstr);
> {code}
> There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
> It contains email content. We have "URI is too large" error when email has 
> large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CONNECTORS-1408) Request-URI Too Long

[Cihad Guzel (JIRA)]

Cihad Guzel created CONNECTORS-1408:
---

 Summary: Request-URI Too Long
 Key: CONNECTORS-1408
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1408
 Project: ManifoldCF
  Issue Type: Bug
  Components: Email connector, Solr 6.x component
Affects Versions: ManifoldCF 2.6
Reporter: Cihad Guzel


I run email connector job and follow "Simple History" from UI. I see an error 
as follow:


{code}
Error from server at http://localhost:8983/solr/mycore: non ok status: 414, 
message:Request-URI Too Long
{code}
It is sent by Solr. 

Solr logs say: 
{code}
HttpParser - URI is too large >8192
{code}

and 
{code}
HttpParser - bad HTTP parsed: 414 for 
HttpChannelOverHttp@2b6931dd{r=0,c=false,a=IDLE,uri=null} 
{code}

ManifoldCF ModifiedHttpSolrClient.java has following code:

{code}
 // It is has one stream, it is the post body, put the params in the URL
  else {
String pstr = toQueryString(wparams, false);
HttpEntityEnclosingRequestBase postOrPut = SolrRequest.METHOD.POST == 
request.getMethod() ?
new HttpPost(url + pstr) : new HttpPut(url + pstr);

{code}

There is "pstr" field appended to the URL. "pstr" field have all Solr params. 
It contains email content. We have "URI is too large" error when email has 
large content.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1254) jetty dependencies is missing in jetty-runner

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1254:
-

mcf-parent/pom.xml : 

{code}

org.apache.maven.plugins
maven-compiler-plugin
2.3.2

  1.7
  1.7
  true
  128m
  512m

  
{code}

The target line shows that it is "1.7" . Should be "1.8" ?

> jetty dependencies is missing in jetty-runner
> -
>
> Key: CONNECTORS-1254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1254
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Framework core
>Affects Versions: ManifoldCF 2.2
>Reporter: Shinichiro Abe
>Assignee: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 2.3
>
> Attachments: CONNECTORS-1254.patch
>
>
> In current trunk, I run jetty-runner by mvn exec and operate crawler ui.
> Then I saw the following message on my console.
> {noformat}
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> ...
> {noformat}
> When I append lost jetty dependencies in jetty-runner' pom, that message 
> doesn't happen.
> It seems I've forgotten to do that on CONNECTORS-1050.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1396) Email processing multipart casting problem

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1396:
-

Thanks [~kwri...@metacarta.com], the problem resolved.

> Email processing multipart casting problem
> --
>
> Key: CONNECTORS-1396
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1396
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Email connector
>Affects Versions: ManifoldCF 2.6
>    Reporter: Cihad Guzel
>Assignee: Karl Wright
> Fix For: ManifoldCF 2.7
>
> Attachments: CONNECTORS-1396.patch
>
>
> I try email connector with exchange server 2013. I have some errors.
> If I select the "Encoding of Attachment" from metadata tab of email connector:
> {code}
> DEBUG 2017-03-08 19:31:13,646 (Worker thread '1') - Email: Processing 
> document identifier 
> 'INBOX:<6bc4ff202f884bc396aab70cdfd01...@exchange.mydomain.com>'
> FATAL 2017-03-08 19:31:18,243 (Worker thread '1') - Error tossed: 
> java.lang.String cannot be cast to javax.mail.Multipart
> java.lang.ClassCastException: java.lang.String cannot be cast to 
> javax.mail.Multipart
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:631)
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399)
> {code}
> If I select the "MIME type of attachment" from metadata tab of email 
> connector:
> {code}
> DEBUG 2017-03-08 19:37:40,026 (Worker thread '40') - Email: Processing 
> document identifier 
> 'INBOX:<173298b91b9f4d439aeb14169b306...@exchange..mydomain.com>'
> FATAL 2017-03-08 19:37:40,633 (Worker thread '30') - Error tossed: 
> java.lang.String cannot be cast to javax.mail.Multipart
> java.lang.ClassCastException: java.lang.String cannot be cast to 
> javax.mail.Multipart
>   at 
> org.apache.manifoldcf.crawler.connectors.email.EmailConnector.processDocuments(EmailConnector.java:651)
>   at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399)
> {code}
> I saw similar issue : https://issues.apache.org/jira/browse/CONNECTORS-1260



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CONNECTORS-1254) jetty dependencies is missing in jetty-runner

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on CONNECTORS-1254:
-

ı use trunk and I have same error: 

{code}
[main] INFO org.eclipse.jetty.server.Server - Started @8871ms
Jetty started.
Starting crawler...
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
{code}

> jetty dependencies is missing in jetty-runner
> -
>
> Key: CONNECTORS-1254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1254
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Framework core
>Affects Versions: ManifoldCF 2.2
>Reporter: Shinichiro Abe
>Assignee: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 2.3
>
> Attachments: CONNECTORS-1254.patch
>
>
> In current trunk, I run jetty-runner by mvn exec and operate crawler ui.
> Then I saw the following message on my console.
> {noformat}
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> ...
> {noformat}
> When I append lost jetty dependencies in jetty-runner' pom, that message 
> doesn't happen.
> It seems I've forgotten to do that on CONNECTORS-1050.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (CONNECTORS-1254) jetty dependencies is missing in jetty-runner

[Cihad Guzel (JIRA)]

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

Cihad Guzel edited comment on CONNECTORS-1254 at 3/30/17 2:00 PM:
--

I use trunk and I have same error: 

{code}
[main] INFO org.eclipse.jetty.server.Server - Started @8871ms
Jetty started.
Starting crawler...
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
{code}


was (Author: cguzel):
ı use trunk and I have same error: 

{code}
[main] INFO org.eclipse.jetty.server.Server - Started @8871ms
Jetty started.
Starting crawler...
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
WARN: Unknown target VM 1.7 ignored.
WARN: Unknown source VM 1.7 ignored.
{code}

> jetty dependencies is missing in jetty-runner
> -
>
> Key: CONNECTORS-1254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1254
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Framework core
>Affects Versions: ManifoldCF 2.2
>Reporter: Shinichiro Abe
>Assignee: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 2.3
>
> Attachments: CONNECTORS-1254.patch
>
>
> In current trunk, I run jetty-runner by mvn exec and operate crawler ui.
> Then I saw the following message on my console.
> {noformat}
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> WARN: Unknown target VM 1.7 ignored.
> WARN: Unknown source VM 1.7 ignored.
> ...
> {noformat}
> When I append lost jetty dependencies in jetty-runner' pom, that message 
> doesn't happen.
> It seems I've forgotten to do that on CONNECTORS-1050.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)