First I want to say I've been a happy java developer for years. I'm not here to bash java. :)
However, I am concerned about the amount of time it takes to load a browser based applet (version 1.5.04).
Here is a quick example: on a PIII system (yes a slow pc) it takes on average 48 seconds to load the applet (not the browser) the first time after a reboot, if we then close the browser and start it again (without rebooting the PC) and try to load the same applet it takes on average 15 seconds.
Now I realize that the JVM library code is being cached by windows but doesn't this seem like a show stopper? Approximately 33 seconds to load the JVM?
I have people from sales and marketing complaining back to me that the load times are unacceptable longer and the only thing that has changed is moving from 1.4.2 to 1.5.4!
Should I be looking into tuning the client jvm via -X options? Is this a known issue?
Here is the jsp plugin used to load the applet we tested :
<jsp:plugin type="applet"
code="com.mycompany.hm.callq.client.reports.CallQSummaryApplet.class"
codebase="/Monitor"
name="Stats" align="middle"
height="100%"
width="100%"
jreversion="1.5"
nspluginurl="https://www.java.com/en/download/manual.jsp"
iepluginurl="https://java.sun.com/update/1.5.0/jinstall-1_5_0_04-windows-i586.cab#Version=1,5,0,40"
archive="monitorClient.jar,HXMSCommon.jar,Filters.jar,Actions.jar,jcommon-0.9.5.jar,jfreechart-0.9.20.jar">
<jsp:params>
<jsp:param name="image" value="images/LoadingLogo.gif"/>
<jsp:param name="boxbgcolor" value="#FFFFFF"/>
<jsp:param name="swing.defaultlaf" value="com.sun.java.swing.plaf.windows.WindowsLookAndFeel" />
</jsp:params>
<jsp:fallback>
<p>Unable to load applet! Please load the java plugin at <a href="https://www.java.com/en/download/windows_automatic.jsp">Load Java Plugin</a></p>
</jsp:fallback>
</jsp:plugin>
You'll notice that we disabled the 1.5 loading graphic, with a very small and simple gif.
I appreciate any and all comments ;)
-Dennis