Yes, we throw UndeclaredThrowableException whenever a non-Exception shows up in an invocation stack as our interceptor signature allows for Exceptions, not Throwables or Errors. Search in our codebase for UndeclaredThrowableException and you'll see where this happens.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sebastian Hauer Sent: Wednesday, January 28, 2004 10:59 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] OOM wrapped in UndeclaredThrowable Hi Scott, > Its simply a wrapping of the exception resulting from a reflected call > that is not a subclass of java.lang.Exception. That is what I thought but if that would be the case wouldn't it be wrapped inside a InvocationTargetException? I than assumed it could maybe be caused by a dynamic proxy throwing this exception. Yet in case of a java.lang.Error it would actually not get wrapped in a UndeclaredThrowableException according to javadoc and my tests. > Its possible that this is an exception marshalled back to a client and > that the OOM is occuring on the server. Maybe a naïve question but, is there code in JBoss that would explicitly throw an UndeclaredThrowableException and stuff a "marshalled" exception inside it? Regards, Sebastian ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
