Can anyone give me a link to a download of JRE 1.5.x for Windows 2003 Server x64? We are running the x64 version of Windows 2003 on a server with Intel Xeons (32-bit). Thanks.
1- Go to Java Runtime Environment (JRE) 5.0 Update 12 then click Download
2- Accept the user license and choose the last one (Windows x64 Platform - Java Runtime Environment 5.0 Update 12)
3- if you can't download it, try the sun download manager
Just to note: I am the same person as the original poster.
Those links point me to download jdk-1_5_0_12-windows-amd64.exe and jre-1_5_0_12-windows-amd64.exe but these only work on AMD 64-bit processors. We have Intel Xeon 32-bit processors but with Windows 2003 Server x64. Is there a version of the JVM that is optimized for x64 that will run on a 32-bit platform that takes advantage of Windows x64 use of the higher memory allocation. We are running Windows 2003 x64 on a 32-bit platform so we can access memory over the 4gb limit. We have 8gb of ram installed.
Also, how much memory should we be allocating to the JVM for a performance testing server running Tomcat 5.5.23?
Yes you can install Windows 2003 Server x64 Enterprise Edition on a Intel Xeon 32-bit based server. We have many servers that we have done that on. It is done so we can access the higher memory range.
Yes you can install Windows 2003 Server x64
Enterprise Edition on a Intel Xeon 32-bit based
server. We have many servers that we have done that
on.
If this is true, which I doubt, 32-bit processors have a maximum of 32 address lines so they can only access 2^32 bytes or 4GiB. And since windows puts its dll's somewhere in the middle you usually can't get more that 2GiB with a 32bit processor and windows.
It is done so we can access the higher memory
range.
Still wouldn't be able to get more than 4GiB.
More likely you only think your using a 32-bit processor but you're actually using an Intel Xeon EM64T processor. Or you are confusing the ability of running 32-bit software on Windows x64.
How about providing a link to a screen shot of your System Properties Page(Control Panel->System->General Tab) or give me one link that says you can run Windows 2003 x64 on 32-bit hardware. I can find many links that say you can't:
Four of the above links are from Microsoft's own web site. They pretty much all say the system requirements for Windows x64 is a 64-bit hardware architecture.
According to http://processorfinder.intel.com/details.aspx?sSpec=SL9YL the Intel Xeon E5345 has EM64T and therefore 64 bit. That processor is a "quad" core and isn't even a year old. Of course it is going to be 64 bit.
There are a patch for Windows 2003 Server that allows to assign 3 Gb of memory. Check this interesting text that send me IBM support in the past.
Memory Support and Windows Operating Systems
Updated: February 9, 2005
Operating systems based on Microsoft Windows NT technologies have always
provided applications with a flat 32-bit virtual address space that
describes 4 gigabytes (GB) of virtual memory. The address space is usually
split so that 2 GB of address space is directly accessible to the
application and the other 2 GB is only accessible to the Windows executive
software.
The 32-bit versions of the Windows 2000 Advanced Server and Windows NT
Server 4.0, Enterprise Edition, operating systems were the first versions
of Windows to provide applications with a 3-GB flat virtual address space,
with the kernel and executive components using only 1 GB. In response to
customer requests, Microsoft has expanded the availability of this support
to the 32-bit version of Windows XP Professional and all 32-bit versions
of Windows Server 2003.
Windows 2000 Memory Support. With Windows 2000 Professional and Server,
the maximum amount of memory that can be supported is 4 GB (identical to
Windows NT 4.0, as described later in this section). However, Windows 2000
Advanced Server supports 8 GB of physical RAM and Windows 2000 Datacenter
Server supports 32 GB of physical RAM using the PAE feature of the IA-32
processor family, beginning with Intel Pentium Pro and later.
Windows XP Professional and Windows Server 2003 Memory Support. The
maximum amount of memory that can be supported on Windows XP Professional
and Windows Server 2003 is also 4 GB. However, Windows Server 2003,
Enterprise Edition supports 32 GB of physical RAM and Windows Server 2003,
Datacenter Edition supports 64 GB of physical RAM using the PAE feature.
The virtual address space of processes and applications is still limited
to 2 GB unless the /3GB switch is used in the Boot.ini file. When the
physical RAM in the system exceeds 16 GB and the /3GB switch is used, the
operating system will ignore the additional RAM until the /3GB switch is
removed. This is because of the increased size of the kernel required to
support more Page Table Entries. The assumption is made that the
administrator would rather not lose the /3GB functionality silently and
automatically; therefore, this requires the administrator to explicitly
change this setting.
The /3GB switch allocates 3 GB of virtual address space to an application
that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process header. This
switch allows applications to address 1 GB of additional virtual address
space above 2 GB.
The virtual address space of processes and applications is still limited
to 2 GB, unless the /3GB switch is used in the Boot.ini file. The
following example shows how to add the /3GB parameter in the Boot.ini file
to enable application memory tuning:
Note: "????" in the previous example can be the programmatic name of any
of the following operating system versions:
Windows XP Professional
Windows Server 2003
Windows Server 2003, Enterprise Edition
Windows Server 2003, Datacenter Edition
Windows 2000 Advanced Server
Windows 2000 Datacenter Server
Windows NT Server 4.0, Enterprise Edition
Windows NT 4.0 Memory Support. With Microsoft Windows NT 4.0 Workstation
and Server operating systems, the maximum amount of physical memory
supported is 4 GB. The maximum amount of virtual memory is 2 GB.
With Windows NT 4.0 Server, Enterprise Edition, the /3GB switch was first
added to Boot.ini.
Application Memory Tuning. This capability allows memory-intensive
applications to utilize up to 50 percent more virtual memory on
Intel-based computers. Application memory tuning provides more of the
computer's virtual memory to applications by providing less virtual memory
to the operating system.
Application Changes. No APIs are required to support application memory
tuning. However, it would be ineffective to automatically provide every
application with a 3-GB address space.
Executables that can use the 3-GB address space are required to have the
bit IMAGE_FILE_LARGE_ADDRESS_AWARE set in their image header. If you are
the developer of the executable, you can specify a linker flag
(/LARGEADDRESSAWARE).
To set this bit, you must use Microsoft Visual Studio Version 6.0 or later
and the Editbin.exe utility, which has the ability to modify the image
header (/LARGEADDRESSAWARE) flag. For more information on setting this
flag, see the Microsoft Visual Studio documentation.
Some manufacturers preconfigure their applications to use application
memory tuning, making it unnecessary for you to make this change. For more
information, see your application documentation and contact your
application vendor to determine whether they support Large Address
Awareness or whether you can enable it in their application.
Physical Address Extension. PAE is an Intel-provided memory address
extension that enables support of up to 64 GB of physical memory for
applications running on most 32-bit (IA-32) Intel Pentium Pro and later
platforms. Support for PAE is provided under Windows 2000 and 32-bit
versions of Windows XP and Windows Server 2003. 64-bit versions of Windows
do not support PAE.
PAE allows the most recent IA-32 processors to expand the number of bits
that can be used to address physical memory from 32 bits to 36 bits
through support in the host operating system for applications using the
Address Windowing Extensions (AWE) application programming interface
(API). For information about the AWE API, see the Base Services section of
the Platform SDK.
Email this Topic
Edit this Topic
10 Duke Stars available
