Why is deleted artifact still available for modification, querying and delete? (Error 410: Gone)
Error 410: Gone
com.ibm.rdm.fronting.server.exception.GoneException
There is also this problem in the RM logs trace.
CRJAZ2388E The background process that synchronizes user data between servers could not be completed. The synchronizer will attempt the synchronization again.
CRJAZ1166I The stack trace hash is 047303824DB7D286FDAC30219224818C0554ADD7.
com.ibm.team.repository.common.TeamRepositoryException: Connection refused: connect
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.send(AuthenticatingClientService.java:841)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.access$2(AuthenticatingClientService.java:663)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService.sendAsApplication(AuthenticatingClientService.java:163)
at sun.reflect.GeneratedMethodAccessor527.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy737.sendAsApplication(Unknown Source)
at com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.doCommunicate(CrossServerHttpClient.java:358)
at com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.sendAsApplication(CrossServerHttpClient.java:274)
at com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClientService.send(CrossServerHttpClientService.java:69)
at sun.reflect.GeneratedMethodAccessor791.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy1590.send(Unknown Source)
at com.ibm.team.repository.service.compatibility.AbstractCompatibilityService.send(AbstractCompatibilityService.java:55)
at com.ibm.team.repository.service.compatibility.contributor.internal.CompatContributorService.get(CompatContributorService.java:739)
at com.ibm.team.repository.service.compatibility.contributor.internal.CompatContributorService.query(CompatContributorService.java:715)
at com.ibm.team.repository.service.compatibility.contributor.internal.ServicesBasedContributorSynchronizerHelper.queryUrl(ServicesBasedContributorSynchronizerHelper.java:108)
at com.ibm.team.repository.service.compatibility.contributor.internal.ContributorSynchronizer.runQuery(ContributorSynchronizer.java:731)
at com.ibm.team.repository.service.compatibility.contributor.internal.ContributorSynchronizer.runQuery(ContributorSynchronizer.java:718)
at com.ibm.team.repository.service.compatibility.contributor.internal.ContributorSynchronizer.doPerformSynchronization(ContributorSynchronizer.java:261)
at com.ibm.team.repository.service.compatibility.contributor.internal.ContributorSynchronizer.performSynchronization(ContributorSynchronizer.java:198)
at com.ibm.team.repository.service.compatibility.contributor.internal.CompatContributorService$2.run(CompatContributorService.java:469)
at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:245)
at com.ibm.team.repository.service.compatibility.contributor.internal.CompatContributorService.performSynchronization(CompatContributorService.java:465)
at com.ibm.team.repository.service.compatibility.contributor.internal.CompatContributorService.performSynchronization(CompatContributorService.java:434)
at sun.reflect.GeneratedMethodAccessor1485.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy2003.performSynchronization(Unknown Source)
at com.ibm.team.repository.service.compatibility.contributor.internal.ContributorSynchronizingTask.runTask(ContributorSynchronizingTask.java:38)
at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:96)
at sun.reflect.GeneratedMethodAccessor397.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy2007.executeTask(Unknown Source)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:185)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:138)
at java.lang.Thread.run(Thread.java:773)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:243)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:230)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:539)
at com.ibm.jsse2.SSLSocketImpl.connect(SSLSocketImpl.java:56)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at com.ibm.team.jfs.app.http.client.internal.ExtensibleRequestDirector.execute(ExtensibleRequestDirector.java:168)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.send(AuthenticatingClientService.java:839)
Accepted answer
One other answer
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=82128
The scenarios which could lead to the situation can be:
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=81011
From the above WI 82128, there is a suggested solution:
B. Method for repairing Module Structure: (case where core artifact is deleted but is referenced in Structure)
Method -
1. In the RMAdmin interface (url: ".../rdm/rmadmin"), go to the 'Modules' page under Services.
2. Choose your Project from the dropdown and click 'List Modules', find your Module in the list and click 'ANALYZE' -
- this provides a section called "DETECTED ISSUES WITH BOUND ARTIFACTS" listing the url of the deleted core artifact.
3. Find its binding url by matching it in the list labeled "BINDING STRUCTURE FROM STORAGE" & copy it.
4. Go to the 'Debug Service' page, & paste in the url at the top, choose DELETE from the dropdown, ensure the Response Format == RM & click Submit.
5. Go back to the Modules page and enter same details as step 2 and click ANALYZE to conform that both the Structure & Index are repaired.
The Web Client should be able to open the Module now.
Note: If you have v5.x, you can go to rm/admin URL and from menu 'Debug', you would find 'Modules' there.
Hopefully this helps.
Comments
Thank you, Don.
I've done as recommended and it didn't work. This artifact was never in a module, the modules that I tested did not have URLs in the "DETECTED ISSUES WITH BOUND ARTIFACTS" section, and the debug does not find even the artifacts that are in the "BINDING STRUCTURE FROM STORAGE".
The error in the log I believe is related to the problem I'm dealing with.
What else should I do?
Hi, Manuel
If the suggested approach is not applicable to your environment, the only option I can think of is to do reindex and see if it helps. if you are at prior to v5.0, you can run against jts(as rm is a part of jts). if it is v5.0 and over, you can run against rm application.
if it does not help, I would suggest to contact Support to further investigate.
Comments
Donald Nong
Feb 10 '16, 10:03 p.m.You'd better open a separate post for your second problem. It can be quite messy when people try to discuss different things at the same time.