You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Cristian Tarsoaga (JIRA)" <ji...@apache.org> on 2017/05/02 11:01:04 UTC

[jira] [Comment Edited] (MRM-1933) No message body writer has been found for class org.apache.archiva.rest.services.ArchivaRestError

    [ https://issues.apache.org/jira/browse/MRM-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992707#comment-15992707 ] 

Cristian Tarsoaga edited comment on MRM-1933 at 5/2/17 11:00 AM:
-----------------------------------------------------------------

Tracked the same problem via debug logs. Seems that archiva 2.2.1 always adds 2 slashes at the end of my repo url.
If I specify http://repo.maven.apache.org/maven2/ as my remote url, archiva actually queries http://repo.maven.apache.org/maven2///

The workaround I used in archiva, was to put a ? at the end of my remote repo url - which later discards those two slashes 
So this seems to work: http://repo.maven.apache.org/maven2/?

Note1: nexus repo allows those //, no problem there. 
Maven central doesn't. A query http://repo.maven.apache.org/maven2/// results in code 400.

Note2: I had no problem whatsoever as long as I used a lan proxy. When I removed it, I hit this problem.
Probably a proxy translates that url and removed those trailing slashes, which avoids the whole problem.



was (Author: kcris):
Tracked the same problem via debug logs. Seems that archiva always adds 2 slashes at the end of my repo url.
If I specify http://repo.maven.apache.org/maven2/ as my remote url, archiva actually queries http://repo.maven.apache.org/maven2///

The workaround I used in archiva, was to put a ? at the end of my remote repo url - which later discards those two slashes 
So this seems to work: http://repo.maven.apache.org/maven2/?

Note1: nexus repo allows those //, no problem there. 
Maven central doesn't. A query http://repo.maven.apache.org/maven2/// results in code 400.

Note2: I had no problem whatsoever as long as I used a lan proxy. When I removed it, I hit this problem.
Probably a proxy translates that url and removed those trailing slashes, which avoids the whole problem.


> No message body writer has been found for class org.apache.archiva.rest.services.ArchivaRestError
> -------------------------------------------------------------------------------------------------
>
>                 Key: MRM-1933
>                 URL: https://issues.apache.org/jira/browse/MRM-1933
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>         Environment: WAR Deployment im Tomcat 7 on JDK 8
>            Reporter: Jörg Delker
>
> After adding the following remote repository via UI, this error appears in UI and archive.log each time the repository page is loaded:
> 2017-01-02 16:57:31,927 [http-bio-8000-exec-8] ERROR org.apache.cxf.jaxrs.utils.JAXRSUtils [] - No message body writer has been found for class org.apache.archiva.rest.services.ArchivaRestError, ContentType: text/plain
> Repository: http://download.oracle.com/maven
> Note: The repository does obviously provide no index (results in 404).
> However, fetching artifacts (e.g. http://download.oracle.com/maven/com/sleepycat/je/5.0.104/je-5.0.104.pom) is working ok.
> Besides the above error, requests to Archiva are proxies without problems and artifacts are retrieved without error from that repository.



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