Issue with cached artifacts in proxy repository

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with cached artifacts in proxy repository

Kiesswetter, Reinhard
Hi Nexus Users,

We experienced a strange issue with a proxied repository in regard of delivering already cached artifacts. The remote repository is not to stable and so goes off-line once in a while, but according to the documentation this should not hold our Nexus from serving artifacts which are already available in its cache, but this is what happens, when the remote repository is in state "out of service".

The remote repository is a release repository and our expiration settings for the proxy repository are the default ones:

Not Found Cache TTL:     1440 minutes
Artifact Max Age:    -1 minutes
Metadata Max Age:    1440 minutes
Item Max Age:    1440 minutes

The proxy repository is included in a group and this group is used by Maven in the settings.xml.

Currently we are on Nexus OSS version 2.6.3-01

My question is, does anyone experiance a simmilar issue or do we have a config issue?

Another question is about the Metadata Max Age: If the Max Age is reached and the remote repo is down are the metadata information kept until the remote repo is reachable again or are they deleted from the cache?

Thanks a lot
Reinhard


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
Reply | Threaded
Open this post in threaded view
|

Re: Issue with cached artifacts in proxy repository

Tamás Cservenák
Hi Reinhard,

I did not quite get the problem, what is happening on your instance?

About md max age: no cached item should be removed unless a new one is found remotely. So, the cached one should be served even if remote is auto/manual blocked.


Thanks,
~t~


On Thu, Dec 19, 2013 at 10:43 AM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Nexus Users,

We experienced a strange issue with a proxied repository in regard of delivering already cached artifacts. The remote repository is not to stable and so goes off-line once in a while, but according to the documentation this should not hold our Nexus from serving artifacts which are already available in its cache, but this is what happens, when the remote repository is in state "out of service".

The remote repository is a release repository and our expiration settings for the proxy repository are the default ones:

Not Found Cache TTL:     1440 minutes
Artifact Max Age:    -1 minutes
Metadata Max Age:    1440 minutes
Item Max Age:    1440 minutes

The proxy repository is included in a group and this group is used by Maven in the settings.xml.

Currently we are on Nexus OSS version 2.6.3-01

My question is, does anyone experiance a simmilar issue or do we have a config issue?

Another question is about the Metadata Max Age: If the Max Age is reached and the remote repo is down are the metadata information kept until the remote repo is reachable again or are they deleted from the cache?

Thanks a lot
Reinhard


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

Reply | Threaded
Open this post in threaded view
|

AW: [nexus-user] Issue with cached artifacts in proxy repository

Kiesswetter, Reinhard
Hi Tamas,

thx for the reply.

When running a Maven build when the repo is marked as  "out of service" due to auto blocking (remote is down) we get an error saying "Could not find artifact ..." although the artifact was already cached and is served when the remote repo is up.

thx
Reinhard

Von: [hidden email] [[hidden email]]" im Auftrag von "Tamás Cservenák [[hidden email]]
Gesendet: Donnerstag, 19. Dezember 2013 12:18
An: [hidden email]
Betreff: Re: [nexus-user] Issue with cached artifacts in proxy repository

Hi Reinhard,

I did not quite get the problem, what is happening on your instance?

About md max age: no cached item should be removed unless a new one is found remotely. So, the cached one should be served even if remote is auto/manual blocked.


Thanks,
~t~


On Thu, Dec 19, 2013 at 10:43 AM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Nexus Users,

We experienced a strange issue with a proxied repository in regard of delivering already cached artifacts. The remote repository is not to stable and so goes off-line once in a while, but according to the documentation this should not hold our Nexus from serving artifacts which are already available in its cache, but this is what happens, when the remote repository is in state "out of service".

The remote repository is a release repository and our expiration settings for the proxy repository are the default ones:

Not Found Cache TTL:     1440 minutes
Artifact Max Age:    -1 minutes
Metadata Max Age:    1440 minutes
Item Max Age:    1440 minutes

The proxy repository is included in a group and this group is used by Maven in the settings.xml.

Currently we are on Nexus OSS version 2.6.3-01

My question is, does anyone experiance a simmilar issue or do we have a config issue?

Another question is about the Metadata Max Age: If the Max Age is reached and the remote repo is down are the metadata information kept until the remote repo is reachable again or are they deleted from the cache?

Thanks a lot
Reinhard


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
Reply | Threaded
Open this post in threaded view
|

