• Type: Bug
• Resolution: Tracked Elsewhere
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 7.5.0-EAP01
• Component/s: Troubleshooting and Support Tools (ATST)
• Labels:

  • SQLServer
  • database
  • healthcheck

[JRASERVER-66190] Database truncation error when inserting certain translated messages

Bugfix Automation Bot made changes - 28/Mar/2019 12:24 AM

Minimum Version

New: 7.05

Owen made changes - 16/Oct/2018 12:51 AM

Workflow	Original: JAC Bug Workflow v2 [ 2849146 ]	New: JAC Bug Workflow v3 [ 2921438 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Tom Davies made changes - 05/Oct/2018 4:23 AM

Resolution		New: Tracked Elsewhere [ 15 ]
Status	Original: Needs Triage [ 10030 ]	New: Resolved [ 5 ]

Collapse comment: Tom Davies added a comment - 05/Oct/2018 4:23 AM

Tom Davies added a comment - 05/Oct/2018 4:23 AM

This is tracked as https://ecosystem.atlassian.net/browse/ATST-919

Expand comment: Tom Davies added a comment - 05/Oct/2018 4:23 AM

Tom Davies added a comment - 05/Oct/2018 4:23 AM This is tracked as https://ecosystem.atlassian.net/browse/ATST-919

Dave Norton made changes - 05/Oct/2018 3:32 AM

Description

Original: h5. Issue Summary * A description entered into the dbo.AO_2F1435_HEALTH_CHECK_STATUS table exceeds the default Description column size. The problem happens for certain languages. Current confirmed languages: # Francais # Russian h5. Steps to Reproduce * Trigger health check error with the following message {code} Vérifie le nombre maximum de processus (threads) que le compte d'utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d'exploitation et s'il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM). {code} * Alternatively, directly insert the following into DB {code} insert into dbo.AO_2F1435_HEALTH_CHECK_STATUS (STATUS_NAME,DESCRIPTION) VALUES ('test3','Vérifie le nombre maximum de processus (threads) que le compte d''utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d''exploitation et s''il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM).'); {code}  h5. Expected Behavior * JIRA is able to insert the health check error into DB.   h5. Actual Behavior * We receive the following failed error: {code}com.microsoft.sqlserver.jdbc.SQLServerException: Les données de chaîne ou binaires seront tronquées. at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:94) at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects.create(TenantAwareActiveObjects.java:266) ... 3 filtered ... Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Les données de chaîne ou binaires seront tronquées. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258){code} h5. Cause * Error message translated to certain languages exceeds the default column size.

New: h3. Summary When a health check fails, the translated Description and Failure Reason strings are inserted into the table {{AO_2F1435_HEALTH_CHECK_STATUS}}. In some languages, the translated string can exceed the default column size. This has been confirmed for the following languages: # French # Russian h3. Steps to Reproduce Trigger health check error with the following message {code} Vérifie le nombre maximum de processus (threads) que le compte d'utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d'exploitation et s'il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM). {code} Alternatively, directly insert the following into DB {code} insert into dbo.AO_2F1435_HEALTH_CHECK_STATUS (STATUS_NAME,DESCRIPTION) VALUES ('test3','Vérifie le nombre maximum de processus (threads) que le compte d''utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d''exploitation et s''il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM).'); {code}  h3. Expected Behavior JIRA is able to insert the health check error into DB.   h3. Actual Behavior The insert will fail - and the error message will vary by database type. h3.Workaround There is no valid workaround at this time. While it would be possible to alter the database column type (so it can accomodate a larger string) this is not the recommended approach. In Active Objects Tables, the database schema is more abstracted than traditional application tables - making adjustments directly to the schema inadvisable. If you do make changes, ensure you've got a full database backup; and that changes are tested before applying to production.

Dave C made changes - 04/Oct/2018 7:59 AM

Component/s		New: System Administration - Troubleshooting and Support Tools (ATST) [ 36920 ]
Component/s	Original: System Administration - Statuses [ 43597 ]

Owen made changes - 25/Sep/2018 4:27 AM

Symptom Severity

Original: Minor [ 14432 ]

New: Severity 3 - Minor [ 15832 ]

Owen made changes - 25/Sep/2018 12:44 AM

Workflow	Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2592701 ]	New: JAC Bug Workflow v2 [ 2849146 ]
Status	Original: Open [ 1 ]	New: Needs Triage [ 10030 ]

Kit Tin Mak (Inactive) made changes - 06/Sep/2018 2:25 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 385662 ]

Collapse comment: Dominique Jean-Prost added a comment - 06/Apr/2018 10:53 AM

Dominique Jean-Prost added a comment - 06/Apr/2018 10:53 AM

I had to reapply the manual database change after upgrading to the last Jira version this morning. Will this issue be soon be fixed ?

Expand comment: Dominique Jean-Prost added a comment - 06/Apr/2018 10:53 AM

Dominique Jean-Prost added a comment - 06/Apr/2018 10:53 AM I had to reapply the manual database change after upgrading to the last Jira version this morning. Will this issue be soon be fixed ?

Load more older events