JDK-4222760 : Set JPI Java runtime via HTML applet parameters
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.1.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_2.6,windows_nt
  • CPU: generic,x86,sparc
  • Submitted: 1999-03-22
  • Updated: 2000-10-18
  • Resolved: 2000-08-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.1_01 pr3Fixed
Related Reports
Duplicate :  
Relates :  
Description

Name: gsC80088			Date: 03/22/99


Due to the large size of our applet (3 MB jar), JPI doesn't execute
very stable unless runtime settings are set to something like -ms8m -mx64m.
Customers are unlikely to have these settings, it would be nice if
applet parameters could be specified to set the runtime environment.
(Review ID: 55698) 
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: firefly-pr3 FIXED IN: firefly-pr3 INTEGRATED IN: firefly-pr3
14-06-2004

WORK AROUND Name: gsC80088 Date: 03/22/99 User needs to open the JPI console and set the runtime parameters. The user needs to be told to do this before attempting to execute our applet. ======================================================================
11-06-2004

EVALUATION This requires multiple-JVM support in Java Plug-in. stanley.ho@Eng 2000-02-18 The problem will be fixed in Ladybird. The maximum heap size will be re-adjusted according to the machine configuration. There is no need to pass parameters to the VM to adjust the heap size anymore. stanley.ho@Eng 2000-08-04
04-08-2000