Thanks for all the replies.  

Yes, I was referring to clashing Windows PC Java versions, with a
homegrown, or rather custom written code from a vendor for an in-house
project, needing one level, and this beautiful performance tool needing
a different level.  I appreciate the Firefox idea, it seems it would be
too far outside the current corporate box.

There have been lots of attempts to make this work by the PC folks, the
most promising seems to be me signing onto the server and running my
analysis there.  I'm sure the authorizations to do that will eventually
filter back to me.  :-)  

Loads of fun.  Our outsourcer here spent a lot of time coming up with a
great process to do before and after measurements of performance for
applications, systems software, and vendor software installs and major
changes.  Great idea after the last big project left us with a third
party database that tripled CPU use for its applications.

I hope the various mainframe projects don't need me to signoff on the
performance hit aspect anytime soon.  Short of sitting down at one of
their PCs running their images I'm not likely to be able to do that for
now.

Thanks again,
Peter
LA, CA, USA
 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Timothy Sipples
Sent: Saturday, November 19, 2005 6:12 AM
To: [email protected]
Subject: Re: Performance tools and JAVA

I assume you're talking about a Windows PC's Java.

It's an issue, Java applet "clashes."  (Also sometimes happens with
Internet Explorer itself because it's at least very difficult to run two
IEs on the same system.  Firefox doesn't seem to have that restriction.)
I know IBM solved it in Host On-Demand in the past couple versions by
adding the functionality to our applets to let them choose which
installed JVM to use.  (The Administrator can configure that.)  If the
newer applet could add comparable function to their code you'd be all
set.  (I believe many applet vendors are doing just that.)

In the meantime I can think of a workaround.  There's the old separate
browser trick.  For example, put Firefox on the system, then configure
the newer JVM to only provide plug-in support for that browser.  Or, if
the newer applet supports Java Web Start, then you don't even need a
separate browser.

- - - - -
Timothy F. Sipples

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to