Recommended JVM on Solaris 10

Hi,
I am currently trying load test a web application under iPlanet 6.1 after a recent upgrade from Solaris 8 to Solaris 10. The performance under Solaris 10 is not the same as under Solaris 8, so I wanted to verify some information about versions we are using of iPlanet and Java and make sure they make sense under Solaris 10.
We are using Java 1.4.2 and can not upgrade to 1.5.x at this time. On Solaris 8 we are running 1.4.2_b11 and on Solaris 10 we are running 1.4.2_b12. I seem to recall that Sun has in the past recommended that we pair a Java version with a patch level on Solaris. Is this true? I noticed that b14 was now available for download, so I have versions 11-14 that I could be running on the Solaris 10 box. Which offers the best performance?
For iPlanet we are running the same version under both OSes. Is there a patch after the one that we are on that would address performance issues under Solaris 10? The version we are running is: iPlanet 6.1 sp6 64 bit b05082006
uname -r shows us 5.10.. I'm not sure how to show patch levels?

Well, if you feel unsafe about upgrading to Java 1.5.0 or 1.6.0, I'd recommend you to run the latest 1.4.2 release. It probably have quite some bugfixes compared with the earlier versions.
.7/M.

Similar Messages

I want to add a solar charger for iPhone 5 and iPad to my emergency kit. Are there recommendations for compatible solar products?

I want to add a solar charger for iPhone 5 and iPad to my emergency kit. Are there recommendations for compatible solar products?

If you are seldom in a Wi-Fi Network Area, then you can turn off Wi-Fi until you knowingly are in such a Network Area. You can go through your Applications where you don't really need to know the instant an Update is available and turn off the push update notifications. You can turn down the screen brightness. You can set the sleep cycle to 1-min. You could set your email to check for new messages every 30-min. rather than less than 1 min. Just some of many steps available.

Smpatch and Recommended Patches for Solaris 10

Hi,
Is there any way to make smpatch only retrieve recommended patches for Solaris 10 ?
I've seen several forum posts saying to use
smpatch set patchpro.patchset=recommended
but other posters indicate that this only works for Solaris 9 (additionally, it doesn't seem to work at all currently:
Failure: Cannot connect to retrieve recommended.zip: Not Found )
As far as I'm aware, Sun's patching policy is to apply the Recommended patches, as well as any that address specific issues you are having. This seems to contrast with the behaviour of smpatch which grabs all patches..

Hi.
Depending on your hardware, you can use the following in place of 'current' in patchpro.patchset to get recommended patches:
sunu45 = Sun Ultra45/Ultra25 Recommended
sftxk = Sun Fire T1000/T2000 Recommended
sfv2x5 = Sun Fire V215/245 Recommended
sfv445 = Sun Fire V445 Recommended
Mod.

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.

Help on JVM at Solaris 10.x

Hi
Currently we have Solaris 8.x installed and we have JVM version of 1.3 installed in it. Now we are going to upgraed the OS to Solaris 10.x. I want to know whether we need to upgrade the JVM to accomodate the new OS?
Regards
Ravi.

[http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/crashes.html]

JDriver for Oracle crashes JVm on solaris

Hi,
I'm using the weblogic jDriver/XA for oracle with oracle 8.1.7 on solaris 2.8.
The weblogic version is 6.1 SP2.
The JVM randomly crashes with this error:
Is the jDriver/XA that comes with weblogic stable ?
Has the jDriver that comes with wlserver 6.1 SP3 fixed this problem ?
Unexpected Signal : 11 occurred at PC=0xfe557f64
Function name=JVM_InternString
Library=/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
Current Java thread:
     at weblogic.jdbc.oci.xa.XA.native_start(Native Method)
     at weblogic.jdbc.oci.xa.XA.start(XA.java:70)
     at weblogic.jdbc.oci.xa.XADataSource.start(XADataSource.java:640)
     at weblogic.jdbc.jta.DataSource.detectedUnavailable(DataSource.java:445)
     at weblogic.transaction.internal.ResourceDescriptor$2.execute(ResourceDescriptor.java:991)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000      /bea/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000      /usr/lib/libthread.so.1
