[jira] [Commented] (CONNECTORS-474) Create build stubs for all proprietary connectors
[ https://issues.apache.org/jira/browse/CONNECTORS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280051#comment-13280051 ] Karl Wright commented on CONNECTORS-474: Completed Documentum stubs; working now on FileNet. Create build stubs for all proprietary connectors - Key: CONNECTORS-474 URL: https://issues.apache.org/jira/browse/CONNECTORS-474 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 If we create build stubs for all connectors with proprietary dependencies, then anyone will be able to build a bin release or the website. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-476) When running on MySQL initialize.sh causes access denied error
[
https://issues.apache.org/jira/browse/CONNECTORS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-476:
---
Description:
initialize.sh causes access denied error if DB server is seperated from MCF's.
Suppose each server's IP are like followings:
MySQL Server IP: A
MCF Server IP: B
and properties.xml has the follwing parameters and values:
{code}
property name=org.apache.manifoldcf.databaseimplementationclass
value=org.apache.manifoldcf.core.database.DBInterfaceMySQL/
property name=org.apache.manifoldcf.dbsuperusername value=root/
property name=org.apache.manifoldcf.dbsuperuserpassword value=password/
property name=org.apache.manifoldcf.database.name value=manifoldcf/
property name=org.apache.manifoldcf.mysql.server value=A/
{code}
Then, executing initialize.sh causes the follwing error:
{code}
Caused by: java.sql.SQLException: Access denied for user 'manifoldcf'@'B'
(using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:943)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1308)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
at
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
{code}
The problem is that MCF requests MySQL to create a new manifoldcf user with
localhost access.
In this case, of course, MCF is on the server with IP B, MySQL should create a
new user with IP Address B.
The following method is the one creating a new MySQL user in the user table.
Modifying the part where IP information is added solves this problem.
JAR NAME :mcf-core.jar
PACKAGE:org.apache.manifoldcf.core.database
CLASS NAME :DBInterfaceMySQL
METHOD NAME: public void createUserAndDatabase
{code}
if(userName != null)
try
{
list.clear();
list.add(userName);
// list.add(localhost);
list.add(IP_ADDRESS_B);
list.add(password);
...
...
}
{code}
I guess it would be nice if properties.xml can have a new property taking MCF
server IP to
have MySQL create a manifoldcf user with that IP.
was:
initialize.sh causes access denied error if DB server is seperated from MCF's.
Suppose each server's IP are like followings:
MySQL Server IP: A
MCF Server IP: B
and properties.xml has the follwing parameters and values:
property name=org.apache.manifoldcf.databaseimplementationclass
value=org.apache.manifoldcf.core.database.DBInterfaceMySQL/
property name=org.apache.manifoldcf.dbsuperusername value=root/
property name=org.apache.manifoldcf.dbsuperuserpassword value=password/
property name=org.apache.manifoldcf.database.name value=manifoldcf/
property name=org.apache.manifoldcf.mysql.server value=A/
Then, executing initialize.sh causes the follwing error:
Caused by: java.sql.SQLException: Access denied for user 'manifoldcf'@'B'
(using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:943)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1308)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
at
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
The problem is that MCF requests MySQL to create a new manifoldcf user with
localhost access.
In this case, of course, MCF is on the server with IP B, MySQL should create a
new user with IP Address B.
The following
[jira] [Updated] (CONNECTORS-476) When running on MySQL initialize.sh causes access denied error
[
https://issues.apache.org/jira/browse/CONNECTORS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-476:
---
Affects Version/s: ManifoldCF 0.6
Fix Version/s: ManifoldCF 0.6
Assignee: Karl Wright
When running on MySQL initialize.sh causes access denied error
--
Key: CONNECTORS-476
URL: https://issues.apache.org/jira/browse/CONNECTORS-476
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Shigeki Kobayashi
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
initialize.sh causes access denied error if DB server is seperated from MCF's.
Suppose each server's IP are like followings:
MySQL Server IP: A
MCF Server IP: B
and properties.xml has the follwing parameters and values:
{code}
property name=org.apache.manifoldcf.databaseimplementationclass
value=org.apache.manifoldcf.core.database.DBInterfaceMySQL/
property name=org.apache.manifoldcf.dbsuperusername value=root/
property name=org.apache.manifoldcf.dbsuperuserpassword
value=password/
property name=org.apache.manifoldcf.database.name value=manifoldcf/
property name=org.apache.manifoldcf.mysql.server value=A/
{code}
Then, executing initialize.sh causes the follwing error:
{code}
Caused by: java.sql.SQLException: Access denied for user 'manifoldcf'@'B'
(using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:943)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1308)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
at
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
{code}
The problem is that MCF requests MySQL to create a new manifoldcf user with
localhost access.
In this case, of course, MCF is on the server with IP B, MySQL should create
a new user with IP Address B.
The following method is the one creating a new MySQL user in the user table.
Modifying the part where IP information is added solves this problem.
JAR NAME :mcf-core.jar
PACKAGE:org.apache.manifoldcf.core.database
CLASS NAME :DBInterfaceMySQL
METHOD NAME: public void createUserAndDatabase
{code}
if(userName != null)
try
{
list.clear();
list.add(userName);
// list.add(localhost);
list.add(IP_ADDRESS_B);
list.add(password);
...
...
}
{code}
I guess it would be nice if properties.xml can have a new property taking MCF
server IP to
have MySQL create a manifoldcf user with that IP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-476) When running on MySQL initialize.sh causes access denied error
[
https://issues.apache.org/jira/browse/CONNECTORS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280678#comment-13280678
]
Karl Wright commented on CONNECTORS-476:
r1341288.
When running on MySQL initialize.sh causes access denied error
--
Key: CONNECTORS-476
URL: https://issues.apache.org/jira/browse/CONNECTORS-476
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Shigeki Kobayashi
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
initialize.sh causes access denied error if DB server is seperated from MCF's.
Suppose each server's IP are like followings:
MySQL Server IP: A
MCF Server IP: B
and properties.xml has the follwing parameters and values:
{code}
property name=org.apache.manifoldcf.databaseimplementationclass
value=org.apache.manifoldcf.core.database.DBInterfaceMySQL/
property name=org.apache.manifoldcf.dbsuperusername value=root/
property name=org.apache.manifoldcf.dbsuperuserpassword
value=password/
property name=org.apache.manifoldcf.database.name value=manifoldcf/
property name=org.apache.manifoldcf.mysql.server value=A/
{code}
Then, executing initialize.sh causes the follwing error:
{code}
Caused by: java.sql.SQLException: Access denied for user 'manifoldcf'@'B'
(using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:943)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1308)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
at
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
{code}
The problem is that MCF requests MySQL to create a new manifoldcf user with
localhost access.
In this case, of course, MCF is on the server with IP B, MySQL should create
a new user with IP Address B.
The following method is the one creating a new MySQL user in the user table.
Modifying the part where IP information is added solves this problem.
JAR NAME :mcf-core.jar
PACKAGE:org.apache.manifoldcf.core.database
CLASS NAME :DBInterfaceMySQL
METHOD NAME: public void createUserAndDatabase
{code}
if(userName != null)
try
{
list.clear();
list.add(userName);
// list.add(localhost);
list.add(IP_ADDRESS_B);
list.add(password);
...
...
}
{code}
I guess it would be nice if properties.xml can have a new property taking MCF
server IP to
have MySQL create a manifoldcf user with that IP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-476) When running on MySQL initialize.sh causes access denied error
[
https://issues.apache.org/jira/browse/CONNECTORS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-476.
Resolution: Fixed
When running on MySQL initialize.sh causes access denied error
--
Key: CONNECTORS-476
URL: https://issues.apache.org/jira/browse/CONNECTORS-476
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Shigeki Kobayashi
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
initialize.sh causes access denied error if DB server is seperated from MCF's.
Suppose each server's IP are like followings:
MySQL Server IP: A
MCF Server IP: B
and properties.xml has the follwing parameters and values:
{code}
property name=org.apache.manifoldcf.databaseimplementationclass
value=org.apache.manifoldcf.core.database.DBInterfaceMySQL/
property name=org.apache.manifoldcf.dbsuperusername value=root/
property name=org.apache.manifoldcf.dbsuperuserpassword
value=password/
property name=org.apache.manifoldcf.database.name value=manifoldcf/
property name=org.apache.manifoldcf.mysql.server value=A/
{code}
Then, executing initialize.sh causes the follwing error:
{code}
Caused by: java.sql.SQLException: Access denied for user 'manifoldcf'@'B'
(using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:943)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4113)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1308)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
at
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792)
at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
{code}
The problem is that MCF requests MySQL to create a new manifoldcf user with
localhost access.
In this case, of course, MCF is on the server with IP B, MySQL should create
a new user with IP Address B.
The following method is the one creating a new MySQL user in the user table.
Modifying the part where IP information is added solves this problem.
JAR NAME :mcf-core.jar
PACKAGE:org.apache.manifoldcf.core.database
CLASS NAME :DBInterfaceMySQL
METHOD NAME: public void createUserAndDatabase
{code}
if(userName != null)
try
{
list.clear();
list.add(userName);
// list.add(localhost);
list.add(IP_ADDRESS_B);
list.add(password);
...
...
}
{code}
I guess it would be nice if properties.xml can have a new property taking MCF
server IP to
have MySQL create a manifoldcf user with that IP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-474) Create build stubs for all proprietary connectors
Karl Wright created CONNECTORS-474: -- Summary: Create build stubs for all proprietary connectors Key: CONNECTORS-474 URL: https://issues.apache.org/jira/browse/CONNECTORS-474 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 If we create build stubs for all connectors with proprietary dependencies, then anyone will be able to build a bin release or the website. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-473) We need to separate our site into two pieces: One for the ManifoldCF project, and one for each release
Karl Wright created CONNECTORS-473: -- Summary: We need to separate our site into two pieces: One for the ManifoldCF project, and one for each release Key: CONNECTORS-473 URL: https://issues.apache.org/jira/browse/CONNECTORS-473 Project: ManifoldCF Issue Type: Improvement Components: Build, Documentation Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 Part of the ManifoldCF site has to do with the ManifoldCF project, and part of it is germane to a given release. We should separate these so that the project-related part builds separately, under site/trunk, and references one (or more) release-related sites, under branches/XXX/site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-472) Changes related to graduation
[ https://issues.apache.org/jira/browse/CONNECTORS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277187#comment-13277187 ] Karl Wright commented on CONNECTORS-472: r1339386 (0.5 release branch) Changes related to graduation - Key: CONNECTORS-472 URL: https://issues.apache.org/jira/browse/CONNECTORS-472 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5.1, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 We need to do the following: - remove the disclaimer.txt files - modify the site to remove the disclaimer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-472) Changes related to graduation
[ https://issues.apache.org/jira/browse/CONNECTORS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-472. Resolution: Fixed Changes related to graduation - Key: CONNECTORS-472 URL: https://issues.apache.org/jira/browse/CONNECTORS-472 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5.1, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 We need to do the following: - remove the disclaimer.txt files - modify the site to remove the disclaimer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-471: --- Affects Version/s: ManifoldCF 0.5 HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-471: HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-467: Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-467: --- Priority: Critical (was: Major) Affects Version/s: ManifoldCF 0.6 Fix Version/s: ManifoldCF 0.5.1 Assignee: Karl Wright (was: Erlend Garåsen) Triaging this for the 0.5.1 release. Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273862#comment-13273862 ] Karl Wright commented on CONNECTORS-467: r1337451 on release branch. Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-467. Resolution: Fixed Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273864#comment-13273864 ] Karl Wright commented on CONNECTORS-471: r1337452 on release branch HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-453: --- Priority: Critical (was: Major) Fix Version/s: ManifoldCF 0.5.1 ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-453: Reopening for inclusion in 0.5.1 ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273872#comment-13273872 ] Karl Wright commented on CONNECTORS-453: r1337457 (release branch) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-453. Resolution: Fixed ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-470) SharePoint 2010 support
[
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274208#comment-13274208
]
Karl Wright commented on CONNECTORS-470:
Further analysis indicates that some of these services still work, while others
(e.g. the DspSts service) have problems. Specifically, this query request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
SharePoint 2010 support
---
Key: CONNECTORS-470
URL: https://issues.apache.org/jira/browse/CONNECTORS-470
Project: ManifoldCF
Issue Type: Improvement
Components: SharePoint connector
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
See here for list of the SharePoint web services for SharePoint 2010:
http://msdn.microsoft.com/en-us/library/ee705814.aspx
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-470) SharePoint 2010 support
[
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274208#comment-13274208
]
Karl Wright edited comment on CONNECTORS-470 at 5/13/12 4:52 AM:
-
Further analysis indicates that some of these services still work, while others
(e.g. the DspSts service) have problems. Specifically, this query request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
From this I conclude that the DspSts service on this installation is broken -
and ONLY that service is broken. This is because the GUID that is included is
indeed valid and must have come from somewhere - the Lists service, no doubt,
which still seems to actually work on SharePoint 2010.
was (Author: kwri...@metacarta.com):
Further analysis indicates that some of these services still work, while
others (e.g. the DspSts service) have problems. Specifically, this query
request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
SharePoint 2010 support
---
Key: CONNECTORS-470
URL: https://issues.apache.org/jira/browse/CONNECTORS-470
Project: ManifoldCF
Issue Type: Improvement
Components: SharePoint connector
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
See here for list of the SharePoint web services for SharePoint 2010:
http://msdn.microsoft.com/en-us/library/ee705814.aspx
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-471) HSQLDB runs out of memory during load test
Karl Wright created CONNECTORS-471: -- Summary: HSQLDB runs out of memory during load test Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-471. Resolution: Fixed HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-96) Replace the current connection pool by one that is more up-to-date
[ https://issues.apache.org/jira/browse/CONNECTORS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13272906#comment-13272906 ] Karl Wright commented on CONNECTORS-96: --- r1336965 Replace the current connection pool by one that is more up-to-date -- Key: CONNECTORS-96 URL: https://issues.apache.org/jira/browse/CONNECTORS-96 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jettro Coenradie Assignee: Karl Wright Fix For: ManifoldCF 0.6 At the moment we use a connection pool from bitmechanic. This is the least to say some what outdated. Hard to find any information about it. The only thing I could find was this: http://www.knightsofthenet.com/projects/SQLPool/ Can we replace this with an implementation of for instance dbcp http://commons.apache.org/dbcp/index.html I think there is a big risk in using this old versions that are not tested on new java systems anymore. We can be missing a lot of optimizations (jdbc4 for instance) For the pooling behavior we can use something like commons-pool -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-96) Replace the current connection pool by one that is more up-to-date
[ https://issues.apache.org/jira/browse/CONNECTORS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-96. --- Resolution: Fixed Replace the current connection pool by one that is more up-to-date -- Key: CONNECTORS-96 URL: https://issues.apache.org/jira/browse/CONNECTORS-96 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jettro Coenradie Assignee: Karl Wright Fix For: ManifoldCF 0.6 At the moment we use a connection pool from bitmechanic. This is the least to say some what outdated. Hard to find any information about it. The only thing I could find was this: http://www.knightsofthenet.com/projects/SQLPool/ Can we replace this with an implementation of for instance dbcp http://commons.apache.org/dbcp/index.html I think there is a big risk in using this old versions that are not tested on new java systems anymore. We can be missing a lot of optimizations (jdbc4 for instance) For the pooling behavior we can use something like commons-pool -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-96) Replace the current connection pool by one that is more up-to-date
[ https://issues.apache.org/jira/browse/CONNECTORS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-96: - Assignee: Karl Wright Replace the current connection pool by one that is more up-to-date -- Key: CONNECTORS-96 URL: https://issues.apache.org/jira/browse/CONNECTORS-96 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jettro Coenradie Assignee: Karl Wright Fix For: ManifoldCF 0.6 At the moment we use a connection pool from bitmechanic. This is the least to say some what outdated. Hard to find any information about it. The only thing I could find was this: http://www.knightsofthenet.com/projects/SQLPool/ Can we replace this with an implementation of for instance dbcp http://commons.apache.org/dbcp/index.html I think there is a big risk in using this old versions that are not tested on new java systems anymore. We can be missing a lot of optimizations (jdbc4 for instance) For the pooling behavior we can use something like commons-pool -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-470) SharePoint 2010 moves web services to new names; need SharePoint 2010 support to be able to reach them
Karl Wright created CONNECTORS-470: -- Summary: SharePoint 2010 moves web services to new names; need SharePoint 2010 support to be able to reach them Key: CONNECTORS-470 URL: https://issues.apache.org/jira/browse/CONNECTORS-470 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 See here for list of the SharePoint web services for SharePoint 2010: http://msdn.microsoft.com/en-us/library/ee705814.aspx -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-470) SharePoint 2010 support
[ https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-470: --- Summary: SharePoint 2010 support (was: SharePoint 2010 moves web services to new names; need SharePoint 2010 support to be able to reach them) SharePoint 2010 support --- Key: CONNECTORS-470 URL: https://issues.apache.org/jira/browse/CONNECTORS-470 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 See here for list of the SharePoint web services for SharePoint 2010: http://msdn.microsoft.com/en-us/library/ee705814.aspx -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-469) Upgrade the way framework core is shut down to also allow for webapp context shutdowns
Karl Wright created CONNECTORS-469:
--
Summary: Upgrade the way framework core is shut down to also allow
for webapp context shutdowns
Key: CONNECTORS-469
URL: https://issues.apache.org/jira/browse/CONNECTORS-469
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.5
Shutdown of a web application under Tomcat sometimes leaves exceptions due to
non-up-to-date ability to deal with web application shutdown events.
Specifically, we need the following:
(1) An implementation of javax.servlet.ServletContextListener in every web
application
(2) Appropriate locking to prevent an already-shut-down web application from
trying to shut itself down another time
(3) The following addition to the web.xml file for the web applications:
{code}
web-app
!-- Usual stuff here --
listener
listener-classcom.mycompany.MyClass/listener-class
/listener
/web-app
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-469) Upgrade the way framework core is shut down to also allow for webapp context shutdowns
[
https://issues.apache.org/jira/browse/CONNECTORS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13268012#comment-13268012
]
Karl Wright commented on CONNECTORS-469:
r1333735
Upgrade the way framework core is shut down to also allow for webapp context
shutdowns
--
Key: CONNECTORS-469
URL: https://issues.apache.org/jira/browse/CONNECTORS-469
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
Shutdown of a web application under Tomcat sometimes leaves exceptions due to
non-up-to-date ability to deal with web application shutdown events.
Specifically, we need the following:
(1) An implementation of javax.servlet.ServletContextListener in every web
application
(2) Appropriate locking to prevent an already-shut-down web application from
trying to shut itself down another time
(3) The following addition to the web.xml file for the web applications:
{code}
web-app
!-- Usual stuff here --
listener
listener-classcom.mycompany.MyClass/listener-class
/listener
/web-app
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13263531#comment-13263531 ] Karl Wright commented on CONNECTORS-467: Attached the patch, since the community will want it for the 0.5 release. Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has severe performance problems
[
https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13263090#comment-13263090
]
Karl Wright commented on CONNECTORS-453:
Clicking pause during the job run yields the following to be displayed in the
UI:
A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
Lock : ROW, JOBS, (1,7) Waiting XID : {147028, X} , APP, UPDATE jobs SET
status=? WHERE id=? Granted XID : {146703, S} , {146941, S} Lock : ROW,
JOBQUEUE, (481,10) Waiting XID : {146941, S} , APP, SELECT
jobid,CAST(COUNT(dochash) AS bigint) AS doccount FROM jobqueue t1 WHERE
EXISTS(SELECT 'x' FROM jobs t0 WHERE t0.id=t1.jobid AND id=?) GROUP BY jobid
Granted XID : {146612, X} Lock : ROW, HOPCOUNT, (1734,27) Waiting XID :
{146612, S} , APP, SELECT parentidhash,linktype,distance FROM hopcount WHERE
jobid=? AND parentidhash IN (?,?,?,?,?,?,?,?,?,?) AND linktype=? Granted XID :
{14, X} Lock : ROW, JOBS, (1,7) Waiting XID : {14, S} , APP, INSERT
INTO hopcount (deathmark,parentidhash,id,distance,jobid,linktype) VALUES
(?,?,?,?,?,?) . The selected victim is XID : 147028.
ManifoldCF running with Derby 10.8.1.1 has severe performance problems
--
Key: CONNECTORS-453
URL: https://issues.apache.org/jira/browse/CONNECTORS-453
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20
documents. Clearly the Derby contention/locking bugs are back with a
vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to
look at them again.
In the interim, maybe it is time to use hsqldb as the default embedded
database for the single-process example instead of Derby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has severe performance problems
[
https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13263092#comment-13263092
]
Karl Wright commented on CONNECTORS-453:
Here's another example:
Error!
A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
Lock : ROW, JOBS, (1,7) Waiting XID : {157800, X} , APP, UPDATE jobs SET
status=? WHERE id=? Granted XID : {157521, S} , {157653, S} Lock : ROW,
JOBQUEUE, (503,86) Waiting XID : {157653, S} , APP, SELECT
t0.id,t0.jobid,t0.dochash,t0.docid,t0.status,t0.failtime,t0.failcount,t0.priorityset
FROM jobqueue t0 WHERE t0.status IN (?,?) AND t0.checkaction=? AND
t0.checktime=? AND EXISTS(SELECT 'x' FROM jobs t1 WHERE t1.status IN (?,?) AND
t1.id=t0.jobid AND t1.priority=?) AND NOT EXISTS(SELECT 'x' FROM jobqueue t2
WHERE t2.dochash=t0.dochash AND t2.status IN (?,?,?,?,?,?) AND
t2.jobid!=t0.jobid) AND NOT EXISTS(SELECT 'x' FROM prereqevents t3,events t4
WHERE t0.id=t3.owner AND t3.eventname=t4.name) ORDER BY t0.docpriority
ASC,t0.status ASC,t0.checkaction ASC,t0.checktime ASC FETCH NEXT 120 ROWS ONLY
Granted XID : {157557, X} Lock : ROW, JOBS, (1,7) Waiting XID : {157557, S} ,
APP, INSERT INTO hopcount (deathmark,parentidhash,id,distance,jobid,linktype)
VALUES (?,?,?,?,?,?) . The selected victim is XID : 157800.
ManifoldCF running with Derby 10.8.1.1 has severe performance problems
--
Key: CONNECTORS-453
URL: https://issues.apache.org/jira/browse/CONNECTORS-453
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20
documents. Clearly the Derby contention/locking bugs are back with a
vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to
look at them again.
In the interim, maybe it is time to use hsqldb as the default embedded
database for the single-process example instead of Derby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has severe performance problems
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13263148#comment-13263148 ] Karl Wright commented on CONNECTORS-453: r1331102 ManifoldCF running with Derby 10.8.1.1 has severe performance problems -- Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has severe performance problems
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-453. Resolution: Fixed ManifoldCF running with Derby 10.8.1.1 has severe performance problems -- Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
[ https://issues.apache.org/jira/browse/CONNECTORS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261595#comment-13261595 ] Karl Wright commented on CONNECTORS-468: r1330240. Forgot to add the darned file to svn. Using ResourceBundle under Velocity has unhelpful behavior when a key is missing Key: CONNECTORS-468 URL: https://issues.apache.org/jira/browse/CONNECTORS-468 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When you use ResourceBundle.getString in a Velocity template, the behavior for a missing key is to throw an exception - which causes the template to not render and an exception to be printed in the log. It would be much better if the behavior was more similar to Messages.getString. We can do this by wrapping ResourceBundle and using the wrapped class in the context instead of ResourceBundle itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-467) MCF version 0.5 does not run on Resin
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260385#comment-13260385 ] Karl Wright commented on CONNECTORS-467: You would only need to open a vote thread if you are removing an option or destroying backwards compatibility. So please just go ahead with (2). MCF version 0.5 does not run on Resin - Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF 0.6 Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
Karl Wright created CONNECTORS-468: -- Summary: Using ResourceBundle under Velocity has unhelpful behavior when a key is missing Key: CONNECTORS-468 URL: https://issues.apache.org/jira/browse/CONNECTORS-468 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When you use ResourceBundle.getString in a Velocity template, the behavior for a missing key is to throw an exception - which causes the template to not render and an exception to be printed in the log. It would be much better if the behavior was more similar to Messages.getString. We can do this by wrapping ResourceBundle and using the wrapped class in the context instead of ResourceBundle itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
[ https://issues.apache.org/jira/browse/CONNECTORS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260867#comment-13260867 ] Karl Wright commented on CONNECTORS-468: r1329957 Using ResourceBundle under Velocity has unhelpful behavior when a key is missing Key: CONNECTORS-468 URL: https://issues.apache.org/jira/browse/CONNECTORS-468 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When you use ResourceBundle.getString in a Velocity template, the behavior for a missing key is to throw an exception - which causes the template to not render and an exception to be printed in the log. It would be much better if the behavior was more similar to Messages.getString. We can do this by wrapping ResourceBundle and using the wrapped class in the context instead of ResourceBundle itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
[ https://issues.apache.org/jira/browse/CONNECTORS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-468. Resolution: Fixed Using ResourceBundle under Velocity has unhelpful behavior when a key is missing Key: CONNECTORS-468 URL: https://issues.apache.org/jira/browse/CONNECTORS-468 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When you use ResourceBundle.getString in a Velocity template, the behavior for a missing key is to throw an exception - which causes the template to not render and an exception to be printed in the log. It would be much better if the behavior was more similar to Messages.getString. We can do this by wrapping ResourceBundle and using the wrapped class in the context instead of ResourceBundle itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-466) CMIS UI test fails
Karl Wright created CONNECTORS-466: -- Summary: CMIS UI test fails Key: CONNECTORS-466 URL: https://issues.apache.org/jira/browse/CONNECTORS-466 Project: ManifoldCF Issue Type: Bug Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The CMIS UI test fails. Not clear yet whether this is a bug in the Javascript or in the revised Javascript tester. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-466) CMIS UI test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259468#comment-13259468
]
Karl Wright commented on CONNECTORS-466:
Here's the error:
{code}
[junit] Multipart posting url
'http://localhost:8346/mcf-crawler-ui/execute.jsp' with parameters
'username=foopassword=barthrottlecount=0description=connname=MyRepositoryConnectionisnewconnection=truebinding=atomserver=localhostclassname=org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnectortabname=Namemaxconnections=10protocol=httppath=%2Fchemistry-opencmis-server-inmemory%2Fatomauthorityname=_none_type=connectionport=9090repositoryId=op=Continue'
and 0 files...
[junit] Traceback (most recent call last):
[junit] File test.py, line 102, in module
[junit] var73.click()
...
[junit] File
C:\wip\mcf\trunk\tests\cmis\test-derby-output\Javascript.py, line 69, in
bool_value
[junit] raise Exception(Object %s has no boolean value %
unicode(self) )
[junit] Exception: Object Numeric value (-1) has no boolean value
{code}
CMIS UI test fails
--
Key: CONNECTORS-466
URL: https://issues.apache.org/jira/browse/CONNECTORS-466
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
The CMIS UI test fails. Not clear yet whether this is a bug in the
Javascript or in the revised Javascript tester.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-466) CMIS UI test fails
[ https://issues.apache.org/jira/browse/CONNECTORS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259493#comment-13259493 ] Karl Wright commented on CONNECTORS-466: r1329160 (fix to CMIS connector) CMIS UI test fails -- Key: CONNECTORS-466 URL: https://issues.apache.org/jira/browse/CONNECTORS-466 Project: ManifoldCF Issue Type: Bug Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The CMIS UI test fails. Not clear yet whether this is a bug in the Javascript or in the revised Javascript tester. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-466) CMIS UI test fails
[ https://issues.apache.org/jira/browse/CONNECTORS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-466. Resolution: Fixed CMIS UI test fails -- Key: CONNECTORS-466 URL: https://issues.apache.org/jira/browse/CONNECTORS-466 Project: ManifoldCF Issue Type: Bug Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The CMIS UI test fails. Not clear yet whether this is a bug in the Javascript or in the revised Javascript tester. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-464) Hopcount logic does not remove all references to a document when the document is deleted from the queue
Karl Wright created CONNECTORS-464: -- Summary: Hopcount logic does not remove all references to a document when the document is deleted from the queue Key: CONNECTORS-464 URL: https://issues.apache.org/jira/browse/CONNECTORS-464 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.5, ManifoldCF 0.4, ManifoldCF 0.3, ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When a document is deleted during crawling, the hopcount, intrinsiclink, and hopdeletedeps tables are incompletely cleaned up to reflect the deletion. Specifically, only child references of the document are removed; references from parents are not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-464) Hopcount logic does not remove all references to a document when the document is deleted from the queue
[ https://issues.apache.org/jira/browse/CONNECTORS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259081#comment-13259081 ] Karl Wright commented on CONNECTORS-464: r1328881 Hopcount logic does not remove all references to a document when the document is deleted from the queue --- Key: CONNECTORS-464 URL: https://issues.apache.org/jira/browse/CONNECTORS-464 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3, ManifoldCF 0.4, ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 When a document is deleted during crawling, the hopcount, intrinsiclink, and hopdeletedeps tables are incompletely cleaned up to reflect the deletion. Specifically, only child references of the document are removed; references from parents are not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-347) MySQL HopCount test sometimes fails
[
https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259082#comment-13259082
]
Karl Wright commented on CONNECTORS-347:
I've created (and resolved) a new ticket, CONNECTORS-464, to cover the
long-standing document deletion cleanup problem.
MySQL HopCount test sometimes fails
---
Key: CONNECTORS-347
URL: https://issues.apache.org/jira/browse/CONNECTORS-347
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
The HopcountMySQLIT test sometimes fails complaining that it is expecting to
see 6 documents but only sees 4.
{code}
[junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
number of documents processed - expected 6, saw 4
[junit] at
org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
{code}
This does not happen on every run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-465) Python UI tester needs an overhaul
[ https://issues.apache.org/jira/browse/CONNECTORS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-465. Resolution: Fixed Python UI tester needs an overhaul -- Key: CONNECTORS-465 URL: https://issues.apache.org/jira/browse/CONNECTORS-465 Project: ManifoldCF Issue Type: Improvement Components: Tests Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The python UI tester needs to handle references reasonably throughout its entire expression evaluation process, rather than special-casing them deep inside the innermost level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-465) Python UI tester needs an overhaul
[ https://issues.apache.org/jira/browse/CONNECTORS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259176#comment-13259176 ] Karl Wright commented on CONNECTORS-465: r1328897 Python UI tester needs an overhaul -- Key: CONNECTORS-465 URL: https://issues.apache.org/jira/browse/CONNECTORS-465 Project: ManifoldCF Issue Type: Improvement Components: Tests Affects Versions: ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 The python UI tester needs to handle references reasonably throughout its entire expression evaluation process, rather than special-casing them deep inside the innermost level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-265) Remove all the HTML snippets from the Java code
[ https://issues.apache.org/jira/browse/CONNECTORS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114625#comment-13114625 ] Karl Wright commented on CONNECTORS-265: Could you attach a patch for this before committing? I'd love to see what the plan is. Remove all the HTML snippets from the Java code --- Key: CONNECTORS-265 URL: https://issues.apache.org/jira/browse/CONNECTORS-265 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 48h Remaining Estimate: 48h We have to start to remove all the HTML code inside Java classes, I started a refactoring to create a simple outputResource method that can be considered globally for all the connectors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114626#comment-13114626 ] Karl Wright commented on CONNECTORS-257: Any progress on this ticket? If you want, I can perhaps attach an updated patch this evening describing what I think needs to be done. Input-able response lifetime for Active Directory authority --- Key: CONNECTORS-257 URL: https://issues.apache.org/jira/browse/CONNECTORS-257 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-257-1.patch The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want not to access Active Directory frequently, I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-266) Upgrade to OpenCMIS 0.5.0
[ https://issues.apache.org/jira/browse/CONNECTORS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114725#comment-13114725 ] Karl Wright commented on CONNECTORS-266: Are there any new capabilities as far as user ACLs are concerned? We need to keep abreast of developments in that area. Upgrade to OpenCMIS 0.5.0 - Key: CONNECTORS-266 URL: https://issues.apache.org/jira/browse/CONNECTORS-266 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 48h Remaining Estimate: 48h We have to upgrade the CMIS Connector with the latest stable OpenCMIS release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-263) Long-running tests should all be moved to Maven's integration-test phase
[ https://issues.apache.org/jira/browse/CONNECTORS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114734#comment-13114734 ] Karl Wright commented on CONNECTORS-263: We should update the how-to-build-and-deploy site page to correspond. Long-running tests should all be moved to Maven's integration-test phase Key: CONNECTORS-263 URL: https://issues.apache.org/jira/browse/CONNECTORS-263 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.4 Long-running tests should be moved to Maven's integration-test phase. (which are all in root-level tests directory) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-259) Support MySQL in the JDBC connector
Support MySQL in the JDBC connector --- Key: CONNECTORS-259 URL: https://issues.apache.org/jira/browse/CONNECTORS-259 Project: ManifoldCF Issue Type: New Feature Components: JDBC connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Fix For: ManifoldCF 0.4 A couple of folks would like to see the JDBC connector support MySQL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13109388#comment-13109388 ] Karl Wright commented on CONNECTORS-258: In order for me to do this, I have to figure out/get permissions to promote jars into the central maven repository. Can you tell me how this is done? Or, better yet, do you have these permissions yourself? pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-262) Ant build could download WSDL's for SharePoint, if the public Microsoft SharePoint site has them
Ant build could download WSDL's for SharePoint, if the public Microsoft SharePoint site has them Key: CONNECTORS-262 URL: https://issues.apache.org/jira/browse/CONNECTORS-262 Project: ManifoldCF Issue Type: Improvement Components: Build, SharePoint connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Shinichiro Abe Fix For: ManifoldCF 0.4 There is a public Microsoft SharePoint site. If we can get at it, we might be able to download the Microsoft WSDL's we need from it automatically during the download-dependencies target. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-263) Long-running tests should all be moved to Maven's integration-test phase
Long-running tests should all be moved to Maven's integration-test phase Key: CONNECTORS-263 URL: https://issues.apache.org/jira/browse/CONNECTORS-263 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Fix For: ManifoldCF 0.4 Long-running tests should be moved to Maven's integration-test phase. (which are all in root-level tests directory) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-261) Maven build needs to be conditionalized in order to handle proprietary connectors
[ https://issues.apache.org/jira/browse/CONNECTORS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13109422#comment-13109422 ] Karl Wright commented on CONNECTORS-261: Alex Ott says: I think, that problem with conditional dependencies/compilation could be solved using Maven profiles, so user could use them when working with code Maven build needs to be conditionalized in order to handle proprietary connectors - Key: CONNECTORS-261 URL: https://issues.apache.org/jira/browse/CONNECTORS-261 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright The maven build currently does not handle proprietary connectors, but should. This involves figuring out how to conditionalize it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13109430#comment-13109430 ] Karl Wright commented on CONNECTORS-258: r1173584 Committed script for setting up maven build, in both .sh and .bat forms. pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Attachments: mvn-bootstrap.sh Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108454#comment-13108454 ] Karl Wright commented on CONNECTORS-257: The patch looks technically correct. A couple of things I recommend changing, however: (1) A point of English: Let's call it Cache lifetime in the UI and in the configuration data, not Response lifetime. (2) It's probably better to parse the cache lifetime into a numeric member variable (a long) at either connect() or getSession() time. At getSession() time you can report an error if the number is incorrect. (3) When you parse the cache lifetime, you need to be careful because the parameter may be null (e.g. from an older installation). Input-able response lifetime for Active Directory authority --- Key: CONNECTORS-257 URL: https://issues.apache.org/jira/browse/CONNECTORS-257 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-257-1.patch The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want not to access Active Directory frequently, I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108456#comment-13108456 ] Karl Wright commented on CONNECTORS-257: I also found a technical problem - sorry! The line: protected static long responseLifetime = 6L; ... obviously cannot remain the same, since it is a static. Instead you will need to pass the response lifetime as an argument to the AuthorizationResponseDescription class - either that, or make that class non-static and move the responseLifetime variable to be a non-static member variable of the connector class. Otherwise individual authorities will have their cache lifetimes conflated. Input-able response lifetime for Active Directory authority --- Key: CONNECTORS-257 URL: https://issues.apache.org/jira/browse/CONNECTORS-257 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-257-1.patch The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want not to access Active Directory frequently, I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-256) Connector for crawling Wikis
[ https://issues.apache.org/jira/browse/CONNECTORS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-256: --- Component/s: Wiki connector Connector for crawling Wikis Key: CONNECTORS-256 URL: https://issues.apache.org/jira/browse/CONNECTORS-256 Project: ManifoldCF Issue Type: New Feature Components: Wiki connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 People have been trying to crawl wikis with ManifoldCF, but using the generic crawler is not a good way to do this. Instead, it looks like we really could use a wiki connector, which would understand the wiki API and thus crawl wiki content quickly and effectively. Some pertinent API references follow: I don't know if it is possible to link to a wiki document with just the pageid, but it is possible to to get the url for the referring pageid via api: http://en.wikipedia.org/w/api.php?action=queryprop=infopageids=27697087inprop=url It is possible to get the metadata of a document using the pages id (instead of title) directly: Titel - http://en.wikipedia.org/w/api.php?action=queryprop=revisionstitles=APIrvprop=timestamp|user|comment|content PageID - http://en.wikipedia.org/w/api.php?action=queryprop=revisionspageids=27697087rvprop=timestamp|user|comment|content - There needs to be some notion of an overall list of pages: - http://www.mediawiki.org/wiki/API:Allpages - Example: http://en.wikipedia.org/w/api.php?action=querylist=allpagesapfrom=Kreaplimit=5 - Metadata information (author and pub date) also needs to be separated out in some way: - http://www.mediawiki.org/wiki/API:Properties#Revisions:_Example - Example: http://en.wikipedia.org/w/api.php?action=queryprop=revisionstitles=API|Main%20Pagervprop=timestamp|user|comment|content -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-158) SharePoint 2010 evaluation needed; possible changes and removal of custom web service for this version
[ https://issues.apache.org/jira/browse/CONNECTORS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107153#comment-13107153 ] Karl Wright commented on CONNECTORS-158: If you have a test setup, it would be great to find out if the current connector still works on sharepoint 2010. SharePoint 2010 evaluation needed; possible changes and removal of custom web service for this version -- Key: CONNECTORS-158 URL: https://issues.apache.org/jira/browse/CONNECTORS-158 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next We need to evaluate the SharePoint connector against SharePoint 2010. The goal would be to see if it works, and also to see if Microsoft provides functionality that would make the deployment of the custom MCPermissions web service unnecessary for this version of SharePoint. Modifications may be necessary or desired based on what the research indicates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-255) Consider adding SiteMap support to RSS connector
Consider adding SiteMap support to RSS connector Key: CONNECTORS-255 URL: https://issues.apache.org/jira/browse/CONNECTORS-255 Project: ManifoldCF Issue Type: New Feature Components: RSS connector, Web connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The RSS connector seems well suited for parsing sitemap XML and just doing the right thing. I'd propose adding the ability to parse sitemap XML in addition to parsing RSS and Atom. I would not go so far as automatically picking up the SiteMap field from robots.txt yet, however, since that would require another level of indirection that would need to be thought out. A direct reference in the RSS URLs field to the root sitemap URL would be where I'd start. The Web connector should, of course, also get the ability to do this parsing, as it has for RSS feeds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-255) Consider adding SiteMap support to RSS connector
[ https://issues.apache.org/jira/browse/CONNECTORS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106011#comment-13106011 ] Karl Wright commented on CONNECTORS-255: r1171519. Consider adding SiteMap support to RSS connector Key: CONNECTORS-255 URL: https://issues.apache.org/jira/browse/CONNECTORS-255 Project: ManifoldCF Issue Type: New Feature Components: RSS connector, Web connector Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 The RSS connector seems well suited for parsing sitemap XML and just doing the right thing. I'd propose adding the ability to parse sitemap XML in addition to parsing RSS and Atom. I would not go so far as automatically picking up the SiteMap field from robots.txt yet, however, since that would require another level of indirection that would need to be thought out. A direct reference in the RSS URLs field to the root sitemap URL would be where I'd start. The Web connector should, of course, also get the ability to do this parsing, as it has for RSS feeds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105367#comment-13105367 ] Karl Wright commented on CONNECTORS-202: Hi Jan, please let me know if the attached code patch works for you. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-202-code.patch, CONNECTORS-202.patch The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104317#comment-13104317
]
Karl Wright commented on CONNECTORS-254:
It appears that the major difference is that curl's POST is not a multi-part
post. It's apparently the multi-part form post with zero-length content that
Solr (or Jetty) doesn't like.
The Solr connector must use multi-part in order to include other fields such as
metadata, so it's not an option to do things just like post.sh does. Can you
modify the curl POST command to do a multi-part form post, and try that with a
zero-length file? Then we can really compare apples against apples.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104330#comment-13104330
]
Karl Wright commented on CONNECTORS-254:
I fooled around with curl and found the command we need. Here it is (assuming
hello.txt is a zero-length file):
curl --trace dump.out -location -F id=123 -F file=@hello.txt
http://localhost:8983/solr/update/extract
The --trace option dumps a trace file which is essentially equivalent to
wireshark output. Good to know. Anyway, when I try this, I get the following
in Solr:
Sep 14, 2011 3:45:45 AM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:50)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
at
org.apache.solr.core.RequestHandlers$LazyRequestHandlerWrapper.handleRequest(RequestHandlers.java:238)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1360)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:356)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:252)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Sep 14, 2011 3:45:45 AM org.apache.solr.core.SolrCore execute
INFO: [] webapp=/solr path=/update/extract params={id=123} status=400 QTime=300
If this looks familiar, it's because we get the exact same trace when
multi-part form posting from ManifoldCF. So there is apparently a bug in Solr,
and there's no magic here.
My suggestion is that you follow up by creating a Solr ticket, trying to be
sure there isn't one already. I'll ping Simon and see if he knows anything.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104332#comment-13104332 ] Karl Wright commented on CONNECTORS-252: I just ran into a problem with this. If the after-build cleanup is run automatically, then each subsequent build is essentially building clean, and thus this is much much slower for development work. Could we separate out the after-build cleanup and leave it in its own target? Either that, or have two different build targets, one for development and one for casual builders? clean up build, dist and lib of each connector after build -- Key: CONNECTORS-252 URL: https://issues.apache.org/jira/browse/CONNECTORS-252 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-252.patch After running ant build, folder size increases about five times. Building resources in connectors are expected not to use, except for test output. I want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-252: clean up build, dist and lib of each connector after build -- Key: CONNECTORS-252 URL: https://issues.apache.org/jira/browse/CONNECTORS-252 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-252.patch After running ant build, folder size increases about five times. Building resources in connectors are expected not to use, except for test output. I want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104396#comment-13104396 ] Karl Wright commented on CONNECTORS-252: looks good, please go ahead and commit clean up build, dist and lib of each connector after build -- Key: CONNECTORS-252 URL: https://issues.apache.org/jira/browse/CONNECTORS-252 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-252-1.patch, CONNECTORS-252-2.patch, CONNECTORS-252.patch After running ant build, folder size increases about five times. Building resources in connectors are expected not to use, except for test output. I want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104449#comment-13104449
]
Karl Wright commented on CONNECTORS-254:
I created a Solr ticket for the problem. SOLR-2763.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103465#comment-13103465
]
Karl Wright commented on CONNECTORS-254:
I have some concerns about this approach.
First, I'm not sure it is the right thing to do. It would be good to know more
about the case you are comparing against when you say On the other hand when
using Solr request handler without MCF, this exception is not thrown and the
posting 0 byte files is indexed normally. How are you posting the content
normally? When you post the content in that way, what does the entire http
request look like? You can use Wireshark to capture it, or I can, so we can
see exactly what happens in that case.
Second, if it turns out that adding a space is the correct thing to do, I'm
concerned because this change is not being reflected in the content-length
header. If the header reports a different length than what is posted, the
posted data will be truncated. This may be the whole goal, though, in which
case we should add a comment to the code noting that the content MUST be the
last field posted for this reason.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103589#comment-13103589 ] Karl Wright commented on CONNECTORS-202: Looks fine. I'll commit it and update the site this evening. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-202.patch The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103622#comment-13103622 ] Karl Wright commented on CONNECTORS-202: r1170174 for the documentation update. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-202.patch The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103639#comment-13103639
]
Karl Wright commented on CONNECTORS-254:
The curl command you have described is not even a POST, it's a GET. The
document itself is not being sent, just the file name. The stream.file
argument may well be used by Solr on the update handler side to open the file
directly. That's not going to work with ManifoldCF though because there's no
guarantee of a shared file system between ManifoldCF and the Solr instance.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103678#comment-13103678
]
Karl Wright commented on CONNECTORS-254:
The --data-binary switch to curl causes it to use POST. Here's a bit of the
manpage:
--data-binary data
(HTTP) This posts data exactly as specified with no extra proâ
cessing whatsoever.
So, what happens when you use curl to post your zero-length file? Do you get
back a 400 response? Try using the CURL -vvv switch to see what it is doing.
If it comes back with a 200 OK response and not a 400, then either you or I
should try to do the same thing while Wireshark is capturing packets. If you
are using a Linux system, you could instead want to use tcpdump to do the
capture, and then examine the capture with Wireshark (on Windows). If this is
too confusing, now that I have a test case I can try to do this later today.
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
Attachments: CONNECTORS-254-1.patch, sample0byte.zip
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. missing content stream. Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txtliteral.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103187#comment-13103187 ] Karl Wright commented on CONNECTORS-251: This looks very good. I think it is now ready to commit. Sorry about the Oracle jar problem - I think they make it impossible because they want all your contact info first. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-251-1.patch, CONNECTORS-251-2.patch, CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102003#comment-13102003 ] Karl Wright commented on CONNECTORS-251: It occurred to me also that the JDBC connector could benefit from this. It should download the jtds MSSQL/Sybase JDBC driver, and maybe (if we can figure out how) the Oracle JDBC driver. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-251-1.patch, CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101047#comment-13101047 ] Karl Wright commented on CONNECTORS-250: Shinichiro, you should go ahead and commit this. Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101048#comment-13101048 ] Karl Wright commented on CONNECTORS-251: We cannot redistribute jcifs.jar, but the code can certainly download it. So you can go ahead and commit this patch too. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101050#comment-13101050 ] Karl Wright commented on CONNECTORS-251: Final comment: Since we build the images for distribution using ant, we need some way of PREVENTING the download in that case. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101049#comment-13101049 ] Karl Wright commented on CONNECTORS-251: The only caution I have is that, if the person is running off of the net, the download might fail. The conditional logic looks like it would catch that situation though. Just so long as the build does not fail in that case. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101058#comment-13101058 ] Karl Wright commented on CONNECTORS-251: Thinking further on this, making this completely automatic won't work because there's no good way in ant to make one dependency of a target fire before another dependency of the same target, without linking the two dependencies together. So instead I'd propose we introduce a new root-level target as well, download-dependencies, which does the job of picking up the non-redistributable dependencies for all connectors. In practice this will just be the jcifs.jar at this time. But the build structure should support each connector making the determination of what to download. jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-253) Script test fails on some machines due to hash order
Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-253: -- Assignee: Karl Wright Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101066#comment-13101066 ] Karl Wright commented on CONNECTORS-253: r1167039 in trunk. r1167043 in release-0.3-incubating branch. Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-253) Script test fails on some machines due to hash order
[ https://issues.apache.org/jira/browse/CONNECTORS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-253. Resolution: Fixed Script test fails on some machines due to hash order Key: CONNECTORS-253 URL: https://issues.apache.org/jira/browse/CONNECTORS-253 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 On some machines, the following failure is seen: run-script-engine-tests: [junit] Testsuite: org.apache.manifoldcf.scriptengine.tests.ExpressionTest [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.092 sec [junit] [junit] Testcase: basicConfigurationnodeOperations(org.apache.manifoldcf.scriptengine.tests.ExpressionTest): FAILED [junit] expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] junit.framework.AssertionFailedError: expected:...e : value : attr[1=av1, attr2=av2] : childn1 : ... but was:...e : value : attr[2=av2, attr1=av1] : childn1 : ... [junit] at org.apache.manifoldcf.scriptengine.tests.ExpressionTest.basicConfigurationnodeOperations(ExpressionTest.java:514) [junit] [junit] BUILD FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-250: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF 0.3 Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-250) Dead link for jcifs.jar
[ https://issues.apache.org/jira/browse/CONNECTORS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101116#comment-13101116 ] Karl Wright commented on CONNECTORS-250: r1167088 for release-0.3-incubating branch. Dead link for jcifs.jar --- Key: CONNECTORS-250 URL: https://issues.apache.org/jira/browse/CONNECTORS-250 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-250.patch Jcifs site link is incorrect at how-to-build-and-deploy.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-240. Resolution: Fixed r1167110 (trunk) OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: opensearchserver-connection-parameters.PNG, opensearchserver-history-report.PNG, opensearchserver-job-parameters.PNG, opensearchserver-user.PNG, oss-mfc-doc.patch, oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-202: --- Affects Version/s: ManifoldCF 0.3 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Assignee: Karl Wright SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-87) Connector Framework load test needs to be written
[ https://issues.apache.org/jira/browse/CONNECTORS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-87: -- Affects Version/s: ManifoldCF 0.3 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Assignee: Karl Wright Connector Framework load test needs to be written - Key: CONNECTORS-87 URL: https://issues.apache.org/jira/browse/CONNECTORS-87 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 LCF needs a load or performance test, which verifies that the core software is performing as expected. This test can use the file system connector, but must verify that individual throttle bins are getting approximately equal time, and that the system as a whole is behaving efficiently. Furthermore, at least 1,000,000 documents should be crawled by this test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101586#comment-13101586 ] Karl Wright commented on CONNECTORS-202: MCF 0.3 RC1 is currently under review as well. I've triaged this ticket for the 0.4 release. SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Jan Høydahl Assignee: Karl Wright Labels: commit Fix For: ManifoldCF 0.4 The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100509#comment-13100509 ] Karl Wright commented on CONNECTORS-240: I put together an RC0, but have not yet called a vote. If you can contribute the documentation by tomorrow, I'll spin an RC1 after it's merged. OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13097794#comment-13097794 ] Karl Wright commented on CONNECTORS-240: That's great! I'm holding the 0.3 release a day or two in hopes of getting more complete documentation for this connector. Please let me know if anything happens that impact your plans, and thanks again! OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-246) A file crawl exited with an unexpected jobqueue status error under HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-246. Resolution: Fixed r1165561. A file crawl exited with an unexpected jobqueue status error under HSQLDB --- Key: CONNECTORS-246 URL: https://issues.apache.org/jira/browse/CONNECTORS-246 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Under HSQLDB, a file crawl terminated with: Error: Unexpected jobqueue status - record id 1314721269570, expecting active status. The full trace was: ERROR 2011-08-30 12:23:48,962 (Worker thread '38') - Exception tossed: Unexpected jobqueue status - record id 1314721269570, expecting active status org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected jobqueue status - record id 1314721269570, expecting active status at org.apache.manifoldcf.crawler.jobs.JobQueue.updateCompletedRecord(JobQueue.java:633) at org.apache.manifoldcf.crawler.jobs.JobManager.markDocumentCompletedMultiple(JobManager.java:2386) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:798) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
[ https://issues.apache.org/jira/browse/CONNECTORS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-248. Resolution: Fixed r1165561. File system crawl with HSQLDB aborts with a constraint error Key: CONNECTORS-248 URL: https://issues.apache.org/jira/browse/CONNECTORS-248 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 While running two jobs with overlapping files with HSQLDB, I got this error on the second job that aborted it: Error: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS The complete exception is here: ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) at org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) at org.apache.manifoldcf.core.database.Database.execute(Database.java:606) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.error.Error.error(Error.java:134) at org.hsqldb.Constraint.getException(Constraint.java:914) at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) at org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) at org.hsqldb.Session.addInsertAction(Session.java:434) at org.hsqldb.Table.insertSingleRow(Table.java:2553) at org.hsqldb.StatementDML.update(StatementDML.java:1032) at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) at org.hsqldb.StatementDML.getResult(StatementDML.java:196) at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) at org.hsqldb.Session.execute(Session.java:993) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
[ https://issues.apache.org/jira/browse/CONNECTORS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13097798#comment-13097798 ] Karl Wright commented on CONNECTORS-248: Attempts to turn this into a standard test failed because it needs at least 20 minutes of run time to reliably cause the problem. Nevertheless I've got a test, just trying to figure out where to check it in so it doesn't get run all the time. File system crawl with HSQLDB aborts with a constraint error Key: CONNECTORS-248 URL: https://issues.apache.org/jira/browse/CONNECTORS-248 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 While running two jobs with overlapping files with HSQLDB, I got this error on the second job that aborted it: Error: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS The complete exception is here: ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) at org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) at org.apache.manifoldcf.core.database.Database.execute(Database.java:606) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.error.Error.error(Error.java:134) at org.hsqldb.Constraint.getException(Constraint.java:914) at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) at org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) at org.hsqldb.Session.addInsertAction(Session.java:434) at org.hsqldb.Table.insertSingleRow(Table.java:2553) at org.hsqldb.StatementDML.update(StatementDML.java:1032) at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) at org.hsqldb.StatementDML.getResult(StatementDML.java:196) at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) at org.hsqldb.Session.execute(Session.java:993) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
