eXist with Windows 10 - working at all?

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

eXist with Windows 10 - working at all?

Joe Wicentowski
Hi all,

I've been seeing reports here of people with Windows 10 having
problems installing eXist 3.1.1. Do we know if anyone has successfully
installed eXist 3.1.1 on Windows 10?

I ask because I have recently got another office in my organization
interested in eXist, and they wrote saying they were having trouble
installing it on a Windows 10 machine. They are complete newbies,
though, so even asking for logging info will be intimidating for them.

Any info on known routes to success with Windows would be very
helpful!  Has anyone had success?

Thanks,
Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Dominique Rabeuf
I have successfully installed eXist 3.1.1
under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits


I have tried to install under Windows 10 with Java 8 (build 1.8.0_121-b13) x86
The service eXist-db is created with status stopped
When click on start in Windows Monitor the service is displayed as started then stopped after a while
Below the exist.log after a new installation this morning
Next the Wapper Log reports
several start/stop due to time out
and finally:
too many restarts,

--------------------------------------------------------
2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) - Reading configuration from file c:\eXist-db\conf.xml
2017-03-31 10:08:48,679 [main] INFO  (Configuration.java [configureStartup]:1280) - Registered StartupTrigger: org.exist.security.GnuCryptoJceProviderStartupTrigger
2017-03-31 10:08:48,679 [main] INFO  (Configuration.java [configureStartup]:1280) - Registered StartupTrigger: org.exist.protocolhandler.URLStreamHandlerStartupTrigger
2017-03-31 10:08:48,679 [main] INFO  (Configuration.java [configureStartup]:1280) - Registered StartupTrigger: org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
2017-03-31 10:08:48,698 [main] INFO  (Configuration.java [configureStartup]:1280) - Registered StartupTrigger: org.exist.repo.AutoDeploymentTrigger
2017-03-31 10:08:48,958 [main] ERROR (Configuration.java [lookupModuleClass]:448) - Configuration problem: class not found for module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException); class:'org.exist.xquery.modules.jndi.JNDIModule'; message:'org.exist.xquery.modules.jndi.JNDIModule'
2017-03-31 10:08:48,958 [main] INFO  (Configuration.java [configureValidation]:1490) - Add catalog uri file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) - Initializing GrammarPool.
2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) - database instance 'exist' will wait  120 000 ms during shutdown
2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) - database instance 'exist' is enabled for recovery : true
2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) - database instance 'exist' will have between 1 and 20 brokers
2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) - database instance 'exist' will be synchronized every 120 000 ms
2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java [<init>]:139) - The cacheSize="256" setting in conf.xml is too large. Java has only 760256k available. Cache manager will not use more than 253418k to avoid memory issues which may lead to database corruptions.
2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354; maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) - QueryPool: size = 128; maxStackSize = 64; timeout = 120 000; timeoutCheckInterval = 30 000
2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java [getQuartzProperties]:117) - Successfully loaded quartz.properties
2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118) - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118) - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118) - Registered index org.exist.indexing.sort.SortIndex as sort-index
2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118) - Registered index org.exist.indexing.range.RangeIndex as range-index
2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118) - Registered index org.exist.storage.structural.NativeStructuralIndex as structural-index
2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) - Using DATA_DIR: c:\eXist-data. Minimal disk space required for database to continue operations: 128mb
2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) - Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) - Memory: 63 424K total; 760 256K max; 34 774K free
2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619) - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency : 100 %
2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out of 256) Cache efficiency : 100 %
2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619) - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency : 100 %
2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419) - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache efficiency : 100 %
2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619) - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency : N/A
2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419) - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache efficiency : N/A
2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/config.xml
2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/exist/accounts/admin.xml
2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/config.xml
2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java [removeXMLResource]:2707) - Removing document config.xml (2) ...
2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/exist/accounts/admin.xml
2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java [removeXMLResource]:2707) - Removing document admin.xml (3) ...
2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/exist/accounts/guest.xml
2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/config.xml
2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java [removeXMLResource]:2707) - Removing document config.xml (2) ...
2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/exist/accounts/guest.xml
2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java [removeXMLResource]:2707) - Removing document guest.xml (4) ...
2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/plugins/config.xml
2017-03-31 10:08:49,858 [main] INFO  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE Security Provider: gnu.crypto.jce.GnuCrypto
2017-03-31 10:08:49,858 [main] INFO  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61) - Successfully registered eXistURLStreamHandlerFactory.
2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) - Storing configuration /db/system/security/exist/accounts/admin.xml
2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java [removeXMLResource]:2707) - Removing document admin.xml (3) ...
2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) - Database is shutting down ...
2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) - Transaction journal cleanly shutting down with checkpoint...
2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) - Deleting lock file: c:\eXist-data\journal.lck
2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) - Deleting lock file: c:\eXist-data\dbx_dir.lck
2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread: Signal Dispatcher
2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread: Finalizer
2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread: Reference Handler
2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread: Attach Listener
2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread: Thread-3
2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) - shutdown complete !
2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO  (BrokerPools.java [run]:67) - Executing shutdown thread
2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO  (BrokerPools.java [run]:67) - Executing shutdown thread
2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO  (BrokerPools.java [run]:67) - Executing shutdown thread
-------------------------------------------------------------------------------------------
Here the Wrapper Log [Action start in Windows Monitor]
[WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows 10/10.0/x86
WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to default exit code rule
INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with pid/timeout 256 45000
INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to default exit code rule
INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with pid/timeout 560 45000
INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid 4700
INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to default exit code rule
INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with pid/timeout 4700 45000
INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid 9920
INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to default exit code rule
INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with pid/timeout 9920 45000
INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid 2148
INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to default exit code rule
INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with pid/timeout 2148 45000
INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid 5684
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - timeout: 30000
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service wrapper.control -> stopping application
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after shutdown
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - before notify
INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
----------------------------------------------------------------------------------------

If you have some experiments to suggest.  will try them


2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]>:
Hi all,

I've been seeing reports here of people with Windows 10 having
problems installing eXist 3.1.1. Do we know if anyone has successfully
installed eXist 3.1.1 on Windows 10?

I ask because I have recently got another office in my organization
interested in eXist, and they wrote saying they were having trouble
installing it on a Windows 10 machine. They are complete newbies,
though, so even asking for logging info will be intimidating for them.

Any info on known routes to success with Windows would be very
helpful!  Has anyone had success?

Thanks,
Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open



--
Dominique Rabeuf

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Joe Wicentowski
Thanks for your reply, Dominique.

So we have:

1. One confirmed successful install of eXist 3.1.1 under Windows
Server 2012 R2 with Java 8 (build 1.8.0_121-b13) 64 bits

2. One confirmed failed installation of eXist 3.1.1 under Windows 10
with Java 8 (build 1.8.0_121-b13) x86

Can anyone else report on their experience trying to install eXist
3.1.1 on Windows 10?

I'm afraid I do not have any Windows 10 machines to test on.

Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Joe Wicentowski
To the eXist developer team: I notice this warning about running YAJSW
in Windows since Vista:

  http://yajsw.sourceforge.net/#mozTocId245576

I assume eXist has already accounted for this limitation, but I'm
raising it just in case.

On Fri, Mar 31, 2017 at 1:08 PM, Joe Wicentowski <[hidden email]> wrote:

> Thanks for your reply, Dominique.
>
> So we have:
>
> 1. One confirmed successful install of eXist 3.1.1 under Windows
> Server 2012 R2 with Java 8 (build 1.8.0_121-b13) 64 bits
>
> 2. One confirmed failed installation of eXist 3.1.1 under Windows 10
> with Java 8 (build 1.8.0_121-b13) x86
>
> Can anyone else report on their experience trying to install eXist
> 3.1.1 on Windows 10?
>
> I'm afraid I do not have any Windows 10 machines to test on.
>
> Joe

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Martin Holmes
In reply to this post by Dominique Rabeuf
I have a Windows 10 vm that I use for testing various things, and I just
tried this out. It worked fine. For anyone struggling, these are the
steps I took.

I have the JDK 1.8 installed:

C:\Users\mholmes>echo %JAVA_HOME%
C:\Program Files\Java\jdk1.8.0_121

C:\Users\mholmes>java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

I ran the installer with

   java -jar exist-db-setup-3.1.1.jar

as a regular user.

I installed eXist with the default settings, except that I installed it
into:

   C:\Users\mholmes\exist-db

rather than the default c:\exist-db.

I set an admin password when prompted. When the installer completed and
started up the instance, I saw this:

The system cannot find the file C:\Program.
A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
exists.
"-Xms64m -Xmx768m
-Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
--- Starting embedded database instance ---
Setting admin user password...
--- Initialization complete. Shutdown embedded database instance ---

Then I launched exist from the start menu, or whatever it's called now.
I saw the splash screen and the usual process of installing demos etc.
Then Windows Firewall popped up to ask for access, which I gave it. Then
I went to localhost:8080 in my browser, and everything seemed to be
working fine.

Hope this helps,
Martin

On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:

> I have successfully installed eXist 3.1.1
> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>
>
> I have tried to install under Windows 10 with Java 8 (build
> 1.8.0_121-b13) x86
> The service eXist-db is created with status stopped
> When click on start in Windows Monitor the service is displayed as
> started then stopped after a while
> Below the exist.log after a new installation this morning
> Next the Wapper Log reports
> several start/stop due to time out
> and finally:
> too many restarts,
>
> --------------------------------------------------------
> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
> Reading configuration from file c:\eXist-db\conf.xml
> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
> [configureStartup]:1280) - Registered StartupTrigger:
> org.exist.security.GnuCryptoJceProviderStartupTrigger
> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
> [configureStartup]:1280) - Registered StartupTrigger:
> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
> [configureStartup]:1280) - Registered StartupTrigger:
> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
> [configureStartup]:1280) - Registered StartupTrigger:
> org.exist.repo.AutoDeploymentTrigger
> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
> [lookupModuleClass]:448) - Configuration problem: class not found for
> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
> class:'org.exist.xquery.modules.jndi.JNDIModule';
> message:'org.exist.xquery.modules.jndi.JNDIModule'
> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
> [configureValidation]:1490) - Add catalog uri
> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
> Initializing GrammarPool.
> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
> database instance 'exist' will wait  120 000 ms during shutdown
> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
> database instance 'exist' is enabled for recovery : true
> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
> database instance 'exist' will have between 1 and 20 brokers
> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
> database instance 'exist' will be synchronized every 120 000 ms
> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
> Java has only 760256k available. Cache manager will not use more than
> 253418k to avoid memory issues which may lead to database corruptions.
> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
> timeoutCheckInterval = 30 000
> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
> [getQuartzProperties]:117) - Successfully loaded quartz.properties
> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
> - Registered index org.exist.indexing.sort.SortIndex as sort-index
> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
> - Registered index org.exist.indexing.range.RangeIndex as range-index
> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
> - Registered index org.exist.storage.structural.NativeStructuralIndex as
> structural-index
> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
> to continue operations: 128mb
> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
> Memory: 63 424K total; 760 256K max; 34 774K free
> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
> : 100 %
> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
> of 256) Cache efficiency : 100 %
> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
> efficiency : 100 %
> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
> efficiency : 100 %
> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
> efficiency : N/A
> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
> efficiency : N/A
> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/config.xml
> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/exist/accounts/admin.xml
> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/config.xml
> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
> [removeXMLResource]:2707) - Removing document config.xml (2) ...
> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/exist/accounts/admin.xml
> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/exist/accounts/guest.xml
> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/config.xml
> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
> [removeXMLResource]:2707) - Removing document config.xml (2) ...
> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/exist/accounts/guest.xml
> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/plugins/config.xml
> 2017-03-31 10:08:49,858 [main] INFO
>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
> Security Provider: gnu.crypto.jce.GnuCrypto
> 2017-03-31 10:08:49,858 [main] INFO
>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
> - Successfully registered eXistURLStreamHandlerFactory.
> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
> Storing configuration /db/system/security/exist/accounts/admin.xml
> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
> Database is shutting down ...
> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
> Transaction journal cleanly shutting down with checkpoint...
> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
> Deleting lock file: c:\eXist-data\journal.lck
> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
> Deleting lock file: c:\eXist-data\dbx_dir.lck
> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
> Signal Dispatcher
> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
> Finalizer
> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
> Reference Handler
> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
> Attach Listener
> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
> Thread-3
> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
> shutdown complete !
> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>  (BrokerPools.java [run]:67) - Executing shutdown thread
> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>  (BrokerPools.java [run]:67) - Executing shutdown thread
> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>  (BrokerPools.java [run]:67) - Executing shutdown thread
> -------------------------------------------------------------------------------------------
> Here the Wrapper Log [Action start in Windows Monitor]
> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
> 10/10.0/x86
> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
> default exit code rule
> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
> pid/timeout 256 45000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
> default exit code rule
> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
> pid/timeout 560 45000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
> 4700
> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
> default exit code rule
> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
> pid/timeout 4700 45000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
> 9920
> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
> default exit code rule
> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
> pid/timeout 9920 45000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
> 2148
> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
> default exit code rule
> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
> pid/timeout 2148 45000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
> 5684
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
> timeout: 30000
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
> wrapper.control -> stopping application
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
> shutdown
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
> before notify
> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
> ----------------------------------------------------------------------------------------
>
> If you have some experiments to suggest.  will try them
>
>
> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
> <mailto:[hidden email]>>:
>
>     Hi all,
>
>     I've been seeing reports here of people with Windows 10 having
>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>     installed eXist 3.1.1 on Windows 10?
>
>     I ask because I have recently got another office in my organization
>     interested in eXist, and they wrote saying they were having trouble
>     installing it on a Windows 10 machine. They are complete newbies,
>     though, so even asking for logging info will be intimidating for them.
>
>     Any info on known routes to success with Windows would be very
>     helpful!  Has anyone had success?
>
>     Thanks,
>     Joe
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Exist-open mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>
>
>
>
> --
> /Dominique Rabeuf/
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Joe Wicentowski
Hi Martin,

Thanks so much for sharing your experience and pointers!

One question: Do you think that setting the JAVA_HOME environment
variable is required for eXist 3.1.1 to start on Windows?  Asking the
question another way, did you begin setting JAVA_HOME after having
problems starting eXist on Windows?

I should mention that I see nothing about setting JAVA_HOME in the
documentation for installing eXist on Windows; see
http://exist-db.org/exist/apps/doc/quickstart.xml.  I fully realize
that that page could be out of date, with regard to new requirements
for starting eXist on Windows.  If we confirm that setting JAVA_HOME
is a requirement, I'll gladly file an issue to have this added to the
documentation.

Joe

On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]> wrote:

> I have a Windows 10 vm that I use for testing various things, and I just
> tried this out. It worked fine. For anyone struggling, these are the
> steps I took.
>
> I have the JDK 1.8 installed:
>
> C:\Users\mholmes>echo %JAVA_HOME%
> C:\Program Files\Java\jdk1.8.0_121
>
> C:\Users\mholmes>java -version
> java version "1.8.0_121"
> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>
> I ran the installer with
>
>    java -jar exist-db-setup-3.1.1.jar
>
> as a regular user.
>
> I installed eXist with the default settings, except that I installed it
> into:
>
>    C:\Users\mholmes\exist-db
>
> rather than the default c:\exist-db.
>
> I set an admin password when prompted. When the installer completed and
> started up the instance, I saw this:
>
> The system cannot find the file C:\Program.
> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
> exists.
> "-Xms64m -Xmx768m
> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
> --- Starting embedded database instance ---
> Setting admin user password...
> --- Initialization complete. Shutdown embedded database instance ---
>
> Then I launched exist from the start menu, or whatever it's called now.
> I saw the splash screen and the usual process of installing demos etc.
> Then Windows Firewall popped up to ask for access, which I gave it. Then
> I went to localhost:8080 in my browser, and everything seemed to be
> working fine.
>
> Hope this helps,
> Martin
>
> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>> I have successfully installed eXist 3.1.1
>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>>
>>
>> I have tried to install under Windows 10 with Java 8 (build
>> 1.8.0_121-b13) x86
>> The service eXist-db is created with status stopped
>> When click on start in Windows Monitor the service is displayed as
>> started then stopped after a while
>> Below the exist.log after a new installation this morning
>> Next the Wapper Log reports
>> several start/stop due to time out
>> and finally:
>> too many restarts,
>>
>> --------------------------------------------------------
>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
>> Reading configuration from file c:\eXist-db\conf.xml
>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>> [configureStartup]:1280) - Registered StartupTrigger:
>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>> [configureStartup]:1280) - Registered StartupTrigger:
>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>> [configureStartup]:1280) - Registered StartupTrigger:
>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>> [configureStartup]:1280) - Registered StartupTrigger:
>> org.exist.repo.AutoDeploymentTrigger
>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>> [lookupModuleClass]:448) - Configuration problem: class not found for
>> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>> [configureValidation]:1490) - Add catalog uri
>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
>> Initializing GrammarPool.
>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
>> database instance 'exist' will wait  120 000 ms during shutdown
>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
>> database instance 'exist' is enabled for recovery : true
>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
>> database instance 'exist' will have between 1 and 20 brokers
>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
>> database instance 'exist' will be synchronized every 120 000 ms
>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
>> Java has only 760256k available. Cache manager will not use more than
>> 253418k to avoid memory issues which may lead to database corruptions.
>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>> timeoutCheckInterval = 30 000
>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
>> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>> - Registered index org.exist.indexing.range.RangeIndex as range-index
>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>> - Registered index org.exist.storage.structural.NativeStructuralIndex as
>> structural-index
>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
>> to continue operations: 128mb
>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
>> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
>> Memory: 63 424K total; 760 256K max; 34 774K free
>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
>> : 100 %
>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
>> of 256) Cache efficiency : 100 %
>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>> efficiency : 100 %
>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>> efficiency : 100 %
>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>> efficiency : N/A
>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>> efficiency : N/A
>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/config.xml
>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/exist/accounts/admin.xml
>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/config.xml
>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/exist/accounts/admin.xml
>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/exist/accounts/guest.xml
>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/config.xml
>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/exist/accounts/guest.xml
>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/plugins/config.xml
>> 2017-03-31 10:08:49,858 [main] INFO
>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
>> Security Provider: gnu.crypto.jce.GnuCrypto
>> 2017-03-31 10:08:49,858 [main] INFO
>>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
>> - Successfully registered eXistURLStreamHandlerFactory.
>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
>> Storing configuration /db/system/security/exist/accounts/admin.xml
>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
>> Database is shutting down ...
>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>> Transaction journal cleanly shutting down with checkpoint...
>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>> Deleting lock file: c:\eXist-data\journal.lck
>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>> Signal Dispatcher
>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>> Finalizer
>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>> Reference Handler
>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>> Attach Listener
>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>> Thread-3
>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
>> shutdown complete !
>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>> -------------------------------------------------------------------------------------------
>> Here the Wrapper Log [Action start in Windows Monitor]
>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>> 10/10.0/x86
>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
>> default exit code rule
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
>> pid/timeout 256 45000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
>> default exit code rule
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
>> pid/timeout 560 45000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
>> 4700
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
>> default exit code rule
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
>> pid/timeout 4700 45000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
>> 9920
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
>> default exit code rule
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
>> pid/timeout 9920 45000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
>> 2148
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
>> default exit code rule
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
>> pid/timeout 2148 45000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
>> 5684
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>> timeout: 30000
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>> wrapper.control -> stopping application
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
>> shutdown
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>> before notify
>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
>> ----------------------------------------------------------------------------------------
>>
>> If you have some experiments to suggest.  will try them
>>
>>
>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>> <mailto:[hidden email]>>:
>>
>>     Hi all,
>>
>>     I've been seeing reports here of people with Windows 10 having
>>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>>     installed eXist 3.1.1 on Windows 10?
>>
>>     I ask because I have recently got another office in my organization
>>     interested in eXist, and they wrote saying they were having trouble
>>     installing it on a Windows 10 machine. They are complete newbies,
>>     though, so even asking for logging info will be intimidating for them.
>>
>>     Any info on known routes to success with Windows would be very
>>     helpful!  Has anyone had success?
>>
>>     Thanks,
>>     Joe
>>
>>     ------------------------------------------------------------------------------
>>     Check out the vibrant tech community on one of the world's most
>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>     _______________________________________________
>>     Exist-open mailing list
>>     [hidden email]
>>     <mailto:[hidden email]>
>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>>
>>
>>
>>
>> --
>> /Dominique Rabeuf/
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Martin Holmes
Hi Joe,

I already had JAVA_HOME set before I started, because of a project using
Ant, so I don't know whether its presence or absence is significant,
unfortunately.

I did uninstall Java completely and reinstall it afresh (leaving
JAVA_HOME alone), because I had a messed-up Java install due to having
started with the JRE and added the JDK. I made sure I had only a fresh
JDK on the system.

Incidentally, it's quite difficult to find the JDK installer on the
Oracle site. My guess is that the average Windows user will end up with
only the JRE unless they have very helpful instructions. Does eXist need
the JDK?

Cheers,
Martin

On 2017-03-31 11:00 AM, Joe Wicentowski wrote:

> Hi Martin,
>
> Thanks so much for sharing your experience and pointers!
>
> One question: Do you think that setting the JAVA_HOME environment
> variable is required for eXist 3.1.1 to start on Windows?  Asking the
> question another way, did you begin setting JAVA_HOME after having
> problems starting eXist on Windows?
>
> I should mention that I see nothing about setting JAVA_HOME in the
> documentation for installing eXist on Windows; see
> http://exist-db.org/exist/apps/doc/quickstart.xml.  I fully realize
> that that page could be out of date, with regard to new requirements
> for starting eXist on Windows.  If we confirm that setting JAVA_HOME
> is a requirement, I'll gladly file an issue to have this added to the
> documentation.
>
> Joe
>
> On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]> wrote:
>> I have a Windows 10 vm that I use for testing various things, and I just
>> tried this out. It worked fine. For anyone struggling, these are the
>> steps I took.
>>
>> I have the JDK 1.8 installed:
>>
>> C:\Users\mholmes>echo %JAVA_HOME%
>> C:\Program Files\Java\jdk1.8.0_121
>>
>> C:\Users\mholmes>java -version
>> java version "1.8.0_121"
>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>
>> I ran the installer with
>>
>>    java -jar exist-db-setup-3.1.1.jar
>>
>> as a regular user.
>>
>> I installed eXist with the default settings, except that I installed it
>> into:
>>
>>    C:\Users\mholmes\exist-db
>>
>> rather than the default c:\exist-db.
>>
>> I set an admin password when prompted. When the installer completed and
>> started up the instance, I saw this:
>>
>> The system cannot find the file C:\Program.
>> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
>> exists.
>> "-Xms64m -Xmx768m
>> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
>> --- Starting embedded database instance ---
>> Setting admin user password...
>> --- Initialization complete. Shutdown embedded database instance ---
>>
>> Then I launched exist from the start menu, or whatever it's called now.
>> I saw the splash screen and the usual process of installing demos etc.
>> Then Windows Firewall popped up to ask for access, which I gave it. Then
>> I went to localhost:8080 in my browser, and everything seemed to be
>> working fine.
>>
>> Hope this helps,
>> Martin
>>
>> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>>> I have successfully installed eXist 3.1.1
>>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>>>
>>>
>>> I have tried to install under Windows 10 with Java 8 (build
>>> 1.8.0_121-b13) x86
>>> The service eXist-db is created with status stopped
>>> When click on start in Windows Monitor the service is displayed as
>>> started then stopped after a while
>>> Below the exist.log after a new installation this morning
>>> Next the Wapper Log reports
>>> several start/stop due to time out
>>> and finally:
>>> too many restarts,
>>>
>>> --------------------------------------------------------
>>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
>>> Reading configuration from file c:\eXist-db\conf.xml
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.repo.AutoDeploymentTrigger
>>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>>> [lookupModuleClass]:448) - Configuration problem: class not found for
>>> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
>>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>>> [configureValidation]:1490) - Add catalog uri
>>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
>>> Initializing GrammarPool.
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
>>> database instance 'exist' will wait  120 000 ms during shutdown
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
>>> database instance 'exist' is enabled for recovery : true
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
>>> database instance 'exist' will have between 1 and 20 brokers
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
>>> database instance 'exist' will be synchronized every 120 000 ms
>>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
>>> Java has only 760256k available. Cache manager will not use more than
>>> 253418k to avoid memory issues which may lead to database corruptions.
>>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
>>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>>> timeoutCheckInterval = 30 000
>>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.range.RangeIndex as range-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.storage.structural.NativeStructuralIndex as
>>> structural-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
>>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
>>> to continue operations: 128mb
>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
>>> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
>>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
>>> Memory: 63 424K total; 760 256K max; 34 774K free
>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
>>> : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
>>> of 256) Cache efficiency : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
>>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : 100 %
>>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : N/A
>>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
>>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>>> efficiency : N/A
>>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/plugins/config.xml
>>> 2017-03-31 10:08:49,858 [main] INFO
>>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
>>> Security Provider: gnu.crypto.jce.GnuCrypto
>>> 2017-03-31 10:08:49,858 [main] INFO
>>>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
>>> - Successfully registered eXistURLStreamHandlerFactory.
>>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
>>> Database is shutting down ...
>>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>>> Transaction journal cleanly shutting down with checkpoint...
>>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>>> Deleting lock file: c:\eXist-data\journal.lck
>>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Signal Dispatcher
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Finalizer
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Reference Handler
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Attach Listener
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Thread-3
>>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
>>> shutdown complete !
>>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> -------------------------------------------------------------------------------------------
>>> Here the Wrapper Log [Action start in Windows Monitor]
>>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>>> 10/10.0/x86
>>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
>>> pid/timeout 256 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
>>> pid/timeout 560 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
>>> 4700
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
>>> pid/timeout 4700 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
>>> 9920
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
>>> pid/timeout 9920 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
>>> 2148
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
>>> pid/timeout 2148 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
>>> 5684
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>> timeout: 30000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>>> wrapper.control -> stopping application
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
>>> shutdown
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>> before notify
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
>>> ----------------------------------------------------------------------------------------
>>>
>>> If you have some experiments to suggest.  will try them
>>>
>>>
>>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>>> <mailto:[hidden email]>>:
>>>
>>>     Hi all,
>>>
>>>     I've been seeing reports here of people with Windows 10 having
>>>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>>>     installed eXist 3.1.1 on Windows 10?
>>>
>>>     I ask because I have recently got another office in my organization
>>>     interested in eXist, and they wrote saying they were having trouble
>>>     installing it on a Windows 10 machine. They are complete newbies,
>>>     though, so even asking for logging info will be intimidating for them.
>>>
>>>     Any info on known routes to success with Windows would be very
>>>     helpful!  Has anyone had success?
>>>
>>>     Thanks,
>>>     Joe
>>>
>>>     ------------------------------------------------------------------------------
>>>     Check out the vibrant tech community on one of the world's most
>>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>     _______________________________________________
>>>     Exist-open mailing list
>>>     [hidden email]
>>>     <mailto:[hidden email]>
>>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>>>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>>>
>>>
>>>
>>>
>>> --
>>> /Dominique Rabeuf/
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>>
>>>
>>> _______________________________________________
>>> Exist-open mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Joe Wicentowski
Hi Martin,

Thanks.  I look forward to hearing from a core developer about
JAVA_HOME.  I have seen discussion in the issues about this but don't
know what the actual status is.

As to JRE vs. JDK, the Quick Start Guide says this:

> eXist-db can run with both the Java "JRE" (Java Runtime Environment) and the "JDK" (Java Development Kit). The JRE is adequate for running eXist-db; you do not need the JDK unless you intend to compile eXist-db from its source code.

I assume this is still the case, but did you have problems running
eXist with just the JRE installed?  Or did it work until you tried to
compile eXist from source?

Joe

On Fri, Mar 31, 2017 at 2:50 PM, Martin Holmes <[hidden email]> wrote:

> Hi Joe,
>
> I already had JAVA_HOME set before I started, because of a project using
> Ant, so I don't know whether its presence or absence is significant,
> unfortunately.
>
> I did uninstall Java completely and reinstall it afresh (leaving
> JAVA_HOME alone), because I had a messed-up Java install due to having
> started with the JRE and added the JDK. I made sure I had only a fresh
> JDK on the system.
>
> Incidentally, it's quite difficult to find the JDK installer on the
> Oracle site. My guess is that the average Windows user will end up with
> only the JRE unless they have very helpful instructions. Does eXist need
> the JDK?
>
> Cheers,
> Martin
>
> On 2017-03-31 11:00 AM, Joe Wicentowski wrote:
>> Hi Martin,
>>
>> Thanks so much for sharing your experience and pointers!
>>
>> One question: Do you think that setting the JAVA_HOME environment
>> variable is required for eXist 3.1.1 to start on Windows?  Asking the
>> question another way, did you begin setting JAVA_HOME after having
>> problems starting eXist on Windows?
>>
>> I should mention that I see nothing about setting JAVA_HOME in the
>> documentation for installing eXist on Windows; see
>> http://exist-db.org/exist/apps/doc/quickstart.xml.  I fully realize
>> that that page could be out of date, with regard to new requirements
>> for starting eXist on Windows.  If we confirm that setting JAVA_HOME
>> is a requirement, I'll gladly file an issue to have this added to the
>> documentation.
>>
>> Joe
>>
>> On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]> wrote:
>>> I have a Windows 10 vm that I use for testing various things, and I just
>>> tried this out. It worked fine. For anyone struggling, these are the
>>> steps I took.
>>>
>>> I have the JDK 1.8 installed:
>>>
>>> C:\Users\mholmes>echo %JAVA_HOME%
>>> C:\Program Files\Java\jdk1.8.0_121
>>>
>>> C:\Users\mholmes>java -version
>>> java version "1.8.0_121"
>>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>>
>>> I ran the installer with
>>>
>>>    java -jar exist-db-setup-3.1.1.jar
>>>
>>> as a regular user.
>>>
>>> I installed eXist with the default settings, except that I installed it
>>> into:
>>>
>>>    C:\Users\mholmes\exist-db
>>>
>>> rather than the default c:\exist-db.
>>>
>>> I set an admin password when prompted. When the installer completed and
>>> started up the instance, I saw this:
>>>
>>> The system cannot find the file C:\Program.
>>> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
>>> exists.
>>> "-Xms64m -Xmx768m
>>> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
>>> --- Starting embedded database instance ---
>>> Setting admin user password...
>>> --- Initialization complete. Shutdown embedded database instance ---
>>>
>>> Then I launched exist from the start menu, or whatever it's called now.
>>> I saw the splash screen and the usual process of installing demos etc.
>>> Then Windows Firewall popped up to ask for access, which I gave it. Then
>>> I went to localhost:8080 in my browser, and everything seemed to be
>>> working fine.
>>>
>>> Hope this helps,
>>> Martin
>>>
>>> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>>>> I have successfully installed eXist 3.1.1
>>>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>>>>
>>>>
>>>> I have tried to install under Windows 10 with Java 8 (build
>>>> 1.8.0_121-b13) x86
>>>> The service eXist-db is created with status stopped
>>>> When click on start in Windows Monitor the service is displayed as
>>>> started then stopped after a while
>>>> Below the exist.log after a new installation this morning
>>>> Next the Wapper Log reports
>>>> several start/stop due to time out
>>>> and finally:
>>>> too many restarts,
>>>>
>>>> --------------------------------------------------------
>>>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
>>>> Reading configuration from file c:\eXist-db\conf.xml
>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>>>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>> org.exist.repo.AutoDeploymentTrigger
>>>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>>>> [lookupModuleClass]:448) - Configuration problem: class not found for
>>>> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
>>>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>>>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>>>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>>>> [configureValidation]:1490) - Add catalog uri
>>>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>>>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
>>>> Initializing GrammarPool.
>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
>>>> database instance 'exist' will wait  120 000 ms during shutdown
>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
>>>> database instance 'exist' is enabled for recovery : true
>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
>>>> database instance 'exist' will have between 1 and 20 brokers
>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
>>>> database instance 'exist' will be synchronized every 120 000 ms
>>>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>>>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
>>>> Java has only 760256k available. Cache manager will not use more than
>>>> 253418k to avoid memory issues which may lead to database corruptions.
>>>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>>>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>>>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>>>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
>>>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>>>> timeoutCheckInterval = 30 000
>>>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>>>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>>>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
>>>> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>> - Registered index org.exist.indexing.range.RangeIndex as range-index
>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>> - Registered index org.exist.storage.structural.NativeStructuralIndex as
>>>> structural-index
>>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
>>>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
>>>> to continue operations: 128mb
>>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
>>>> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
>>>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
>>>> Memory: 63 424K total; 760 256K max; 34 774K free
>>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
>>>> : 100 %
>>>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>>>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
>>>> of 256) Cache efficiency : 100 %
>>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>>> efficiency : 100 %
>>>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
>>>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>>>> efficiency : 100 %
>>>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
>>>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>>> efficiency : N/A
>>>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
>>>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>>>> efficiency : N/A
>>>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/config.xml
>>>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/config.xml
>>>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/config.xml
>>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>>>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/plugins/config.xml
>>>> 2017-03-31 10:08:49,858 [main] INFO
>>>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
>>>> Security Provider: gnu.crypto.jce.GnuCrypto
>>>> 2017-03-31 10:08:49,858 [main] INFO
>>>>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
>>>> - Successfully registered eXistURLStreamHandlerFactory.
>>>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
>>>> Database is shutting down ...
>>>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>>>> Transaction journal cleanly shutting down with checkpoint...
>>>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>>>> Deleting lock file: c:\eXist-data\journal.lck
>>>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>>>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>> Signal Dispatcher
>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>> Finalizer
>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>> Reference Handler
>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>> Attach Listener
>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>> Thread-3
>>>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
>>>> shutdown complete !
>>>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>> -------------------------------------------------------------------------------------------
>>>> Here the Wrapper Log [Action start in Windows Monitor]
>>>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>>>> 10/10.0/x86
>>>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>>>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
>>>> default exit code rule
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
>>>> pid/timeout 256 45000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
>>>> default exit code rule
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
>>>> pid/timeout 560 45000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
>>>> 4700
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
>>>> default exit code rule
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
>>>> pid/timeout 4700 45000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
>>>> 9920
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
>>>> default exit code rule
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
>>>> pid/timeout 9920 45000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
>>>> 2148
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
>>>> default exit code rule
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
>>>> pid/timeout 2148 45000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
>>>> 5684
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>>> timeout: 30000
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>>>> wrapper.control -> stopping application
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
>>>> shutdown
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>>> before notify
>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
>>>> ----------------------------------------------------------------------------------------
>>>>
>>>> If you have some experiments to suggest.  will try them
>>>>
>>>>
>>>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>>>> <mailto:[hidden email]>>:
>>>>
>>>>     Hi all,
>>>>
>>>>     I've been seeing reports here of people with Windows 10 having
>>>>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>>>>     installed eXist 3.1.1 on Windows 10?
>>>>
>>>>     I ask because I have recently got another office in my organization
>>>>     interested in eXist, and they wrote saying they were having trouble
>>>>     installing it on a Windows 10 machine. They are complete newbies,
>>>>     though, so even asking for logging info will be intimidating for them.
>>>>
>>>>     Any info on known routes to success with Windows would be very
>>>>     helpful!  Has anyone had success?
>>>>
>>>>     Thanks,
>>>>     Joe
>>>>
>>>>     ------------------------------------------------------------------------------
>>>>     Check out the vibrant tech community on one of the world's most
>>>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>     _______________________________________________
>>>>     Exist-open mailing list
>>>>     [hidden email]
>>>>     <mailto:[hidden email]>
>>>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> /Dominique Rabeuf/
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Exist-open mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Exist-open mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Dominique Rabeuf
In reply to this post by Martin Holmes
Hi Martin
Are you sure that eXist has been installed as a service ?
Have you a background task (eXist Launcher) on which  right click display eXist menu ?


2017-03-31 20:50 GMT+02:00 Martin Holmes <[hidden email]>:
Hi Joe,

I already had JAVA_HOME set before I started, because of a project using
Ant, so I don't know whether its presence or absence is significant,
unfortunately.

I did uninstall Java completely and reinstall it afresh (leaving
JAVA_HOME alone), because I had a messed-up Java install due to having
started with the JRE and added the JDK. I made sure I had only a fresh
JDK on the system.

Incidentally, it's quite difficult to find the JDK installer on the
Oracle site. My guess is that the average Windows user will end up with
only the JRE unless they have very helpful instructions. Does eXist need
the JDK?

Cheers,
Martin

