Operating System - HP-UX
1832995 Members
2232 Online
110048 Solutions
New Discussion

Bug JAGae20385 fixed in Java SDK 1.2.2.14 appears in SDK 1.3.1.05

 
Mayadevi
New Member

Bug JAGae20385 fixed in Java SDK 1.2.2.14 appears in SDK 1.3.1.05

Problem details: According to HP the bug JAGae20385 is fixed Java version SDK 1.2.2.14 (JAGae20385 HP SR 8606256070 Infinite loop in readServerResponse()). Our version in of Java in HP 9000 shows 1.3.1.05. The bug still appears in the version 1.3.1.05 and is random.

Version : HP-UX B.11.00 U 9000/800 193901537
Java Version : "1.3.1.05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1.05-020425-12:07) Java HotSpot(TM) Server VM (build 1.3.1 1.3.1.05-JPSE_1.3.1.05_20020425 PA2.0, mixed mode)

Workaround for this problem? No : The only option is to restart the whole JVM.

Switch to SDK 1.3.1.10? : Took a look at the release notes between 1.3.1.05 and 1.3.1.10 and didn't find anything directly related to this issue.
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: Bug JAGae20385 fixed in Java SDK 1.2.2.14 appears in SDK 1.3.1.05

The latest version is a must for us. Also, there may be new patches in the patch section of http://www.hp.com/go/java

Its really important that they all be installed and properly configured.

I am not having this bug and using the later version to service a high volume Oracle environment.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Cheryl Griffin
Honored Contributor

Re: Bug JAGae20385 fixed in Java SDK 1.2.2.14 appears in SDK 1.3.1.05

I am not sure where you are getting your information but this JAG/SR has not been fixed in a general release of Java.
"Downtime is a Crime."
Mayadevi
New Member

Re: Bug JAGae20385 fixed in Java SDK 1.2.2.14 appears in SDK 1.3.1.05

This readServerResponse Bug fix information is listed only for 1.2.2.14, not for any 1.3.* versions. Have checked the patch information for all 1.3.* and couldn't find anything related to this bug.

For me this bug appears in 1.3.1.05, not convinced whether this has been fixed in any of 1.3.* versions? (Probably not documented). If so we would like to switch to that version.

SDK for Java 2 version 1.2.2.14 (November 2002)
SDK for Java 2 version 1.3.1.05 (Apr. 2002)