RE: change jvm settings (1.3.1 to 1.4.2) in websphere -- JAVA400-L

Subject: RE: change jvm settings (1.3.1 to 1.4.2) in websphere
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Date: Thu, 9 Feb 2006 07:30:28 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Hi Frances!  I hope the New Year has been good so far.

I was wondering why WebSphere required a specific JDK.  I can understand
there being a MINIMUM level for the JDK, but why would there be a maximum?
What features are you using that makes it impossible to, for example, run
WebSphere under Tiger?  It just seems to sort of go against the whole Java
message when I can't upgrade my application to the next version of the JDK.

Joe

> From: Frances Stewart
> 
> Each WAS version requires a specific JDK level which cannot be changed.
> WAS 5.0 = JDK 1.3.1
> WAS 5.1 = JDK 1.4.2
> WAS 6.0 = JDK 1.4.2.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: change jvm settings (1.3.1 to 1.4.2) in websphere , Ashish Kulkarni
RE: change jvm settings (1.3.1 to 1.4.2) in websphere , Frances Stewart

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.