Suppressing complete stack trace in getMessage()

How do I get the message (using getMessage() method on the trapped exception) from
a remotely thrown (inside of an ejb) exception. The getMessage returns the COMPLETE
stack dump and somewhere in the deep, mentions in the passing , a "nested exception".
I want this "nested exception"'s message. I have turned off the "Implement Stack
Traces" option in the debug screen of the server. What else do I need to do? What
am I doing wrong.
Thanks

Try posting in WebLogic Server forum:
WebLogic Server - General

Similar Messages

How to get the complete Stack-Trace ?

Hi,
I'm getting the following error on the screen.
oracle.jbo.DMLException: JBO-26041: Failed to post data to database during "Insert": SQL Statement " INSERT INTO OTA.OTA_QUESTIONS(QUESTION_ID,TEXT,ALLOW_HTML_FLAG,OBJECT_VERSION_NUMBER,BUSINESS_GROUP_ID,START_DATE_ACTIVE) VALUES (:1,:2,:3,:4,:5,:6)".
I want to get the complete stack-trace. I turned on the screen log, but still not getting the error-stack. Can anyone lemme know, how to get the complete error-stack ? This error is raised from a seeded page.
Thanks,
Guna.

This is a developer raised exception and not a standard expection(depends on a profile), that is why you cannot see the error stack.You have to put system.out.println, to debug.You get such errors when there is some fundamental mistake and not framework exception.
As the error says look into the query and see all bind variables are setting properly.
--Mukul

WLST, how do I suppress unwanted stack traces and make WLST less verbose?

Hi everyone,
I've just started out with WLST but have ended up somewhat confused. My script works as intended but is very verbose.
Suppose I want to log in:
try:
     connect(user, "wrong_password", url)
except WLSTException, err:
     print str(err)
     print "Run with option \"-h\" for help"The password is wrong so I get something like this printed out by me:
{noformat}
Error occured while performing connect : User: wm714, failed to be authenticated. Use dumpStack() to view the full stacktrace
{noformat}
But I also get a totally unwanted Java stack trace (before my message):
{noformat}This Exception occurred at Fri May 21 15:49:01 CEST 2010.
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: wm714, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:677)
{noformat}
I don't want to confuse the user with all that! I found this:
http://objectmix.com/weblogic/529822-wlst-exception-handling-unwanted-stack-trace.html
Which discusses WLS.commandExceptionHandler.setSilent(1) I'm running on WLS 10.3.0.0 and can execute that statement but it has no effect. I didn't even know about the WLS-object and I can find no documentation on commandExceptionHandler.
On the matter of verbosity, is there any way to get rid of stuff like:
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)I avoid using the "interactive" commands like cd and use stuff like getMBean("domainRuntime:/ServerRuntimes/" + appServer.getName()
+ "/JMSRuntime/" + appServer.getName() + ".jms/JMSServers") but I still get the clutter printed out.
Thanks!

Workaround:
wlstOut = tempfile.mktemp(suffix="_wlst.txt")
redirect(wlstOut, "false")
... do useful stuff
stopRedirect()
os.remove(wlstOut)I would have preffered to turn off the messages (yes I could try /dev/null) but this will do. A funny thing is that the stack trace I wrote about doesn't appear in the log file. Somehow "redirect" must have a nice side effect.
/Roger

Turning off server side stack trace in error message for weblogic81

Hi,
I am seeing server side stack trace in getMessage() method which is being stuffed
by application server. I am using weblogic 81. Could you please let me know how
to turn off that in getMessage() to return my only original message?
Thanks
Praveen

Did you solve this problem? I am facing this problem and don't seem to solve with
"Instrument Stack Traces" flag
"Franck" <[email protected]> wrote:
>
Hi there,
In order to manage my own exceptions in some EJB, i have developped some
classes
extending Exception.
Now i would like to display proper messages to the final user, based
on the messages
defined in my exception classes.
Using standard try/catch, i can easily get reference to the exception
that can
occur during EJB execution.
The problem is that my message (myException.getMessage) is followed by
the extra
long message generated by the Server and starting with "Start server
side stack
trace:".
For exemple :
com.xx.ejb.DamageHistoryException: Can't find the price for this object
(objId=7569,
sizeCode=LI, colorCode=2)
Start server side stack trace:
com.xx.ejb.DamageHistoryException: Can't find the price for this object
(objId=7569,
sizeCode=LI, colorCode=2)
at com.xx.ObjectAccess.getObjectPrice(Unknown Source)
at com.xx.ejb.ObjectBusinessService.getObjectPrice(Unknown Source)
<....>
about 20 lines here !!
<....>
Any idea about how to avoid the extra message ??
Thanx in advance
Franck

No stack trace outpu on eclipse-jboss project

Good moring. I am facing a problem and after a few days of googling ia haven't found a solution so I am posting it here.
The problem is this.
We have a web portal built on jboss, seam, ejb3, jsf etc. The previous developer sent me an eclipse project folder, so I could work on the project. When I set it up, I have to change some classpath references (different jboss and jre version) and thats all.
But when i run the project and something wrong happens, there is no stack trace so I can locate the problem and fix it. I have built some other test projects and there is no problem.
So the question is: Is there any specific adjustment that could suppress the stack trace output? And how could I trim it?
Thanks.

I would advise against reverting to very old versions just because you can't get the new versions to work. Try to read the installation instructions and manuals of the new versions and try to get those to work.

Suppressing server side stack trace

Hi All,
Was wondering if anybody knows how to prevent WebLogic 6.1 from
generating a server side stack trace whenever an exception is thrown?
Following is an example:
Start server side stack trace:
com.ffusion.alert.interfaces.AEException: The value "313z" for the audit
history length property is invalid.
     at com.ffusion.alert.engine.AEConfigManager.if(AEConfigManager.java)
     at com.ffusion.alert.engine.AEConfigManager.if(AEConfigManager.java)
     at com.ffusion.alert.engine.AlertEngine.a(AlertEngine.java)
     at com.ffusion.alert.admin.AlertAdmin.setEngineProperties(AlertAdmin.java)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean.setEngineProperties(AEAlertAdminBean.java)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean_n5fc0q_EOImpl.setEngineProperties(AEAlertAdminBean_n5fc0q_EOImpl.java:267)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean_n5fc0q_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Thanks,
Van

There is a property in the ServerConfig:
InstrumentStackTraceEnabled - Determines whether exception messages include the server-side stack trace.
Van Tu <[email protected]> wrote:
Hi All,
Was wondering if anybody knows how to prevent WebLogic 6.1 from
generating a server side stack trace whenever an exception is thrown?
Following is an example:
Start server side stack trace:
com.ffusion.alert.interfaces.AEException: The value "313z" for the audit
history length property is invalid.
     at com.ffusion.alert.engine.AEConfigManager.if(AEConfigManager.java)
     at com.ffusion.alert.engine.AEConfigManager.if(AEConfigManager.java)
     at com.ffusion.alert.engine.AlertEngine.a(AlertEngine.java)
     at com.ffusion.alert.admin.AlertAdmin.setEngineProperties(AlertAdmin.java)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean.setEngineProperties(AEAlertAdminBean.java)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean_n5fc0q_EOImpl.setEngineProperties(AEAlertAdminBean_n5fc0q_EOImpl.java:267)
     at
com.ffusion.alert.adminEJB.AEAlertAdminBean_n5fc0q_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Thanks,
Van--
Dimitri

Oracle 11g: stack trace misses first line

Hi,
I am working with an Oracle 11g database and trying to make a Java file work. I get an error when I try to run it (using SQL developer), and when I output the stack trace it is not complete.
My stack trace is:
java.lang.NoSuchMethodError
at oracle.security.xmlsec.wss.WSSecurity.sign(WSSecurity.java:1169)
at Discimus.generateSoapMessage(DISCIMUS:176)
I have a library issue somewhere, but I can't figure out where it is if I can't get a full stack trace. The sign method is large, so I need to know where the error is thrown.
Any ideas?
Thanks in advance!

Hi,
I am working with an Oracle 11g database and trying to make a Java file work. I get an error when I try to run it (using SQL developer), and when I output the stack trace it is not complete.
My stack trace is:
java.lang.NoSuchMethodError
at oracle.security.xmlsec.wss.WSSecurity.sign(WSSecurity.java:1169)
at Discimus.generateSoapMessage(DISCIMUS:176)
I have a library issue somewhere, but I can't figure out where it is if I can't get a full stack trace. The sign method is large, so I need to know where the error is thrown.
Any ideas?
Thanks in advance!

SEVERE: SAAJ0009: How do I stop stack trace being printed to standard out