Re: Issue with cached artifacts in proxy repository

Tamás Cservenák
This sounds like a bug,
Could you please create an issue in NEXUS [1] and provide a reproduce scenario?


Thanks
~t~


On Thu, Dec 19, 2013 at 12:33 PM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Tamas,

thx for the reply.

When running a Maven build when the repo is marked as  "out of service" due to auto blocking (remote is down) we get an error saying "Could not find artifact ..." although the artifact was already cached and is served when the remote repo is up.

thx
Reinhard

Von: [hidden email] [[hidden email]]" im Auftrag von "Tamás Cservenák [[hidden email]]
Gesendet: Donnerstag, 19. Dezember 2013 12:18
An: [hidden email]
Betreff: Re: [nexus-user] Issue with cached artifacts in proxy repository

Hi Reinhard,

I did not quite get the problem, what is happening on your instance?

About md max age: no cached item should be removed unless a new one is found remotely. So, the cached one should be served even if remote is auto/manual blocked.


Thanks,
~t~


On Thu, Dec 19, 2013 at 10:43 AM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Nexus Users,

We experienced a strange issue with a proxied repository in regard of delivering already cached artifacts. The remote repository is not to stable and so goes off-line once in a while, but according to the documentation this should not hold our Nexus from serving artifacts which are already available in its cache, but this is what happens, when the remote repository is in state "out of service".

The remote repository is a release repository and our expiration settings for the proxy repository are the default ones:

Not Found Cache TTL:     1440 minutes
Artifact Max Age:    -1 minutes
Metadata Max Age:    1440 minutes
Item Max Age:    1440 minutes

The proxy repository is included in a group and this group is used by Maven in the settings.xml.

Currently we are on Nexus OSS version 2.6.3-01

My question is, does anyone experiance a simmilar issue or do we have a config issue?

Another question is about the Metadata Max Age: If the Max Age is reached and the remote repo is down are the metadata information kept until the remote repo is reachable again or are they deleted from the cache?

Thanks a lot
Reinhard


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

Reply | Threaded
Open this post in threaded view
|

Re: Issue with cached artifacts in proxy repository

Brian Fox
In reply to this post by Kiesswetter, Reinhard
Out of service is a different state than manually and automatically blocked. Are you sure something else isn't putting the repo oos?


On Thu, Dec 19, 2013 at 6:33 AM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Tamas,

thx for the reply.

When running a Maven build when the repo is marked as  "out of service" due to auto blocking (remote is down) we get an error saying "Could not find artifact ..." although the artifact was already cached and is served when the remote repo is up.

thx
Reinhard

Von: [hidden email] [[hidden email]]" im Auftrag von "Tamás Cservenák [[hidden email]]
Gesendet: Donnerstag, 19. Dezember 2013 12:18
An: [hidden email]
Betreff: Re: [nexus-user] Issue with cached artifacts in proxy repository

Hi Reinhard,

I did not quite get the problem, what is happening on your instance?

About md max age: no cached item should be removed unless a new one is found remotely. So, the cached one should be served even if remote is auto/manual blocked.


Thanks,
~t~


On Thu, Dec 19, 2013 at 10:43 AM, Kiesswetter, Reinhard <[hidden email]> wrote:
Hi Nexus Users,

We experienced a strange issue with a proxied repository in regard of delivering already cached artifacts. The remote repository is not to stable and so goes off-line once in a while, but according to the documentation this should not hold our Nexus from serving artifacts which are already available in its cache, but this is what happens, when the remote repository is in state "out of service".

The remote repository is a release repository and our expiration settings for the proxy repository are the default ones:

Not Found Cache TTL:     1440 minutes
Artifact Max Age:    -1 minutes
Metadata Max Age:    1440 minutes
Item Max Age:    1440 minutes

The proxy repository is included in a group and this group is used by Maven in the settings.xml.

Currently we are on Nexus OSS version 2.6.3-01

My question is, does anyone experiance a simmilar issue or do we have a config issue?

Another question is about the Metadata Max Age: If the Max Age is reached and the remote repo is down are the metadata information kept until the remote repo is reachable again or are they deleted from the cache?

Thanks a lot
Reinhard


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.


INFONOVA GmbH
Sitz: Unterpremstätten bei Graz
Firmenbuchgericht: Landesgericht für ZRS Graz
Firmenbuchnummer: FN 44354b


The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.