[#JRA-5635] Workflows over 64k truncated in MySQL

JIRA

Workflows over 64k truncated in MySQL

Created: 11/Jan/05 09:12 PM Updated: 30/Jul/06 07:37 PM

Component/s:

Backend / Domain Model

Affects Version/s:

3.0 Standard Beta, 3.0 Professional Beta, 3.0 Enterprise Beta, 3.0, 3.0.1, 3.0.2, 3.0.3

Fix Version/s:

3.1

Time Tracking:

Not Specified

Environment:

MySQL

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-5842~~ Workflow definition limited to 64kb!

~~JRA-6377~~ XML Backup/Restore, workflow truncation

Participants:	Jeff Turner [Atlassian] and Mark Chaimungkalanont [Atlassian]
Since last comment:	3 years, 27 weeks, 4 days ago
Resolution Date:	08/Feb/05 11:04 PM
Labels:

Description

« Hide

When editing particularly large workflows (eg. 15 steps, over 40 transitions), JIRA may hit MySQL's 64k limit on the size of TEXT fields. When this happens, MySQL silently truncates the data from the last edit. Trying to edit the workflow will result in an error, and the workflow will not properly display in the 'View Workflows' page. An error like the following will appear in the logs:

2005-01-12 13:07:14,979 ERROR [atlassian.jira.workflow.OSWorkflowManager] Could not get workflow called: New Development Life Cycle workflow: com.opensymphony.workflow.FactoryException: Error in workflow descriptor: New Development Life Cycle workflow: root cause: XML document structures must start and end within the same entity. (line:1280 col:24)
com.opensymphony.workflow.FactoryException: Error in workflow descriptor: New Development Life Cycle workflow: root cause: XML document structures must start and end within the same entity. (line:1280 col:24)
at com.atlassian.jira.workflow.JiraWorkflowFactory.loadJiraWorkflow(JiraWorkflowFactory.java:186)
at com.atlassian.jira.workflow.JiraWorkflowFactory.getWorkflow(JiraWorkflowFactory.java:88)
at com.opensymphony.workflow.config.DefaultConfiguration.getWorkflow(DefaultConfiguration.java:76)
at com.atlassian.jira.workflow.OSWorkflowManager.getWorkflow(OSWorkflowManager.java:152)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 12/Jan/05 01:33 AM

In MySQL, the type can can be changed from 'text' to 'mediumtext' as
follows:

mysql> desc jiraworkflows;
----------------------------------------------+

Field

Type

Null

Key

Default

Extra

----------------------------------------------+

ID	decimal(18,0)		PRI	0
workflowname	varchar(255)	YES		NULL
creatorname	varchar(255)	YES		NULL
DESCRIPTOR	text	YES		NULL
ISLOCKED	varchar(60)	YES		NULL

----------------------------------------------+
5 rows in set (0.00 sec)

mysql> alter table jiraworkflows change DESCRIPTOR DESCRIPTOR MEDIUMTEXT;
Query OK, 2 rows affected (0.00 sec)
Records: 2 Duplicates: 0 Warnings: 0

mysql> desc jiraworkflows;
----------------------------------------------+

Field

Type

Null

Key

Default

Extra

----------------------------------------------+

ID	decimal(18,0)		PRI	0
workflowname	varchar(255)	YES		NULL
creatorname	varchar(255)	YES		NULL
DESCRIPTOR	mediumtext	YES		NULL
ISLOCKED	varchar(60)	YES		NULL

----------------------------------------------+

You will see a warning on startup subsequently, but this can be ignored.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 08/Feb/05 11:04 PM

Entity definitions are now fixed. MySQL users will still need to run the SQL update task

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 08/Feb/05 11:09 PM

Note:

Use the line:

alter table jiraworkflows change DESCRIPTOR DESCRIPTOR LONGTEXT;

to upgrade