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();

Similar Messages

How to get stack contents in an Exception stack trace

Hi
Currenty when an exception in thrown in a java class copiled with debug option we get line numbers in the stacktrace but we do not get the state of the stack.
How can I the details of the stack (i.e. values of all the local variables visible in that thread) ?
As information is available when we debug the application so I presume this information should be available but I do not know how to access it.
Obviously I would need to override this in my custom Exception as this feature is not provided by JAVA currently
I analyzed that the fillStacktrace() method is the most likely candidate but it has a native implementation in class Throwable hence was not able to get the details.
This would be a nice feature to have in future Java release

Without any debugger agent running [a JVMDI or a JVM TI agent (since 5.0)], you won't be able to get values of local variables etc. When you debug a Java program "jdwp" agent is running in the JVM. With JVM running without any debugger agent, you can just get stacktrace with line numbers (provided you compiled java program with -g).

Can anyone help how to print stack trace messages using log4j?

Can anyone help how to print stack trace messages using log4j?

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
<appender name="STDOUT" class="org.apache.log4j.ConsoleAppender">
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %m%n"/>
</layout>
</appender>
<appender name="DEBUG" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-debug.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="1000KB"/>
<param name="MaxBackupIndex" value="5"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %m%n"/>
</layout>
<filter class="org.apache.log4j.varia.LevelRangeFilter">
<param name="LevelMin" value="DEBUG" />
<param name="LevelMax" value="DEBUG" />
</filter>
</appender>
<appender name="INFO" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-info.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="1000KB"/>
<param name="MaxBackupIndex" value="5"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %m%n"/>
</layout>
<filter class="org.apache.log4j.varia.LevelRangeFilter">
<param name="LevelMin" value="INFO" />
<param name="LevelMax" value="INFO" />
</filter>
</appender>
<appender name="WARN" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-warn.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="1000KB"/>
<param name="MaxBackupIndex" value="5"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %m%n"/>
</layout>
<filter class="org.apache.log4j.varia.LevelRangeFilter">
<param name="LevelMin" value="WARN" />
<param name="LevelMax" value="WARN" />
</filter>
</appender>
<appender name="ERROR" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-error.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="1000KB"/>
<param name="MaxBackupIndex" value="5"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %m%n"/>
</layout>
<filter class="org.apache.log4j.varia.LevelRangeFilter">
<param name="LevelMin" value="ERROR" />
<param name="LevelMax" value="ERROR" />
</filter>
</appender>
<root>
<priority value="debug"/>
<appender-ref ref="DEBUG"/>
<appender-ref ref="INFO"/>
<appender-ref ref="WARN"/>
<appender-ref ref="ERROR"/>
</root>
</log4j:configuration>
I ve written like this
and to print stack trace I used
log.error(Throwable(e))
but does nt display printstacktrace how to do it

Display of stack trace of uncaught exception

Hello,
on the mini SAP Web AS 6.40 SP11 that I have installed on my local Windows system, the server provides stack trace information for uncaught exceptions. First, a screen is shown saying that the request could not be processed and that the Administrator should be contacted. After pressing on a link "Get Details ...", the stack trace of the error is displayed. Everything is fine, so far.
On the contrary, when I run on a server SAP Web AS SP12 on a UNIX system (SPARC, Sun OS 5.9), only the screen saying that the request could not be processed is shown, but no "Get Details ..." link appears.
Does anybody know what I need to do to enable the display of detailed stack traces also on the Unix machine?
Any help is appreciated!
Regards, Nick.

Is the flow of code to the point where exception occurs:
1) Data saved in Db
2) Navigated back
3)Navigated to another page
4) Method ListMenu() is called(as soon as navigated to page in step 3) to retrieve the saved data from db & exception occurs.
Can you paste here the definition of ListMenu(), also does the exception occurs as soon as db is accessed inside this method or else.
http://developer.nokia.com/community/wiki/Using_Crypto%2B%2B_library_with_Windows_Phone_8

