You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Andreas Baumann (JIRA)" <ji...@codehaus.org> on 2010/03/12 14:30:24 UTC
[jira] Created: (MRM-1363) Behaviour of multiple proxy connectors,
persistence of configuration
Behaviour of multiple proxy connectors, persistence of configuration
--------------------------------------------------------------------
Key: MRM-1363
URL: http://jira.codehaus.org/browse/MRM-1363
Project: Archiva
Issue Type: Bug
Affects Versions: 1.3
Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
Reporter: Andreas Baumann
Priority: Critical
Situation, I configured two proxy connectors:
central
Central Repository
http://repo1.maven.org/maven2
Return error when: always
Cache failures: no
Releases: always
On remote error: queue error
Checksum: fix
Snapshots: never
followed by:
maven2-repository.dev.java.net
Java.net Repository for Maven 2
http://download.java.net/maven/2/
Return error when: always
Cache failures: no
Releases: always
On remote error: stop
Checksum: fix
Snapshots: never
Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
tried (I see that in the network proxy squid), the second never (though I
understand the 'queue error' should do that).
Some remarks:
- I don't see any code which actually handles the 'queue error' case (policies in
the configuration parser)
- At least the 'On remote error' setting is not persistet in the XML configuration
file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Andreas Baumann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214471#action_214471 ]
Andreas Baumann commented on MRM-1363:
--------------------------------------
Ok. Adding "rome/rome/**" to the second proxy connector does the job. Problem
solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Andreas Baumann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214449#action_214449 ]
Andreas Baumann commented on MRM-1363:
--------------------------------------
Yes, you are right. I forgot to add 'rome' there. The
problem is just doing that for evey new artifact is
not so nice.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1363) Behaviour of multiple proxy connectors,
persistence of configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1363:
------------------------------
Fix Version/s: Backlog
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214433#action_214433 ]
Brett Porter commented on MRM-1363:
-----------------------------------
Is this the default configuration, or have you customised it? The Java.NET repository is configured only to handle javax/** requests by default in its whitelist.
I'll file this in the backlog to investigate the configuration saving problems.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214450#action_214450 ]
Brett Porter commented on MRM-1363:
-----------------------------------
you can do it for whole groups, of which you probably only trust a few from that repo. Given the status of the metadata in that repository, it pays to be selective - and from what I understand it will be in central soon enough that we won't need to worry about it.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Andreas Baumann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214471#action_214471 ]
Andreas Baumann edited comment on MRM-1363 at 3/20/10 7:37 AM:
---------------------------------------------------------------
Ok. Adding "rome/rome/**" to the white list the second proxy connector does the job.
Problem solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
was (Author: andreas_baumann):
Ok. Adding "rome/rome/**" to the second proxy connector does the job. Problem
solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-1363) Behaviour of multiple proxy connectors,
persistence of configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1363.
-----------------------------
Resolution: Not A Bug
Fix Version/s: (was: Backlog)
Behaving as expected - resolving
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: https://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRM-1363) Behaviour of multiple proxy
connectors, persistence of configuration
Posted by "Andreas Baumann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214471#action_214471 ]
Andreas Baumann edited comment on MRM-1363 at 3/20/10 7:37 AM:
---------------------------------------------------------------
Ok. Adding "rome/rome/**" to the white list of the second proxy connector does the job.
Problem solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
was (Author: andreas_baumann):
Ok. Adding "rome/rome/**" to the white list the second proxy connector does the job.
Problem solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML configuration
> file, because it's back to default if I restart archiva.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira