Windows startup script problems
Thursday, 27 November 2014 · 2 messages
MG
Marc van Grootel27 Nov 2014 10:45 #
Hi,
I just downloaded the latest snapshot and on Windows I got a problem with the startup scripts. I saw that compared to earlier the way to set JVM options has changed.
In my case this was causing problems.
When I started the default basexhttp.bat I got:
Invalid maximum heap size: -Xmx512m
I looked at the batch script and had to change the BASEX_JVM line from
set BASEX_JVM=-Xmx512m %BASEX_JVM%
to
set BASEX_JVM=-Xmx512m
Could it be that the extra space after 512m is causing the problem.
Probably same issue in other startup scripts.
(nice language windows batch file, isn't it ...)
--Marc
CG
Christian Grün27 Nov 2014 11:44 #
Marc,
thanks for the hint. I have updated the startup scripts in question.
Best,
Christian
Quoted text · Marc van Grootel · 30 lines
On Thu, Nov 27, 2014 at 10:45 AM, Marc van Grootel <marc.van.grootel at gmail.com> wrote: > Hi, > > I just downloaded the latest snapshot and on Windows I got a problem > with the startup scripts. I saw that compared to earlier the way to > set JVM options has changed. > > In my case this was causing problems. > > When I started the default basexhttp.bat I got: > > Invalid maximum heap size: -Xmx512m > > I looked at the batch script and had to change the BASEX_JVM line from > > set BASEX_JVM=-Xmx512m %BASEX_JVM% > > to > > set BASEX_JVM=-Xmx512m > > Could it be that the extra space after 512m is causing the problem. > > Probably same issue in other startup scripts. > > (nice language windows batch file, isn't it ...) > > > --Marc
Written for BaseX 7.9. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery