You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Christian (Jira)" <ji...@apache.org> on 2019/10/08 10:03:00 UTC
[jira] [Comment Edited] (MRM-2003) The owner of this website
(www.terracotta.org) has banned your access based on your browser's
signature (521f0006ab85c286-ua21).
[ https://issues.apache.org/jira/browse/MRM-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946674#comment-16946674 ]
Christian edited comment on MRM-2003 at 10/8/19 10:02 AM:
----------------------------------------------------------
Hi Martin,
> Archiva 2.2.4 runs only with JDK 7 or 8. It is not able to start with JDK 12.
If it so, it seems so, then you should better made a change in the _System Requirements_ on the [download.cgi|http://archiva.apache.org/download.cgi] page. I'll cite: `JDK 1.7 or above`. In my universe Java12 is included at »above« ;).
> but you may deactivate it with the line:
> wrapper.java.additional.9=-Dnet.sf.ehcache.skipUpdateCheck=true
I have switched back to Java8 and add the above line.
The result is,
{code:html}
User-Agent: Java/1.8.0_222
{code}
that the terracotta request are reduced from sixteen occurences to only one, seen by Wireshark.
But unfortunately the accesses to the internet repositories are still not visible.
> Is the requested archive ... really in your archiva repository?
No, it is a totaly new and therefore empty virtual machine with an empty Apache Archiva 2.2.4.
> ... Is your repository a mirror or only a local repository?
???
Here is the content of my settings.xml
{code:xml}
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd"
>
<!--
<localRepository>${user.home}/.m2/repository</localRepository>
<interactiveMode>true</interactiveMode>
<offline>false</offline>
<pluginGroups>
<pluginGroup>org.apache.maven.plugins</pluginGroup>
<pluginGroup>org.codehaus.mojo</pluginGroup>
</pluginGroups>
<servers/>
-->
<mirrors>
<mirror>
<id>internal</id>
<name>Archiva Managed Internal Repository</name>
<url>http://archiva.FOO.intern:8080/archiva/repository/internal/</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
<proxies/>
<profiles/>
<activeProfiles/>
</settings>
{code}
As a help for a faster solution, I pulled my system off, anonymized it a bit,shrank it a bit (the apps/ and lib/ folders are empty) and attached it to the ticket. Also the content of the logs/ folder is attached.
*Note*:
You may want to use the systemd service file (etc/systemd/system/archiva.service) as another startup option for the [standalone.html|http://archiva.apache.org/docs/2.2.4/adminguide/standalone.html] page.
Regards
Christian
was (Author: chris64):
Hi Martin,
> Archiva 2.2.4 runs only with JDK 7 or 8. It is not able to start with JDK 12.
If it so, it seems so, then you should better made a change in the _System Requirements_ on the [download.cgi|http://archiva.apache.org/download.cgi] page. I'll cite: `JDK 1.7 or above`. In my universe Java12 is included at »above« ;).
> but you may deactivate it with the line:
> wrapper.java.additional.9=-Dnet.sf.ehcache.skipUpdateCheck=true
I have switched back to Java8 and add this line.
{code:html}
User-Agent: Java/1.8.0_222
{code}
The result is, that the terracotta request are reduced to only one, seen by Wireshark.
But unfortunately the accesses to the internet repositories are still not visible.
> Is the requested archive ... really in your archiva repository?
No, it is a totaly new and therefore empty virtual machine with an empty Apache Archiva 2.2.4.
> ... Is your repository a mirror or only a local repository?
???
Here is the content of my settings.xml
{code:xml}
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd"
>
<!--
<localRepository>${user.home}/.m2/repository</localRepository>
<interactiveMode>true</interactiveMode>
<offline>false</offline>
<pluginGroups>
<pluginGroup>org.apache.maven.plugins</pluginGroup>
<pluginGroup>org.codehaus.mojo</pluginGroup>
</pluginGroups>
<servers/>
-->
<mirrors>
<mirror>
<id>internal</id>
<name>Archiva Managed Internal Repository</name>
<url>http://archiva.FOO.intern:8080/archiva/repository/internal/</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
<proxies/>
<profiles/>
<activeProfiles/>
</settings>
{code}
As a help for a faster solution, I pulled my system off, anonymized it a bit,shrank it a bit (the apps/ and lib/ folders are empty) and attached it to the ticket. Also the content of the logs/ folder is attached.
*Note*:
You may want to use the systemd service file (etc/systemd/system/archiva.service) as another startup option for the [standalone.html|http://archiva.apache.org/docs/2.2.4/adminguide/standalone.html] page.
Regards
Christian
> The owner of this website (www.terracotta.org) has banned your access based on your browser's signature (521f0006ab85c286-ua21).
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-2003
> URL: https://issues.apache.org/jira/browse/MRM-2003
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 2.2.4
> Reporter: Christian
> Assignee: Martin Stockhammer
> Priority: Blocker
> Attachments: archiva-2.2.4.tbz, v_a_logs.tbz
>
>
> I set up a new Archiva 2.2.4 (the standalone version: [apache-archiva-2.2.4-bin.tar.gz)|http://mirror.dkd.de/apache/archiva/2.2.4/binaries/apache-archiva-2.2.4-bin.tar.gz)] and get then from my local maven (after switching to the new Archiva via settings.xml):
> {code:java}
> [ERROR] Plugin org.apache.maven.plugins:maven-failsafe-plugin:2.18.1 or one of its dependencies could not be resolved: Could not find artifact org.apache.maven.plugins:maven-failsafe-plugin:jar:2.18.1 in internal (http://archiva.FOO.intern:8080/archiva/repository/internal/)
> {code}
> ... Investigate ...
> It seems so, that the indexer works together with _www.terracotta.org_ (from my Wireshark).
> {code:java}
> GET /kit/reflector?pageID=update.properties&patch=UNKNOWN&tc-product=ehcache-core+2.7.5&tc-version=2.7.5&uptime-secs=11&kidID=ehcache.default&jvm-version=12.0.2&os-name=Linux&id=-1408104395&source=ehcache-core&jvm-name=OpenJDK+64-Bit+Server+VM&platform=amd64
> Host: www.terracotta.org
> User-Agent: Java/1.8.0_222
> {code}
> But from that side my archiva virtual machine gets only the subjected message.
> {code:java}
> The owner of this website (www.terracotta.org) has banned your access based on your browser's signature (521f0006ab85c286-ua21).
> {code}
> My first thought was, that this message would be generated, because Java8 is EOL. Also switched I my linux VM (opensuse tumbleweed) to java12, but get only a lot of Exceptions after restarting Archiva. That would not better after asking the big brother, downloading the following jars and adding the lines in the wrapper,conf.
> {code:java}
> wrapper.java.classpath.27=/home/archiva/jaxb-api-2.3.0.jar
> wrapper.java.classpath.28=/home/archiva/jaxb-core-2.3.0.jar
> wrapper.java.classpath.29=/home/archiva/jaxb-impl-2.3.0.jar
> {code}
> But nevertheless I get another user agent:
> {code:java}
> User-Agent: Java/12.0.2
> {code}
> and another bann message:
> {code:java}
> You don't have permission to access /kit/reflector on this server.
> {code}
> Exists a quick solution that my local Archiva could run (again), maybe without using _www.terracotta.org_?
> Thanks, cu.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)