Polarion throws exception after Jira Connection removal

Posts: 3
Joined: Thu Feb 06, 2014 2:58 pm

Polarion throws exception after Jira Connection removal

Postby rcomblen » Fri Feb 28, 2014 3:17 pm


I get an issue with our Polarion instance.
We want to sync our requirements from Polarion into JIRA issues.
To test that configuration, I've created
- a test JIRA instance
- a JIRA Connection in the Connectors admin panel of my project
- a Synchronisation Pair (only left to right direction)

I observe the following:
- The first sync works fine.
- If I drop the JIRA instance and recreate it, the second sync doesn't do anything, it says XXX deleted items on right side, and does not create them, as it thinks they were explicitly deleted from JIRA.

As mentioned in the documentation (bottom of http://almdemo.polarion.com/polarion/he ... ctors.html), the Connector Data contains sync information, and is stored in the data/synchronizer folder. When I get there, I see the following folders:
so I guess the data is kept if I drop the Sync Pair and create another one.

Therefore, I considered deleting the Connection and recreating it.
1) All Connections are gone in the Connector panel (including an existing connection I did not touch)
2) I cannot create a new Connection anymore, I get a big red message saying (in short, full log attached):
com.polarion.platform.repository.config.RepositoryConfigurationException: [/BA/.polarion/synchronizer/configuration.xml]: Undefined ID "TestJira".
where TestJira is the Connection that I deleted.

Any clue how to recover from that error ?

Where is that /BA/.polarion/synchronizer/configuration.xml file stored, it's not on filesystem, how can I inspect it ?
Error message in the log
(14.48 KiB) Downloaded 230 times

Posts: 199
Joined: Wed Aug 09, 2006 10:55 am

Re: Polarion throws exception after Jira Connection removal

Postby engeleb » Mon Mar 03, 2014 8:18 am

the problem is that loading the configuration fails if a sync pair references a connection that does not exist.
To solve the problem you should restore the configuration to the state just before you deleted the connection.
You can do that using the Repository Browser (or any other Subversion client):
1. Open the Repository Browser in the affected project.
2. Navigate to .polarion/synchronizer/configuration.xml
3. Open history of the file an download the working version of the configuration, should be the version before the last one.
4. Go back to configuration.xml
5. Update configuration.xml with the working version.

With Polarion 2013 SR3 it is no longer possible to delete a connection that is used in a sync pair, therefore it is no longer possible to get the problem you encountered.

There are two possible solutions for you initial problem:
1. Update to Polarion 2013 SR3 and set Delete Direction" to "Disabled", running synchronization will recreate all now missing issues in Jira.
2. With older versions of Polarion you can just delete (or better move away) the folder on the server (MyProject/JIRA-MyConnection) that contains the connection data.

Best Regards,

Posts: 3
Joined: Thu Feb 06, 2014 2:58 pm

Re: Polarion throws exception after Jira Connection removal

Postby rcomblen » Mon Mar 10, 2014 7:50 am

Thanks for that feedback!

I'll give it a try and let you know if I face any further issues.



Return to “Polarion Application Lifecycle Management (ALM)”

Who is online

Users browsing this forum: Google [Bot], TammyApork and 6 guests