Capture for JIRA throwing unexpected exception

Chris I'm New Here Jan 03, 2018

We use Capture to record exploratory test sessions.  A number of my team members who are on Windows machines cannot "capture" a test session.  When they create a session they cannot start it

When they log in to JIRA they see the following error: 

com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1)

1 answer

1 vote

Hi Chris,

We have an article titled Only whitespace content allowed before start tag when trying to view project within JIRA Software that may help with this:

Cause

JIRA Software's configurations are stored as XML within the database.  With that, if the XML is invalid, it can result in the above.

For example, a normal entry may look like this:

  id   |  propertyvalue
------------------------
 10399 | <map>
       :   <entry>
       :     <string>GH_gh.issue.releasedVersionHistoryField</string>
       :     <string>customfield_10006</string>
       :   </entry>
       :   <entry>
       :     <string>FIX_VERSION_SYNCHER</string>
       :     <boolean>false</boolean>
       :   </entry>
       :   <entry>
       :     <string>gh.configuration.rapidboard.scrum</string>
       :     <boolean>true</boolean>
       :   </entry>
       : </map>

Problematic entry:

  id   |  propertyvalue
------------------------
 10399 | ![CDATA[<map>
       :   <entry>
       :     <string>GH_gh.issue.releasedVersionHistoryField</string>
       :     <string>customfield_10006</string>
       :   </entry>
       :   <entry>
       :     <string>FIX_VERSION_SYNCHER</string>
       :     <boolean>false</boolean>
       :   </entry>
       :   <entry>
       :     <string>gh.configuration.rapidboard.scrum</string>
       :     <boolean>true</boolean>
       :   </entry>
       : </map>]]

Workaround

Remove the problematic entry from both the propertyentry and propertytext tables.

(warning) back up your data first.

Resolution

(warning) back up your data first. Only attempt this if you are comfortable with database administration.

  1. Identify the problematic XML:
    1. Identify the Project's ID:

      select * from project;
    2. Identify the Project's configurations (this may return quite a few results):

      select * from propertytext where ID in (select ID from propertyentry where property_key = 'GREENHOPPER%XXXXX');
    3. With the list of results, check the XML data. Note that this may return a large list of results
  2. Once the problematic XML is found, update the entry with the proper format

Take a look at the knowledge base article and go through the steps and let me know if that helps.  If not we'll go from there.

Cheers,

Branden

Chris I'm New Here Jan 04, 2018

Thanks! we are looking into this I will let you know if the advice helped!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,224 views 14 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot