Liferay 6.2 startup is too slow with my windows 8.1 development enviroment....
1.- With my windows 8.1 64 bits development enviroment:
About 12 -15 minutes startup....Changing jvm parameters, same results...too slow. The critical step is "INFO [localhost-startStop-1][AutoDeployDir:139] Auto deploy scanner started for ...." with 5-7 minutes duration. Tested with Java 6 , Java 7 and Java 8, (32 and 64 bits versions).
2.- With the SAME windows 8 machine, but using them like virtual box host and Linux Ubuntu guest....With the same jvm parameters....
About 3 minutes (that's a normal startup time!). With ubuntu virtual machine critical step "INFO [localhost-startStop-1][AutoDeployDir:139] Auto deploy scanner started for ...." is 30 seconds! and within a virtual machine!
3.- With the SAME windows 8 machine, but using them like virtual box host and Windows 7 guest.....With the same jvm parameters...
Just only 3 minutes too! And within a virtual machine!
Definitely the problem seems to be Windows 8.1 . ... but... what is the problem, tomcat + win8? liferay 6.2 + win 8.1?
Anyone works with Windows 8.1? I have discarted hardware problem with the Ubuntu virtual machine (only 3 minutes startup) and the Windows 7 virtual machine (only 3 minutes). I tested all posible java versions and parameters, and liferay startup is not normal.
Best combination should be
Windows server 2008 64bit, 64-bit JDK 1.6 and Tomcat 64-bit.
Windows server 2003 32bit, 32-bit JDK 1.6 and Tomcat 32-bit.
Related
How to install BITS IIS Server Extension on Windows 10?
I can't find anything about windows 10, everything is only about windows servers or is BITS IIS Server Extension not available for windows 10
I have tried to install GraphDB free 9.0.0 on a Windows 10 laptop (x64). The installation finishes succesfully but when I double click GraphDB it does not run. What should I check in order to fiind out why it does not run?
Thank you
I install GDB regularly on Windows 10 using the installer (eg GraphDB_Free-9.3.0.exe). It comes bundled with Java. Here's the version:
cd C:\Users\vladimir.alexiev.000\AppData\Local\GraphDB Free\runtime\bin
java --version
openjdk 11.0.7 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
It's convenient because after starting, it opens Workbench in your browser, and a small control panel where you can see the log etc, and a tray icon.
If you use one of the other distributions, check your Java version.
I installed Server Core 2016 (without the GUI) onto my Windows 10 computer.
Now, whenever I boot up the computer, it just opens a single command prompt with Server Core commands.
How do I go back to Windows 10?
I just need to install Windows 2008 64Bit on a virtual machine. How to??? Do I need a special type of processor? Do I need a "special" virtualization tool? Actually installation fails on startup with the message that the CPU is not able to handle a 64Bit system.
host system: Windows 7 64Bit
CPU: Pentium D (seems to be Smithfield 805)
You need a 64-bit capable processor. VMware / Hyper-V don't emulate CPUs, they execute on them. You don't mention what hypervisor you're using.
I tried Virtual PC 2007 and VirtualBox. Installation stopped with following information:
File: \windows\system32\boot\winload.exe
Status: 0xc000035a
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
I want to use OnlyBelowVersion to install the sc.exe program if the Windows version is 2000 and not at all for Windows NT and below.
What is the only below version required for Windows 2000 only, ie what is the minimum windows XP or Windows 2003 string?
From the InnoSetup help file:
Windows versions:
4.0.950 Windows 95
4.0.1111 Windows 95 OSR 2 & OSR 2.1
4.0.1212 Windows 95 OSR 2.5
4.1.1998 Windows 98
4.1.2222 Windows 98 Second Edition
4.9.3000 Windows Me
Windows NT versions:
4.0.1381 Windows NT 4.0
5.0.2195 Windows 2000
5.01.2600 Windows XP or Windows XP 64-Bit Edition Version 2002 (Itanium)
5.02.3790 Windows Server 2003 or Windows XP x64 Edition (AMD64/EM64T)
or Windows XP 64-Bit Edition Version
2003 (Itanium)
6.0.6000 Windows Vista
6.0.6001 Windows Vista with Service Pack 1 or Windows Server 2008
6.01.7600 Windows 7 or Windows Server 2008 R2
>
And:
OnlyBelowVersion Basically the
opposite of MinVersion. Specifies the
minimum Windows and Windows NT version
for the entry not to be processed. For
example, if you put 4.1,5.0 and the
user is running Windows 95 or NT 4.0
the entry will be processed, but if
the user is running Windows 98 (which
reports its version as 4.1) or Windows
2000 (which reports its version as NT
5.0), it will not be processed. Putting "0" for one of the versions
means there is no upper version limit.
Build numbers and/or service pack
levels may be included in the version
numbers. This overrides any
OnlyBelowVersion directive in the
script's [Setup] section.
An entry without an OnlyBelowVersion
parameter is always processed, unless
other parameters say it shouldn't be.
Example: OnlyBelowVersion: 4.1,5.0