[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927614#comment-16927614 ] Karl Wright commented on CONNECTORS-1566: - [~schuch], there are no legal problems with including it. The only code that would at all raise concerns would be the wsdl files, but it turns out those are considered interface specifications, and a court case about 5 years ago made those non-copyrightable. Apache Legal signed off on that for the SharePoint connector, which also includes wsdls. So please go ahead and make sure everything I overlooked is fixed. > Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector > -- > > Key: CONNECTORS-1566 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1566 > Project: ManifoldCF > Issue Type: Task > Components: LiveLink connector >Affects Versions: ManifoldCF 2.12 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.14 > > Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png > > > LAPI is being deprecated. We need to develop a replacement for it using the > ContentServer Web Services API. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927607#comment-16927607
]
Markus Schuch commented on CONNECTORS-1566:
---
Ok, will address both connection checks.
In the mean time i fixed the maven build. I hesitated to add the csws module to
the maven reactor. Was it not included as a module due to legal implications?
Or can i just add it to the list of connector modules in {{connectors/pom.xml}}.
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927563#comment-16927563 ] Karl Wright commented on CONNECTORS-1566: - Sounds like a bug, yes. Probably same fix should be included in the repository check() function. > Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector > -- > > Key: CONNECTORS-1566 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1566 > Project: ManifoldCF > Issue Type: Task > Components: LiveLink connector >Affects Versions: ManifoldCF 2.12 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.14 > > Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png > > > LAPI is being deprecated. We need to develop a replacement for it using the > ContentServer Web Services API. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927529#comment-16927529
]
Markus Schuch commented on CONNECTORS-1566:
---
The connection check of the authority connector requires that a user named
{{Admin}} does not exist to report "Connection Working". Is that really
intended?
{code}
final User user = cswsSession.getUserByLoginName("Admin");
if (user == null) {
return super.check();
}
return "Connection failed: User authentication failed";
{code}
I propose to use {{this.serverUsername}} and check for {{!= null}}.
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927501#comment-16927501 ] Karl Wright commented on CONNECTORS-1566: - Thanks for the confirmation. I've committed a fix to trunk for the "only some services are needed" issue. I'll keep an eye out for the rest of your commits. Please be sure to include these wsdls in the .xml configuration file so they do not need to be fetched from the server. I patched the ones already included so they would operate in a file-based environment, FWIW. > Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector > -- > > Key: CONNECTORS-1566 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1566 > Project: ManifoldCF > Issue Type: Task > Components: LiveLink connector >Affects Versions: ManifoldCF 2.12 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.14 > > Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png > > > LAPI is being deprecated. We need to develop a replacement for it using the > ContentServer Web Services API. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch edited comment on CONNECTORS-1566 at 9/11/19 11:14 AM:
-
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
was (Author: schuchm):
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch edited comment on CONNECTORS-1566 at 9/11/19 11:14 AM:
-
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{Connection failed: Malformed URL: null}}. This happens because
{{CswsSession}} tries to construct all service stubs, but some URLs are
{{null}} (services not needed in the authority connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
was (Author: schuchm):
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{Connection failed: Malformed URL: null. This happens because
{{CswsSession}} tries to construct all service stubs, but some URLs are
{{null}} (services not needed in the authority connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch edited comment on CONNECTORS-1566 at 9/11/19 11:14 AM:
-
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
was (Author: schuchm):
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch edited comment on CONNECTORS-1566 at 9/11/19 11:14 AM:
-
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{Connection failed: Malformed URL: null. This happens because
{{CswsSession}} tries to construct all service stubs, but some URLs are
{{null}} (services not needed in the authority connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
was (Author: schuchm):
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch commented on CONNECTORS-1566:
---
* The only situation we could reproduce a {{Failed to create service}} was the
connection refused scenario, as you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error \{{}}. This happens because {{CswsSession}} tries to construct all
service stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927488#comment-16927488
]
Markus Schuch edited comment on CONNECTORS-1566 at 9/11/19 11:13 AM:
-
* The only situation where we could reproduce a {{Failed to create service}}
was the connection refused scenario, like you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error {{}}. This happens because {{CswsSession}} tries to construct all service
stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
was (Author: schuchm):
* The only situation we could reproduce a {{Failed to create service}} was the
connection refused scenario, as you did as well
* We successfully established a connection with SSL. The strange thing is that
our livelink instance needs different WSDLs. This might be related to
differences due to the used authentication mechanism. We have one that is
called {{OTDS}}, a single-sign-on authentication mechanism. I hopefully can
provide those WSDLs, later today. Maybe we can add both variants to the
connector and somehow build a switch.
* Another issue we found: When creating an authority connection, we get the
error \{{}}. This happens because {{CswsSession}} tries to construct all
service stubs, but some URLs are {{null}} (services not needed in the authority
connector)
* The maven build fails. There are missing CXF dependencies. I will commit a
fix for that right away
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
Re: Error:-Missing Resource Bundle
The translations bundle error is completely harmless. It will not prevent anything from starting. Karl On Wed, Sep 11, 2019 at 3:23 AM Priya Arora wrote: > *Regarding resource bundle exception :- * > No i have not changed anything from default configuration. > My question here is :- > "This only means there are no specific en_GB translations for the UI. It > is > harmless." > Being this an error, does it allow manifoldcf to work smoothly., while > using single process(apache-manifoldcf-2.13/example/') and multi process( > 'apache-manifoldcf-2.13/multiprocess-zk-example') both? > > This mail chain does not include any Hardware configurations' > > Thanks > Priya > > On Wed, Sep 11, 2019 at 12:46 PM Karl Wright wrote: > > > 'Because when i tried launching manifoldcf multiprocess with > > zookeeper, it didnt allow manifold UI to load. ' > > > > WHAT didn't allow manifold UI to load??? > > > > If you are using a multiprocess deployment, the process that isn't > getting > > enough memory is the java-agents process. Changing the UI process > > parameters makes no sense. > > > > Perhaps instead of telling us your hardware configuration, you tell us > > precisely how you set up your manifoldcf instance. What example are you > > basing it on? What have you changed from the defaults for the particular > > example? > > > > Thanks, > > Karl > > > > > > On Wed, Sep 11, 2019 at 2:56 AM Priya Arora wrote: > > > > > Does that means this Error allows ManifoldCF to run smoothly on single > > > process. Because when i tried launching manifoldcf multiprocess with > > > zookeeper, it didnt allow manifold UI to load. > > > Thanks > > > Priya > > > > > > On Wed, Sep 11, 2019 at 12:09 PM Karl Wright > wrote: > > > > > > > Hi, > > > > This only means there are no specific en_GB translations for the UI. > > It > > > is > > > > harmless. > > > > > > > > Karl > > > > > > > > > > > > On Wed, Sep 11, 2019 at 2:36 AM Priya Arora > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > While ingesting records to Elastic Search via manifoldCF(2.13) > > > crawler. I > > > > > am facing this issue , > > > > > ERROR 2019-09-11T05:44:49,641 (qtp307829448-510) - Missing resource > > > > bundle > > > > > 'org.apache.manifoldcf.ui.i18n.common' for locale 'en_GB': Can't > find > > > > > bundle for base name org.apache.manifoldcf.ui.i18n.common, locale > > > en_GB; > > > > > trying en > > > > > java.util.MissingResourceException: Can't find bundle for base name > > > > > org.apache.manifoldcf.ui.i18n.common, locale en_GB > > > > > at > > > > > > > > > > > > > > > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1581) > > > > > ~[?:1.8.0_222] > > > > > > > > > > I also research ed its resolution on net, but no help till now. > > > > > Can anybody suggest something, do i need to add some file, as of > now > > i > > > > > have these files in my project setup. > > > > > > > > > > [image: image.png] > > > > > > > > > > Thanks and regards > > > > > Priya > > > > > > > > > > > > > > >
Re: Error:-Missing Resource Bundle
'Because when i tried launching manifoldcf multiprocess with zookeeper, it didnt allow manifold UI to load. ' WHAT didn't allow manifold UI to load??? If you are using a multiprocess deployment, the process that isn't getting enough memory is the java-agents process. Changing the UI process parameters makes no sense. Perhaps instead of telling us your hardware configuration, you tell us precisely how you set up your manifoldcf instance. What example are you basing it on? What have you changed from the defaults for the particular example? Thanks, Karl On Wed, Sep 11, 2019 at 2:56 AM Priya Arora wrote: > Does that means this Error allows ManifoldCF to run smoothly on single > process. Because when i tried launching manifoldcf multiprocess with > zookeeper, it didnt allow manifold UI to load. > Thanks > Priya > > On Wed, Sep 11, 2019 at 12:09 PM Karl Wright wrote: > > > Hi, > > This only means there are no specific en_GB translations for the UI. It > is > > harmless. > > > > Karl > > > > > > On Wed, Sep 11, 2019 at 2:36 AM Priya Arora wrote: > > > > > Hi All, > > > > > > While ingesting records to Elastic Search via manifoldCF(2.13) > crawler. I > > > am facing this issue , > > > ERROR 2019-09-11T05:44:49,641 (qtp307829448-510) - Missing resource > > bundle > > > 'org.apache.manifoldcf.ui.i18n.common' for locale 'en_GB': Can't find > > > bundle for base name org.apache.manifoldcf.ui.i18n.common, locale > en_GB; > > > trying en > > > java.util.MissingResourceException: Can't find bundle for base name > > > org.apache.manifoldcf.ui.i18n.common, locale en_GB > > > at > > > > > > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1581) > > > ~[?:1.8.0_222] > > > > > > I also research ed its resolution on net, but no help till now. > > > Can anybody suggest something, do i need to add some file, as of now i > > > have these files in my project setup. > > > > > > [image: image.png] > > > > > > Thanks and regards > > > Priya > > > > > >
[jira] [Commented] (CONNECTORS-1566) Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927302#comment-16927302
]
Karl Wright commented on CONNECTORS-1566:
-
More analysis:
Locally when I run this WITHOUT the meta-inf that I've been including in the
jar, I get:
{code}
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'http://localhost:2099/cws/Authentication.svc'.:
java.net.ConnectException: Connection refused: connect
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:266)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:165)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 36 more
Caused by: java.net.ConnectException: Connection refused: connect
{code}
This makes sense since I am not running a livelink instance here.
> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> --
>
> Key: CONNECTORS-1566
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
> Project: ManifoldCF
> Issue Type: Task
> Components: LiveLink connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.14
>
> Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated. We need to develop a replacement for it using the
> ContentServer Web Services API.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
Re: Error:-Missing Resource Bundle
Hi, This only means there are no specific en_GB translations for the UI. It is harmless. Karl On Wed, Sep 11, 2019 at 2:36 AM Priya Arora wrote: > Hi All, > > While ingesting records to Elastic Search via manifoldCF(2.13) crawler. I > am facing this issue , > ERROR 2019-09-11T05:44:49,641 (qtp307829448-510) - Missing resource bundle > 'org.apache.manifoldcf.ui.i18n.common' for locale 'en_GB': Can't find > bundle for base name org.apache.manifoldcf.ui.i18n.common, locale en_GB; > trying en > java.util.MissingResourceException: Can't find bundle for base name > org.apache.manifoldcf.ui.i18n.common, locale en_GB > at > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1581) > ~[?:1.8.0_222] > > I also research ed its resolution on net, but no help till now. > Can anybody suggest something, do i need to add some file, as of now i > have these files in my project setup. > > [image: image.png] > > Thanks and regards > Priya >
Re: Unexpected HTTP result code: -1: null
"I have -Xms1024m ,-Xmx1024m memory allocated in
*start-options.env.unix, start-options.env.win file.*
Also Configuration:-
1) *For Crawler server *- 16 GB RAM and 8-Core Intel(R) Xeon(R) CPU
E5-2660v3 @ 2.60GHz and"
What is "crawler server"?
You said "single process example", right? That means there is one MCF
process. That process is running out of memory. You are giving it one
gigabyte. It is not enough. Add more memory to the -Xmx setting in
start-options.
Karl
On Wed, Sep 11, 2019 at 1:43 AM Priya Arora wrote:
> Hi all,
>
> Manifold CF crashes.
> Raising this issue again, after enhancing memory and otherwise, still
> facing the same issue. TRied every possible solution If anybody can help ,
> please suggest me some solution.
> *Problem:-* Manifoldcf crashes while crawling data from an intranet URL
> hinting out below error in logs:-
>
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.HashMap.resize(HashMap.java:704)
> at java.util.HashMap.putVal(HashMap.java:629)
> at java.util.HashMap.put(HashMap.java:612)
> at
> org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndEx
>
> ecute(CacheManager.java:135)
> at
> org.apache.manifoldcf.agents.transformationconnection.TransformationC
>
>
>
> onnectionManager.loadMultipleInternal(TransformationConnectionManager.java:265)
> at
> org.apache.manifoldcf.agents.transformationconnection.TransformationC
>
> onnectionManager.loadMultiple(TransformationConnectionManager.java:246)
> agents process could not start - shutting down
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at
> org.postgresql.jdbc.PgConnection.createStatement(PgConnection.java:11
>
> 93)
> at
> org.postgresql.jdbc.PgConnection.createStatement(PgConnection.java:15
>
> 77)
> at
> org.postgresql.jdbc.PgConnection.createStatement(PgConnection.java:36
>
> 7)
> at
> org.apache.manifoldcf.core.database.Database.execute(Database.java:87
>
> 3)
> at
> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(D
>
> atabase.java:696)
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> [Thread-491] INFO org.eclipse.jetty.server.ServerConnector - Stopped
> ServerConne
>ctor@3a4621bd{HTTP/1.1}{0.0.0.0:8345}
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> [Thread-491] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Stopped o.e.
>
> j.w.WebAppContext@6a57ae10{/mcf-api-service,file:/tmp/jetty-0.0.0.0-8345-mcf-api
>
>
>
> -service.war-_mcf-api-service-any-2010273384908625074.dir/webapp/,UNAVAILABLE}{/
>
>usr/share/manifoldcf/example/./../web/war/mcf-api-service.war}
> [Thread-491] INFO org.eclipse.jetty.server.handler.ContextHandler -
> Stopped o.e.
>
> j.w.WebAppContext@51c693d{/mcf-authority-service,file:/tmp/jetty-0.0.0.0-8345-mc
>
>
>
> f-authority-service.war-_mcf-authority-service-any-1431262612693374489.dir/webap
>
>
>
> p/,UNAVAILABLE}{/usr/share/manifoldcf/example/./../web/war/mcf-authority-service
>
>.war}
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: Java heap space
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: Java heap space
> agents process ran out of memory - shutting down
> java.lang.OutOfMemoryError: Java heap space
> Exception in thread "PostgreSQL-JDBC-SharedTimer-1"
> java.lang.OutOfMemoryError:
>
> Java heap space
>
> All configuration are:-
> I have -Xms1024m ,-Xmx1024m memory allocated in
> *start-options.env.unix, start-options.env.win file.*
> Also Configuration:-
> 1) *For Crawler server *- 16 GB RAM and 8-Core Intel(R) Xeon(R) CPU
> E5-2660v3 @ 2.60GHz and
>
> 2) *For Elasticsearch server* - 48GB and 16-Core Intel(R) Xeon(R) CPU
> E5-2660 v3 @ 2.60GHz and i am using postgres as database.
>
> 3) Database as PostgreSQL
> 4) No of worker threads:-20.
> 5) manifold Version :-2.13
>
> Can anybody please suggest some solution to get rid of this error and
> crash, as whenever this istutaion comes, manifoldCF UI results me this:_
> [image: image.png]
>
> Any suggestion would be highly appreciated.
>
> Thanks
> Priya
>
> On Fri, Aug 16, 2019 at 6:41 PM Priya Arora wrote:
>
>> Sure I will try to do that.. and will get back to you
>>
>> Sent from my iPhone
>>
>> > On 16-Aug-2019, at 6:23 PM, Michael Cizmar
>> wrote:
>> >
>> > Priya - Was this right?
>> >
>> > 48GB and 1-Core Intel(R) Xeon(R) CPU
>> >
>> > While not directly related to an out of memory issue, you should have
>> more
>> > cores allocated to ES.
>> >
>> >> On Fri, Aug 16, 2019 at 1:09 AM Priya Arora
>> wrote:
>> >>
>> >> *Existing
Error:-Missing Resource Bundle
Hi All, While ingesting records to Elastic Search via manifoldCF(2.13) crawler. I am facing this issue , ERROR 2019-09-11T05:44:49,641 (qtp307829448-510) - Missing resource bundle 'org.apache.manifoldcf.ui.i18n.common' for locale 'en_GB': Can't find bundle for base name org.apache.manifoldcf.ui.i18n.common, locale en_GB; trying en java.util.MissingResourceException: Can't find bundle for base name org.apache.manifoldcf.ui.i18n.common, locale en_GB at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1581) ~[?:1.8.0_222] I also research ed its resolution on net, but no help till now. Can anybody suggest something, do i need to add some file, as of now i have these files in my project setup. [image: image.png] Thanks and regards Priya