0xff390000      /usr/lib/libdl.so.1
0xff200000      /usr/lib/libc.so.1
0xff330000      /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
0xfe400000      /bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000      /usr/lib/libCrun.so.1
0xff1e0000      /usr/lib/libsocket.so.1
0xff100000      /usr/lib/libnsl.so.1
0xff0d0000      /usr/lib/libm.so.1
0xff310000      /usr/lib/libw.so.1
0xff0b0000      /usr/lib/libmp.so.2
0xff080000      /bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000      /bea/jdk131/jre/lib/sparc/libverify.so
0xfe7c0000      /bea/jdk131/jre/lib/sparc/libjava.so
0xff020000      /bea/jdk131/jre/lib/sparc/libzip.so
0xfe3b0000      /usr/lib/locale/en_US.ISO8859-1/en_US.ISO8859-1.so.2
0xfe390000      /bea/jdk131/jre/lib/sparc/libnet.so
0xfaed0000      /usr/lib/nss_files.so.1
0xd9200000      /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
0xd8400000      /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
0xfad90000      /usr/lib/libC.so.5
0xfaea0000      /u01/app/oracle/product/8.1.7/lib/libwtc8.so
0xface0000      /usr/lib/libgen.so.1
0xfacc0000      /usr/lib/libsched.so.1
0xfaca0000      /usr/lib/libaio.so.1
0xfac80000      /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoxa37.so
0xfac10000      /bea/jdk131/jre/lib/sparc/libioser12.so
0xdeae0000      /bea/jdk131/jre/lib/sparc/libawt.so
0xd7480000      /bea/jdk131/jre/lib/sparc/motif21/libmawt.so
0xdc8b0000      /bea/jdk131/jre/bin/../lib/sparc/libmlib_image.so
0xd7200000      /usr/dt/lib/libXm.so.4
0xd7190000      /usr/openwin/lib/libXt.so.4
0xdc7d0000      /usr/openwin/lib/libXext.so.0
0xdce60000      /usr/openwin/lib/libXtst.so.1
0xd7080000      /usr/openwin/lib/libX11.so.4
0xdc7b0000      /usr/openwin/lib/libSM.so.6
0xdc6d0000      /usr/openwin/lib/libICE.so.6
0xdc6a0000      /usr/openwin/lib/libdga.so.1
0xd6f80000      /bea/jdk131/jre/lib/sparc/libfontmanager.so
0xdc5a0000      /usr/openwin/lib/libdps.so.5
0xdc4c0000      /bea/jdk131/jre/lib/sparc/libdcpr.so
0xdc3b0000      /bea/jdk131/jre/lib/sparc/libcmm.so
0xdc2c0000      /bea/jdk131/jre/lib/sparc/libjpeg.so
0xdc890000      /bea/wlserver6.1/lib/solaris/libmuxer.so
0xdc4a0000      /usr/ucblib/libucb.so.1
0xdc790000      /usr/lib/libresolv.so.1
0xdc1c0000      /usr/lib/libelf.so.1
Local Time = Sun Aug 25 19:12:47 2002
Elapsed Time = 21231
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002BD 01
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
# An error report file has been saved as hs_err_pid342.log.
# Please refer to the file for further information.