On 2017-03-31 11:00 AM, Joe Wicentowski wrote:
> Hi Martin,
>
> Thanks so much for sharing your experience and pointers!
>
> One question: Do you think that setting the JAVA_HOME environment
> variable is required for eXist 3.1.1 to start on Windows?  Asking the
> question another way, did you begin setting JAVA_HOME after having
> problems starting eXist on Windows?
>
> I should mention that I see nothing about setting JAVA_HOME in the
> documentation for installing eXist on Windows; see
> http://exist-db.org/exist/apps/doc/quickstart.xml.  I fully realize
> that that page could be out of date, with regard to new requirements
> for starting eXist on Windows.  If we confirm that setting JAVA_HOME
> is a requirement, I'll gladly file an issue to have this added to the
> documentation.
>
> Joe
>
> On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]> wrote:
>> I have a Windows 10 vm that I use for testing various things, and I just
>> tried this out. It worked fine. For anyone struggling, these are the
>> steps I took.
>>
>> I have the JDK 1.8 installed:
>>
>> C:\Users\mholmes>echo %JAVA_HOME%
>> C:\Program Files\Java\jdk1.8.0_121
>>
>> C:\Users\mholmes>java -version
>> java version "1.8.0_121"
>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>
>> I ran the installer with
>>
>>    java -jar exist-db-setup-3.1.1.jar
>>
>> as a regular user.
>>
>> I installed eXist with the default settings, except that I installed it
>> into:
>>
>>    C:\Users\mholmes\exist-db
>>
>> rather than the default c:\exist-db.
>>
>> I set an admin password when prompted. When the installer completed and
>> started up the instance, I saw this:
>>
>> The system cannot find the file C:\Program.
>> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
>> exists.
>> "-Xms64m -Xmx768m
>> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
>> --- Starting embedded database instance ---
>> Setting admin user password...
>> --- Initialization complete. Shutdown embedded database instance ---
>>
>> Then I launched exist from the start menu, or whatever it's called now.
>> I saw the splash screen and the usual process of installing demos etc.
>> Then Windows Firewall popped up to ask for access, which I gave it. Then
>> I went to localhost:8080 in my browser, and everything seemed to be
>> working fine.
>>
>> Hope this helps,
>> Martin
>>
>> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>>> I have successfully installed eXist 3.1.1
>>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>>>
>>>
>>> I have tried to install under Windows 10 with Java 8 (build
>>> 1.8.0_121-b13) x86
>>> The service eXist-db is created with status stopped
>>> When click on start in Windows Monitor the service is displayed as
>>> started then stopped after a while
>>> Below the exist.log after a new installation this morning
>>> Next the Wapper Log reports
>>> several start/stop due to time out
>>> and finally:
>>> too many restarts,
>>>
>>> --------------------------------------------------------
>>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
>>> Reading configuration from file c:\eXist-db\conf.xml
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>>> [configureStartup]:1280) - Registered StartupTrigger:
>>> org.exist.repo.AutoDeploymentTrigger
>>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>>> [lookupModuleClass]:448) - Configuration problem: class not found for
>>> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
>>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>>> [configureValidation]:1490) - Add catalog uri
>>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
>>> Initializing GrammarPool.
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
>>> database instance 'exist' will wait  120 000 ms during shutdown
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
>>> database instance 'exist' is enabled for recovery : true
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
>>> database instance 'exist' will have between 1 and 20 brokers
>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
>>> database instance 'exist' will be synchronized every 120 000 ms
>>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
>>> Java has only 760256k available. Cache manager will not use more than
>>> 253418k to avoid memory issues which may lead to database corruptions.
>>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
>>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>>> timeoutCheckInterval = 30 000
>>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.indexing.range.RangeIndex as range-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>> - Registered index org.exist.storage.structural.NativeStructuralIndex as
>>> structural-index
>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
>>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
>>> to continue operations: 128mb
>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
>>> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
>>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
>>> Memory: 63 424K total; 760 256K max; 34 774K free
>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
>>> : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
>>> of 256) Cache efficiency : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : 100 %
>>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
>>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : 100 %
>>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
>>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>> efficiency : N/A
>>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
>>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>>> efficiency : N/A
>>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/config.xml
>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/plugins/config.xml
>>> 2017-03-31 10:08:49,858 [main] INFO
>>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
>>> Security Provider: gnu.crypto.jce.GnuCrypto
>>> 2017-03-31 10:08:49,858 [main] INFO
>>>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
>>> - Successfully registered eXistURLStreamHandlerFactory.
>>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
>>> Database is shutting down ...
>>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>>> Transaction journal cleanly shutting down with checkpoint...
>>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>>> Deleting lock file: c:\eXist-data\journal.lck
>>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Signal Dispatcher
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Finalizer
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Reference Handler
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Attach Listener
>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>> Thread-3
>>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
>>> shutdown complete !
>>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>> -------------------------------------------------------------------------------------------
>>> Here the Wrapper Log [Action start in Windows Monitor]
>>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>>> 10/10.0/x86
>>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
>>> pid/timeout 256 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
>>> pid/timeout 560 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
>>> 4700
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
>>> pid/timeout 4700 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
>>> 9920
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
>>> pid/timeout 9920 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
>>> 2148
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
>>> default exit code rule
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
>>> pid/timeout 2148 45000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
>>> 5684
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>> timeout: 30000
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>>> wrapper.control -> stopping application
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
>>> shutdown
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>> before notify
>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
>>> ----------------------------------------------------------------------------------------
>>>
>>> If you have some experiments to suggest.  will try them
>>>
>>>
>>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>>> <mailto:[hidden email]>>:
>>>
>>>     Hi all,
>>>
>>>     I've been seeing reports here of people with Windows 10 having
>>>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>>>     installed eXist 3.1.1 on Windows 10?
>>>
>>>     I ask because I have recently got another office in my organization
>>>     interested in eXist, and they wrote saying they were having trouble
>>>     installing it on a Windows 10 machine. They are complete newbies,
>>>     though, so even asking for logging info will be intimidating for them.
>>>
>>>     Any info on known routes to success with Windows would be very
>>>     helpful!  Has anyone had success?
>>>
>>>     Thanks,
>>>     Joe
>>>
>>>     ------------------------------------------------------------------------------
>>>     Check out the vibrant tech community on one of the world's most
>>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>     _______________________________________________
>>>     Exist-open mailing list
>>>     [hidden email]
>>>     <mailto:[hidden email]>
>>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>>>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>>>
>>>
>>>
>>>
>>> --
>>> /Dominique Rabeuf/
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>>
>>>
>>> _______________________________________________
>>> Exist-open mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open



--
Dominique Rabeuf

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Martin Holmes
In reply to this post by Joe Wicentowski
HI Joe,

I never tried installing eXist with only the JRE; I'd set up my VM
originally with only the JRE, then realized I needed the JDK for another
project, installed it, and ended up with a mess, so I uninstalled both
and installed the JDK from scratch. All that happened before I tried the
eXist install. I didn't set restore points in the VM before doing any of
this, so I can't just roll back and try with only the JRE. I need the VM
for various other things (including, would you believe, filling in
timesheets that my employer only makes available in Excel with required
macros), so I'd rather not risk blowing it up.

Cheers,
Martin

On 2017-03-31 12:00 PM, Joe Wicentowski wrote:

