So is it possible for our VM support an option by which our customer can customize the policy while the VM still supply a default policy, for example, assuming the native heap limit as that of the java heap?
On 2/9/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote:
On 2/8/07, Robin Garner <[EMAIL PROTECTED]> wrote: > > Tim Ellison wrote: > > Rana Dasgupta wrote: > >> On 2/5/07, Tim Ellison <[EMAIL PROTECTED]> wrote: > > >>> I don't think that we need to expand the scope of the problem to do > >>> all types of resource accounting in the JVM or in an underlying > >>> platform layer. I don't see the spec providing any basic guidance in > >>> this area, it falls in the category of failsafe JVM's which is an > >>> interesting area, but IMHO beyond scope at this point. My suggestion > >>> is that we treat this as a specific nio api implementation problem > >>> for which we can think of adding some VM/GC support if it helps. > >>> > >> We may have to disagree here then, I think we should indeed be > >> considering a general solution for detecting early when these Java > >> 'handle' objects are collectable -- then we can apply it to direct > >> buffers or other handle types. > > >My point was that by adding a single GC -> VM interface function, all > >types of native resources could be addressed in a simple extensible way. > >The subsequent policy and mechanism decisions then become an ongoing > >design process for the VM and classlib native implementers, but once > >this interface function is added, GC can support freeing of native > >resources by whatever mechanisms the VM chooses to implement. I don't understand very well how the JVM can define policies on its platform/OS resource usage when it may be hosted by a server which wants to define such policies itself. In other words, say the JVM is running an RDBMS managed stored procedure. Should it be making assumptions about how much native heap to use etc. when the hosting RDBMS may have negotiated such policies itself and may be choosing to invoke one or more instances of the JVM?
-- Leo Li China Software Development Lab, IBM