We have observed some problems for XA in oracle 817 client. You should use 901 client and 901 jDriver
to talk to 817 database as a solution.
Mitesh
prajod wrote:
Hi,
I'm using the weblogic jDriver/XA for oracle with oracle 8.1.7 on solaris 2.8.
The weblogic version is 6.1 SP2.
The JVM randomly crashes with this error:
Is the jDriver/XA that comes with weblogic stable ?
Has the jDriver that comes with wlserver 6.1 SP3 fixed this problem ?
Unexpected Signal : 11 occurred at PC=0xfe557f64
Function name=JVM_InternString
Library=/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
Current Java thread:
at weblogic.jdbc.oci.xa.XA.native_start(Native Method)
at weblogic.jdbc.oci.xa.XA.start(XA.java:70)
at weblogic.jdbc.oci.xa.XADataSource.start(XADataSource.java:640)
at weblogic.jdbc.jta.DataSource.detectedUnavailable(DataSource.java:445)
at weblogic.transaction.internal.ResourceDescriptor$2.execute(ResourceDescriptor.java:991)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000 /bea/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
0xfe400000 /bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /bea/jdk131/jre/lib/sparc/libverify.so
0xfe7c0000 /bea/jdk131/jre/lib/sparc/libjava.so
0xff020000 /bea/jdk131/jre/lib/sparc/libzip.so
0xfe3b0000 /usr/lib/locale/en_US.ISO8859-1/en_US.ISO8859-1.so.2
0xfe390000 /bea/jdk131/jre/lib/sparc/libnet.so
0xfaed0000 /usr/lib/nss_files.so.1
0xd9200000 /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
0xd8400000 /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
0xfad90000 /usr/lib/libC.so.5
0xfaea0000 /u01/app/oracle/product/8.1.7/lib/libwtc8.so
0xface0000 /usr/lib/libgen.so.1
0xfacc0000 /usr/lib/libsched.so.1
0xfaca0000 /usr/lib/libaio.so.1
0xfac80000 /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoxa37.so
0xfac10000 /bea/jdk131/jre/lib/sparc/libioser12.so
0xdeae0000 /bea/jdk131/jre/lib/sparc/libawt.so
0xd7480000 /bea/jdk131/jre/lib/sparc/motif21/libmawt.so
0xdc8b0000 /bea/jdk131/jre/bin/../lib/sparc/libmlib_image.so
0xd7200000 /usr/dt/lib/libXm.so.4
0xd7190000 /usr/openwin/lib/libXt.so.4
0xdc7d0000 /usr/openwin/lib/libXext.so.0
0xdce60000 /usr/openwin/lib/libXtst.so.1
0xd7080000 /usr/openwin/lib/libX11.so.4
0xdc7b0000 /usr/openwin/lib/libSM.so.6
0xdc6d0000 /usr/openwin/lib/libICE.so.6
0xdc6a0000 /usr/openwin/lib/libdga.so.1
0xd6f80000 /bea/jdk131/jre/lib/sparc/libfontmanager.so
0xdc5a0000 /usr/openwin/lib/libdps.so.5
0xdc4c0000 /bea/jdk131/jre/lib/sparc/libdcpr.so
0xdc3b0000 /bea/jdk131/jre/lib/sparc/libcmm.so
0xdc2c0000 /bea/jdk131/jre/lib/sparc/libjpeg.so
0xdc890000 /bea/wlserver6.1/lib/solaris/libmuxer.so
0xdc4a0000 /usr/ucblib/libucb.so.1
0xdc790000 /usr/lib/libresolv.so.1
0xdc1c0000 /usr/lib/libelf.so.1
Local Time = Sun Aug 25 19:12:47 2002
Elapsed Time = 21231
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002BD 01
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
# An error report file has been saved as hs_err_pid342.log.
# Please refer to the file for further information.

Recommended JVM Parameters for Master and ClientManager (v 6.1.0)

What are the recommened JVM parameters for a master and client manager running on the same Linux machine?
Current VM Specs:
OS: Suse Linux
Processor Count: 4
Physical Memory: 8GB
Using Java: jdk1.6.0_13
Current Master Params: JVMARGS=-Xms2048m -Xmx2048m
Current Client Manager Params: JVMARGS=-Xms2048m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=128m
Recommendations would be appreciated.
Thanks!
Grant Alexander

What are the recommened JVM parameters for a master and client manager running on the same Linux machine?
Current VM Specs:
OS: Suse Linux
Processor Count: 4
Physical Memory: 8GB
Using Java: jdk1.6.0_13
Current Master Params: JVMARGS=-Xms2048m -Xmx2048m
Current Client Manager Params: JVMARGS=-Xms2048m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=128m
Recommendations would be appreciated.
Thanks!
Grant Alexander

Recommended patches for solaris 10

I cant find the latest solaris 10 Recommended patches. I spending too much time looking for it.. without success
does any one can send me the link were to get it.. Thank-you

Hello,
Latest recommended patches are available through Oracle Support. If you have a valid account/support contract, you can login to http://support.oracle.com goto the "Patches" tab, and perform the following search:
Product: Solaris Operating System
Release: Solaris 10 Operating System
Description CONTAINS recommended
Remember to check the "Exclude superseded patches" to exclude the old ones.
HTH,
Marco

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

Difference between WinXp 1.3.1 JVM and Solaris 1.3.1 with JavaMail

When I send a mail within Windows through jvm1.3.1, the french special characters are correctly handled.
Inside a Sun Solaris, I must set the LANG=FR before executing to be able to get the right encoping.
But the application must work for almost 15 countries (same number of language) and I cannot change the LANG property within the .profile without harming the whole application.
Is there any parametrization in the javamail to set the character enconding before sending
Thanks

Nothing that would jump at you if you're new to the platform. The list of new features is here:
http://java.sun.com/j2se/1.4.2/docs/relnotes/features.html
Any book which talks about 1.2 is good enough, there were no fundamental language changes between 1.2 and 1.4 . I've never seen "Sams Teach Yourself Java2 in 21 Days, Second Edition" but I don't like the sound of the title. Bruce Eckel's "Thinking in Java" is usually recommended to beginners. It's available online in full.

Recommended JVM Version for ZfS 6.5 SP1 on NetWare 6 SP5 w/NCS

Quick question - what is the recommended version of the NetWare JVM to use
with ZfS 6.5 SP1? I'm running NW6SP5, ZfS65 with SP1 applied, and Tomcat
3.3. Right now I'm using JVM 1.4.2_6 and just wanted to verify there are no
known issues with JVM 1.4.2_6 playing well with ZfS 6.5 SP1. Running on on
a 2 node cluster.I plan to add ZfD 6.5 SP1 to the cluster soon - primarily
for HA inventory services. Thanks in advance for any input.

Ron,
Thanks for the general advice. That's what I thought, but sometimes we
all need a sanity check. Especially when you see java thread death
messages when the distributor starts up :-) Not due to the JVM.
> In General, use the JVM version that shipped at the same time as the
NetWare
> Service Pack you're using.
>
> For NetWare 6 this still gives you the choice between JVM 1.3.x and
1.4.x,
> my preference is the JVM 1.4.2 as it has better performance then the
1.3.x.
> The 1.4.2_6 your using is quit stable, no major issues known.
>
> Ron
>
>
> <[email protected]> wrote in message
> news:MaeMe.444$[email protected]..
> > Quick question - what is the recommended version of the NetWare JVM
to use
> > with ZfS 6.5 SP1? I'm running NW6SP5, ZfS65 with SP1 applied, and
Tomcat
> > 3.3. Right now I'm using JVM 1.4.2_6 and just wanted to verify there
are
> no
> > known issues with JVM 1.4.2_6 playing well with ZfS 6.5 SP1. Running
on on
> > a 2 node cluster.I plan to add ZfD 6.5 SP1 to the cluster soon -
primarily
> > for HA inventory services. Thanks in advance for any input.
>
>

Hardware recommendations for learning Solaris Cluster on Sparc (at home)