Anyone know why the following stack trace is printed when connection.call(message, endpoint); throws an exception? It happens when the server or web service is offline
using jdb I can see that the next statement to execute is the return("FAIL .... but the stack trace is already printed by then. How do I tell it not to print the stack trace. I've tried adding a catch for java.io.IOException but the compiler says it's not thrown. Any ideas
SOAPMessage response = null;
try{
response = connection.call(message, endpoint); <= blows up here "myClient.auth myClient.java:333)
connection.close();
catch (SOAPException ex){
return("FAIL Error sending authentication soap message " + ex.getMessage());
java.io.IOException
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:593)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:29)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPCon
ection.java:151)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:12)
at myClient.auth(myClient.java:333)
at myClient.send(myClient.java:93)
at myClient.main(myClient.java:550)
Caused by: java.net.ProtocolException: Server redirected too many times (20)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:27)
... 6 more
May 18, 2004 12:23:05 PM com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
SEVERE: SAAJ0009: Message send failed
java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send
failed
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:12)
at myClient.authenticate(myClient.java:333)
at myClient.send(myClient.java:93)
at myClient.main(myClient.java:550)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:30)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConection.java:151)
... 5 more
Caused by: java.io.IOException
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:593)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:29)
... 6 more
Caused by: java.net.ProtocolException: Server redirected too many times (20)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:27)
... 6 more

For anyone who's interested, apparently I'm not the only one with this problem, others have asked the developrs to remove printStackTrace() from the SAAJ code. For now we have to redirect standard error or ignore

JDeveloper stack trace - what's happened to JDev overnight?

Hi,
It's one of those days. JDeveloper worked fine when I left work last night, load it up this morning and I get this stack trace:
java.lang.StackOverflowError
     at java.util.HashMap.get(HashMap.java:320)
     at oracle.ide.net.URLFileSystem.findHelper(URLFileSystem.java:126)
     at oracle.ide.net.URLFileSystem.findHelper(URLFileSystem.java:163)
     at oracle.ide.net.URLFileSystem.openInputStream(URLFileSystem.java:1164)
     at oracle.ide.net.IdeURLConnection.getInputStream(IdeURLConnection.java:44)
     at java.net.URL.openStream(URL.java:1007)
     at oracle.ide.net.URLFileSystemHelper.openInputStream(URLFileSystemHelper.java:993)
     at oracle.ide.net.URLFileSystem.openInputStream(URLFileSystem.java:1164)
     at oracle.ide.net.IdeURLConnection.getInputStream(IdeURLConnection.java:44)
     at java.net.URL.openStream(URL.java:1007)
(The last 4 lines repeat about 30 times).
Then, when I opened a file in JDev, the IDE just disappeared on me. I loaded it again, no stack trace, run my app and get some weir error in the JDev log about not loading persistance, and my app has no database connection. I restart my computer, load JDeveloper, stack trace again. Oh man this is frustrating, why do these things happen when it was working perfectly fine when I shut my computer down last night? Grrr.
I'll feel sorry for myself for about another 30 mins, then I'll reinstall, just thought I'd send the stack trace.
R

I'm not sure this is the problem you are having, but when I get a StackOverflowError on start up, I follow this procedure (while JDeveloper is not running):
- Open <JDeveloper>\jdev\system\oracle.ide.<version>\preferences.xml
- Remove all but one Item tags from the lruFiles tag
- Save the file
- Run JDeveloper
As I say, it could be a completely different problem, but whether it works or not could you reply here? Thanks.
DominionSpy

Unwanted stack trace in weblogic.log for thrown JSP Exceptions

We are throwing a JSP exception within a custom tag when data validation
          errors occur; the errorPage for the JSP page is then invoked to show the
          appropriate errors. However, in the weblogic.log, a stack trace is shown
          indicating the exception (example below). We do not want this stack track
          shown unless there is a real "error" in our system vs. invoking the
          errorPage to show "application" errors. Is there any way to supress this,
          as we are not explicitly causing this to happen. It appears to be a
          weblogic feature. This causes us problems in finding true system errors
          that might be occurring due to these non-problems showing up in the
          weblogic.log.
          Thanks for the help.
          John Bauer
          Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception raised
          on '/test/test.jsp'
          javax.servlet.ServletException: runtime failure in custom tag 'testtag'
          at jsp_servlet._test._test._jspService(_test.java:89)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :124)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:
          60)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:
          07)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager
          java:251)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)


