[ 
https://issues.apache.org/jira/browse/MRM-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sujeet Kumar updated MRM-1946:
------------------------------
    Priority: Critical  (was: Major)

> Archiva Issue - v2.2.1 - Not authorized , ReasonPhrase:Unauthorized.
> --------------------------------------------------------------------
>
>                 Key: MRM-1946
>                 URL: https://issues.apache.org/jira/browse/MRM-1946
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>         Environment: Linux
>            Reporter: Sujeet Kumar
>            Priority: Critical
>
> I use Jenkins to build the artifact. And in Jenkins post build action the 
> artifact is pushed to Archiva once the build is successful. This works but 
> from last 2 days I am facing issues while pushing the artifact to archiva. 
> And when the archiva is restarted the issue disappears and the artifact gets 
> pushed to archiva successfully. I tried to Flush the cache but no luck.
>  
> The following is the stacktrace of the exception received
>  
> Caused by: org.eclipse.aether.transfer.MetadataTransferException: Could not 
> transfer metadata 
> RoleManagementService:RoleManagementService:0.0.1-SNAPSHOT/maven-metadata.xml 
> from/to qa-snapshots 
> (http://10.159.70.63:8060/archiva/repository/qa-snapshots): Not authorized , 
> ReasonPhrase:Unauthorized.
>  at 
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$5.wrap(WagonRepositoryConnector.java:995)
>  at 
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$5.wrap(WagonRepositoryConnector.java:983)
>  at 
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:725)
>  at 
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to