Is anyone having issue with roadtest submissions? Having some SQL error message.

rscasny

Aside from the fact there appears to be a problem with submission, it may be a one off, it may be ongoing but worse than that, the error handler is giving away internal infrastructure and details that could be used to compromise the system

You may want to get your support guys on this ASAP (Fix the error handling and the submission problem)

Jordan, im sure well get this fixed asap, your issue is bad but the implications of error handler is worse... I am sure E14 will get both fixed asap.

Peter

Peter, I'll ask the support. But first I updated your RoadTest application. Try it again.

Randall

It was Jordan's Road test, not mine but i'm sure he will realise that.

Hi Randall,

I tried again to submit, looks like identical SQL error message.

Any suggestion you have would be much appreciated

PreparedStatementCallback; SQL [ INSERT INTO e14RoadTestApp ( roadTestAppID, containerID, containerType, userID, status, creationDate, modificationDate, title, description, roadTestID, fullName, email, address1, address2, language_code, city, province, postal, phone, fax, country, internalStatus, eeExperience, jobRole, comparableProducts, applicationUsage, projectTitle ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ); ]; Data truncation; nested exception is java.sql.DataTruncation: Data truncation

Data truncation,  Is it a really long submission?

Could try to isolate truncation issue by submitting review with single word in body, see if that works?

Thank you for the suggestions Andy and Frederick.

I played with it a bit further and managed to find the problem. I have now managed to submit my application. The issue was not in the word limit of the main submission, but the character limit of postal code field.

Problem was that I was allowing Chrome to autofill my address details. This shouldn't cause an issue in theory but I noticed that Chrome seems to be overfilling the postal code field (I cram my postal code and country here since there is no country field in the application).

Chrome autofilled 11 characters into this field, but I can see when I erase the postal code field and manually type it, the browser truncates my text at 10 characters. So this is where the truncation error was in that SQL error.

Thanks folks!

I submitted a computer ticket to figure out this problem.

Thanks for notifying me.

Randall

I'm here because someone submitted a computer ticket

I'm not even a little bit up to speed yet, I'm still getting my facts together. But jdlui - can you tell me which roadtest it is that you're applying to?

There are at least two bugs here, one is that we're presenting you the actual error, and the other is that you're getting the error at all

The first one is a doozy and entirely on me as the coder of that logic, I've got an untrapped error that I'm presenting to the user, and I'll get a ticket raised to get that fixed in the near future. Oops!

The second one is the one that is causing you the drama. The error in question is a database related error, and happens because you the system is trying to insert into a fixed width column, and the data you are inserting is wider than the fixed width of the column. If this error were being trapped, I'd have a lot more information as we automatically log the data that caused a data trunc error, but because somehow this error is slipping the net and not being trapped, none of that has happened.

So one of the fields you are entering is wider than is allowed on the database. The question is, is this one of the ones that you have entered, or is it one of the ones that I enter under the hood for our own internal use. I can't see the data you're trying to insert (because you've not inserted it), and I can't see any more information in the logs than what you've already given me.

jdlui - I suspect you won't want to publish your application here, so is there any chance you can email me a screenshot of you getting this error?