Bugs item #565279, was opened at 2002-06-06 14:11
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=565279&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Rejected
Priority: 5
Submitted By: Marius Kotsbak (mkotsbak)
Assigned to: Scott M Stark (starksm)
Summary: null instead of stacktrace!!!!

Initial Comment:
When a runtimeexception (nullpointer,
arrayindexoutofbound etc) happens inside a bean method,
a serverexception is displayed, but it does NOT display
the stacktrace, only ex.getMessage(), which is often
null. This gives no clue of where the error really is.
Example:

----------------------
java.rmi.ServerException: RemoteException occurred in
server thread; nested exception is:
        java.rmi.ServerException: null
Embedded Exception
null; nested exception is:
        javax.ejb.EJBException: null
Embedded Exception
null
-------------------------

ex.printstacktrace is needed!

Check out my patch #562036
(http://sourceforge.net/tracker/index.php?func=detail&aid=562036&group_id=22866&atid=376687),
which does that. Don't know any problems applying this
(i haven't had any problem myself, other than I often
forget to apply it -> so please include it in cvs)

This bug is really annoying, I get this exception quite
often because of nullpointers.

Marius K
Boostcom.no

----------------------------------------------------------------------

>Comment By: Marius Kotsbak (mkotsbak)
Date: 2002-06-14 14:13

Message:
Logged In: YES 
user_id=366650

Do you have a reason for not having that as the default config? I cat't see 
that it slows down jboss when there are no errors, and the extra memory 
requirement isn't significant..

I have heard many on jboss-user that disagrees with you, and it is very 
hard to track down bugs when you only get ServerException : null.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2002-06-14 08:17

Message:
Logged In: YES 
user_id=175228

We are not going to dump out application errors by default. If you want 
to enable debugging of exceptions set the trace priority for the 
org.jboss.invocation.jrmp.server.JRMPInvoker category.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=565279&group_id=22866

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to