You do not need to delete it, just zap its caches - it is one of the actions
available for an admin user when selecting the repository in the UI from the
tree browser (see:
http://wiki.jfrog.org/confluence/display/RTF20/Managing+Caches).
In your configuration negative lookups will be cached for 12 hours (43200
secs), so I doubt it if these caches are still effective for artifacts not
found before.
Try to issue a get request for an artifact via curl or via a browser and see
what happens (e.g.: http://host:port
/artifactory/maven2/ant/ant/1.7.0/ant-1.7.0.pom).
If you can get your system admin to verify that your proxy is indeed
contacted by Artifactory and inspect how incoming requests are being
handled, that would be the most helpful, I think.
On Fri, Apr 22, 2011 at 10:33 PM, pradeep <[email protected]> wrote:
> Thanks for looking into it.
>
> Here is the configuration for remote repository.
>
> <remoteRepository>
> <key>maven2</key>
> <type>maven2</type>
> <includesPattern>**/*</includesPattern>
> <blackedOut>false</blackedOut>
> <handleReleases>true</handleReleases>
> <handleSnapshots>true</handleSnapshots>
> <maxUniqueSnapshots>0</maxUniqueSnapshots>
>
> <suppressPomConsistencyChecks>false</suppressPomConsistencyChecks>
> <propertySets/>
> <url>http://repo1.maven.org/maven2/</url>
> <offline>false</offline>
> <hardFail>false</hardFail>
> <storeArtifactsLocally>true</storeArtifactsLocally>
> <fetchJarsEagerly>false</fetchJarsEagerly>
> <fetchSourcesEagerly>false</fetchSourcesEagerly>
> <retrievalCachePeriodSecs>43200</retrievalCachePeriodSecs>
>
> <failedRetrievalCachePeriodSecs>30</failedRetrievalCachePeriodSecs>
>
> <missedRetrievalCachePeriodSecs>43200</missedRetrievalCachePeriodSecs>
>
>
> <remoteRepoChecksumPolicyType>generate-if-absent</remoteRepoChecksumPolicyType>
>
> <unusedArtifactsCleanupEnabled>false</unusedArtifactsCleanupEnabled>
>
> <unusedArtifactsCleanupPeriodHours>0</unusedArtifactsCleanupPeriodHours>
> <shareConfiguration>false</shareConfiguration>
> <synchronizeProperties>false</synchronizeProperties>
> <socketTimeoutMillis>15000</socketTimeoutMillis>
> <proxyRef>corp.proxy:port</proxyRef>
> </remoteRepository>
>
> This repo is empty for now. Do I still delete it to remove negative look
> ups?
>
> >From the log messages in the original post, it seems to be accessing the
> proxy(When no credentials were specified errors were different).
>
>
>
> --
> View this message in context:
> http://forums.jfrog.org/could-not-get-artifacts-from-central-Required-credentials-not-available-for-BASIC-any-realm-repo1-ma0-tp6291153p6297956.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