The design of the data entry pages is such that the error page is the same
          page as the data entry page, and a validation JSP tag validates the data and
          if it finds a problem, it will set some variables and throw a JSP exception
          to redisplay the page. Unfortunately, we are forced to live with this
          design. Are you aware of any mechanism to suppress the automatic logging of
          thrown JSP exceptions in the weblogic log?
          Thanks,
          JDB
          Cameron Purdy <[email protected]> wrote in message
          news:[email protected]...
          > Exception handling for custom tags is very poorly handled right now. For
          > one thing, WL hides the actual exception.
          >
          > However, the way that you are doing this seems very odd. The error page
          is
          > for server errors, not user typos.
          >
          > Peace,
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          >
          > "John Bauer" <[email protected]> wrote in message
          > news:[email protected]...
          > > We are throwing a JSP exception within a custom tag when data validation
          > > errors occur; the errorPage for the JSP page is then invoked to show the
          > > appropriate errors. However, in the weblogic.log, a stack trace is
          shown
          > > indicating the exception (example below). We do not want this stack
          track
          > > shown unless there is a real "error" in our system vs. invoking the
          > > errorPage to show "application" errors. Is there any way to supress
          this,
          > > as we are not explicitly causing this to happen. It appears to be a
          > > weblogic feature. This causes us problems in finding true system errors
          > > that might be occurring due to these non-problems showing up in the
          > > weblogic.log.
          > >
          > > Thanks for the help.
          > > John Bauer
          > >
          > > Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception
          raised
          > > on '/test/test.jsp'
          > > javax.servlet.ServletException: runtime failure in custom tag 'testtag'
          > > at jsp_servlet._test._test._jspService(_test.java:89)
          > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > > :124)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > l.java:
          > > 60)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > l.java:
          > > 07)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          > > Manager
          > > java:251)
          > > at
          > >
          >
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          > > at
          > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
          Compiled
          > > Code)
          > >
          > >
          >
          >

Application Stack trace visible to user

Hello All,
Is there any way in which i can disable the visibility of application stack trace to users. Here i am not talking about the Webdynpro Java application. I can be any portal application or an KM iview.
The reason i have to do this is, at times when there is an error in an application or an ivew the stack trace is completely visible to the user and it can be used in an wrong and manipulative manner. So instead of the stack trace can any other message be shown to the user? and how can that be acheived?
Thank in advance
Jeet Tibrewala

Hi Jeet,
Check the below link which mentions how to acheive this.
http://wiki.sdn.sap.com/wiki/display/EP/CustomizingErrorMessagesinPortal
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/18398
Cheers
Deb

Stack traces mysteriously disappear from Exceptions