On a low budget, I'd like to put together a Solaris Cluster on Sparc (at home). At "work" in the next year we will be implementing a Solaris Cluster to run Tomcat and a custom CORBA server. (These apps will be migrated from very old hardware and VCS) The CORBA server is a Sparc binary, hence the need for Sparc. I'd like my home-office cluster to be similar in function to what I have at work. At work we have (2) T5120 Servers and a 2540 (2500-M2) Array waiting. From looking at the Solaris Cluster docs, it looks like you use a 2540 in a Direct-Connect configuration. We will be going to Solaris Cluster training eventually, but not soon. In the meantime, I'd like to keep/gain some skills/experience.
Potential (cheap) Home Cluster:
(2) SunFire V245 or (2) T1000 or (2) something_cheap
connected to
(1) Storedge D2 or (1) Storedge S1
My main desire, is for the interconnects and failover on this Home Cluster to behave the same way as the T5120s with the 2540 Array. Example, if I yank a HD (or replace) then I'd like it to give very similar messages to what I will face at work in the future. I'd like the creation of ZFS pools etc to work similarly. I'd like SCSI cards (HBAs or whatever) and cabling to be cheap.
Any recommendations on hardware> Servers? Arrays? SCSI Cards/cabling?
Thanks,
Scott

I settled on:
(2) Sunfire V210
Storedge 3120
Connected by VHDCI
All used equipment at a cheap price. Should be a great little testbed.

Launching jvm in solaris from java...

I have a problem launching jvm from java in solaris...
java.io.IOException: "/opt/XX/YY/jre/bin/java": not found
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
But when I give /opt/XX/YY/jre/bin/java from my console it's working fine...
what could be the problem ?? (I mean the path is correct..)
Message was edited by:
chaos_begins_here

When I try to System.exec() a program that doesn't exist, I get the following:
java.io.IOException: foo: not found
Note that foo (the program I tried to exec) is not in quotes. Check the strings you are passing to exec() to make sure there are no extra quotes. It's possible the difference in format is due to different java versions, but the point is to sanity check the strings you're passing.

What options do I have to patch the recommended patchset on Solaris 10 with a bunch of non-global zones?

With the standard patching process(installcluster), it takes a looong time since each zone needs veridated. Any option that I can apply the patchset to the global zone only, then later upgrade the non-global zones?
If possible, I'd like to use LU.

You can use LU but it will depend of your system config. There are instructions in the README of the patchset to install it on an alternate boot environment (previously created using lucreate).
If you plan to use LU, read the following docs first to avoid common issues:
Solaris Live Upgrade Software Patch Requirements(Doc ID 1004881.1)
List of currently unsupported Live Upgrade (LU) configurations (Doc ID 1396382.1)
You can also use Parallel Patching feature to improve performance :
https://blogs.oracle.com/patch/entry/zones_parallel_patching_feature_now
Solaris 10 10/09: Zones Parallel Patching to ReducePatching Time (System Administration Guide: Oracle Solaris Containers…
What you can't do is patch the global zone only and the non-global zones later (unless the zones are detached). It's a requirement that the global and non-global stay synchronize at all time (considering that they are sharing the same kernel).

Multiple JVMs on Solaris 10 (x64)

I just downloaded the new 1.6 JDK, but when I went to install it I became confused. /usr/java is a symbolic link to jdk/jdk1.5.0_11, which is itself a symbolic link to /usr/jdk/instances/jdk1.5.0. Then, to further muddy the waters, /usr/j2se is actually a JRE for Java 1.4.2_11!
So what's the consensus on configuration conventions? Should I put my new 1.6 JDK under /usr/jdk/instances then add a link to it in /usr/jdk? Is it safe to trash the 1.4 JRE and point /usr/j2se to my new 1.6 JRE? Does it seem odd to anyone else that the symlink to the JDK specifies a patch level, but the actual JDK directory doesn't?
I know I can put it anywhere and just point JAVA_HOME at it, but it looks like there's some kind of system already in place, and I'd just as soon conform to a standard if one actually exists.

Hi,
I hope this is not coming too late... I had a similar problem and just kind of figured it out.
remove the current symbolic link:
rm /usr/java
Create a new link to the new JDK installation:
ln -s /usr/jdk<version...> /usr/java
That should do it.
Cheers

Recommended JVM on Solaris 10

Similar Messages

Maybe you are looking for