Failure to fully delete project

Description
pjy
Posts: 1
Joined: Wed Jun 06, 2012 4:49 am

Failure to fully delete project

Postby pjy » Wed Jun 06, 2012 4:58 am

When testing Polarion (ALM 2012) for the first time, users at our site created some test projects and then deleted them.
Afterward when trying to create a project of the same name (e.g. RSAA/Junk) as the one deleted, the following error message is displayed:

The repository access file already contains a reference to child location /RSAA/Junk/.polarion/tracker/baselines/. A user group starting with this ID is defined in the repository access file.

Editing the srv/polarion/svn/access file directly and removing any mention of the RSAA/Junk file solves the problem. It seems, then, that this last removal step is not being done by the Polarion ALM software.

Looking at the logs we notice quite a few Java stack traces, the first of which is:

2012-06-06 14:40:58,152 [TP-Processor6] INFO com.polarion.usdp.persistence.document.impl.XMLStructuredDocument - Invalid content set for document AbstractDocument[docStor=DocumentStorage[contextId=ContextId[cluster default, context Junk], context=context id ContextId[cluster default, context Junk], context object subterra:data-service:objects:/default/Junk${Project}Junk, location Location[repository default, path /RSAA/Junk], idgen=com.polarion.platform.persistence.internal.pe.CustomIdGenerator@6e4486a5, locations=[Location[path documents], Location[path modules], Location[path _wiki], Location[path .polarion]], autoPromotion=1, readOnly=false, useTransactionalDocumentCache=true, transactionalDocumentCacheSize=10000, useGlobalDocumentCache=true, globalDocumentCacheSize=100, useGlobalDocumentCacheWithHistory=false], location=Location[repository default, path /RSAA/Junk/.polarion/tracker/categories/Persistence.xml, revision 1077], format=xml, modified=false, promoted=true, fixed=false]
AbstractStructuredDocument[invalid=true, secondary=false, stickyRevision=
java.lang.IllegalArgumentException: No such context exists: ContextId[cluster default, context Junk]
at com.polarion.platform.repository.internal.context.RepositoryContextService.getContextforId(RepositoryContextService.java:102)
at $IContextService_137c0156a12.getContextforId($IContextService_137c0156a12.java)
at com.polarion.platform.persistence.internal.pe.ContextManager.getContext(ContextManager.java:89)

...

last lines of stack-trace removed for brevity.

So - does anyone else see this?

Have we done something wrong when installing the software?

Our current work-around is to edit the access file manually after each project deletion. Not really what we would like to continue doing.

Cheers and thanks, Peter

jandlj
Posts: 20
Joined: Mon Aug 23, 2010 11:40 am
Location: Polarion Software, Prague
Contact:

Re: Failure to fully delete project

Postby jandlj » Fri Jun 15, 2012 8:30 am

Hello,
you did nothing wrong. It's an issue in Polarion which is tracked and dev. team is working to fix that.
Manuall edit of access is a valid workaround, if you need to delete a project and recreate new one on the same place.

Regards
Jiri

patroklos
Posts: 2
Joined: Tue Aug 27, 2019 3:01 pm

Re: Failure to fully delete project

Postby patroklos » Tue Aug 27, 2019 3:03 pm

Is this still active 7 years after?
Creating a project with the same name as a deleted one returns:
"A user group starting with this ID is defined in the repository access file"

patroklos
Posts: 2
Joined: Tue Aug 27, 2019 3:01 pm

Re: Failure to fully delete project

Postby patroklos » Thu Aug 29, 2019 1:42 pm

Same behavior when creating a document with same name as one deleted before, within a project.
Is there a clear workaround without SVN access?

Server error:

com.polarion.subterra.persistence.PersistenceException: Cannot create the Module in existing location 'modules/Initiation/Project Charter/module.xml'. Most probably the Module with the same ID already exists.


Return to “Polarion Application Lifecycle Management (ALM)”

Who is online

Users browsing this forum: No registered users and 10 guests