I'm using Sun Java System Application Server Platform Edition 8.0.0_01 on Solaris 8 on a Sun-Fire machine. The problem is that some exceptions thrown in session beans make it to the presentation tier without their stack traces.
Here is a session bean method:
* @ejb.interface-method
public void generateException() throws SbankInternalException
try { System.exit(0); }
catch (Exception e) {
throw new SbankInternalException("Unexpected exception", e);
SbankInternalException is a simple wrapper on Exception:
public class SbankInternalException
extends Exception
public SbankInternalException() {}
public SbankInternalException(String message)
super(message);
public SbankInternalException(String message, Throwable cause)
super(message, cause);
public SbankInternalException(Throwable cause)
super(cause);
Here is the code that triggers the problem:
<h3>Exception testing:</h3>
<%
try {
maintenanceServices.generateException();
} catch (Exception E) {
Throwable e = (Throwable) E;
%>
<h3>Caught exception <%=E%></h3>
<pre>
<%
do {
%>CLASS: <%=e.getClass().getName()%>
MESSAGE: <%=e.getMessage()%><br><%
StackTraceElement se[] = e.getStackTrace();
if (se.length == 0) {
%> EMPTY STACK TRACE<br><br><%
} else {
for (int i = 0; i < se.length; i++) {
%> <%=se.toString()%><br><%
%> <br><br><%
e = e.getCause();
} while (e != null);
%>
</pre>
And here is what I get:
<h3>Exception testing:</h3>
     <h3>Caught exception sbank.services.SbankInternalException: Unexpected exception</h3>
     <pre>
CLASS: sbank.services.SbankInternalException
MESSAGE: Unexpected exception<br>
EMPTY STACK TRACE<br><br>
CLASS: java.security.AccessControlException
MESSAGE: access denied (java.lang.RuntimePermission exitVM)<br>
EMPTY STACK TRACE<br><br>
     </pre>
Server log does not contain any message about that.
This only seems to be the problem for exceptions declared in bean interface. When a RuntimeException is thrown in the bean, then it is properly logged to the server log (with strack trace), and I catch a nice RemoteException in the presentation layer, as expected (also with stack trace, though the top frame is somewhere in the demarshalling code of application server guts, so it's not very useful).
Is it my error, or a bug?
regards
Marcin

I'm not complaining that the exceptions declared to be thrown from session bean interface are not logged. AFAIR that is OK with the EJB spec.
I'm complaining that the stack traces are stripped from the exception on its way from the session bean to the client (presentation layer in this case).
I know that I could log the error in the session bean, that is just a workaround. I still would like to know why my exceptions are being broken? After all the whole point of exceptions is that they can be generated in one place, and investigated/displayed in another.
The only explanation I can think of that there is some silly optimization, that omits stack frames when serializing the exceptions, so that they propagate faster. If it is so, can I disable that?
Marcin

Stack trace error need help

Hi guys im getting the following error when im running this on resin:
What does it mean how do i solve it?
CODE:
//Start database connection
                              try
                         conn = DriverManager.getConnection(url,username,password);
                         st2 = conn.createStatement();
                              insert=columntitle+" "+value;
                              //out.println(insert);
                              st2.executeQuery(insert);
                         conn.close();
                    catch (SQLException e)
                                   System.out.println("Error1: "+e.getMessage());
                                   //out.println("<h3><font color=\"white\">"+e.getMessage()+"</font></h3>");
                                   //Error=1;
                              //finish database connection
ERROR:
Error1: An I/O error occured while reading from backend - Exception: java.net.So
cketException: Connection reset by peer: JVM_recv in socket input stream read
Stack Trace:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input str
eam read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:90)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
at org.postgresql.PG_Stream.ReceiveChar(PG_Stream.java:181)
at org.postgresql.Connection.openConnection(Connection.java:160)
at org.postgresql.Driver.connect(Driver.java:122)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at FYP.ReadingCSV4.doPost(ReadingCSV4.java:311)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet
.java:82)
at com.caucho.server.http.Invocation.service(Invocation.java:288)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:1
32)
at com.caucho.server.http.ServletServer.serviceTop(ServletServer.java:93
7)
at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:213
at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:
158)
at com.caucho.server.TcpConnection.run(TcpConnection.java:140)
at java.lang.Thread.run(Thread.java:484)
End of Stack Trace
thanks tzaf

sorry error is coming from:
//check whether table already exists
          try
               conn = DriverManager.getConnection(url,username,password);
     // Gets the database metadata
          DatabaseMetaData dbmd = conn.getMetaData();
     // Specify the type of object; in this case we want tables
     String[] types = {"TABLE"};
     ResultSet resultSet = dbmd.getTables(null, null, "%", types);
     // Get the table names
     while (resultSet.next())
     // Get the table name
     String tableName = resultSet.getString(3);
     //used for testing
     //out.println(tableName+"<br>");
               if (tableName.equals("studentsele304a"))
                    tableFound++;
                    carryon=1;
                    out.println("table found<br>");
               else
                    //tableFound=1;
                    out.println("table not found<br>");
     catch (SQLException e)
          out.println("error4: "+e.getMessage());
     }

How to get stack trace of an exception

Hi,
I want to get whole stack trace and show it in a new Frame instead of showing on command line.
when I say,
e.getMessage();
it gives just first line, not rest of the part.
Can anybody help me with that?
Thanks in advance.

StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
String stackTrace = sw.toString();

Startflightrecording: any way to get methods deeper stack traces?(dept 64)

I'm using jrcmd PID start_flightrecording in order to get some useful samplings, but it seems the stack traces are limited to depth 64 (i.e. in the Hot Methods's Predecessors view of JRockit Mission Control 4.1.0 I see only the last 64 frames) hence I miss important info about calling dynamics. I'm using jrockit-jdk1.6.0_37-R28.2.5-4.1.0. I've seen the [R27 version|http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionXX.html] supported a -XX:Tracedepth argument, but I don't see it on [R28 documentation|http://docs.oracle.com/cd/E15289_01/doc.40/e15062/toc.htm].
Any idea?
Kind regards
Davide
Edited by: user970531 on Apr 15, 2013 8:39 AM

I'm using jrcmd PID start_flightrecording in order to get some useful samplings, but it seems the stack traces are limited to depth 64 (i.e. in the Hot Methods's Predecessors view of JRockit Mission Control 4.1.0 I see only the last 64 frames) hence I miss important info about calling dynamics. I'm using jrockit-jdk1.6.0_37-R28.2.5-4.1.0. I've seen the [R27 version|http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionXX.html] supported a -XX:Tracedepth argument, but I don't see it on [R28 documentation|http://docs.oracle.com/cd/E15289_01/doc.40/e15062/toc.htm].
Any idea?
Kind regards
Davide
Edited by: user970531 on Apr 15, 2013 8:39 AM

Suppressing complete stack trace in getMessage()

Similar Messages

Maybe you are looking for