You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Viktor Nordling (JIRA)" <ji...@codehaus.org> on 2009/08/31 14:15:41 UTC
[jira] Commented: (MRM-588) proxy logging is not always effective
for diagnosing issues
[ http://jira.codehaus.org/browse/MRM-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189215#action_189215 ]
Viktor Nordling commented on MRM-588:
-------------------------------------
Maybe off topic, but I think logging which remote URL Archiva is _about_ to request would be immensely helpful.
We are having problems where Archiva hangs forever, so we never see the connection error in the log, which makes figuring out which remote repository is causing the problem very difficult.
We are using 1.1.3.
> proxy logging is not always effective for diagnosing issues
> -----------------------------------------------------------
>
> Key: MRM-588
> URL: http://jira.codehaus.org/browse/MRM-588
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.0-beta-4
> Reporter: Brett Porter
> Fix For: 1.x
>
>
> I would like to open discussion for what exactly needs to be logged, and at what level, for proxy issues to be effectively diagnosed. With the current configuration, I was unable to pinpoint some problems easily.
> Some thoughts:
> - don't talk about policies, but state what is happening
> - always include the artifact and repository requested
> - log more if it results in a NotFoundException
> - condense information onto fewer lines where possible (if there are concurrent requests, without an NDC these will start getting mixed up in the logs)
> Here are my thoughts:
> DEBUG Artifact [x/y/z.jar] will not be requested from remote repository [foo] as it didn't match whitelist items
> DEBUG Artifact [x/y/z.jar] will not be requested from remote repository [foo] as it matched blacklist item x/**
> INFO Artifact [x/y/z.jar] requested from managed repository [internal], checking remote repositories [central,java.net], excluding remote repositories [foo]
> Then:
> INFO Artifact [x/y/z.jar] retrieved from remote repository [central], skipping others
> or
> INFO Artifact [x/y/z.jar] not retrieved as it failed post-download policy [bar-policy] (include reason)
> And so on...
> Thoughts?
> An open question is what level to log this at: I feel that it should be at INFO, but that might be too noisy by default. Perhaps the right thing to do here is to add a connector configuration property that says whether to log all requests (and if not, only log at debug level).
--
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