AppletTalk.com Forum Index AppletTalk.com
Java discussions newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

asynchronous exceptions

 
Post new topic   Reply to topic    AppletTalk.com Forum Index -> JVM, native methods and hardware
View previous topic :: View next topic  
Author Message
blair
Guest





PostPosted: Sun Dec 19, 2004 12:29 pm    Post subject: asynchronous exceptions Reply with quote



I've been reading about exceptions in the JVM spec and am confused
about what exceptions are asynchronous. Sec 2.16.4 states that
InternalError may be delivered asynchronously, but does not make this
claim for any other of the subclasses of VirtualMachineError. But sec
6.3 mentions that any subclass of VirtualMachineError may be thrown at
any time during the operation of the JVM. So are all subclasses of VME
asynchronous? And if not, what is the difference between InternalError
being raised asynchronously and OutOfMemoryError being raised at any
time?

Back to top
Artur Biesiadowski
Guest





PostPosted: Thu Jan 06, 2005 10:19 pm    Post subject: Re: asynchronous exceptions Reply with quote



blair wrote:
Quote:
I've been reading about exceptions in the JVM spec and am confused
about what exceptions are asynchronous. Sec 2.16.4 states that
InternalError may be delivered asynchronously, but does not make this
claim for any other of the subclasses of VirtualMachineError. But sec
6.3 mentions that any subclass of VirtualMachineError may be thrown at
any time during the operation of the JVM. So are all subclasses of VME
asynchronous? And if not, what is the difference between InternalError
being raised asynchronously and OutOfMemoryError being raised at any
time?


My understanding is that 'throw at any time' means throwing at any
moment if error happened at this very moment. For example, you can throw
OOME at any bytecode which allocates memory directly or indirectly - but
you have to throw it before next bytecode is executed. On the other
hand, asynchronous throw can happen at any point in the future, possibly
even in different thread, from place which triggered the error itself.

It is just my idea how to interpret that - I'm in no way expert on the
subject.

Artur

Back to top
Display posts from previous:   
Post new topic   Reply to topic    AppletTalk.com Forum Index -> JVM, native methods and hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.