Solaris 2.6 and Volume Manager 3.0 - After DST Patch
I've never had any issues with Volume Manager on our E4500 running Solaris 2.6 until I had to apply this DST patch last week. When I try to run the GUI for Volume Manager I am getting the following errors:
java.lang.IllegalMonitorStateException: current thread not owner
at sun.rmi.transport.Reaper.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)
and then a stream of: err = 22
What did this DST patch do to me?
Message was edited by:
IRag
[500 byte] By [
IRaga] at [2007-11-26 21:44:46]
# 1
I didn't realize there was a DST patch for 2.6.
I have no idea what it does or does not do.
Most of the DST patches involve changes to /usr/share/lib/zoneinfo. Changes there aren't likely to affect Java at all.
You might want to back out the patch and just modify /usr/share/lib/zoneinfo files by hand.
Or was this the JRE patch for the java installation to be DST aware? I've not had any problem with tzupdater on various JREs installed by Veritas.
--
Darren
# 2
We had to purchase the patch for 2.6 from SUN since its no longer supported.
PATCHINFOVERSION="1.0"
PATCHID=105210-53
PATCH_CORRECTS='BaseOS.SolarisArchiveLibs-5.6 BaseOS.SolarisCore-5.6'
PATCH_ARCH='sparc'
PATCH_OS='SunOS'
PATCH_OSRELEASE='5.6'
PATCH_PROPERTIES='rebootafter clientusr clientroot'
PATCH_REQUIRES="105181-22"
PATCH_OBSOLETES="106044-03"
IRaga at 2007-7-10 3:32:52 >