> Hi Martin,
>
> Thanks.  I look forward to hearing from a core developer about
> JAVA_HOME.  I have seen discussion in the issues about this but don't
> know what the actual status is.
>
> As to JRE vs. JDK, the Quick Start Guide says this:
>
>> eXist-db can run with both the Java "JRE" (Java Runtime Environment) and the "JDK" (Java Development Kit). The JRE is adequate for running eXist-db; you do not need the JDK unless you intend to compile eXist-db from its source code.
>
> I assume this is still the case, but did you have problems running
> eXist with just the JRE installed?  Or did it work until you tried to
> compile eXist from source?
>
> Joe
>
> On Fri, Mar 31, 2017 at 2:50 PM, Martin Holmes <[hidden email]> wrote:
>> Hi Joe,
>>
>> I already had JAVA_HOME set before I started, because of a project using
>> Ant, so I don't know whether its presence or absence is significant,
>> unfortunately.
>>
>> I did uninstall Java completely and reinstall it afresh (leaving
>> JAVA_HOME alone), because I had a messed-up Java install due to having
>> started with the JRE and added the JDK. I made sure I had only a fresh
>> JDK on the system.
>>
>> Incidentally, it's quite difficult to find the JDK installer on the
>> Oracle site. My guess is that the average Windows user will end up with
>> only the JRE unless they have very helpful instructions. Does eXist need
>> the JDK?
>>
>> Cheers,
>> Martin
>>
>> On 2017-03-31 11:00 AM, Joe Wicentowski wrote:
>>> Hi Martin,
>>>
>>> Thanks so much for sharing your experience and pointers!
>>>
>>> One question: Do you think that setting the JAVA_HOME environment
>>> variable is required for eXist 3.1.1 to start on Windows?  Asking the
>>> question another way, did you begin setting JAVA_HOME after having
>>> problems starting eXist on Windows?
>>>
>>> I should mention that I see nothing about setting JAVA_HOME in the
>>> documentation for installing eXist on Windows; see
>>> http://exist-db.org/exist/apps/doc/quickstart.xml.  I fully realize
>>> that that page could be out of date, with regard to new requirements
>>> for starting eXist on Windows.  If we confirm that setting JAVA_HOME
>>> is a requirement, I'll gladly file an issue to have this added to the
>>> documentation.
>>>
>>> Joe
>>>
>>> On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]> wrote:
>>>> I have a Windows 10 vm that I use for testing various things, and I just
>>>> tried this out. It worked fine. For anyone struggling, these are the
>>>> steps I took.
>>>>
>>>> I have the JDK 1.8 installed:
>>>>
>>>> C:\Users\mholmes>echo %JAVA_HOME%
>>>> C:\Program Files\Java\jdk1.8.0_121
>>>>
>>>> C:\Users\mholmes>java -version
>>>> java version "1.8.0_121"
>>>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>>>
>>>> I ran the installer with
>>>>
>>>>    java -jar exist-db-setup-3.1.1.jar
>>>>
>>>> as a regular user.
>>>>
>>>> I installed eXist with the default settings, except that I installed it
>>>> into:
>>>>
>>>>    C:\Users\mholmes\exist-db
>>>>
>>>> rather than the default c:\exist-db.
>>>>
>>>> I set an admin password when prompted. When the installer completed and
>>>> started up the instance, I saw this:
>>>>
>>>> The system cannot find the file C:\Program.
>>>> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp already
>>>> exists.
>>>> "-Xms64m -Xmx768m
>>>> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
>>>> --- Starting embedded database instance ---
>>>> Setting admin user password...
>>>> --- Initialization complete. Shutdown embedded database instance ---
>>>>
>>>> Then I launched exist from the start menu, or whatever it's called now.
>>>> I saw the splash screen and the usual process of installing demos etc.
>>>> Then Windows Firewall popped up to ask for access, which I gave it. Then
>>>> I went to localhost:8080 in my browser, and everything seemed to be
>>>> working fine.
>>>>
>>>> Hope this helps,
>>>> Martin
>>>>
>>>> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>>>>> I have successfully installed eXist 3.1.1
>>>>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>>>>>
>>>>>
>>>>> I have tried to install under Windows 10 with Java 8 (build
>>>>> 1.8.0_121-b13) x86
>>>>> The service eXist-db is created with status stopped
>>>>> When click on start in Windows Monitor the service is displayed as
>>>>> started then stopped after a while
>>>>> Below the exist.log after a new installation this morning
>>>>> Next the Wapper Log reports
>>>>> several start/stop due to time out
>>>>> and finally:
>>>>> too many restarts,
>>>>>
>>>>> --------------------------------------------------------
>>>>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java [<init>]:175) -
>>>>> Reading configuration from file c:\eXist-db\conf.xml
>>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>>>>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>>>>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>>>>> [configureStartup]:1280) - Registered StartupTrigger:
>>>>> org.exist.repo.AutoDeploymentTrigger
>>>>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>>>>> [lookupModuleClass]:448) - Configuration problem: class not found for
>>>>> module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException);
>>>>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>>>>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>>>>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>>>>> [configureValidation]:1490) - Add catalog uri
>>>>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>>>>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java [<init>]:54) -
>>>>> Initializing GrammarPool.
>>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:378) -
>>>>> database instance 'exist' will wait  120 000 ms during shutdown
>>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:381) -
>>>>> database instance 'exist' is enabled for recovery : true
>>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:386) -
>>>>> database instance 'exist' will have between 1 and 20 brokers
>>>>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java [<init>]:390) -
>>>>> database instance 'exist' will be synchronized every 120 000 ms
>>>>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>>>>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too large.
>>>>> Java has only 760256k available. Cache manager will not use more than
>>>>> 253418k to avoid memory issues which may lead to database corruptions.
>>>>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>>>>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>>>>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>>>>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java [configure]:126) -
>>>>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>>>>> timeoutCheckInterval = 30 000
>>>>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>>>>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>>>>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java [initIndex]:118)
>>>>> - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>>> - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>>> - Registered index org.exist.indexing.range.RangeIndex as range-index
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java [initIndex]:118)
>>>>> - Registered index org.exist.storage.structural.NativeStructuralIndex as
>>>>> structural-index
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:73) -
>>>>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for database
>>>>> to continue operations: 128mb
>>>>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java [configure]:76) -
>>>>> Usable space on partition containing DATA_DIR: c:\eXist-data: 816143mb
>>>>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java [sync]:3687) -
>>>>> Memory: 63 424K total; 760 256K max; 34 774K free
>>>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>>>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache efficiency
>>>>> : 100 %
>>>>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>>>>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 % (1 out
>>>>> of 256) Cache efficiency : 100 %
>>>>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java [printStatistics]:2619)
>>>>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>>>> efficiency : 100 %
>>>>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java [printStatistics]:419)
>>>>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>>>>> efficiency : 100 %
>>>>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java [printStatistics]:2619)
>>>>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>>>>> efficiency : N/A
>>>>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java [printStatistics]:419)
>>>>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>>>>> efficiency : N/A
>>>>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/config.xml
>>>>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/config.xml
>>>>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>>>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>>>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>>>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/config.xml
>>>>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>>>>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>>>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/exist/accounts/guest.xml
>>>>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>>>>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>>>>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/plugins/config.xml
>>>>> 2017-03-31 10:08:49,858 [main] INFO
>>>>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) - Registered JCE
>>>>> Security Provider: gnu.crypto.jce.GnuCrypto
>>>>> 2017-03-31 10:08:49,858 [main] INFO
>>>>>  (URLStreamHandlerStartupTrigger.java [registerStreamHandlerFactory]:61)
>>>>> - Successfully registered eXistURLStreamHandlerFactory.
>>>>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java [save]:1280) -
>>>>> Storing configuration /db/system/security/exist/accounts/admin.xml
>>>>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>>>>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>>>>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java [shutdown]:1518) -
>>>>> Database is shutting down ...
>>>>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>>>>> Transaction journal cleanly shutting down with checkpoint...
>>>>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>>>>> Deleting lock file: c:\eXist-data\journal.lck
>>>>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>>>>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>>> Signal Dispatcher
>>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>>> Finalizer
>>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>>> Reference Handler
>>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>>> Attach Listener
>>>>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>>>>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>>>>> Thread-3
>>>>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java [shutdown]:1646) -
>>>>> shutdown complete !
>>>>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>>>>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>>>>> -------------------------------------------------------------------------------------------
>>>>> Here the Wrapper Log [Action start in Windows Monitor]
>>>>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>>>>> 10/10.0/x86
>>>>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>>>>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process with pid 256
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process due to
>>>>> default exit code rule
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal RUNNING
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process with
>>>>> pid/timeout 256 45000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process with pid 560
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process due to
>>>>> default exit code rule
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal RUNNING
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process with
>>>>> pid/timeout 560 45000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process with pid
>>>>> 4700
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process due to
>>>>> default exit code rule
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal RUNNING
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process with
>>>>> pid/timeout 4700 45000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process with pid
>>>>> 9920
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process due to
>>>>> default exit code rule
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal RUNNING
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process with
>>>>> pid/timeout 9920 45000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process with pid
>>>>> 2148
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process due to
>>>>> default exit code rule
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal RUNNING
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process with
>>>>> pid/timeout 2148 45000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process with pid
>>>>> 5684
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>>>> timeout: 30000
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>>>>> wrapper.control -> stopping application
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop - after
>>>>> shutdown
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>>>>> before notify
>>>>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service terminated
>>>>> ----------------------------------------------------------------------------------------
>>>>>
>>>>> If you have some experiments to suggest.  will try them
>>>>>
>>>>>
>>>>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>>>>> <mailto:[hidden email]>>:
>>>>>
>>>>>     Hi all,
>>>>>
>>>>>     I've been seeing reports here of people with Windows 10 having
>>>>>     problems installing eXist 3.1.1. Do we know if anyone has successfully
>>>>>     installed eXist 3.1.1 on Windows 10?
>>>>>
>>>>>     I ask because I have recently got another office in my organization
>>>>>     interested in eXist, and they wrote saying they were having trouble
>>>>>     installing it on a Windows 10 machine. They are complete newbies,
>>>>>     though, so even asking for logging info will be intimidating for them.
>>>>>
>>>>>     Any info on known routes to success with Windows would be very
>>>>>     helpful!  Has anyone had success?
>>>>>
>>>>>     Thanks,
>>>>>     Joe
>>>>>
>>>>>     ------------------------------------------------------------------------------
>>>>>     Check out the vibrant tech community on one of the world's most
>>>>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>     _______________________________________________
>>>>>     Exist-open mailing list
>>>>>     [hidden email]
>>>>>     <mailto:[hidden email]>
>>>>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> /Dominique Rabeuf/
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Exist-open mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Exist-open mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist with Windows 10 - working at all?

Martin Holmes
In reply to this post by Dominique Rabeuf
Hi Dominique,

Sorry, I didn't install eXist as a service; this is a desktop vm, and I
don't want it running that way. I just thought I'd try a regular install
and report back, since there was some doubt about whether it was
runnable on Windows 10.

Cheers,
Martin

On 2017-03-31 12:00 PM, Dominique Rabeuf wrote:

> Hi Martin
> Are you sure that eXist has been installed as a service ?
> Have you a background task (eXist Launcher) on which  right click
> display eXist menu ?
>
>
> 2017-03-31 20:50 GMT+02:00 Martin Holmes <[hidden email]
> <mailto:[hidden email]>>:
>
>     Hi Joe,
>
>     I already had JAVA_HOME set before I started, because of a project using
>     Ant, so I don't know whether its presence or absence is significant,
>     unfortunately.
>
>     I did uninstall Java completely and reinstall it afresh (leaving
>     JAVA_HOME alone), because I had a messed-up Java install due to having
>     started with the JRE and added the JDK. I made sure I had only a fresh
>     JDK on the system.
>
>     Incidentally, it's quite difficult to find the JDK installer on the
>     Oracle site. My guess is that the average Windows user will end up with
>     only the JRE unless they have very helpful instructions. Does eXist need
>     the JDK?
>
>     Cheers,
>     Martin
>
>     On 2017-03-31 11:00 AM, Joe Wicentowski wrote:
>     > Hi Martin,
>     >
>     > Thanks so much for sharing your experience and pointers!
>     >
>     > One question: Do you think that setting the JAVA_HOME environment
>     > variable is required for eXist 3.1.1 to start on Windows?  Asking the
>     > question another way, did you begin setting JAVA_HOME after having
>     > problems starting eXist on Windows?
>     >
>     > I should mention that I see nothing about setting JAVA_HOME in the
>     > documentation for installing eXist on Windows; see
>     > http://exist-db.org/exist/apps/doc/quickstart.xml
>     <http://exist-db.org/exist/apps/doc/quickstart.xml>.  I fully realize
>     > that that page could be out of date, with regard to new requirements
>     > for starting eXist on Windows.  If we confirm that setting JAVA_HOME
>     > is a requirement, I'll gladly file an issue to have this added to the
>     > documentation.
>     >
>     > Joe
>     >
>     > On Fri, Mar 31, 2017 at 1:47 PM, Martin Holmes <[hidden email]
>     <mailto:[hidden email]>> wrote:
>     >> I have a Windows 10 vm that I use for testing various things, and
>     I just
>     >> tried this out. It worked fine. For anyone struggling, these are the
>     >> steps I took.
>     >>
>     >> I have the JDK 1.8 installed:
>     >>
>     >> C:\Users\mholmes>echo %JAVA_HOME%
>     >> C:\Program Files\Java\jdk1.8.0_121
>     >>
>     >> C:\Users\mholmes>java -version
>     >> java version "1.8.0_121"
>     >> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>     >> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>     >>
>     >> I ran the installer with
>     >>
>     >>    java -jar exist-db-setup-3.1.1.jar
>     >>
>     >> as a regular user.
>     >>
>     >> I installed eXist with the default settings, except that I
>     installed it
>     >> into:
>     >>
>     >>    C:\Users\mholmes\exist-db
>     >>
>     >> rather than the default c:\exist-db.
>     >>
>     >> I set an admin password when prompted. When the installer
>     completed and
>     >> started up the instance, I saw this:
>     >>
>     >> The system cannot find the file C:\Program.
>     >> A subdirectory or file C:\Users\mholmes\exist-db\tools\jetty\tmp
>     already
>     >> exists.
>     >> "-Xms64m -Xmx768m
>     >> -Djava.endorsed.dirs="C:\Users\mholmes\exist-db"\lib\endorsed"
>     >> --- Starting embedded database instance ---
>     >> Setting admin user password...
>     >> --- Initialization complete. Shutdown embedded database instance ---
>     >>
>     >> Then I launched exist from the start menu, or whatever it's
>     called now.
>     >> I saw the splash screen and the usual process of installing demos
>     etc.
>     >> Then Windows Firewall popped up to ask for access, which I gave
>     it. Then
>     >> I went to localhost:8080 in my browser, and everything seemed to be
>     >> working fine.
>     >>
>     >> Hope this helps,
>     >> Martin
>     >>
>     >> On 2017-03-31 09:29 AM, Dominique Rabeuf wrote:
>     >>> I have successfully installed eXist 3.1.1
>     >>> under Windows 2012 R2 with Java 8 (build 1.8.0_121-b13) 64bits
>     >>>
>     >>>
>     >>> I have tried to install under Windows 10 with Java 8 (build
>     >>> 1.8.0_121-b13) x86
>     >>> The service eXist-db is created with status stopped
>     >>> When click on start in Windows Monitor the service is displayed as
>     >>> started then stopped after a while
>     >>> Below the exist.log after a new installation this morning
>     >>> Next the Wapper Log reports
>     >>> several start/stop due to time out
>     >>> and finally:
>     >>> too many restarts,
>     >>>
>     >>> --------------------------------------------------------
>     >>> 2017-03-31 10:08:48,642 [main] INFO  (Configuration.java
>     [<init>]:175) -
>     >>> Reading configuration from file c:\eXist-db\conf.xml
>     >>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>     >>> [configureStartup]:1280) - Registered StartupTrigger:
>     >>> org.exist.security.GnuCryptoJceProviderStartupTrigger
>     >>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>     >>> [configureStartup]:1280) - Registered StartupTrigger:
>     >>> org.exist.protocolhandler.URLStreamHandlerStartupTrigger
>     >>> 2017-03-31 10:08:48,679 [main] INFO  (Configuration.java
>     >>> [configureStartup]:1280) - Registered StartupTrigger:
>     >>> org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger
>     >>> 2017-03-31 10:08:48,698 [main] INFO  (Configuration.java
>     >>> [configureStartup]:1280) - Registered StartupTrigger:
>     >>> org.exist.repo.AutoDeploymentTrigger
>     >>> 2017-03-31 10:08:48,958 [main] ERROR (Configuration.java
>     >>> [lookupModuleClass]:448) - Configuration problem: class not
>     found for
>     >>> module 'http://exist-db.org/xquery/jndi
>     <http://exist-db.org/xquery/jndi>' (ClassNotFoundException);
>     >>> class:'org.exist.xquery.modules.jndi.JNDIModule';
>     >>> message:'org.exist.xquery.modules.jndi.JNDIModule'
>     >>> 2017-03-31 10:08:48,958 [main] INFO  (Configuration.java
>     >>> [configureValidation]:1490) - Add catalog uri
>     >>> file:///c:/eXist-db/webapp//WEB-INF/catalog.xml
>     >>> 2017-03-31 10:08:48,958 [main] INFO  (GrammarPool.java
>     [<init>]:54) -
>     >>> Initializing GrammarPool.
>     >>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java
>     [<init>]:378) -
>     >>> database instance 'exist' will wait  120 000 ms during shutdown
>     >>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java
>     [<init>]:381) -
>     >>> database instance 'exist' is enabled for recovery : true
>     >>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java
>     [<init>]:386) -
>     >>> database instance 'exist' will have between 1 and 20 brokers
>     >>> 2017-03-31 10:08:49,027 [main] INFO  (BrokerPool.java
>     [<init>]:390) -
>     >>> database instance 'exist' will be synchronized every 120 000 ms
>     >>> 2017-03-31 10:08:49,042 [main] WARN  (DefaultCacheManager.java
>     >>> [<init>]:139) - The cacheSize="256" setting in conf.xml is too
>     large.
>     >>> Java has only 760256k available. Cache manager will not use more
>     than
>     >>> 253418k to avoid memory issues which may lead to database
>     corruptions.
>     >>> 2017-03-31 10:08:49,042 [main] INFO  (DefaultCacheManager.java
>     >>> [<init>]:154) - Cache settings: 253 418k; totalPages: 63 354;
>     >>> maxCacheSize: 57 018; cacheShrinkThreshold: 10 000
>     >>> 2017-03-31 10:08:49,080 [main] INFO  (XQueryPool.java
>     [configure]:126) -
>     >>> QueryPool: size = 128; maxStackSize = 64; timeout = 120 000;
>     >>> timeoutCheckInterval = 30 000
>     >>> 2017-03-31 10:08:49,112 [main] INFO  (QuartzSchedulerImpl.java
>     >>> [getQuartzProperties]:117) - Successfully loaded quartz.properties
>     >>> 2017-03-31 10:08:49,313 [main] INFO  (IndexManager.java
>     [initIndex]:118)
>     >>> - Registered index org.exist.indexing.ngram.NGramIndex as
>     ngram-index
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java
>     [initIndex]:118)
>     >>> - Registered index org.exist.indexing.lucene.LuceneIndex as
>     lucene-index
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java
>     [initIndex]:118)
>     >>> - Registered index org.exist.indexing.sort.SortIndex as sort-index
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java
>     [initIndex]:118)
>     >>> - Registered index org.exist.indexing.range.RangeIndex as
>     range-index
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (IndexManager.java
>     [initIndex]:118)
>     >>> - Registered index
>     org.exist.storage.structural.NativeStructuralIndex as
>     >>> structural-index
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java
>     [configure]:73) -
>     >>> Using DATA_DIR: c:\eXist-data. Minimal disk space required for
>     database
>     >>> to continue operations: 128mb
>     >>> 2017-03-31 10:08:49,443 [main] INFO  (SyncTask.java
>     [configure]:76) -
>     >>> Usable space on partition containing DATA_DIR: c:\eXist-data:
>     816143mb
>     >>> 2017-03-31 10:08:49,701 [main] INFO  (NativeBroker.java
>     [sync]:3687) -
>     >>> Memory: 63 424K total; 760 256K max; 34 774K free
>     >>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java
>     [printStatistics]:2619)
>     >>> - dom.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>     efficiency
>     >>> : 100 %
>     >>> 2017-03-31 10:08:49,702 [main] INFO  (DOMFile.java
>     >>> [printStatistics]:1393) - dom.dbx DATA Buffers occupation : 0 %
>     (1 out
>     >>> of 256) Cache efficiency : 100 %
>     >>> 2017-03-31 10:08:49,702 [main] INFO  (BTree.java
>     [printStatistics]:2619)
>     >>> - collections.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>     >>> efficiency : 100 %
>     >>> 2017-03-31 10:08:49,702 [main] INFO  (BFile.java
>     [printStatistics]:419)
>     >>> - collections.dbx DATA Buffers occupation : 2 % (1 out of 64) Cache
>     >>> efficiency : 100 %
>     >>> 2017-03-31 10:08:49,703 [main] INFO  (BTree.java
>     [printStatistics]:2619)
>     >>> - values.dbx INDEX Buffers occupation : 2 % (1 out of 64) Cache
>     >>> efficiency : N/A
>     >>> 2017-03-31 10:08:49,703 [main] INFO  (BFile.java
>     [printStatistics]:419)
>     >>> - values.dbx DATA Buffers occupation : 0 % (0 out of 64) Cache
>     >>> efficiency : N/A
>     >>> 2017-03-31 10:08:49,729 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/config.xml
>     >>> 2017-03-31 10:08:49,745 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/exist/accounts/admin.xml
>     >>> 2017-03-31 10:08:49,761 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/config.xml
>     >>> 2017-03-31 10:08:49,761 [main] INFO  (NativeBroker.java
>     >>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>     >>> 2017-03-31 10:08:49,796 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/exist/accounts/admin.xml
>     >>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>     >>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>     >>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/exist/accounts/guest.xml
>     >>> 2017-03-31 10:08:49,812 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/config.xml
>     >>> 2017-03-31 10:08:49,812 [main] INFO  (NativeBroker.java
>     >>> [removeXMLResource]:2707) - Removing document config.xml (2) ...
>     >>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/exist/accounts/guest.xml
>     >>> 2017-03-31 10:08:49,827 [main] INFO  (NativeBroker.java
>     >>> [removeXMLResource]:2707) - Removing document guest.xml (4) ...
>     >>> 2017-03-31 10:08:49,827 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/plugins/config.xml
>     >>> 2017-03-31 10:08:49,858 [main] INFO
>     >>>  (GnuCryptoJceProviderStartupTrigger.java [execute]:46) -
>     Registered JCE
>     >>> Security Provider: gnu.crypto.jce.GnuCrypto
>     >>> 2017-03-31 10:08:49,858 [main] INFO
>     >>>  (URLStreamHandlerStartupTrigger.java
>     [registerStreamHandlerFactory]:61)
>     >>> - Successfully registered eXistURLStreamHandlerFactory.
>     >>> 2017-03-31 10:08:49,881 [main] INFO  (Configurator.java
>     [save]:1280) -
>     >>> Storing configuration /db/system/security/exist/accounts/admin.xml
>     >>> 2017-03-31 10:08:49,901 [main] INFO  (NativeBroker.java
>     >>> [removeXMLResource]:2707) - Removing document admin.xml (3) ...
>     >>> 2017-03-31 10:08:49,906 [main] INFO  (BrokerPool.java
>     [shutdown]:1518) -
>     >>> Database is shutting down ...
>     >>> 2017-03-31 10:08:50,444 [main] INFO  (Journal.java [shutdown]:507) -
>     >>> Transaction journal cleanly shutting down with checkpoint...
>     >>> 2017-03-31 10:08:50,444 [main] INFO  (FileLock.java [release]:188) -
>     >>> Deleting lock file: c:\eXist-data\journal.lck
>     >>> 2017-03-31 10:08:50,460 [main] INFO  (FileLock.java [release]:188) -
>     >>> Deleting lock file: c:\eXist-data\dbx_dir.lck
>     >>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>     >>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>     >>> Signal Dispatcher
>     >>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>     >>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>     >>> Finalizer
>     >>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>     >>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>     >>> Reference Handler
>     >>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>     >>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>     >>> Attach Listener
>     >>> 2017-03-31 10:08:50,460 [main] WARN  (BrokerPool.java
>     >>> [clearThreadLocals]:1691) - Could not clear ThreadLocals for thread:
>     >>> Thread-3
>     >>> 2017-03-31 10:08:50,460 [main] INFO  (BrokerPool.java
>     [shutdown]:1646) -
>     >>> shutdown complete !
>     >>> 2017-03-31 10:08:50,460 [BrokerPools-ShutdownHook] INFO
>     >>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>     >>> 2017-03-31 10:10:25,807 [BrokerPools-ShutdownHook] INFO
>     >>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>     >>> 2017-03-31 11:08:26,219 [BrokerPools-ShutdownHook] INFO
>     >>>  (BrokerPools.java [run]:67) - Executing shutdown thread
>     >>>
>     -------------------------------------------------------------------------------------------
>     >>> Here the Wrapper Log [Action start in Windows Monitor]
>     >>> [WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|OS   : Windows
>     >>> 10/10.0/x86
>     >>> WARNING|wrapper|Service eXist-db|17-03-31 17:47:27|JVM  : Oracle
>     >>> Corporation/1.8.0_121/C:\Program Files (x86)\Java\jre1.8.0_121/32
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|start delay: 0
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|started process
>     with pid 256
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart process
>     due to
>     >>> default exit code rule
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|restart internal
>     RUNNING
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:27|stopping process
>     with
>     >>> pid/timeout 256 45000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:28|process exit code: 1
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|started process
>     with pid 560
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart process
>     due to
>     >>> default exit code rule
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|restart internal
>     RUNNING
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:33|stopping process
>     with
>     >>> pid/timeout 560 45000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:34|process exit code: 1
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|started process
>     with pid
>     >>> 4700
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart process
>     due to
>     >>> default exit code rule
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|restart internal
>     RUNNING
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:39|stopping process
>     with
>     >>> pid/timeout 4700 45000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:40|process exit code: 1
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|started process
>     with pid
>     >>> 9920
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart process
>     due to
>     >>> default exit code rule
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|restart internal
>     RUNNING
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:45|stopping process
>     with
>     >>> pid/timeout 9920 45000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:46|process exit code: 1
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:51|started process
>     with pid
>     >>> 2148
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart process
>     due to
>     >>> default exit code rule
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|restart internal
>     RUNNING
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|stopping process
>     with
>     >>> pid/timeout 2148 45000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:52|process exit code: 1
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:57|started process
>     with pid
>     >>> 5684
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|too many restarts
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|calling onStop
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>     >>> timeout: 30000
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>     >>> wrapper.control -> stopping application
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop
>     - after
>     >>> shutdown
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service stop -
>     >>> before notify
>     >>> INFO|wrapper|Service eXist-db|17-03-31 17:47:58|Win service
>     terminated
>     >>>
>     ----------------------------------------------------------------------------------------
>     >>>
>     >>> If you have some experiments to suggest.  will try them
>     >>>
>     >>>
>     >>> 2017-03-31 16:15 GMT+02:00 Joe Wicentowski <[hidden email]
>     <mailto:[hidden email]>
>     >>> <mailto:[hidden email] <mailto:[hidden email]>>>:
>     >>>
>     >>>     Hi all,
>     >>>
>     >>>     I've been seeing reports here of people with Windows 10 having
>     >>>     problems installing eXist 3.1.1. Do we know if anyone has
>     successfully
>     >>>     installed eXist 3.1.1 on Windows 10?
>     >>>
>     >>>     I ask because I have recently got another office in my
>     organization
>     >>>     interested in eXist, and they wrote saying they were having
>     trouble
>     >>>     installing it on a Windows 10 machine. They are complete
>     newbies,
>     >>>     though, so even asking for logging info will be intimidating
>     for them.
>     >>>
>     >>>     Any info on known routes to success with Windows would be very
>     >>>     helpful!  Has anyone had success?
>     >>>
>     >>>     Thanks,
>     >>>     Joe
>     >>>
>     >>>
>      ------------------------------------------------------------------------------
>     >>>     Check out the vibrant tech community on one of the world's most
>     >>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     >>>     _______________________________________________
>     >>>     Exist-open mailing list
>     >>>     [hidden email]
>     <mailto:[hidden email]>
>     >>>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>     >>>     https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>     >>>     <https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>>
>     >>>
>     >>>
>     >>>
>     >>>
>     >>> --
>     >>> /Dominique Rabeuf/
>     >>>
>     >>>
>     >>>
>     ------------------------------------------------------------------------------
>     >>> Check out the vibrant tech community on one of the world's most
>     >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     >>>
>     >>>
>     >>>
>     >>> _______________________________________________
>     >>> Exist-open mailing list
>     >>> [hidden email]
>     <mailto:[hidden email]>
>     >>> https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>     >>>
>     >>
>     >>
>     >>
>     ------------------------------------------------------------------------------
>     >> Check out the vibrant tech community on one of the world's most
>     >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     >> _______________________________________________
>     >> Exist-open mailing list
>     >> [hidden email]
>     <mailto:[hidden email]>
>     >> https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>     >
>     >
>     ------------------------------------------------------------------------------
>     > Check out the vibrant tech community on one of the world's most
>     > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     >
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Exist-open mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>
>
>
>
> --
> /Dominique Rabeuf/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Loading...