Runtime eror in IPC JSP PAGE

Question

Hi
We are using CRM5.0 and AP7.00. We are getting error while displaying
the JSP page sometimes.
Let me give u feedback on the reason.
We have a V-table Say TAB1 with 3 characteristic in it. This V-table is
used in 2 different Models(2 Kmats). KMAT1 has CHAR1 and CHAR2 in the
Class and KMAT2 has CHAR1,CHAR2 and CHAR3 in the Class.
We are creating 2 Procedures PR0_KMAT1 for KMAT1 and PR0_KMAT2 for
KMAT2.
In the Procedure PR0_KMAT1 for KMAT1 we are using the Table TAB1 with
only CHAR1 and CHAR2 while in case of Procedure PR0_KMAT2 for KMAT2 we
are using all the 3 chacteristics CHAR1,CHAR2, and CHAR3.
The error is coming only in the first KMAT1. Is it coming due to using
a V-Table having a characteristic CHAR3 which is not present in the
Class of KMAT1.
My understanding about AP7.00 was that the error will only come if u
are using a Characteristic in a Procedure but that Characteristic is
not present in the Class.
I tried this in a Model but it did not give me an error. Which was
surprising.
Till now we have always maintained all the cstics in the class.if they
ae present in the V-Table.
But as we are going forward we have V-tables which are commonly shared
and don't have cstics present in the Class.
So my question is do we need to have the cstic in the Class if its
present in the V_table even though we are not using it in the Procedure
for that Model.
My understanding was all cstic should be in the class if they are
present in the V_table even if we are not using them in any Model.Is
this the reason why we are sometimes getting an error on the runtime in
JSP.
Incase of ECC i know we need not have the cstic Present in the Class
and it will also not give any error.
Can u please clarify this point.
Amit Bhan

Answer 1

Ay ay ay!! Ok I goofed up my own code. Others might find it helpful to lean from my pain today. Please follow the link at http://bugs.mysql.com/bug.php?id=13289 . There are other posts in the Java forums here on the same problem if I would pay closer attention ;-). I was using executeUpdate(sql); with my parameterized query when I should have been using executeUpdate(); Making this switch solved the problem for me. Here is the complete method that works for your purusal :-)
private void logToolException(ToolExceptions toolException)
Connection connection = null;
String sql = "";
try
connection = ConnectionModerator.getConnection();
Login login = toolException.getLogin();
sql = "INSERT INTO TOOL_ERROR_LOGS (" +
"BUSINESS_ID, " +
"TEAM_ID, " +
"PERSON_ID, " +
"TOOL_NAME, " +
"VERSION, " +
"CLASS_NAME, " +
"METHOD_NAME, " +
"STACK_TRACE, " +
"CREATION_DATE)" +
" VALUES (" +
"?, " +
"?, " +
"?, " +
"?, " +
"?, " +
"?, " +
"?, " +
"?, " +
"NOW())";
PreparedStatement statement = connection.prepareStatement(sql);
statement.setInt(1, login.getBusinessId().intValue());
statement.setInt(2, login.getTeamId().intValue());
statement.setInt(3, login.getPersonId().intValue());
statement.setString(4, toolException.getToolName());
statement.setString(5, toolException.getVersion());
statement.setString(6, toolException.getClassName());
statement.setString(7, toolException.getMethodSignature());
statement.setString(8, toolException.getExceptionStr());
statement.executeUpdate();
catch(Exception e)
//TODO Handle this exception better.
this.getServletContext().log("Using query: " + sql);
String message = "Exception!: ";
this.getServletContext().log(message, e);
finally
try
ConnectionModerator.closeConnection(connection);
catch(Exception e1)
//TODO Handle this exception better.
String message = "Exception!: ";
this.getServletContext().log(message, e1);
-Daniel