[jira] [Updated] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-1145: Attachment: CONNECTORS-1145.patch This patch addresses the problem. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-1145.patch Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CONNECTORS-1140) improve Japanese End User Manual
[ https://issues.apache.org/jira/browse/CONNECTORS-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-1140: --- Assignee: Karl Wright (was: Mingchun Zhao) improve Japanese End User Manual Key: CONNECTORS-1140 URL: https://issues.apache.org/jira/browse/CONNECTORS-1140 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: KOIZUMI Satoru Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: end-user-documentation.xml.patch Thank you for your Japanese translation. I have made a patch to make it more fluent. I will explain each change if you need. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[
https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright reopened CONNECTORS-1145:
-
From Michael:
I'm running into a hanging issue when trying to use the new 2.0 release. Using
the multiprocess-file-example, I do the following:
1. start-database.sh
2. initialize.sh
3. start-webapps.sh
4. start-agents.sh
Then, go to the mcf-crawler-ui, create a new Null output connection, and try to
save it. My browser then just spins (I've given it up to 30 minutes, and
nothing happens).
A stack trace shows the Jetty process hanging here:
{code}
qtp638408253-18 prio=5 tid=0x7fdb3cc3 nid=0x7403 in Object.wait()
[0x00012366f000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00011bdf15a0 (a java.lang.Integer)
at org.apache.manifoldcf.core.system.ManifoldCF.sleep(ManifoldCF.java:1259)
- locked 0x00011bdf15a0 (a java.lang.Integer)
at
org.apache.manifoldcf.core.lockmanager.LockObject.obtainGlobalNonExWriteLock(LockObject.java:245)
at
org.apache.manifoldcf.core.lockmanager.LockObject.enterNonExWriteLock(LockObject.java:190)
- locked 0x00011b30c440 (a
org.apache.manifoldcf.core.lockmanager.FileLockObject)
at
org.apache.manifoldcf.core.lockmanager.LockGate.enterNonExWriteLock(LockGate.java:219)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWrite(BaseLockManager.java:959)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWriteLock(BaseLockManager.java:731)
at
org.apache.manifoldcf.core.lockmanager.LockManager.enterNonExWriteLock(LockManager.java:276)
at
org.apache.manifoldcf.agents.outputconnection.OutputConnectionManager.save(OutputConnectionManager.java:301)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:1047)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
{code}
These steps work fine in the 1.7.2 release. Also, the single process example
work as expected with these steps.
Did I miss a step needed in the 2.0 release with the 'file' example?
multiprocess-file-example blocks in configuration on Windows
Key: CONNECTORS-1145
URL: https://issues.apache.org/jira/browse/CONNECTORS-1145
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0
Environment: Windows 2012
Reporter: Andreas Baumann
Assignee: Karl Wright
Fix For: ManifoldCF 1.9, ManifoldCF 2.1
Saving a configuration setting (for instance a new Output Connector) hangs
forevert. Inspecting the problem with the 'Process Monitor' shows me
that there is an infinite loop while locking and reading a file in the
syncharea.
I disabled Windows Search and virus scanners, so far no luck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277999#comment-14277999 ] Karl Wright commented on CONNECTORS-1145: - I was able to reproduce this on Windows 7 this evening. Looking into the reason why. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-1145: Fix Version/s: ManifoldCF 2.1 ManifoldCF 1.9 multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[
https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277996#comment-14277996
]
Karl Wright edited comment on CONNECTORS-1145 at 1/15/15 1:09 AM:
--
From Michael Wilken:
I'm running into a hanging issue when trying to use the new 2.0 release. Using
the multiprocess-file-example, I do the following:
1. start-database.sh
2. initialize.sh
3. start-webapps.sh
4. start-agents.sh
Then, go to the mcf-crawler-ui, create a new Null output connection, and try to
save it. My browser then just spins (I've given it up to 30 minutes, and
nothing happens).
A stack trace shows the Jetty process hanging here:
{code}
qtp638408253-18 prio=5 tid=0x7fdb3cc3 nid=0x7403 in Object.wait()
[0x00012366f000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00011bdf15a0 (a java.lang.Integer)
at org.apache.manifoldcf.core.system.ManifoldCF.sleep(ManifoldCF.java:1259)
- locked 0x00011bdf15a0 (a java.lang.Integer)
at
org.apache.manifoldcf.core.lockmanager.LockObject.obtainGlobalNonExWriteLock(LockObject.java:245)
at
org.apache.manifoldcf.core.lockmanager.LockObject.enterNonExWriteLock(LockObject.java:190)
- locked 0x00011b30c440 (a
org.apache.manifoldcf.core.lockmanager.FileLockObject)
at
org.apache.manifoldcf.core.lockmanager.LockGate.enterNonExWriteLock(LockGate.java:219)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWrite(BaseLockManager.java:959)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWriteLock(BaseLockManager.java:731)
at
org.apache.manifoldcf.core.lockmanager.LockManager.enterNonExWriteLock(LockManager.java:276)
at
org.apache.manifoldcf.agents.outputconnection.OutputConnectionManager.save(OutputConnectionManager.java:301)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:1047)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
{code}
These steps work fine in the 1.7.2 release. Also, the single process example
work as expected with these steps.
Did I miss a step needed in the 2.0 release with the 'file' example?
was (Author: kwri...@metacarta.com):
From Michael:
I'm running into a hanging issue when trying to use the new 2.0 release. Using
the multiprocess-file-example, I do the following:
1. start-database.sh
2. initialize.sh
3. start-webapps.sh
4. start-agents.sh
Then, go to the mcf-crawler-ui, create a new Null output connection, and try to
save it. My browser then just spins (I've given it up to 30 minutes, and
nothing happens).
A stack trace shows the Jetty process hanging here:
{code}
qtp638408253-18 prio=5 tid=0x7fdb3cc3 nid=0x7403 in Object.wait()
[0x00012366f000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00011bdf15a0 (a java.lang.Integer)
at org.apache.manifoldcf.core.system.ManifoldCF.sleep(ManifoldCF.java:1259)
- locked 0x00011bdf15a0 (a java.lang.Integer)
at
org.apache.manifoldcf.core.lockmanager.LockObject.obtainGlobalNonExWriteLock(LockObject.java:245)
at
org.apache.manifoldcf.core.lockmanager.LockObject.enterNonExWriteLock(LockObject.java:190)
- locked 0x00011b30c440 (a
org.apache.manifoldcf.core.lockmanager.FileLockObject)
at
org.apache.manifoldcf.core.lockmanager.LockGate.enterNonExWriteLock(LockGate.java:219)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWrite(BaseLockManager.java:959)
at
org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterNonExWriteLock(BaseLockManager.java:731)
at
org.apache.manifoldcf.core.lockmanager.LockManager.enterNonExWriteLock(LockManager.java:276)
at
org.apache.manifoldcf.agents.outputconnection.OutputConnectionManager.save(OutputConnectionManager.java:301)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:1047)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
{code}
These steps work fine in the 1.7.2 release. Also, the single process example
work as expected with these steps.
Did I miss a step needed in the 2.0 release with the 'file' example?
multiprocess-file-example blocks in configuration on Windows
Key: CONNECTORS-1145
URL: https://issues.apache.org/jira/browse/CONNECTORS-1145
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0
Environment: Windows 2012
Reporter: Andreas Baumann
Assignee: Karl Wright
Fix For: ManifoldCF 1.9, ManifoldCF 2.1
Saving a configuration setting (for instance a
[jira] [Resolved] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-1145. - Resolution: Fixed r1651921 (trunk) r1651922 (dev_1x) multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-1145.patch Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1140) improve Japanese End User Manual
[ https://issues.apache.org/jira/browse/CONNECTORS-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278309#comment-14278309 ] Mingchun Zhao commented on CONNECTORS-1140: --- Koizumi, thank you for your nice patch. Karl, thank you putting this into trunk,dev_1x(I noticed this just now). improve Japanese End User Manual Key: CONNECTORS-1140 URL: https://issues.apache.org/jira/browse/CONNECTORS-1140 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: KOIZUMI Satoru Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: end-user-documentation.xml.patch Thank you for your Japanese translation. I have made a patch to make it more fluent. I will explain each change if you need. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
Andreas Baumann created CONNECTORS-1145: --- Summary: multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 2.0, ManifoldCF 1.8 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1143) Problem with cached versions of e.g. a repository connection
[ https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277027#comment-14277027 ] Karl Wright commented on CONNECTORS-1143: - Hi David, ManifoldCF does cache connection instances, and is very robust about knowing when to flush those. You should not need to do anything other than make sure everything is correctly configured. The first thing to do is to verify that there's a caching failure. To do that, simply shut down your agents process(es), and start them up again. If you are running the single-process example, then shut the whole thing down and start it up again. See if your jobs succeed on the same documents they failed on before. If they do, then caching is to blame, and we can do some research to figure out why. If they continue to fail, then please remember that the connection checker cannot check *all* possible situations for *all* documents you intend to crawl. It's a basic sanity check only, for most connection types. In that case, please supply more details and I can help determine what the issue is. Thanks! Problem with cached versions of e.g. a repository connection Key: CONNECTORS-1143 URL: https://issues.apache.org/jira/browse/CONNECTORS-1143 Project: ManifoldCF Issue Type: Bug Reporter: Daniel Aschauer I have some issues when i change settings in repository connection: I had to change the password for my connection (JIRA), i review the connection and it works. However the related job(s) keep failing because of an unautorized error. What is more i created a new job with the repository connection and it failed too. I don't know how these things are kept cached in Manifold. Is this a bug or do I have to do some regular cleanup?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
[ https://issues.apache.org/jira/browse/CONNECTORS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277032#comment-14277032 ] Andreas Baumann commented on CONNECTORS-1144: - Hi Karl, Sorry. This is totally mine. :-) Indeed, the Add at end button slipped my mind. Thanks Andreas Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database --- Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CONNECTORS-1143) Problem with cached versions of e.g. a repository connection
[ https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-1143: --- Assignee: Karl Wright Problem with cached versions of e.g. a repository connection Key: CONNECTORS-1143 URL: https://issues.apache.org/jira/browse/CONNECTORS-1143 Project: ManifoldCF Issue Type: Bug Reporter: Daniel Aschauer Assignee: Karl Wright I have some issues when i change settings in repository connection: I had to change the password for my connection (JIRA), i review the connection and it works. However the related job(s) keep failing because of an unautorized error. What is more i created a new job with the repository connection and it failed too. I don't know how these things are kept cached in Manifold. Is this a bug or do I have to do some regular cleanup?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
Andreas Baumann created CONNECTORS-1144: --- Summary: Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 2.0, ManifoldCF 1.8 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277031#comment-14277031 ] Karl Wright edited comment on CONNECTORS-1145 at 1/14/15 3:17 PM: -- I do not see this on Windows. Can you be more specific about what connection type you are creating? Also, please note that file locking is NOT resilient against hard killing of processes. If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the how-to-build-and-deploy page. was (Author: kwri...@metacarta.com): I do not see this on Windows. Can you be more specific about what connection type you are creating? Also, please noted that file locking is NOT resilient against hard killing of processes. If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the how-to-build-and-deploy page. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CONNECTORS-1143) Problem with cached versions of e.g. a repository connection
[ https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-1143: Component/s: Framework core Affects Version/s: ManifoldCF 1.5.1 ManifoldCF 1.6.1 ManifoldCF 1.7.2 ManifoldCF 1.8 ManifoldCF 2.0 Fix Version/s: ManifoldCF 2.1 ManifoldCF 1.9 Inspecting the code, I think I may understand the issue. Basically, the connector instances are pooled. New connector instances are created in a ManifoldCF process only when an instance can't be found to use in the pool. Each local pool is periodically apportioned among all MCF processes, based on usage patterns over the previous five seconds. So, what I'm saying is this: unless your agents process(es) STOP using connector instances for a given connection name for a while (in which case the pool is definitely flushed), the old connector instances based on the previous version of the connection configuration will stick around and be reused. This has been the case since MCF 1.5. I can envision making this more robust, by keeping the configuration along with the connection name for each pooled connector instance. Then, it should be possible to recognize when a connection pulled from the pool is not one that can be used, and create a new one instead. However, please continue to confirm that caching is really the culprit in your case. Problem with cached versions of e.g. a repository connection Key: CONNECTORS-1143 URL: https://issues.apache.org/jira/browse/CONNECTORS-1143 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.5.1, ManifoldCF 1.6.1, ManifoldCF 1.7.2, ManifoldCF 1.8, ManifoldCF 2.0 Reporter: Daniel Aschauer Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 I have some issues when i change settings in repository connection: I had to change the password for my connection (JIRA), i review the connection and it works. However the related job(s) keep failing because of an unautorized error. What is more i created a new job with the repository connection and it failed too. I don't know how these things are kept cached in Manifold. Is this a bug or do I have to do some regular cleanup?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
[ https://issues.apache.org/jira/browse/CONNECTORS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277006#comment-14277006 ] Karl Wright commented on CONNECTORS-1144: - Hi Andreas, I confirmed that everything seems to work. All you seem to have missed was to click the Add to End button after filling in your domain controller information, before you click Save. Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database --- Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
[ https://issues.apache.org/jira/browse/CONNECTORS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-1144. - Resolution: Not a Problem Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database --- Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277031#comment-14277031 ] Karl Wright edited comment on CONNECTORS-1145 at 1/14/15 3:21 PM: -- I do not see this on Windows 7. Can you be more specific about what connection type you are creating? Also, please note that file locking is NOT resilient against hard killing of processes. If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the how-to-build-and-deploy page. was (Author: kwri...@metacarta.com): I do not see this on Windows. Can you be more specific about what connection type you are creating? Also, please note that file locking is NOT resilient against hard killing of processes. If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the how-to-build-and-deploy page. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1143) Problem with cached versions of e.g. a repository connection
[ https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277084#comment-14277084 ] Karl Wright edited comment on CONNECTORS-1143 at 1/14/15 3:42 PM: -- Inspecting the code, I think I may understand the issue. Basically, the connector instances are pooled. New connector instances are created in a ManifoldCF process only when an instance can't be found to use in the pool. Each local pool is periodically apportioned among all MCF processes, based on usage patterns over the previous five seconds. So, what I'm saying is this: unless your agents process(es) STOP using connector instances for a given connection name for a while (in which case the pool is definitely flushed), the old connector instances based on the previous version of the connection configuration will stick around and be reused. This has been the case since MCF 1.5. I can envision making this more robust, by keeping the configuration along with the connection name for each pooled connector instance. Then, it should be possible to recognize when a connector instance pulled from the pool is not one that can be used, and create a new one instead. However, please continue to confirm that caching is really the culprit in your case. was (Author: kwri...@metacarta.com): Inspecting the code, I think I may understand the issue. Basically, the connector instances are pooled. New connector instances are created in a ManifoldCF process only when an instance can't be found to use in the pool. Each local pool is periodically apportioned among all MCF processes, based on usage patterns over the previous five seconds. So, what I'm saying is this: unless your agents process(es) STOP using connector instances for a given connection name for a while (in which case the pool is definitely flushed), the old connector instances based on the previous version of the connection configuration will stick around and be reused. This has been the case since MCF 1.5. I can envision making this more robust, by keeping the configuration along with the connection name for each pooled connector instance. Then, it should be possible to recognize when a connection pulled from the pool is not one that can be used, and create a new one instead. However, please continue to confirm that caching is really the culprit in your case. Problem with cached versions of e.g. a repository connection Key: CONNECTORS-1143 URL: https://issues.apache.org/jira/browse/CONNECTORS-1143 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.5.1, ManifoldCF 1.6.1, ManifoldCF 1.7.2, ManifoldCF 1.8, ManifoldCF 2.0 Reporter: Daniel Aschauer Assignee: Karl Wright Fix For: ManifoldCF 1.9, ManifoldCF 2.1 I have some issues when i change settings in repository connection: I had to change the password for my connection (JIRA), i review the connection and it works. However the related job(s) keep failing because of an unautorized error. What is more i created a new job with the repository connection and it failed too. I don't know how these things are kept cached in Manifold. Is this a bug or do I have to do some regular cleanup?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CONNECTORS-1143) Problem with cached versions of e.g. a repository connection
Daniel Aschauer created CONNECTORS-1143: --- Summary: Problem with cached versions of e.g. a repository connection Key: CONNECTORS-1143 URL: https://issues.apache.org/jira/browse/CONNECTORS-1143 Project: ManifoldCF Issue Type: Bug Reporter: Daniel Aschauer I have some issues when i change settings in repository connection: I had to change the password for my connection (JIRA), i review the connection and it works. However the related job(s) keep failing because of an unautorized error. What is more i created a new job with the repository connection and it failed too. I don't know how these things are kept cached in Manifold. Is this a bug or do I have to do some regular cleanup?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
[ https://issues.apache.org/jira/browse/CONNECTORS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276994#comment-14276994 ] Andreas Baumann commented on CONNECTORS-1144: - Checking the 'configxml' field in 'authconnections' shows me just the XML with the two cache parameters. Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database --- Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1144) Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database
[ https://issues.apache.org/jira/browse/CONNECTORS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276999#comment-14276999 ] Karl Wright commented on CONNECTORS-1144: - Hi Andreas, I will look at this shortly, but first, did you remember to click the Add button? It's necessary to do that in order to add a domain controller to the configured list. Configuration of Domain controller, suffix, bind user, etc. is not respected nor stored in database --- Key: CONNECTORS-1144 URL: https://issues.apache.org/jira/browse/CONNECTORS-1144 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Priority: Critical Added new authority connection of type Active Directory, added domain controller and other configuration. Saved it. The View doesn't show any data but the cache parameters, Edit has an empty domain controller and credentials. Can anybody confirm this. Tried version 1.8 and 2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277223#comment-14277223 ] Andreas Baumann commented on CONNECTORS-1145: - It doesn't really matter what I edit, as soon as the parameter has to be synched to all agents I get this behaviour. I cleaned the locks with the script. I'll try to produce a Processor Monitor trace and put it here.. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277231#comment-14277231 ] Andreas Baumann commented on CONNECTORS-1145: - BTW: no problem here, I'm running the Zookeeper version now without any problems. :-) multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows
[ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-1145. - Resolution: Cannot Reproduce Didn't try to reproduce on Windows 8, but I certainly can't make this happen on Windows 7. Plus, file synch is deprecated at this point. multiprocess-file-example blocks in configuration on Windows Key: CONNECTORS-1145 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 Environment: Windows 2012 Reporter: Andreas Baumann Saving a configuration setting (for instance a new Output Connector) hangs forevert. Inspecting the problem with the 'Process Monitor' shows me that there is an infinite loop while locking and reading a file in the syncharea. I disabled Windows Search and virus scanners, so far no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1142) initialize.sh fails because connector-common-lib dependencies not in classpath
[
https://issues.apache.org/jira/browse/CONNECTORS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-1142.
-
Resolution: Cannot Reproduce
Looks like operator error? Worked fine for me with the shipped properties.xml
file.
initialize.sh fails because connector-common-lib dependencies not in classpath
--
Key: CONNECTORS-1142
URL: https://issues.apache.org/jira/browse/CONNECTORS-1142
Project: ManifoldCF
Issue Type: Bug
Affects Versions: ManifoldCF 2.0
Reporter: Michael Wilken
Priority: Minor
Running initialize.sh from apache-manifoldcf-2.0/multiprocess-file-example in
a fresh ManifoldCF 2.0 install fails because of missing libraries on the
classpath:
{code}
[wilkenm@localhost:multiprocess-file-example ]$ ./initialize.sh
Configuration file successfully read
Successfully unregistered all domains
Successfully unregistered all output connectors
Successfully unregistered all transformation connectors
Successfully unregistered all mapping connectors
Successfully unregistered all authority connectors
Successfully unregistered all repository connectors
Successfully registered output connector
'org.apache.manifoldcf.agents.output.solr.SolrConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.nullconnector.NullConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.hdfs.HDFSOutputConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.gts.GTSConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.filesystem.FileOutputConnector'
Successfully registered output connector
'org.apache.manifoldcf.agents.output.elasticsearch.ElasticSearchConnector'
Exception in thread main java.lang.NoClassDefFoundError:
org/apache/manifoldcf/connectorcommon/jsongen/JSONReader
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at
org.apache.manifoldcf.core.system.ManifoldCFResourceLoader.findClass(ManifoldCFResourceLoader.java:149)
at
org.apache.manifoldcf.core.system.ManifoldCF.findClass(ManifoldCF.java:1522)
at
org.apache.manifoldcf.core.interfaces.ConnectorFactory.getThisConnectorRaw(ConnectorFactory.java:144)
at
org.apache.manifoldcf.core.interfaces.ConnectorFactory.getThisConnectorNoCheck(ConnectorFactory.java:118)
at
org.apache.manifoldcf.core.interfaces.ConnectorFactory.installThis(ConnectorFactory.java:48)
at
org.apache.manifoldcf.agents.interfaces.OutputConnectorFactory.install(OutputConnectorFactory.java:70)
at
org.apache.manifoldcf.agents.outputconnmgr.OutputConnectorManager.registerConnector(OutputConnectorManager.java:180)
at
org.apache.manifoldcf.crawler.system.ManifoldCF.registerConnectors(ManifoldCF.java:492)
at
org.apache.manifoldcf.crawler.system.ManifoldCF.reregisterAllConnectors(ManifoldCF.java:151)
at
org.apache.manifoldcf.crawler.InitializeAndRegister.doExecute(InitializeAndRegister.java:43)
at
org.apache.manifoldcf.crawler.InitializeAndRegister.main(InitializeAndRegister.java:60)
Caused by: java.lang.ClassNotFoundException:
org.apache.manifoldcf.connectorcommon.jsongen.JSONReader
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:789)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 13 more
{code}
This is easily fixed by adding the following needed libs to the
options.env.unix file:
../connector-common-lib/mcf-connector-common.jar
../connector-common-lib/tika-core-1.6.jar
../connector-common-lib/axis-1.4.jar
options.env.unix (and .win) are create during the build process, and I'm not
familiar enough with Ant to provide a patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
