Created attachment 799949 [details]
Description of problem:
Please see screenshot attached.
How reproducible: not known, occurs rarely
Java(TM) SE Runtime Environment (build 1.7.0_25-b17)
This issue seems to be occuring with the installer tries to launch the server. The server is started as a separate Process, in its own JVM. I have not been able to reproduce this issue. I would see if you can reproduce the issue by launching the server outside of the installer (the installer just invokes ./standalone.sh --admin-only or ./domain.sh --admin-only).
It would be helpful to know which job exactly is causing this error (the number in the parenthesis on that panel.)
You are right Thomas, I cannot launch the server outside of the installer.
Created attachment 800016 [details]
The issue here is java and 32bit windows and that there is not enough *contiguous* memory for object heap.
"The maximum theoretical heap limit for the 32-bit JVM is 4G. Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower. On most modern 32-bit Windows systems the maximum heap size will range from 1.4G to 1.6G."
And that is not enough for launching the server inside the installer.
We *do* support x86 architecture on windows. How can we fix this?
From your screenshots above, not only is it not enough to launch the server from inside the installer, but it's not enough to launch the server even from outside of it as well.
I tried today again. There were 1.7GB Free and 2.7GB Available memory according to the windows task manager utility. I was able to run './standalone.bat --admin-only' from within the console. But the installer itself has failed.