Changing the JVM in WebSphere itself would have a higher success rate than with VAJ. However, this is not necessarily a good idea, and IBM would advise against it (unless the version is noted in their support grid).
There are some versions of WebSphere that get a little too friendly with the JVM. The specific that comes to mind was when we used an earlier version of Host On Demand. Since the IBM JDK 1.1.8 didn't have ThreadLocal, IBM's developers were using some system-level calls to pool connections by thread id (thus the multi-page in-flight HOD transactions turned out to be a bad idea). I believe I read that Sun has made VM independence a requirement for J2EE certification. I'm not entirely sure on this, or when it became a requirement. However, this may have made newer versions of WebSphere a little more stable under successive VM versions. Phillip. --- "Conway. Fintan (IT Solutions)" <[EMAIL PROTECTED]> wrote: > Hi, > > Can the JVM in Websphere (not WSAD) be changed, or is that fixed > too? > > Thanks, > > Fintan ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
