[#JRA-2152] Error reporting of Oracle Text Field Size limitations

JIRA

Error reporting of Oracle Text Field Size limitations

Created: 08/Aug/03 09:12 AM Updated: 13/Apr/05 12:17 AM

Component/s:

Backend / Domain Model, Web interface

Affects Version/s:

2.3 Enterprise, 2.3 Pro

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

Sample.htm (2 kb)

Environment:

Oracle users

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-2441~~ NPE when creating new issue

~~JRA-2820~~ Enter more than 6000+ char's in the issue description field. It throws java exception during issue edit event.

~~JRA-3798~~ Import fails -Data too large exception

~~JRA-2994~~ Oracle import fails because text field greater than 4000 characters

~~JRA-2482~~ Lengthy comment validation during create new issue & add comment

~~JRA-3391~~ Funny Bounced message in the logs

~~JRA-4608~~ When adding comments over 300k, a 500 error is thrown

~~JRA-2444~~ bad error message with long descriptions

~~JRA-3745~~ java.lang.reflect.UndeclaredThrowableException

~~JRA-4490~~ bad error message

~~JRA-4011~~ More useful error message required

Reference

This issue relates to:

~~JRA-1273~~ Review database mappings for reserved words

This issue is related to:

~~JRA-3563~~ Description greater than 4k character throws an exception: java.lang.reflect.UndeclaredThrowableException

~~JRA-4180~~ Fix error handling when > 4000 character limit is encountered in Oracle

JRA-4361 Cannot store workflows of over 4000 characters in Oracle

Participants:	Anton Mazkovoi [Atlassian], Bostjan Dolenc, Holger Engels, Jeff Turner [Atlassian], Nick Minutello, Owen Fellows and Scott Farquhar [Atlassian]
Since last comment:	184 weeks, 1 day ago
Labels:

Description

« Hide

On Oracle, we have a size limitation for issue Description and Comment fields of 4000 characters.

So, if you add a description or a comment that is greater than that, you get an error:

Exception: com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:934)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1107)
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:366)
at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80)
at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:65)

The problem here is that there is no hint as to what caused the error. It would be better to be able to give an error:

"Your comment is too large. Consider creating an attachment."

Its practically impossible from the Entity Engine exception, to programmatically work out what happened (even the error message depends on what version of oracle)
The only other thing to do is to make it part of the Web Action validation - thereby forcing a limit on everyone.

This would actually be a good thing, because they might otherwise end up hitting this limitation when changing databases (as we did). Especially since HSQLDB in the stand-alone version doesnt have any limit....

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] - 09/Aug/03 12:50 AM

Now that the new ofbiz entity engine allows validators per-field, we can do this easily (and only for Oracle / other limited dbs)

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 12/Aug/03 09:55 PM

Need to contact OfBiz to see whether we can do it at the OfBiz level.

[ Permlink | « Hide ]

Bostjan Dolenc - 06/Oct/03 04:16 AM

Somewhat related rant: why aren't database exceptions logged in JIRA log? You know, those pesky ORA-XXXX messages on Oracle. All I get is this:
—
WARN [NoModule] org.ofbiz.core.entity.jdbc.SQLProcessor java.sql.SQLException: Connection was closed
—
This is less than usefull - I actually thought a few times that DB completed its part of action OK and that the exception in JIRA caused connection to close prematurely.

I suppose this is really an OFBiz issue, so I wouldn't mind somebody pointing me to their issue tracker/mail list.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 21/Oct/03 12:17 AM

FWIW, there is an XSLT stylesheet that can be run against JIRA's XML dump at:

http://www.atlassian.com/software/jira/docs/latest/etc/jira_checklengths.xsl

Instructions are provided in the file header. Output consists of URLs to problematic issues:

[jeff@localhost jeff]$ java org.apache.xalan.xslt.Process -IN /tmp/a.xml -XSL jira_checklengths.xsl -PARAM url
http://jira.atlassian.com

Issues with descriptions over 4000 chars:
-------------------------------------
http://jira.atlassian.com/secure/ViewIssue.jspa?key=ABC-100
http://jira.atlassian.com/secure/ViewIssue.jspa?key=RDVE-14
http://jira.atlassian.com/secure/ViewIssue.jspa?key=RDVE-64
http://jira.atlassian.com/secure/ViewIssue.jspa?key=RDVE-74
http://jira.atlassian.com/secure/ViewIssue.jspa?key=AVW-242
http://jira.atlassian.com/secure/ViewIssue.jspa?key=AVW-247
http://jira.atlassian.com/secure/ViewIssue.jspa?key=AVW-277

Issues with comments over 4000 chars:
-------------------------------------
http://jira.atlassian.com/secure/ViewIssue.jspa?key=ADVS-86#action_11267 (comment by john)

Long issue summaries can be truncated in the UI (I think - unless they end up in the revision history..), and comment bodies will need to be edited by hand in the XML.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 14/Mar/04 08:14 PM

According to ~~JRA-2994~~, the above XSLT does not correct change log entries (oldstring and newstring) that are > 4000 characters.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 15/Mar/04 08:31 PM

FWIW, here is how Hibernate has tackled the same problem:

http://www.hibernate.org/56.html

[ Permlink | « Hide ]

Owen Fellows - 25/Apr/04 05:46 AM

It would be worth investigating if we can actually retrieve the SQL error message. If we can retrieve this and re throw it atleast we would be able to do display the sql error.
e.g.

<error>
The following database error occured:
ORA-xxxx - Blah Blah Blah

Please contact your DBA from more details on the cause of this.
</error>

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 28/Oct/04 01:20 AM

We discussed this problem with the Ofbiz guys here:

http://lists.ofbiz.org/pipermail/dev/2004-September/006528.html

[ Permlink | « Hide ]

Holger Engels - 07/Dec/04 05:12 AM

Until there is a better solution, could you restrict the textarea's capacity to reflect the storable size?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 13/Jan/05 12:50 AM

This should be solved with the same solution described in ~~JRA-5297~~