You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Marco Ferretti <ma...@axiante.com> on 2023/04/27 09:30:10 UTC
Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Hi,
I have been using Archiva since version 2.2.7 without an issue. I have bumped into the updates of Archiva (2.2.10) and decided I needed to upgrade.
I am using a stand-alone installation proxied by an Apache server (mainly to manage certs).
After installing (unzipping), copying the repository and data directory, and checking the differences in wrapper.conf and jetty.xml I fired the new version.
I can browse my repos but I can't download jars/pom/etc. What I am getting is an HTTP error 400 with any jar I try; here's an exerpt from request.log :
127.0.0.1 - - [27/Apr/2023:08:04:18 +0000] "GET /repository/internal/junit/junit/3.8.1/junit-3.8.1.jar HTTP/1.1" 400 1422 "https://artifact.axiante.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36"
I have then tried to upgrade one version at a time with the following results:
2.2.7: works (the starting version)
2.2.8: works (the current version being served)
2.2.9: same as above, error 400 when trying to download artifacts
2.2.10: same as 2.2.9
I have checked file permissions, memory, jcr logs and made sure I did a systemctl daemon-reload before running the server (I am using symlinks to keep my installations tight)
As far as I am aware, there are a few major changes between 2.2.8 and 2.2.9 (namely spring), and checking (using diff) the wrapper I can see that activation.jar has been upgraded from version 1.1 to 1.1.1.
Also, to complete the description of my problem, I am using OpenJDK 1.8.0_362 on the machine that is serving Archiva.
Can anyone point me somewhere? I have been trying to upgrade for a couple of days, went through a lot of documentation, and checked Google: the only (slightly) related issue I have found was with versions <1.4 and artifacts upload.
TIA
Marco
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Marco Ferretti <ma...@axiante.com>.
not that I can see :
drwxr-xr-x 2 archiva archiva 4096 Apr 27 08:23 ./
drwxr-xr-x 9 archiva archiva 4096 Apr 27 08:23 ../
-rw-r--r-- 1 archiva archiva 382708 Apr 27 08:23 junit-4.13.1.jar
-rw-r--r-- 1 archiva archiva 32 Apr 27 08:23 junit-4.13.1.jar.md5
-rw-r--r-- 1 archiva archiva 40 Apr 27 08:23 junit-4.13.1.jar.sha1
-rw-r--r-- 1 archiva archiva 25062 Apr 27 08:23 junit-4.13.1.pom
-rw-r--r-- 1 archiva archiva 32 Apr 27 08:23 junit-4.13.1.pom.md5
-rw-r--r-- 1 archiva archiva 40 Apr 27 08:23 junit-4.13.1.pom.sha1
-rw-r--r-- 1 archiva archiva 151 May 8 09:53 maven-metadata.xml
-rw-r--r-- 1 archiva archiva 52 Apr 27 08:23 maven-metadata.xml.md5
-rw-r--r-- 1 archiva archiva 60 Apr 27 08:23 maven-metadata.xml.sha1
marco@artifact:/opt/archiva/repositories/internal/junit/junit/4.13.1$ pwd
/opt/archiva/repositories/internal/junit/junit/4.13.1
but then, looking for 'org.bouncycastle;bc-fips-[1.0.2,2.0.0).jar' I can't find it :
drwxr-xr-x 8 archiva archiva 4096 Apr 27 08:23 ./
drwxr-xr-x 51 archiva archiva 4096 May 15 09:32 ../
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcmail-jdk15on/
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcpkix-jdk15on/
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcpkix-jdk18on/
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcprov-jdk15on/
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcprov-jdk18on/
drwxr-xr-x 3 archiva archiva 4096 Apr 27 08:23 bcutil-jdk18on/
marco@artifact:/opt/archiva/repositories/internal/org/bouncycastle$
could this be the actual issue ? And shouldn't it try to download it from central ?
On May 17 2023, at 8:54 am, Olivier Lamy <ol...@apache.org> wrote:
> Hi
> I wonder what is the real path of the repository on disk? Does it
> contain "special characters"?
>
> On Wed, 10 May 2023 at 03:54, Marco Ferretti <ma...@axiante.com> wrote:
> >
> >
> >
> > On May 8 2023, at 10:10 am, Olivier Lamy <ol...@apache.org> wrote:
> > > Hi
> > > I can see this root cause in the stack trace
> > > > Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
> > >
> > > This sounds strange.
> > > Maybe you can simply stop Archiva, delete the jackrabbit data as they
> > > seem to be corrupted then restart.
> > >
> > I have tried removing the jcr directory and restart archiva 2.2.10 with the exact same result. I have even tried the same with archiva 2.2.8 successfully.
> > Here's the result :
> > -- archiva 2.2.8, jcr directory deleted and automatically rebuilt :
> >
> > wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > URL transformed to HTTPS due to an HSTS policy
> > --2023-05-08 11:13:52-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> > Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 261809 (256K) [application/java-archive]
> > Saving to: ‘commons-lang-2.4.jar’
> >
> > commons-lang-2.4.jar 100%[=========================================================================================================================================>] 255,67K 223KB/s in 1,1s
> >
> > -- archiva 2.2.10, jcr directory deleted and automatically rebuilt
> > -- archiva 2.2.10, jcr directory deleted and moved from archiva 2.2.8
> > -- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr directory moved from archiva 2.2.8
> > -- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr rebuilt on startup
> > wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > URL transformed to HTTPS due to an HSTS policy
> > --2023-05-08 11:16:31-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> > Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> > HTTP request sent, awaiting response... 400 Bad Request
> > 2023-05-08 11:16:34 ERROR 400: Bad Request.
> >
> > the log always has
> > Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'org.bouncycastle;bc-fips-[1.0.2,2.0.0).jar' is not a valid path. '�' not a valid name character.
> > at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:327) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:122) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:90) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:98) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:82) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:648) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.session.SessionContext.getQPath(SessionContext.java:338) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:238) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> > ... 23 more
> >
> > I then tried to remove the repository and rebuild :
> > wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > URL transformed to HTTPS due to an HSTS policy
> > --2023-05-08 11:29:32-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> > Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> > Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> > HTTP request sent, awaiting response... 400 Bad Request
> > 2023-05-08 11:29:33 ERROR 400: Bad Request.
> >
> > archiva request.log:
> > 127.0.0.1 - - [08/May/2023:09:29:33 +0000] "GET /repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar HTTP/1.1" 400 1439 "-" "Wget/1.21.2"
> >
> > archiva.log: empty on the request
> >
> > I am totally lost here ...
>
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Olivier Lamy <ol...@apache.org>.
Hi
I wonder what is the real path of the repository on disk? Does it
contain "special characters"?
On Wed, 10 May 2023 at 03:54, Marco Ferretti <ma...@axiante.com> wrote:
>
>
>
> On May 8 2023, at 10:10 am, Olivier Lamy <ol...@apache.org> wrote:
> > Hi
> > I can see this root cause in the stack trace
> > > Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
> >
> > This sounds strange.
> > Maybe you can simply stop Archiva, delete the jackrabbit data as they
> > seem to be corrupted then restart.
> >
> I have tried removing the jcr directory and restart archiva 2.2.10 with the exact same result. I have even tried the same with archiva 2.2.8 successfully.
> Here's the result :
> -- archiva 2.2.8, jcr directory deleted and automatically rebuilt :
>
> wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> URL transformed to HTTPS due to an HSTS policy
> --2023-05-08 11:13:52-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 261809 (256K) [application/java-archive]
> Saving to: ‘commons-lang-2.4.jar’
>
> commons-lang-2.4.jar 100%[=========================================================================================================================================>] 255,67K 223KB/s in 1,1s
>
> -- archiva 2.2.10, jcr directory deleted and automatically rebuilt
> -- archiva 2.2.10, jcr directory deleted and moved from archiva 2.2.8
> -- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr directory moved from archiva 2.2.8
> -- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr rebuilt on startup
> wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> URL transformed to HTTPS due to an HSTS policy
> --2023-05-08 11:16:31-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> HTTP request sent, awaiting response... 400 Bad Request
> 2023-05-08 11:16:34 ERROR 400: Bad Request.
>
> the log always has
> Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'org.bouncycastle;bc-fips-[1.0.2,2.0.0).jar' is not a valid path. '�' not a valid name character.
> at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:327) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:122) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:90) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:98) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:82) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:648) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.session.SessionContext.getQPath(SessionContext.java:338) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:238) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> ... 23 more
>
> I then tried to remove the repository and rebuild :
> wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> URL transformed to HTTPS due to an HSTS policy
> --2023-05-08 11:29:32-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
> Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
> HTTP request sent, awaiting response... 400 Bad Request
> 2023-05-08 11:29:33 ERROR 400: Bad Request.
>
> archiva request.log:
> 127.0.0.1 - - [08/May/2023:09:29:33 +0000] "GET /repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar HTTP/1.1" 400 1439 "-" "Wget/1.21.2"
>
> archiva.log: empty on the request
>
> I am totally lost here ...
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Marco Ferretti <ma...@axiante.com>.
On May 8 2023, at 10:10 am, Olivier Lamy <ol...@apache.org> wrote:
> Hi
> I can see this root cause in the stack trace
> > Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
>
> This sounds strange.
> Maybe you can simply stop Archiva, delete the jackrabbit data as they
> seem to be corrupted then restart.
>
I have tried removing the jcr directory and restart archiva 2.2.10 with the exact same result. I have even tried the same with archiva 2.2.8 successfully.
Here's the result :
-- archiva 2.2.8, jcr directory deleted and automatically rebuilt :
wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
URL transformed to HTTPS due to an HSTS policy
--2023-05-08 11:13:52-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 261809 (256K) [application/java-archive]
Saving to: ‘commons-lang-2.4.jar’
commons-lang-2.4.jar 100%[=========================================================================================================================================>] 255,67K 223KB/s in 1,1s
-- archiva 2.2.10, jcr directory deleted and automatically rebuilt
-- archiva 2.2.10, jcr directory deleted and moved from archiva 2.2.8
-- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr directory moved from archiva 2.2.8
-- archiva 2.2.10, jcr directory deleted, repository directory moved from archiva 2.2.8, jcr rebuilt on startup
wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
URL transformed to HTTPS due to an HSTS policy
--2023-05-08 11:16:31-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2023-05-08 11:16:34 ERROR 400: Bad Request.
the log always has
Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'org.bouncycastle;bc-fips-[1.0.2,2.0.0).jar' is not a valid path. '�' not a valid name character.
at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:327) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:122) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:90) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:98) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:82) ~[jackrabbit-spi-commons-2.9.1.jar:?]
at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:648) ~[jackrabbit-core-2.9.1.jar:2.9.1]
at org.apache.jackrabbit.core.session.SessionContext.getQPath(SessionContext.java:338) ~[jackrabbit-core-2.9.1.jar:2.9.1]
at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:238) ~[jackrabbit-core-2.9.1.jar:2.9.1]
at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
... 23 more
I then tried to remove the repository and rebuild :
wget http://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
URL transformed to HTTPS due to an HSTS policy
--2023-05-08 11:29:32-- https://artifact.axiante.com/repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
Resolving artifact.axiante.com (artifact.axiante.com)... 34.122.158.86
Connecting to artifact.axiante.com (artifact.axiante.com)|34.122.158.86|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2023-05-08 11:29:33 ERROR 400: Bad Request.
archiva request.log:
127.0.0.1 - - [08/May/2023:09:29:33 +0000] "GET /repository/internal/commons-lang/commons-lang/2.4/commons-lang-2.4.jar HTTP/1.1" 400 1439 "-" "Wget/1.21.2"
archiva.log: empty on the request
I am totally lost here ...
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Olivier Lamy <ol...@apache.org>.
Hi
I can see this root cause in the stack trace
> Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
This sounds strange.
Maybe you can simply stop Archiva, delete the jackrabbit data as they
seem to be corrupted then restart.
On Fri, 5 May 2023 at 16:42, Marco Ferretti <ma...@axiante.com> wrote:
>
> Hi,
> thanks for taking the time to come back at my issue.
> Regarding your questions:
> The issue happened with every artifact I tried to download (I tried a few, don't really remember how many)
>
> The only stack trace I see in archivia.log related to dowloading an artifact looks like something to do with char encoding and is the following:
>
> > 2023-04-27 08:14:54,377 [pool-5-thread-1] WARN org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer [] - Error occurred persisting metadata for artifact:org/javassist/javassist/3.28.0-GA/javassist-3.28.0-GA.pom (repository:internal); message: Failed to resolve path junit;junit-[4.13.1,).jar relativ
> > e to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> > org.apache.archiva.metadata.repository.MetadataRepositoryException: Failed to resolve path junit;junit-[4.13.1,).jar relative to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> > at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:365) ~[metadata-store-jcr-2.2.10.jar:?]
> > at org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer.processFile(ArchivaMetadataCreationConsumer.java:192) [archiva-metadata-consumer-2.2.10.jar:?]
> > at org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer.processFile(ArchivaMetadataCreationConsumer.java:222) [archiva-metadata-consumer-2.2.10.jar:?]
> > at org.apache.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:63) [archiva-repository-scanner-2.2.10.jar:?]
> > at org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:118) [commons-collections-3.2.2.jar:3.2.2]
> > at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:389) [commons-collections-3.2.2.jar:3.2.2]
> > at org.apache.archiva.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:167) [archiva-repository-scanner-2.2.10.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:174) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:392) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> > at org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:345) [plexus-utils-3.0.15.jar:?]
> > at org.apache.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:141) [archiva-repository-scanner-2.2.10.jar:?]
> > at org.apache.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:69) [archiva-repository-scanner-2.2.10.jar:?]
> > at org.apache.archiva.scheduler.repository.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:150) [archiva-scheduler-repository-2.2.10.jar:?]
> > at org.apache.archiva.scheduler.repository.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:54) [archiva-scheduler-repository-2.2.10.jar:?]
> > at org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:117) [spring-taskqueue-2.1.jar:?]
> > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_362]
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_362]
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_362]
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_362]
> > at java.lang.Thread.run(Thread.java:750) [?:1.8.0_362]
> > Caused by: javax.jcr.RepositoryException: Failed to resolve path junit;junit-[4.13.1,).jar relative to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:240) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> > ... 23 more
> > Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
> > at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:327) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:122) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:90) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:98) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:82) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:648) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.session.SessionContext.getQPath(SessionContext.java:338) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:238) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> > at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> > ... 23 more
>
> Thanks for any advice you can provide.
> Marco
> On May 5 2023, at 2:56 am, Olivier Lamy <ol...@apache.org> wrote:
> > Hi
> > Can you see anything in archiva.log file?
> > does it happen for every artifacts or only few?
> >
> > On Thu, 27 Apr 2023 at 19:30, Marco Ferretti <ma...@axiante.com> wrote:
> > >
> > > Hi,
> > > I have been using Archiva since version 2.2.7 without an issue. I have bumped into the updates of Archiva (2.2.10) and decided I needed to upgrade.
> > > I am using a stand-alone installation proxied by an Apache server (mainly to manage certs).
> > >
> > > After installing (unzipping), copying the repository and data directory, and checking the differences in wrapper.conf and jetty.xml I fired the new version.
> > > I can browse my repos but I can't download jars/pom/etc. What I am getting is an HTTP error 400 with any jar I try; here's an exerpt from request.log :
> > >
> > > 127.0.0.1 - - [27/Apr/2023:08:04:18 +0000] "GET /repository/internal/junit/junit/3.8.1/junit-3.8.1.jar HTTP/1.1" 400 1422 "https://artifact.axiante.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36"
> > > I have then tried to upgrade one version at a time with the following results:
> > > 2.2.7: works (the starting version)
> > >
> > > 2.2.8: works (the current version being served)
> > >
> > > 2.2.9: same as above, error 400 when trying to download artifacts
> > >
> > > 2.2.10: same as 2.2.9
> > >
> > > I have checked file permissions, memory, jcr logs and made sure I did a systemctl daemon-reload before running the server (I am using symlinks to keep my installations tight)
> > > As far as I am aware, there are a few major changes between 2.2.8 and 2.2.9 (namely spring), and checking (using diff) the wrapper I can see that activation.jar has been upgraded from version 1.1 to 1.1.1.
> > > Also, to complete the description of my problem, I am using OpenJDK 1.8.0_362 on the machine that is serving Archiva.
> > >
> > > Can anyone point me somewhere? I have been trying to upgrade for a couple of days, went through a lot of documentation, and checked Google: the only (slightly) related issue I have found was with versions <1.4 and artifacts upload.
> > > TIA
> > > Marco
> > >
> >
>
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Marco Ferretti <ma...@axiante.com>.
Hi,
thanks for taking the time to come back at my issue.
Regarding your questions:
The issue happened with every artifact I tried to download (I tried a few, don't really remember how many)
The only stack trace I see in archivia.log related to dowloading an artifact looks like something to do with char encoding and is the following:
> 2023-04-27 08:14:54,377 [pool-5-thread-1] WARN org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer [] - Error occurred persisting metadata for artifact:org/javassist/javassist/3.28.0-GA/javassist-3.28.0-GA.pom (repository:internal); message: Failed to resolve path junit;junit-[4.13.1,).jar relativ
> e to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> org.apache.archiva.metadata.repository.MetadataRepositoryException: Failed to resolve path junit;junit-[4.13.1,).jar relative to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:365) ~[metadata-store-jcr-2.2.10.jar:?]
> at org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer.processFile(ArchivaMetadataCreationConsumer.java:192) [archiva-metadata-consumer-2.2.10.jar:?]
> at org.apache.archiva.consumers.metadata.ArchivaMetadataCreationConsumer.processFile(ArchivaMetadataCreationConsumer.java:222) [archiva-metadata-consumer-2.2.10.jar:?]
> at org.apache.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:63) [archiva-repository-scanner-2.2.10.jar:?]
> at org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:118) [commons-collections-3.2.2.jar:3.2.2]
> at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:389) [commons-collections-3.2.2.jar:3.2.2]
> at org.apache.archiva.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:167) [archiva-repository-scanner-2.2.10.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:174) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:392) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386) [plexus-utils-3.0.15.jar:?]
> at org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:345) [plexus-utils-3.0.15.jar:?]
> at org.apache.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:141) [archiva-repository-scanner-2.2.10.jar:?]
> at org.apache.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:69) [archiva-repository-scanner-2.2.10.jar:?]
> at org.apache.archiva.scheduler.repository.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:150) [archiva-scheduler-repository-2.2.10.jar:?]
> at org.apache.archiva.scheduler.repository.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:54) [archiva-scheduler-repository-2.2.10.jar:?]
> at org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:117) [spring-taskqueue-2.1.jar:?]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_362]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_362]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_362]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_362]
> at java.lang.Thread.run(Thread.java:750) [?:1.8.0_362]
> Caused by: javax.jcr.RepositoryException: Failed to resolve path junit;junit-[4.13.1,).jar relative to node /repositories/internal/content/org/javassist/javassist/3.28.0-GA/dependencies
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:240) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> ... 23 more
> Caused by: org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: 'junit;junit-[4.13.1,).jar' is not a valid path. '�' not a valid name character.
> at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:327) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:122) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:90) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:98) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:82) ~[jackrabbit-spi-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:648) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.session.SessionContext.getQPath(SessionContext.java:338) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:238) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:223) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2281) ~[jackrabbit-core-2.9.1.jar:2.9.1]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:952) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.jackrabbit.commons.JcrUtils.getOrAddNode(JcrUtils.java:930) ~[jackrabbit-jcr-commons-2.9.1.jar:?]
> at org.apache.archiva.metadata.repository.jcr.JcrMetadataRepository.updateProjectVersion(JcrMetadataRepository.java:319) ~[metadata-store-jcr-2.2.10.jar:?]
> ... 23 more
Thanks for any advice you can provide.
Marco
On May 5 2023, at 2:56 am, Olivier Lamy <ol...@apache.org> wrote:
> Hi
> Can you see anything in archiva.log file?
> does it happen for every artifacts or only few?
>
> On Thu, 27 Apr 2023 at 19:30, Marco Ferretti <ma...@axiante.com> wrote:
> >
> > Hi,
> > I have been using Archiva since version 2.2.7 without an issue. I have bumped into the updates of Archiva (2.2.10) and decided I needed to upgrade.
> > I am using a stand-alone installation proxied by an Apache server (mainly to manage certs).
> >
> > After installing (unzipping), copying the repository and data directory, and checking the differences in wrapper.conf and jetty.xml I fired the new version.
> > I can browse my repos but I can't download jars/pom/etc. What I am getting is an HTTP error 400 with any jar I try; here's an exerpt from request.log :
> >
> > 127.0.0.1 - - [27/Apr/2023:08:04:18 +0000] "GET /repository/internal/junit/junit/3.8.1/junit-3.8.1.jar HTTP/1.1" 400 1422 "https://artifact.axiante.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36"
> > I have then tried to upgrade one version at a time with the following results:
> > 2.2.7: works (the starting version)
> >
> > 2.2.8: works (the current version being served)
> >
> > 2.2.9: same as above, error 400 when trying to download artifacts
> >
> > 2.2.10: same as 2.2.9
> >
> > I have checked file permissions, memory, jcr logs and made sure I did a systemctl daemon-reload before running the server (I am using symlinks to keep my installations tight)
> > As far as I am aware, there are a few major changes between 2.2.8 and 2.2.9 (namely spring), and checking (using diff) the wrapper I can see that activation.jar has been upgraded from version 1.1 to 1.1.1.
> > Also, to complete the description of my problem, I am using OpenJDK 1.8.0_362 on the machine that is serving Archiva.
> >
> > Can anyone point me somewhere? I have been trying to upgrade for a couple of days, went through a lot of documentation, and checked Google: the only (slightly) related issue I have found was with versions <1.4 and artifacts upload.
> > TIA
> > Marco
> >
>
Re: Archiva 2.2.10 : 400 Bad Request when downloading an artifact
Posted by Olivier Lamy <ol...@apache.org>.
Hi
Can you see anything in archiva.log file?
does it happen for every artifacts or only few?
On Thu, 27 Apr 2023 at 19:30, Marco Ferretti <ma...@axiante.com> wrote:
>
> Hi,
> I have been using Archiva since version 2.2.7 without an issue. I have bumped into the updates of Archiva (2.2.10) and decided I needed to upgrade.
> I am using a stand-alone installation proxied by an Apache server (mainly to manage certs).
>
> After installing (unzipping), copying the repository and data directory, and checking the differences in wrapper.conf and jetty.xml I fired the new version.
> I can browse my repos but I can't download jars/pom/etc. What I am getting is an HTTP error 400 with any jar I try; here's an exerpt from request.log :
>
> 127.0.0.1 - - [27/Apr/2023:08:04:18 +0000] "GET /repository/internal/junit/junit/3.8.1/junit-3.8.1.jar HTTP/1.1" 400 1422 "https://artifact.axiante.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36"
> I have then tried to upgrade one version at a time with the following results:
> 2.2.7: works (the starting version)
>
> 2.2.8: works (the current version being served)
>
> 2.2.9: same as above, error 400 when trying to download artifacts
>
> 2.2.10: same as 2.2.9
>
> I have checked file permissions, memory, jcr logs and made sure I did a systemctl daemon-reload before running the server (I am using symlinks to keep my installations tight)
> As far as I am aware, there are a few major changes between 2.2.8 and 2.2.9 (namely spring), and checking (using diff) the wrapper I can see that activation.jar has been upgraded from version 1.1 to 1.1.1.
> Also, to complete the description of my problem, I am using OpenJDK 1.8.0_362 on the machine that is serving Archiva.
>
> Can anyone point me somewhere? I have been trying to upgrade for a couple of days, went through a lot of documentation, and checked Google: the only (slightly) related issue I have found was with versions <1.4 and artifacts upload.
> TIA
> Marco
>