64-bit JVM on solaris 8/9

Has anyone run the 64-bit JVM (-d64) on Solaris 8 or 9?
1.4.1
http://java.sun.com/products/archive/j2se/1.4.1_05/index.html
1.4.2
http://java.sun.com/j2se/1.4.2/install-solaris-64.html
Support tells me BEA has not certified WLS for use with the 64-bit JVM. However,
according to the following link the -server option is implicit to using the 64-bit
JVM:
http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/java.html
======================
-d32
-d64
Specifies whether the program is to be run in a 32-bit or 64-bit environment.
On Solaris these correspond to the ILP32 and LP64 data models, respectively. The
-d64 option may only be used on 64-bit Solaris systems.
Currently only the Java HotSpot Server VM supports 64-bit operation, and the "-server"
option is implicit with the use of -d64. This is subject to change in a future
release.
If neither -d32 nor -d64 is specified, the default is to run in a 32-bit environment.
This is subject to change in a future release.
======================
If BEA does not officially support the 64-bit JVM on either 1.4.1 or 1.4.2, then
why do the default startup scripts coming with WLS 8.1 sp2 (startWebLogic.sh,
comm_Env.sh) allow for the use of the -server option, which, according to Sun's
docs, means you are using the 64-bit JVM?
If anyone has used the 64-bit JVM, what kind of performance gain, if any, are
they seeing?
Thanks for any help.

My dear friend,
You understood java docs incorrectly. That say that if you specify -d64, -server
is implicit, not the other way.
Regards
"achen" <[email protected]> wrote:
>
Has anyone run the 64-bit JVM (-d64) on Solaris 8 or 9?
1.4.1
http://java.sun.com/products/archive/j2se/1.4.1_05/index.html
1.4.2
http://java.sun.com/j2se/1.4.2/install-solaris-64.html
Support tells me BEA has not certified WLS for use with the 64-bit JVM.
However,
according to the following link the -server option is implicit to using
the 64-bit
JVM:
http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/java.html
======================
-d32
-d64
Specifies whether the program is to be run in a 32-bit or 64-bit environment.
On Solaris these correspond to the ILP32 and LP64 data models, respectively.
The
-d64 option may only be used on 64-bit Solaris systems.
Currently only the Java HotSpot Server VM supports 64-bit operation,
and the "-server"
option is implicit with the use of -d64. This is subject to change in
a future
release.
If neither -d32 nor -d64 is specified, the default is to run in a 32-bit
environment.
This is subject to change in a future release.
======================
If BEA does not officially support the 64-bit JVM on either 1.4.1 or
1.4.2, then
why do the default startup scripts coming with WLS 8.1 sp2 (startWebLogic.sh,
comm_Env.sh) allow for the use of the -server option, which, according
to Sun's
docs, means you are using the 64-bit JVM?
If anyone has used the 64-bit JVM, what kind of performance gain, if
any, are
they seeing?
Thanks for any help.

Similar Messages

Could not start/run 64-bit JVM on solaris

Hi,
Basically I wanted to increase the heap size of java on solaris to 4GB .
some where I read ,2GB is the max limit for 32-bit JVM,
Hence I used 64-bit setting to start JVM,
I added "-d64" option.
after this ,when I tried to start weblogic (which calls java) ,it failed to start . giving below error
execv(): No such file or directory
Error trying to exec /data/mss/bea/jdk142_04/jre/bin/sparcv9/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32 bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)
Environment details are :
os.arch = sparc
os.name = SunOS
os.version = 5.9
java.version = 1.4.2_04
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Server VM
Can any one help me on this issue.
setting heap size of java on solaris to 4GB ??
Thanks

Well...
Check if file exists and permissions are setcorrectly.
Verify all necessary J2SE components have beeninstalled.
Did you do that?I am logged using su
I think i must be having all permissions .
Is there any way to verify "J2SE components have been installed"
please refer below url for this kind the bug in sun website.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6181254
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6181254

Solaris 10 64 bit and 64 bit JVM support for Weblogic Server 9.1

Does the following configuration supported:
Weblogic Server 9.1
Sun Solaris 10 (64 bit)
Sun JVM 5.0 (64 bit)
I could only find reference to 32 bit JVM on bea site.
Any help is appreciated.
Thanks

Hi.
answers inline:
sanjay wrote:
Hi,
Can Weblogic Express (Cluster edition)6.1J sp2 be installed on Sun Solaris(Sparc)
8(64 bit) ?Yes - http://edocs.bea.com/wls/platforms/index.html#solaris8
>
>
Can Weblogic Express (Cluster edition)6.1J sp2 JDBC driver be used for Oracle 8.1.7(Solaris
64 bit) ?
Yes - http://edocs.bea.com/wls/platforms/index.html#jdbc
Michael Young
Developer Relations Engineer
BEA Support

64 bit mod_jk for Solaris 10

Hello
Has anyone been able to successfully compile a 64 bit version of mod_jk compatible with apache 2.2 on Solaris 10 (SPARC)
I got hold of Sun Studio 12 update 1 and tried to build a 64 bit version of apache before compiling mod_jk as a prereq. But running into various issues.
Was hoping if some one has the steps document that can be used as a reference.
Thanks

I am pretty confident that you need the 64 bit JVM for your platform, then you need to use the generic installer, this is based on how it has been done in prior releases.
So you can find the available JVM's for your platform here:
http://www.oracle.com/technology/software/products/ias/files/oracle%20fusion%20middleware%2011gr1%20(11%201%201%201%200)%20certification%20matrix.xls
In this case that would be Sun JVM 1.6.0_11+
OR
JRockit 6 Update 5 R27.6.2+
Then you should be able to run the generic installer here with that downloaded supported JDK:
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
I was not able to find anything specific on the documentation pages that described this process in detail, but you can always open a support case to get some assistance. I will check with the documentation team to see if that is going to be documented or already is.
If you look at the 10gR3 releases, it shows how the generic installer is used, for example:
http://e-docs.bea.com/platform/suppconfigs/configs/solaris/solaris10_103.html#104355

How to use java comm API in 64 bit javn on solaris 10

hi,
I want to connect to a device through serial port on sparc Solaris 10 in 64-Bit JVM, but i cannot find the correct API for that, i have tried using RXTX but it has many issues.
I noticed SUNWjcomx package is removed in Solaris 10.
Please some one help

hi,
I want to connect to a device through serial port on sparc Solaris 10 in 64-Bit JVM, but i cannot find the correct API for that, i have tried using RXTX but it has many issues.
I noticed SUNWjcomx package is removed in Solaris 10.
Please some one help

DTrace support for 64 bit JDK on Solaris 10

Hi,
I installed latest 64 bit jdk 1.6_23, using self-extract file, on solaris 10 machine,
and I can't find the hotspot provider for dtrace when I use 64 bit jvm,
I can find them when I use 32 bit,
I use the following command:
$ dtrace -ln 'hotspot*:::'
When I run java -server TestGreeting, ( This program just does endless loop, I borrowed from internet)
I got the probes
When I run with java -d64 -server TestGreeting
I got the following error:
-bash-3.00$ dtrace -ln 'hotspot*:::'
ID PROVIDER MODULE FUNCTION NAME
dtrace: failed to match hotspot*:::: No probe matches description
and when I use ps -ef to grep the java, it shows
~/jdk1.6.0_23/bin/amd64/java -server TestGreeting
Does dtrace support 64 bit JVM?
Thanks
ow005480

Use 32bit for client VM. 64bit client VM is really
useless.And "No one will ever need more that 640K"

Using 64-bit java on Solaris 10 x86

Hello,
I just got a new X2100 server and installed Solaris 10 on it. Everything's running fine and I installed the most recent x86 64-bit jdk 1.5 update on it. However, I can't find any detailed info on how to set the amd64 java binaries and env as the default.
I had to manually prepend /usr/java/bin/amd64 to my path in order to get the 64-bit jvm to be recognized. And it does - when I type java -version it shows that it's the 64-bit server jvm. But, when I try to configure Resin 3.0.14, the configure output specifcally says there is no 64-bit java detected.
So there's gotta be something I'm not doing right. Any help or suggestions would be greatly appreciated.
Thanks,
-jason

On the x86 solaris 10 system I'm looking at there is
a client VM
/bin/java -client -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
and a server VM
/bin/java -server -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
For the client the 64bit VM is still in development. I don't
think there are dates established for that yet.
If you can use the server VM, then you need to down
load the 64bit binaries. Then you will see
/bin/java -server -d64 -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_12-b04, mixed mode)
The downloads are at (look for the release you want)
http://java.sun.com/javase/downloads/index.jsp
Hope that helps.

32-bit vs 64-bit JVM, JDK, DLL's

I've got a project that has a couple dependencies:
1. My project interacts with an FTDI USB->Serial converter based device. Access to this device is via DLL(FTDI calls them D2XX drivers). FTDI offers both 32-bit and 64-bit drivers. Please see here .
2. In order to get access to the DLL via Java, I'm using a JNI called [jd2xx|http://bleyer.org/jd2xx/] . I don't know if or how a JNI would change if the DLL used is 32-bit or 64-bit.
My build & run environment was XP/32. Now I want to build/run on Vista64. But I'm confused because there are multiple options for downloading and installing the different parts which make up the system:
1. Netbeans is available for 32-bit and 64-bit. Which JVM should I point Netbeans to?
2. JVM comes in 32-bit or 64-bit.
3. JDK comes in 32-bit or 64-bit.
While I don't think anyone else actually uses my project, I'd like to have both XP/32 support and Vista/64 support. If I must go one way or the other, it's gotta be Vista/64.
I have tried multiple combinations, but I get a variety of errors depending on what's installed. The errors are all related to 32-bit/64-bit conflicts.
Can someone point me down the right path?
Thanks
Keith

I searched fairly thoroughly through the NetBeans GUI to see if I could target a particular platform, like 32-bit vs 64-bit ---- and I didn't find one. While it may not matter for java itself, when java interacts with a native dll, there are obviously implications.Java class files are os-agnostic - there isn't a "32-bit version" or a "64-bit version", they're both the same. What is different is the JVM that you run a class file on. A 32-bit JVM requires the appropriate 32-bit libraries, etc; the same requirement exists for a 64-bit JVM. I don't know if you can tell an IDE to run using one JVM or the other (obviously this would be possible only with 64-bit arch). I do know that the java tool for Linux/Solaris allows the use of a -d32 or -d64 option to specify that, and that the options aren't valid for the Windows java tool. I also know that Eclipse has native dependencies due to SWT, so that probably causes some restrictions. And. as you note, doing somethisng like JNI has "implications".
If you have further questions re NB, you should raise then at a NB site, not here.

64 bit JVM on Standard Edition of 8.0.1

http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403277&sliceId=1#_Toc193176416
http://www.adobe.com/products/coldfusion/pdfs/cf8_systemsupportmatrix.pdf
You have to have CF Enterprise before you can use a 64 BIT
JVM. I am very disappointed that the bean counters at Adobe made
this choice. I have 4 standard edition CF servers Iand all are on
64 bit hardware since our company buys nothing but 64 bit hardware
for consistency. I cannot convince anyone to pay the HUGE cost
difference for CF Enterprise. Yes, I know I am just complaining
here.

My dear friend,
You understood java docs incorrectly. That say that if you specify -d64, -server
is implicit, not the other way.
Regards
"achen" <[email protected]> wrote:
>
Has anyone run the 64-bit JVM (-d64) on Solaris 8 or 9?
1.4.1
http://java.sun.com/products/archive/j2se/1.4.1_05/index.html
1.4.2
http://java.sun.com/j2se/1.4.2/install-solaris-64.html
Support tells me BEA has not certified WLS for use with the 64-bit JVM.
However,
according to the following link the -server option is implicit to using
the 64-bit
JVM:
http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/java.html
======================
-d32
-d64
Specifies whether the program is to be run in a 32-bit or 64-bit environment.
On Solaris these correspond to the ILP32 and LP64 data models, respectively.
The
-d64 option may only be used on 64-bit Solaris systems.
Currently only the Java HotSpot Server VM supports 64-bit operation,
and the "-server"
option is implicit with the use of -d64. This is subject to change in
a future
release.
If neither -d32 nor -d64 is specified, the default is to run in a 32-bit
environment.
This is subject to change in a future release.
======================
If BEA does not officially support the 64-bit JVM on either 1.4.1 or
1.4.2, then
why do the default startup scripts coming with WLS 8.1 sp2 (startWebLogic.sh,
comm_Env.sh) allow for the use of the -server option, which, according
to Sun's
docs, means you are using the 64-bit JVM?
If anyone has used the 64-bit JVM, what kind of performance gain, if
any, are
they seeing?
Thanks for any help.

