| ||||
JDK 1.4 will not show me full exception traces ...just sent this RFE to Sun bugs parade ... version 1.4 changed implementation of Throwable.printStackTrace to print chained exception however currently it may print truncated stack trace for chained exceptions and it is not acceptable for several classes of apllications like programming with RMI or EJB instead it should be an optional feature disabled by default! here is an exampe that shows that information provided by printStackTrace is almost useless as important stack trace details of remote exception were truncated after first two lines! Exception in thread "main" java.lang.reflect.UndeclaredThrowableException at $Proxy0.requestMessages(Unknown Source) at SimpleMessageMonitor.main(SimpleMessageMonitor.java:60) Caused by: soaprmi.RemoteException: IO Exception; nested exception is: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read at soaprmi.soaprpc.HttpHandler.invokeTransport(HttpHandler.java:141) at soaprmi.soaprpc.SoapDynamicStub.invoke(SoapDynamicStub.java:120) ... 2 more created tue nov 5 2002 10:30pm cst [2002/11/5 22:30 CST] permalink |
This blog is about: Find more
about
Blogroll:
Projects::
RSS
Filter Entries: |
Disclaimer: personal opinions and observations that may or may not be taken seriously, or even based on shared reality and generally are very unreliable and personal and snapshots of volatile writer mind ...
NOTE: THIS PAGE IS UNDER CONSTANT DEVELOPEMENT