How to disable stack traces in SOAP faults of webservices?

Hi everybody
My problem are the stack traces that WLS automatically puts into SOAP faults if an exception in the webservice code occurs. For security reasons I would like to stop WLS from doing so. But how can I configure this aspect in WLS? In Glassfish there is a system property to enable or disable such a behaviour: com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace. Axis2 knows a similar property, too. What about WLS?
Thanks in advance for any help!
Marc

Thanks for your input. Using a message handler I could filter the created SOAP faults and remove any stack traces, but I'm rather looking for a configuration option or system property that manages the initial creation of SOAP faults, i.e. that lets you turn off stack traces in SOAP faults. I expect such a property to exist in WLS because I know of such properties in Glassfish/Metro and Axis2. Does anybody know of such an option or property in WLS?

How to get short text of a exception thrown by abap rfc

Hi buddy,
I use jco to communicate with backend, an abap function module will raise a exception. I can catch that exception,
The example exception is:
<b>Exception</b>     <b>Short text</b>
Test                   This is exception test.
e.getKey()
will return TEST.
Does any know how to get that short text "This is exception test." from the exception I caught?
Thanks
Austin

Hi Austin,
There are 2 methods to raise errors in function modules.
1) Using the raise Exception statement
2) Using a return structure like BAPIRET to populate the message details like type, error number, error text etc.
Generally method 1 is not recommended for any RFC/BAPI function modules because it causes the calling program to crash if the function raises an exception. Method 2 is the recommended way and is used in all standard BAPI's. ABAP programmers are advised to code RFC's as per method 2, but some times it would not be possible as the function would already be used and could be barred from changes.
But whatever method the RFC uses to raise an exception, web dynpro can handle it in the following ways,
Method 1) If the RFC raises an exception using RAISE EXCEPTION,
Dont catch Exception class in your code, instead do the following,
catch (WDDynamicRFCExecuteException e) {
                  wdComponentAPI.getMessageManager().reportException(
                        e.getLocalizedMessage(),
                        true);
Method 2) If the function returns the errors in the standard bapi return structure, you can do the following
            IWDMessageManager MsgMgr = wdComponentAPI.getMessageManager();
            for (int i = 0; i < ReturnNode.size(); i++) {
                  if (Types.indexOf("S") != -1
                        && ReturnNode.getElementAt(i).getAttributeAsText("Type").equals(
                              "S"))
                        MsgMgr.reportSuccess(
                              ReturnNode.getElementAt(i).getAttributeAsText("Message"));
                  if (Types.indexOf("W") != -1
                        && ReturnNode.getElementAt(i).getAttributeAsText("Type").equals(
                              "W"))
                        MsgMgr.reportWarning(
                              ReturnNode.getElementAt(i).getAttributeAsText("Message"));
                  if (Types.indexOf("E") != -1
                        && ReturnNode.getElementAt(i).getAttributeAsText("Type").equals(
                              "E"))
                        MsgMgr.reportWarning(
                              ReturnNode.getElementAt(i).getAttributeAsText("Message"));

Is it possible to obtain line numbers in the stack trace of an exception

Is it possible for e.StackTrace in the following code to contain line numbers?
try
catch(Exception e)
LogStackTrace("Stack Trace:" + e.StackTrace);}
Hong

Thank you for your response.
The linked article is for Windows Phone and it points out "it's not possible to deploy the PDB alongside the EXE/DLL". Is this also the case for Windows Store app, or Windows Store app is different and it can be deployed with a .pdb file as you
pointed out?
The Windows Store app package is like the following:
My App_1.3.0.5_AnyCPU.appxupload
It is a zip file that contains the following two files:
My App_1.3.0.5_AnyCPU.appx
My App_1.3.0.5_AnyCPU.appxsym
Hong

Get stack trace into a string with CLDC

I want to get the stack trace of an application into a string, so that I may print the stack trace elsewhere.
CLDC api does not have a printStackTrace(PrintWriter pw) or printStackTrace(PrintStream ps) which is present in j2se.
Could you please suggest another way in CLDC to obtain the stack trace into a string.

Set System.err to your designated PrintStream and then call Throwable.printStackTrace().
This will do what you desire.
rob,

How reliable is stack trace?

Hi there,
I am debugging a core on solaris 10. the shared libraries are compiled and linked without -g0 and majority of the symbols are removed using a linker map. Now when I loaded dbx and do a "where", the stack trace only shows
[1] 0xfcb01510(0x0, 0xfebe09d8, 0xfe30b500, 0x433a70, 0x23c428, 0x1), at 0xfcb01510
[2] 0xfcb014a8(0x3937450, 0x0, 0x0, 0x18e7, 0xfccbc4a8, 0x185004a4), at 0xfcb014a8
[3] 0xfdd7b1a4(0x433a70, 0x3ec720, 0xfe30b500, 0x433a70, 0xfe31f1e8, 0xfdd7adc4), at 0xfdd7b1a4
[4] 0xfdd66890(0x433a70, 0x3ec720, 0x8, 0xff1436f8, 0xfc06edb4, 0x23c428), at 0xfdd66890
[5] 0xfc1375fc(0x3ec708, 0x3, 0x3ec720, 0xfc3fddd8, 0x837568, 0x2c0468), at 0xfc1375fc
[6] 0xfc12f3c0(0x3ec708, 0x3ec860, 0x3ec860, 0x5df89a8, 0x0, 0xa770408), at 0xfc12f3c0
[7] 0xfc1d9cfc(0x3ec714, 0x3ec860, 0x8c, 0xb8, 0xfc40002c, 0xfc174638), at 0xfc1d9cfc
[8] 0xfc1d8680(0x0, 0x17, 0x3ec860, 0x2c0558, 0x5, 0x3ec714), at 0xfc1d8680
[9] 0xfc1d8998(0x3ec8a8, 0x17, 0x3ec860, 0x2c0558, 0x3, 0x5), at 0xfc1d8998
[10] 0xfc1339c4(0x3ec708, 0x17, 0x3ec860, 0xff141b0c, 0x5, 0x2c0020), at 0xfc1339c4
[11] 0xfc1341bc(0x3ec708, 0x17, 0x3ec860, 0xa770408, 0xffffff, 0xfc3fd610), at 0xfc1341bc
[12] 0xfc133878(0x3ec708, 0x12, 0x3ec860, 0xfc3f5c60, 0x0, 0xfea56158), at 0xfc133878
[13] 0xfc134b08(0xfa87bd9c, 0xfffad938, 0x0, 0x3ec708, 0xfc40017c, 0xfc3f5c60), at 0xfc134b08
[14] 0xfea7b168(0x23c428, 0x2692c0, 0x23c4c8, 0x3ec998, 0xfeb9bc61, 0xfea56158), at 0xfea7b168
[15] 0xfea80c30(0x2692c0, 0x2692c0, 0xfefecbc0, 0xfd6e2800, 0x4eaa0, 0x0), at 0xfea80c30
[16] os_thread::runThreadFunction(0x21d550, 0xfa87c000, 0x0, 0x0, 0xff141b0c, 0x1), at 0xff11309c
I am not surprised because .so does not have too many symbols to begin with. I used the manual technique to map each frame to a shared library:
1. take address of the function in each frame,
2. compare against base address of a shared library from output of "proc -map" (it shows where each so is loaded into the process).
3. see 1. falls into the range of which library displayed in 2.
4. substract base address from 1. (used for later)
After that, I went ahead to locate function, what I did was pull the exact source code and compile them without applying the linker map (still without -g0). I hope this newly compiled so is the same as the production ones in terms of function offsets:
1. nm the_faulty_so_recompiled.so
2. sorted functions in nm output by its offset,
3. compare 4. in previous step against these offsets.
but I find the result is sometimes not reliable because there is no way some of the function is called by previous frame, it is just impossible if you look at the source code.
Can someone tell me if I am doing something terribly wrong here?
BTW, parameters for each functions show in the "where" stack frames are not the same as I expected, occasionally there is something like 0x1 or 0x17, what are those?
Thanks.

but the core is not reproducible, -g0 version is not particularly helpful in that case. What I am hoping is the following:
1. the release version is compiled without -g0 and with a linker map to eliminate 99% of symbols.
2. recompiled version is with exact same source code and without -g0 and without linker map.
same compiler and everything else. I would expect the function offset is the same in those 2 cases. correct? If not, what have I done wrong?
I am ok with just knowing which function is at fault so without -g0 is ok for me. But why I am seeing stack trace still does not make sense? What is wrong with my calculation of function offset?
Is there some kind of remapping the loaded address of library going on here so I have to manually calculate some offset to get the real function offset?
Thanks.

How to get Error Trace on Linux

Hi All,
I am trying to run my JAR ( A simple JAR that uses JCO) on Linux SUSE 10, when I run it, it just gives me the following error, there is no trace.
How can I get the full trace. Please help.
This is what im doing and the next line is the error message.
dsadm@mach1:/opt/IBM/media/SAP/sapjco> java -jar ditest1.jar
The java class is not found: com/sap/mw/jco/JCO$Exception
dsadm@mach1:/opt/IBM/media/SAP/sapjco>
This is the (ONLY) class file in the JAR, I exported my JAVA project from NWDS as a JAR file.
package com.test;
* Conn.java
* Property of SAP AG, Walldorf
* (c) Copyright SAP AG, Walldorf, 2000-2003.
* All rights reserved.
import com.sap.mw.jco.*;
public class Conn {
// The MySAP.com system we gonna be using
static final String SID = "R3";
// The repository we will be using
com.sap.mw.jco.IRepository repository;
public Conn()
     System.out.println("**** DI11 *****");
         this.buildConnection();
       System.out.println("**** DI 22*****");
public void buildConnection(){
     try {
               System.out.println("**** DI2 *****");
            // Add a connection pool to the specified system
            //    The pool will be saved in the pool list to be used
            //    from other threads by JCO.getClient(SID).
            //    The pool must be explicitely removed by JCO.removeClientPool(SID)
          com.sap.mw.jco.JCO.addClientPool( SID,         // Alias for this pool
                                    10,          // Max. number of connections
                                    "040",       // SAP client
                                    "testuser",   // userid
                                    "pass", // password
                                    "EN",        // language
                                    "ipaddress",// host name
                                    "xx" );
            // Create a new repository
            //    The repository caches the function and structure definitions
            //    to be used for all calls to the system SID. The creation of
            //    redundant instances cause performance and memory waste.
            repository = com.sap.mw.jco.JCO.createRepository("MYRepository", SID);
          catch (Exception ex) {
            System.out.println("Caught an exception: \n" + ex.getMessage());
// Retrieves and prints information about the remote system
public void systemInfo()
    try {
      // Get a function template from the repository
      IFunctionTemplate ftemplate = repository.getFunctionTemplate("RFC_SYSTEM_INFO");
      // if the function definition was found in backend system
      if(ftemplate != null) {
        // Create a function from the template
        JCO.Function function = ftemplate.getFunction();
        // Get a client from the pool
        JCO.Client client = JCO.getClient(SID);
        // We can call 'RFC_SYSTEM_INFO' directly since it does not need any input parameters
        client.execute(function);
        // The export parameter 'RFCSI_EXPORT' contains a structure of type 'RFCSI'
        JCO.Structure s = function.getExportParameterList().getStructure("RFCSI_EXPORT");
        // Use enumeration to loop over all fields of the structure
        System.out.println("System info for " + SID + ":\n" +
        for (JCO.FieldIterator e = s.fields(); e.hasMoreElements(); ) {
          JCO.Field field = e.nextField();
          System.out.println(field.getName() + ":\t" + field.getString());
        }//for
        System.out.println("\n\n");
        // Release the client into the pool
        JCO.releaseClient(client);
      else {
         System.out.println("Function RFC_SYSTEM_INFO not found in backend system.");
     catch (JCO.Exception ex) {
       System.out.println("Caught an exception: \n" + ex);
// Retrieves and displays a sales order list
public void salesOrders()
     JCO.Client client = null;
    try {
      // Get a function template from the repository
      IFunctionTemplate ftemplate = repository.getFunctionTemplate("BAPI_SALESORDER_GETLIST");
      // if the function definition was found in backend system
      if(ftemplate != null) {
          // Create a function from the template
          JCO.Function function = ftemplate.getFunction();
          // Get a client from the pool
          client = JCO.getClient(SID);
          // Fill in input parameters
          JCO.ParameterList input = function.getImportParameterList();
          input.setValue("0000001200", "CUSTOMER_NUMBER"   );
          input.setValue(      "1000", "SALES_ORGANIZATION");
          input.setValue(         "0", "TRANSACTION_GROUP" );
          // Call the remote system
          client.execute(function);
          // Print return message
          JCO.Structure ret = function.getExportParameterList().getStructure("RETURN");
          System.out.println("BAPI_SALES_ORDER_GETLIST RETURN: " + ret.getString("MESSAGE"));
          // Get table containing the orders
          JCO.Table sales_orders = function.getTableParameterList().getTable("SALES_ORDERS");
          // Print results
          if (sales_orders.getNumRows() > 0) {
            // Loop over all rows
            do {
              System.out.println("-----------------------------------------");
              // Loop over all columns in the current row
              for (JCO.FieldIterator e = sales_orders.fields(); e.hasMoreElements(); ) {
                 JCO.Field field = e.nextField();
                 System.out.println(field.getName() + ":\t" + field.getString());
              }//for
            } while(sales_orders.nextRow());
          else {
            System.out.println("No results found");
          }//if
      else {
         System.out.println("Function BAPI_SALESORDER_GETLIST not found in backend system.");
       }//if
    catch (Exception ex) {
      System.out.println("Caught an exception: \n" + ex);
    finally {
       // Release the client to the pool
      JCO.releaseClient(client);
protected void cleanUp() {
    JCO.removeClientPool(SID);
public static void main(String[] argv)
    Conn e = new Conn();
e.systemInfo();
e.salesOrders();
e.cleanUp();
This is standard SAP code, please help on how can I get the complete error trace on linux.

You do not require RFCSDK to build a jaava application that uses JCO on LINUX.

How to get stack.xml for EHP2 Netweaver BI 7.0 Upgrade without SolMan?

Hi Experts,
We are planning for BI 7.0 EHP2 upgrade from BW 3.5
SAP_ABA u2013 6.40 - 24
SAP_BASIS u2013 6.40 - 24
PI_BASIS - 2006-1-640 - 8
SAP_BW u2013 3.50 - 24
To Target version of NW BI 7.0 EHP2,
In SAP Support Package Stacks, Itu2019s not showing SPS (SAP Support Package Stacks) for NW BI 7.0 EHP2 but itu2019s showing NW BI 7.0 EHP1, Please advise, how to download SPS for NW BI 7.0 EHP2 with stack.xml file.
Thanks & Regards
Raja

Hi Experts
After getting the stack.xml file, we started the process of upgrading our BW 3.5 system to BW 7.0 EHP2. We
have downloaded all media list and EHPI tool. The EHPI tool latest
version SAPehpi_111-10005800.SAR has been used and we are getting the
following error.
Release '640' is not supported by this tool.
Request you to please suggest the solution.
Regards,
RajaMurugesan,PMP

How to get the trace file name for current running application?

Hi, I want to know if it is possible to get the file name directly for current running application instance which is launched by javaws.
There is a property "deployment.user.logdir" tells the log directory, it would be great if a file name property
is available. something like "instance.trace.file".
Our application wants it because we would like our client send use the application log by clicking a "send error"
button, the codes finds the trace file and compress it and send it by using a smtp server.
In 1.5, we can do it by using a shell program.

I found other asked it before, but I tried to set both properties, but neither works. my sun JRE version :java version "1.6.0_04"
<property
name="deployment.javaws.traceFileName"
value="abcfefsfdsf"/>
<property
name="deployment.javapi.trace.filename"
value="235235235"/>
But it always write to one trace file with name lik javaws63645.trace

Get the entire stack trace of exception ?

Hi!
If the JVM prints this :
Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (FOO.BAR) violated
at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9040)
at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:517)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242)
... 73 more
then how do I get the missing 73 lines ?

Why would you want to? they are shorthand indicating that they were thrown from the same method: From the API Docs
Note the presence of lines containing the characters "...".
These lines indicate that the remainder of the stack trace for this exception matches the indicated number of frames from the
bottom of the stack trace of the exception that was caused by this exception (the "enclosing" exception).
This shorthand can greatly reduce the length of the output in the common case where a wrapped exception is thrown from same method
as the "causative exception" is caught. ~Tim
Message was edited by:
SomeoneElse
Message was edited by:
SomeoneElse

How to get text of exception in my program, exception is defined in FM?

I have written a function module where i have defined a couple of exceptions. If an error occurrs i raise the exception.
My issue is, in my calling program, i call the function module i have created and once the exception occurrs i need to get the text associated with that exception.
I dont know how to get the text of the exception. The short text is defined in exception tab of the function module.
Any help will be appreciated.
Thanks

hi check this example..
RECEIVE RESULTS FROM FUNCTION 'ZMARD_DATA'
     IMPORTING
       E_RECORDS = g_records
     EXCEPTIONS
       no_data                            = 1
       open_dataset_no_authority          = 2
       convt_codepage_init                = 3
       dataset_too_many_files             = 4
       unknown_file_opening_error         = 5
       dataset_write_error                = 6
       dataset_not_open                   = 7
       dataset_cant_close                 = 8
       OTHERS                             = 9.
CASE sy-subrc.
    WHEN 0.
      error_rec-msg_text     = 'Data Loaded'.
      g_total_rec = g_total_rec + g_records.
    WHEN 1.
      error_rec-msg_text     = c_no_data.
    WHEN 2.
      error_rec-msg_text     = 'OPEN_DATASET_NO_AUTHORITY'.
    WHEN 3.
      error_rec-msg_text     = 'CONVT_CODEPAGE_INIT'.
    WHEN 4.
      error_rec-msg_text     = 'DATASET_TOO_MANY_FILES'.
    WHEN 5.
      error_rec-msg_text     = 'UNKNOWN_FILE_OPENING_ERROR'.
    WHEN 6.
      error_rec-msg_text     = 'DATASET_WRITE_ERROR'.
    WHEN 7.
      error_rec-msg_text     = 'DATASET_NOT_OPEN'.
    WHEN 8.
      error_rec-msg_text     = 'DATASET_CANT_CLOSE'.
    WHEN 9.
      error_rec-msg_text     =
              'Unknown error calling FM : ZMIO_GET_MARD_DATA'.
ENDCASE.

N unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

some one can help me please
i have no idea what i must to do.
an unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

The Exception Handler gave all the info that you need. No need to print the whole stack trace.
The exception handler says
Exception Details: java.lang.IllegalArgumentException
TABLE1.NAME
Look in the session bean (assuming that is where your underlying rowset is). Look in the _init() method for statements similar to the following:
personRowSet.setCommand("SELECT * FROM TRAVEL.PERSON");
personRowSet.setTableName("PERSON");
What do you have?

How to get stack trace of an exception

Similar Messages

Maybe you are looking for