Experiencing a 32-bit Java heap barrier on a 64-bit JVM

We are attempting to run a Java application on a Sun Fire V440 with Solaris 9 and 16GB RAM. We are using the 5.0 JRE.
We are starting the application with the -d64 and -server options, and 6g of heap space with the max/min settings the same.
We have queried the Runtime object to confirm that the heap is what we expect it to be, and have plotted our heap usage.
Our full data matrix requests about 3.4GB of memory at one point in the code. We are unable to analyse the full matrix and encounter an OutOfMemoryError on array allocation. What we notice is that when we scale down the matrix so that heap usage is just under the 32 bit barrier (4.3GB) it runs, but as soon as we cross it we error.
We have checked that we are using the 64-bit JVM via the sun.arch.data.model system property and the java.version property. The Runtime object also clearly shows that the free memory is available.
What we see is that before allocation we are using 1,3GB of heap.
Adding about 3.4GB, on array allocation, to this puts us over the 32-bit threshold and we error. Any input would be greatly appreciated.

Thank you for the replies. It has helped significantly! As was suggested, the problem seems to be a young and old generation heap problem. Unfortunately, it's too late to change the subject heading. The barrier was just an artifact of a number of coincidences.
We are closer to solving the issue, but we're not there yet. We tried an experiment with 8GB of heap split 50/50 for young and old using:
java -d64 -server -Xms8000m -Xmx8000m -Xmn4000m
resulting in settings of:
-XX:MaxHeapSize=8388608000
-XX:MaxNewSize=4194304000
-XX:NewSize=4194304000
-XX:+UseParallelGC
Then we manually GC'd before the array allocation just to make sure the young generation heap was cleared out. Prior to this most of the young generation cycling is due to a BufferedReader readline() command.
After System.gc(), we read in an matrix of 900K x 300 double values = 2.1GB of data. We still run out of heap space. Our manual GC is invocation #3 and clears out the young heap, and even promotes an insignificant amount of data to the old heap, but leaves both generations largely empty:
{Heap before gc invocations=1:
PSYoungGen      total 3584000K, used 3072000K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 100% used [0xfffffffe3d400000,0xfffffffef8c00000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to   space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a718,0xfffffffd3fc00000)
0.000: [GCAdaptiveSizePolicy::compute_survivor_space_size_and_thresh: survived: 1032296 promoted: 0 overflow: falseAdaptiveSizeStart: 0.016 collection: 1
AdaptiveSizePolicy::compute_generation_free_space: minor_time: 0.000157 major_cost: 0.000000 mutator_cost: 0.999843 throughput_goal: 0.990000 live_space: 277243776 free_space: 7340032000 old_promo_size: 4194304000 old_eden_size: 3145728000 desired_promo_size: 4194304000 desired_eden_size: 3145728000
AdaptiveSizeStop: collection: 1
[PSYoungGen: 3072000K->1008K(3584000K)] 3072000K->1008K(7680000K), 0.0162566 secs]
Heap after gc invocations=1:
PSYoungGen total 3584000K, used 1008K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8cfc068,0xffffffff18000000)
to space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
PSOldGen total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a718,0xfffffffd3fc00000)
{Heap before gc invocations=2:
PSYoungGen      total 3584000K, used 2952191K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 96% used [0xfffffffe3d400000,0xfffffffef1603f40,0xfffffffef8c00000)
from space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8cfc068,0xffffffff18000000)
to   space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7596K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6b3d8,0xfffffffd3fc00000)
88.203: [GCAdaptiveSizePolicy::compute_survivor_space_size_and_thresh: survived: 999520 promoted: 0 overflow: falseAdaptiveSizeStart: 88.212 collection: 2
AdaptiveSizeStop: collection: 2
[PSYoungGen: 2952191K->976K(3584000K)] 2952191K->976K(7680000K), 0.0096021 secs]
Heap after gc invocations=2:
PSYoungGen total 3584000K, used 976K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff180f4060,0xffffffff37400000)
to space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen total 24576K, used 7596K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6b3d8,0xfffffffd3fc00000)
{Heap before gc invocations=3:
PSYoungGen      total 3584000K, used 976K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff180f4060,0xffffffff37400000)
to   space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7596K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6b3d8,0xfffffffd3fc00000)
88.213: [Full GCAdaptiveSizeStart: 88.392 collection: 3
AdaptiveSizeStop: collection: 3
[PSYoungGen: 976K->0K(3584000K)] [PSOldGen: 0K->874K(4096000K)] 976K->874K(7680000K) [PSPermGen: 7596K->7596K(24576K)], 0.1788788 secs]
Heap after gc invocations=3:
PSYoungGen total 3584000K, used 0K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen total 4096000K, used 874K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd434da8c0,0xfffffffe3d400000)
PSPermGen total 24576K, used 7596K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6b3d8,0xfffffffd3fc00000)
java.lang.OutOfMemoryError: Requested array size exceeds VM limit
So next we reduced our data to 890K x 300 double values = 2.14GB of data, not a lot less, and it allocates fine. In fact in GC #4 it has even promoted the signal matrix to the old generation:
{Heap before gc invocations=1:
PSYoungGen      total 3584000K, used 3072000K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 100% used [0xfffffffe3d400000,0xfffffffef8c00000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to   space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
0.000: [GCAdaptiveSizePolicy::compute_survivor_space_size_and_thresh: survived: 1048656 promoted: 0 overflow: falseAdaptiveSizeStart: 0.017 collection: 1
AdaptiveSizePolicy::compute_generation_free_space: minor_time: 0.000281 major_cost: 0.000000 mutator_cost: 0.999719 throughput_goal: 0.990000 live_space: 277260224 free_space: 7340032000 old_promo_size: 4194304000 old_eden_size: 3145728000 desired_promo_size: 4194304000 desired_eden_size: 3145728000
AdaptiveSizeStop: collection: 1
[PSYoungGen: 3072000K->1024K(3584000K)] 3072000K->1024K(7680000K), 0.0170110 secs]
Heap after gc invocations=1:
PSYoungGen total 3584000K, used 1024K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8d00050,0xffffffff18000000)
to space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
PSOldGen total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
{Heap before gc invocations=2:
PSYoungGen      total 3584000K, used 2891377K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 94% used [0xfffffffe3d400000,0xfffffffeeda9c6d8,0xfffffffef8c00000)
from space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8d00050,0xffffffff18000000)
to   space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
37.161: [GCAdaptiveSizePolicy::compute_survivor_space_size_and_thresh: survived: 1015880 promoted: 0 overflow: falseAdaptiveSizeStart: 37.171 collection: 2
AdaptiveSizeStop: collection: 2
[PSYoungGen: 2891377K->992K(3584000K)] 2891377K->992K(7680000K), 0.0098960 secs]
Heap after gc invocations=2:
PSYoungGen total 3584000K, used 992K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff180f8048,0xffffffff37400000)
to space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
{Heap before gc invocations=3:
PSYoungGen      total 3584000K, used 992K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff180f8048,0xffffffff37400000)
to   space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen        total 4096000K, used 0K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd43400000,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
37.172: [Full GCAdaptiveSizeStart: 37.352 collection: 3
AdaptiveSizeStop: collection: 3
[PSYoungGen: 992K->0K(3584000K)] [PSOldGen: 0K->874K(4096000K)] 992K->874K(7680000K) [PSPermGen: 7593K->7593K(24576K)], 0.1802284 secs]
Heap after gc invocations=3:
PSYoungGen total 3584000K, used 0K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen total 4096000K, used 874K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd434da8c0,0xfffffffe3d400000)
PSPermGen total 24576K, used 7593K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6a768,0xfffffffd3fc00000)
{Heap before gc invocations=4:
PSYoungGen      total 3584000K, used 3072000K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 100% used [0xfffffffe3d400000,0xfffffffef8c00000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to   space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen        total 4096000K, used 874K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 0% used [0xfffffffd43400000,0xfffffffd434da8c0,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7611K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6eeb0,0xfffffffd3fc00000)
54.054: [GC-- [PSYoungGen: 3072000K->3072000K(3584000K)] 3072874K->5158809K(7680000K), 23.1725940 secs]
Heap after gc invocations=4:
PSYoungGen total 3584000K, used 3072000K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 100% used [0xfffffffe3d400000,0xfffffffef8c00000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to space 512000K, 1% used [0xfffffffef8c00000,0xfffffffef947a490,0xffffffff18000000)
PSOldGen total 4096000K, used 2086809K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 50% used [0xfffffffd43400000,0xfffffffdc29e6578,0xfffffffe3d400000)
PSPermGen total 24576K, used 7611K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6eeb0,0xfffffffd3fc00000)
{Heap before gc invocations=5:
PSYoungGen      total 3584000K, used 3072000K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 100% used [0xfffffffe3d400000,0xfffffffef8c00000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to   space 512000K, 1% used [0xfffffffef8c00000,0xfffffffef947a490,0xffffffff18000000)
PSOldGen        total 4096000K, used 2086809K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 50% used [0xfffffffd43400000,0xfffffffdc29e6578,0xfffffffe3d400000)
PSPermGen       total 24576K, used 7611K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6eeb0,0xfffffffd3fc00000)
77.227: [Full GCAdaptiveSizeStart: 81.903 collection: 5
AdaptiveSizePolicy::compute_generation_free_space limits: desired_promo_size: 5310531271 promo_limit: 4194304000 free_in_old_gen: 2048607488 max_old_gen_size: 4194304000 avg_old_live: 4746786511456829440
AdaptiveSizePolicy::compute_generation_free_space limits: desired_eden_size: 5454285546 old_eden_size: 3145728000 eden_limit: 3145728000 cur_eden: 3145728000 max_eden_size: 3145728000 avg_young_live: 524328
AdaptiveSizePolicy::compute_generation_free_space: minor_time: 0.289393 major_cost: 0.104945 mutator_cost: 0.605662 throughput_goal: 0.990000 live_space: 2422441472 free_space: 7340032000 old_promo_size: 4194304000 old_eden_size: 3145728000 desired_promo_size: 4194304000 desired_eden_size: 3145728000
AdaptiveSizeStop: collection: 5
[PSYoungGen: 3072000K->0K(3584000K)] [PSOldGen: 2086809K->2095406K(4096000K)] 5158809K->2095406K(7680000K) [PSPermGen: 7611K->7611K(24576K)], 4.6758162 secs]
Heap after gc invocations=5:
PSYoungGen total 3584000K, used 0K [0xfffffffe3d400000, 0xffffffff37400000, 0xffffffff37400000)
eden space 3072000K, 0% used [0xfffffffe3d400000,0xfffffffe3d400000,0xfffffffef8c00000)
from space 512000K, 0% used [0xffffffff18000000,0xffffffff18000000,0xffffffff37400000)
to space 512000K, 0% used [0xfffffffef8c00000,0xfffffffef8c00000,0xffffffff18000000)
PSOldGen total 4096000K, used 2095406K [0xfffffffd43400000, 0xfffffffe3d400000, 0xfffffffe3d400000)
object space 4096000K, 51% used [0xfffffffd43400000,0xfffffffdc324bad0,0xfffffffe3d400000)
PSPermGen total 24576K, used 7611K [0xfffffffd3e400000, 0xfffffffd3fc00000, 0xfffffffd43400000)
object space 24576K, 30% used [0xfffffffd3e400000,0xfffffffd3eb6eeb0,0xfffffffd3fc00000)
Apologies for the long trace information, but it's not clear yet what is going on. We even tried to add:
-XX:PretenureSizeThreshold=1000m
to try to force the signal matrix into old generation first upon allocation. This is where it should be, and would save the heap from having to promote it later. So question is: Is there something we're missing w.r.t. eden/from/to space ? Clearly, there is!
Thanks again!

WLS 32-bit installer on a 64-bit JVM

Hi All,
I was also told that I could run the WLS 10.3.1 (32 bit) installer wls1031_solaris32.bin along with a 64-bit JVM and WebLogic will run in 64-bit mode. Is that true?
If yes then what is the need for a 64 bit installer?
My underlying OS is solaris 64 bit.
I wonder how is that possible. Can anyone help me understand?
Thanks in advance.

It doesn't make sense to me that a 32-bit installer is installing a 64-bit JVM unless that installer will install both 32-bit and 64-bit JVMs.
I would suggest you use the installer from the edelivery site: WebLogic Server 9.2 MP3 Sun Solaris SPARC (64-bit) V15433-01 598M.
Regards,
John A. Booth
http://www.metavero.com

Problem in invoking 32 bit JVM by using -d32 option

Hi all,
I am facing the following error message on solaris 10, when i use -d32 option in java command.
execv(): No such file or directory
Error trying to exec /usr/j2se/bin/sparcv9/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32-bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)
I am not able to figure out why this error is coming.
cheers,
ngs

Hi Sush,
I tried executing by giving full path of java. It gave same error. I have one more question. I have compiled the code using 64 bit JVM. Can i run that class code by using -d32 option in java command ?
[ Thats exactly what i am doing. And it is giving the same error. ]
bash-3.00$ /omcsw/29.0.1.3.00/lib/3pt/jdk/jre/bin/java -d32 test
execve(): No such file or directory
Error trying to exec /omcsw/29.0.1.3.00/lib/3pt/jdk/jre/bin/../java.
Check if file exists and permissions are set correctly.
Failed to start a 32-bit JVM process from a 64-bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)
regards,
ngs

Is it Possible to install oracle 9i 32 bit on Sun Solaris Intel Edition

Dear OTN Members ,
It is possible to install ORACLE 9I Sun SPARC Solaris (32 Bit) on
Sun Solaris Intel Editon 2.8 . Please inform me on
email :-
[email protected]
[email protected]
Thanking You
Piyush Patel
- Server name :- pi.com
- Filename
- Date/Time
- Browser + Version : Netscape 4.7
- O/S + Version : Sun Solaris Intel Edition 2.8

857211 wrote:
I just need some advice on installing oracle 11gWhat part/product of "oracle 11g" exactly?
Installation Guides should be clear enough, if read. Also read Release Notes for additional support/unsupport info.
http://docs.oracle.com/cd/E11882_01/install.112/e24186/reqs.htm#CHDHGGFE
http://docs.oracle.com/cd/E11882_01/install.112/e24187/pre_install.htm
However the Installation Guide for Database Client adds:
"Note: Oracle provides 32-bit (Windows x86) and 64-bit (Windows x64) versions of Oracle Database Client. _Oracle certifies 32-bit Oracle Database Client on Windows x64_." (underline added)

INST-07408: Unable to install or configure the product on a 32-bit JVM on a 64-bit machine. Make sure to install and configure the product in supported modes.

Hi there, i have an issue installing oracle forms and reports. its throwing this error"INST-07408: Unable to install or configure the product on a 32-bit JVM on a 64-bit machine. Make sure to install and configure the product in supported modes." on step 5. I have jdk 64bit installed, weblogic server was installed successfully but iam getting stuck somehow.
Below are details of my pc.
OS Name    Microsoft Windows 7 Professional
Version    6.1.7601 Service Pack 1 Build 7601
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name   ...........-HP
System Manufacturer    Hewlett-Packard
System Model    HP ProBook 4530s
System Type    x64-based PC
Processor    Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date    Hewlett-Packard 68SRR Ver. F.23, 09/03/2012
SMBIOS Version    2.6
Windows Directory    C:\windows
System Directory    C:\windows\system32
Boot Device    \Device\HarddiskVolume1
Locale    United Kingdom
Hardware Abstraction Layer    Version = "6.1.7601.17514"
User Name    ...........-HP\................
Time Zone    South Africa Standard Time
Installed Physical Memory (RAM)    4.00 GB
Total Physical Memory    3.94 GB
Available Physical Memory    1.00 GB
Total Virtual Memory    7.87 GB
Available Virtual Memory    1.25 GB
Page File Space    3.94 GB
Page File    C:\pagefile.sys

To clarify further.... It is important to note that Forms/Repors 11.1.2.x software (including WLS and JDK) must be of the same archetecture as the machine. In other words, you cannot use the 32bit Forms/Reports 11.1.2 software on 64bit Windows. If you are using a 64bit OS, you must install the 64bit software. Again, this would include Forms/Reports, WLS, and JDK

64-bit JRE for Solaris 10 x86

I understand that this is not one of the supported configurations at this time. Could anyone comment if there are plans to support 64-bit Java on Solaris 10 x86?
Cheers,
~george

On the x86 solaris 10 system I'm looking at there is
a client VM
/bin/java -client -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
and a server VM
/bin/java -server -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
For the client the 64bit VM is still in development. I don't
think there are dates established for that yet.
If you can use the server VM, then you need to down
load the 64bit binaries. Then you will see
/bin/java -server -d64 -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_12-b04, mixed mode)
The downloads are at (look for the release you want)
http://java.sun.com/javase/downloads/index.jsp
Hope that helps.

64-bit JVM on solaris 8/9

Similar Messages

Maybe you are looking for