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 <marco.ferre...@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 <marco.ferre...@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
> > >
> >
>

Reply via email to