[Exist-open] Problem launching eXist java admin client - commons-pool version mismatch?

[Joe Wicentowski <joewiz@gm...>]

Hi all,

Is anyone else having trouble launching the eXist java admin client
with 1.5dev trunk (rev. 15346)?  I'm using a vanilla build, and have
performed the jarsigner step after building.  I'm downloading a fresh
.jnlp file via http://localhost:8080/exist/webstart/exist.jnlp.

Based on the exception (see below), it appears that the jnlp is trying
to load commons-pool-1.5.5.jar, but the version of this jar in trunk
is 1.5.6.  I'm not sure what needs to be changed in order to reflect
the newer version number.  Does anyone have any tips?

Thanks,
Joe


The Launch File tab has this:

<jnlp spec="1.0+" codebase="http://localhost:8080/exist/webstart/";
href="exist.jnlp">
    <information>
        <title>eXist XML-DB client</title>
        <vendor>exist-db.org</vendor>
        <homepage href="http://exist-db.org"/>;
        <description>Integrated command-line and gui client, entirely
based on the XML:DB API and
            provides commands for most database related tasks, like
creating and removing
            collections, user management, batch-loading XML data or
querying.</description>
        <description kind="short">eXist XML-DB client</description>
        <description kind="tooltip">eXist XML-DB client</description>
        <icon href="jnlp_logo.jpg"/>
        <icon href="jnlp_icon_64x64.gif" width="64" height="64"/>
        <icon href="jnlp_icon_32x32.gif" width="32" height="32"/>
    </information>
    <security>
        <all-permissions/>
    </security>
    <resources>
        <property name="jnlp.packEnabled" value="true"/>
        <j2se version="1.6+"/>
        <jar href="log4j-1.2.16.jar" size="503035"/>
        <jar href="ws-commons-util-1.0.2.jar" size="37759"/>
        <jar href="commons-pool-1.5.5.jar" size="106181"/>
        <jar href="exist.jar" size="4269592"/>
        <jar href="xmlrpc-common-3.1.3.jar" size="119439"/>
        <jar href="slf4j-api-1.6.1.jar" size="28736"/>
        <jar href="sunxacml-1.2.jar" size="205991"/>
        <jar href="excalibur-cli-1.0.jar" size="25695"/>
        <jar href="xmldb.jar" size="12214"/>
        <jar href="xmlrpc-client-3.1.3.jar" size="64043"/>
        <jar href="slf4j-log4j12-1.6.1.jar" size="11702"/>
        <jar href="jline-0.9.94.jar" size="91962"/>
        <jar href="jEdit-syntax.jar" size="85723"/>
    </resources>
    <application-desc main-class="org.exist.client.InteractiveClient">
        <argument>-ouri=xmldb:exist://localhost:8080/exist/xmlrpc</argument>;
        <argument>--no-embedded-mode</argument>
    </application-desc>
</jnlp>

The Exception tab says:

java.io.FileNotFoundException:
http://localhost:8080/exist/webstart/commons-pool-1.5.5.jar
	at sun.reflect.GeneratedConstructorAccessor3.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
	at com.sun.deploy.net.BasicHttpRequest.doRequest(BasicHttpRequest.java:229)
	at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(BasicHttpRequest.java:63)
	at com.sun.deploy.net.DownloadEngine.isUpdateAvailable(DownloadEngine.java:941)
	at com.sun.deploy.net.DownloadEngine.isUpdateAvailable(DownloadEngine.java:838)
	at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(DownloadEngine.java:1574)
	at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(DownloadEngine.java:1534)
	at com.sun.deploy.net.DownloadEngine.getResource(DownloadEngine.java:217)
	at com.sun.javaws.LaunchDownload$DownloadTask.call(LaunchDownload.java:1983)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:680)
Caused by: java.io.FileNotFoundException:
http://localhost:8080/exist/webstart/commons-pool-1.5.5.jar
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
	at com.sun.deploy.net.BasicHttpRequest.doRequest(BasicHttpRequest.java:190)
	... 12 more

[Exist-open] conf.xml comparision between 1.4.0 and 1.4.1(eXist-setup-1.4.1-rev15155.jar)

[kyung88 <ginachoi88@gm...>]

HI,

I am planning to upgrade eXist database from 1.4.0 to 1.4.1. So I download
eXist-setup-1.4.1-rev15155.jar and made comparison on conf.xml.

1. Line138-140( 1.4.1)

1.4.1
    <db-connection cacheSize="48M" collectionCache="24M" database="native"
        files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="1000"
	doc-ids="default">

1.4.0
    <db-connection cacheSize="48M" collectionCache="24M"
database="@database@"
        files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="-1">

Differences: I see doc-ids is added in 1.4.1. How do we use doc-ids? Do I
need to make changes for my application since doc-dis is added? Value of
nodesBuffer is changed from "-1" to "1000". What does this mean?


2. Line 346(1.4.1)

1.4.1
        <watchdog output-size-limit="-1" query-timeout="-1"/>

1.4.0

       <watchdog output-size-limit="1000000" query-timeout="-1"/>

Differences: Value of output-size-limit is changed from "1000000" to "-1".
What does this change mean? Do I need to make corresponding changes to my
application?


Thanks.

Gina

--
View this message in context: http://exist.2174344.n4.nabble.com/conf-xml-comparision-between-1-4-0-and-1-4-1-eXist-setup-1-4-1-rev15155-jar-tp3807616p3807616.html
Sent from the exist-open mailing list archive at Nabble.com.

[Exist-open] what character encoding does backup use for file names?

[Chris Tomlinson <chris.j.tomlinson@gm...>]

Hello,

I have an issue with eXist backup. Versions 1.4.x rev 13904 and 1.5 rev 15339 on Mac OS/X 10.6.8 and 10.7.1. The situation is that users self-register and we create a profile document for the user which has the chosen user id as the name of the profile document. Some users are entering their names in Chinese or Tibetan Unicode, e.g.:

ཉི་མ་

or

བཀྲ་ཤིས་

When we do a backup the profiles for these names are showing up on the file system with names like:

�ི��.xml

Mac OS/X is perfectly capable of using Unicode Tibetan and Chinese file names and the above looks like maybe ISO-8859/1 or similar.

When I look at the profile collection with the Java client the names look reasonable so it seems like the documents are being created properly.

Also if I do a backup and restore in 1.4.x then whatever the encoding is it is getting converted back into Tibetan / Chinese; 

HOWEVER, when I try to use the backup from 1.4.x to migrate to 1.5 by doing a restore the names appear the same as in the file system so the correspondence to user ids is lost.

I'm not sure what to do now in order to migrate the profiles from 1.4.x to 1.5

Thanks for any thoughts on the matter,
Chris