Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cbdb-data-0.6.1.xar 362358k Error unziping the package #71

Closed
pingtzuchu opened this issue Jul 12, 2017 · 8 comments · Fixed by #73
Closed

cbdb-data-0.6.1.xar 362358k Error unziping the package #71

pingtzuchu opened this issue Jul 12, 2017 · 8 comments · Fixed by #73
Assignees
Labels

Comments

@pingtzuchu
Copy link

there is no log file related to this in exist.
eXistdb 3.3 in Tomcat

@duncdrum duncdrum self-assigned this Jul 12, 2017
@duncdrum
Copy link
Owner

duncdrum commented Jul 12, 2017

thanks for the report. According to the documentation the log files should be in either webapp/WEB-INF/logs or in tools/yajsw/logs. I m particularly interested in the exist.log file.
Also how much memory does exist's JVM have? cbdb-data requires a min. of 2GB. But with multiple larger apps in the same exist instance more might be necessary.

@duncdrum
Copy link
Owner

duncdrum commented Jul 13, 2017

@pingtzuchu i see two different types of errors in the logs on Jetty:

[eXist Version : 3.0]
...
2017-07-13 09:03:47,615 [Thread-5] ERROR (Configurator.java [configureByCurrent]:510) - Could not insert configured object 
2017-07-13 09:03:47,615 [Thread-5] ERROR (Configurator.java [configureByCurrent]:557) - Field 'managers' must have '@org.exist.config.annotation.ConfigurationFieldClassMask' annotation [manager], skipping instance creation.
...
2017-07-13 09:05:16,114 [qtp1734049882-42] ERROR (Deploy.java [installAndDeployFromDb]:215) - Error unziping the package 
org.expath.pkg.repo.PackageException: Error unziping the package
…
Caused by: java.nio.file.FileSystemException: c:\eXist-db\webapp\WEB-INF\data\expathrepo\.expath-pkg\install-20170713-8017609748529779274.d\modules\aux.xql: 參數錯誤。

and on tomcat

[eXist Version : 3.0]
...
SEVERE|wrapper|Service eXist-db|17-05-29 11:30:28|java file does not exist: C:\Program Files\Java\jre1.8.0_121\bin\java.exe
SEVERE|wrapper|Service eXist-db|17-05-29 11:30:28|ERROR: could not get java command

While cbdb-data should run on 3.0,I would recommend updating exist to 3.3 😉 regardless. I have an idea what might be causing the error but i ll have to investigate a bit more.

@duncdrum duncdrum added the bug label Jul 13, 2017
@pingtzuchu
Copy link
Author

pingtzuchu commented Jul 14, 2017 via email

@pingtzuchu
Copy link
Author

pingtzuchu commented Jul 14, 2017 via email

@duncdrum
Copy link
Owner

duncdrum commented Jul 15, 2017

  • The problem with Monex under Tomcat is a known issue, not sure why it hasn't been resolved.

  • As for the eXist Version in the logs:
    I ran version-test.xql from the temp folder:

"exist version: " || util:system-property("product-version") || " build: " || util:system-property("product-build")

The result:

exist version: 3.3.0 build: 201707021658

So there is a separate issue with the logs. I'll open a ticket

  • Potential fix for the installation troubles on Win systems incoming. I'll let you know how it goes, in here.

@pingtzuchu
Copy link
Author

pingtzuchu commented Jul 15, 2017 via email

duncdrum added a commit that referenced this issue Jul 15, 2017
… but there are more
see #71
@duncdrum
Copy link
Owner

Progress: The collection cache couldn't handle that many files, but the original error is fixed.
screenshot 2017-07-15 18 09 19

@duncdrum duncdrum mentioned this issue Jul 15, 2017
@duncdrum
Copy link
Owner

Ok the windows file system error is no more, I was an idiot. New release is uploading, once pulled in the issue will close. Installing on systems with insufficient memory is no longer possible.

@pingtzuchu check the temp folder on your tomcat exist.

duncdrum added a commit that referenced this issue Jul 15, 2017
* tackling windows illiteracy one step at a time closes #71
* new ant comments
* add cache warning to Readme
* add debug build target for faster testing
* check user config at pre-install
* bump version 0.6.4

* allign readme with pre-install errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants