Re: Problem reaching central behind corporate proxy
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
|
|
|
RE: Problem reaching central behind corporate proxy
by Matthew Jaskula
::
Rate this Message:
Thanks for the quick reply Brian. It's not only the index, it just seemed like a good way to test. Here's an example of what we are seeing from a build:
Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-clean-plugin Version: 2.2 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-clean-plugin:pom:2.2 from the specified remote repositories: group-mirror (http://gambit/nexus/content/groups/public-eng/) I can download the index through the proxy, in firefox, from s3, so I don't think it is the proxy blocking, at least not in that way. What else can I try? Matthew Jaskula Engineer NYSE Technologies 100 Wall Street, 3rd Floor New York, New York 10005 United States t +1.212.510.3629 mjaskula@... NYSE Euronext Powering the Exchanging World www.nyse.com/technologies ________________________________________ From: Brian Fox [brianf@...] Sent: Friday, October 23, 2009 11:24 AM To: Matthew Jaskula Cc: nexus-user Subject: Re: Problem reaching central behind corporate proxy Is it just the index that isn't working or everyting? The index is actually stored on s3, so central does a redirect. If your proxy doesn't allow s3 or follow redirects, that could explain the index issue you now see. On Fri, Oct 23, 2009 at 11:16 AM, Matthew Jaskula <mjaskula@...> wrote: > Hi all, I tried searching but couldn't find an answer to this issue. > > We've recently moved our nexus server behind the corporate web proxy and can no longer communicate with central. We configured our proxy under Server -> Default HTTP Proxy Settings, our proxy does not use authentication. We are getting the following error when trying to download indexes. > > 2009-10-22 14:45:21 WARN [pool-1-thread-3] - o.s.n.i.IndexerMana~:default - Cannot fetch remote index: > org.sonatype.nexus.proxy.StorageException: Tranport error while executing GET method > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:512) > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.retrieveItem(CommonsHttpClientRemoteStorage.java:133) > at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:699) > at org.sonatype.nexus.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:178) > at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:103) > at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:731) > at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:603) > at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:570) > at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryGroupIndex(DefaultIndexerManager.java:549) > at org.sonatype.nexus.DefaultNexus.downloadRepositoryGroupIndex(DefaultNexus.java:1352) > at org.sonatype.nexus.tasks.DownloadIndexesTask.doRun(DownloadIndexesTask.java:45) > at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:139) > at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:342) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) > at java.io.BufferedInputStream.read(BufferedInputStream.java:237) > at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78) > at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106) > at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413) > at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973) > at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735) > at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:483) > ... 19 more > > We can reach central through the same proxy on a desktop machine, so I don't think it's an issue with the proxy. More likely a config issue somewhere locally. > > Not sure what to try next, or what other information would be helpful in debugging. > > Thanks in advance. > > Matthew Jaskula > Engineer > NYSE Technologies > 100 Wall Street, 3rd Floor > New York, New York 10005 > United States > t +1.212.510.3629 > mjaskula@... > NYSE Euronext > Powering the Exchanging World > www.nyse.com/technologies > > > Visit our website at http://www.nyse.com > > **************************************************** > > Note: The information contained in this message and any attachment > to it is privileged, confidential and protected from disclosure. If the > reader of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify the > sender immediately by replying to the message, and please delete > it from your system. Thank you. NYSE Euronext, Inc. > > Visit our website at http://www.nyse.com **************************************************** Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Problem reaching central behind corporate proxy
by Brian Fox
::
Rate this Message:
Try simply making the request against the repository url instead. so
for example: http://gambit/nexus/content/repositories/central/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom If that doesn't work, right click the repo and expire the cache and try again. If that still doesn't work, then something external is blocking the request. If it does work but doesn't work on the group url after making the request, then the repo isn't in the group or there is a routing rule excluding this repo. If it does work from the group, then clean your local repo and then try maven again. On Fri, Oct 23, 2009 at 1:27 PM, Matthew Jaskula <mjaskula@...> wrote: > Thanks for the quick reply Brian. It's not only the index, it just seemed like a good way to test. Here's an example of what we are seeing from a build: > > Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom > Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom > [INFO] ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > GroupId: org.apache.maven.plugins > ArtifactId: maven-clean-plugin > Version: 2.2 > > Reason: Unable to download the artifact from any repository > > org.apache.maven.plugins:maven-clean-plugin:pom:2.2 > > from the specified remote repositories: > group-mirror (http://gambit/nexus/content/groups/public-eng/) > > > I can download the index through the proxy, in firefox, from s3, so I don't think it is the proxy blocking, at least not in that way. What else can I try? > > Matthew Jaskula > Engineer > NYSE Technologies > 100 Wall Street, 3rd Floor > New York, New York 10005 > United States > t +1.212.510.3629 > mjaskula@... > NYSE Euronext > Powering the Exchanging World > www.nyse.com/technologies > ________________________________________ > From: Brian Fox [brianf@...] > Sent: Friday, October 23, 2009 11:24 AM > To: Matthew Jaskula > Cc: nexus-user > Subject: Re: Problem reaching central behind corporate proxy > > Is it just the index that isn't working or everyting? The index is > actually stored on s3, so central does a redirect. If your proxy > doesn't allow s3 or follow redirects, that could explain the index > issue you now see. > > On Fri, Oct 23, 2009 at 11:16 AM, Matthew Jaskula <mjaskula@...> wrote: >> Hi all, I tried searching but couldn't find an answer to this issue. >> >> We've recently moved our nexus server behind the corporate web proxy and can no longer communicate with central. We configured our proxy under Server -> Default HTTP Proxy Settings, our proxy does not use authentication. We are getting the following error when trying to download indexes. >> >> 2009-10-22 14:45:21 WARN [pool-1-thread-3] - o.s.n.i.IndexerMana~:default - Cannot fetch remote index: >> org.sonatype.nexus.proxy.StorageException: Tranport error while executing GET method >> at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:512) >> at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.retrieveItem(CommonsHttpClientRemoteStorage.java:133) >> at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:699) >> at org.sonatype.nexus.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:178) >> at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:103) >> at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:731) >> at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:603) >> at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:570) >> at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryGroupIndex(DefaultIndexerManager.java:549) >> at org.sonatype.nexus.DefaultNexus.downloadRepositoryGroupIndex(DefaultNexus.java:1352) >> at org.sonatype.nexus.tasks.DownloadIndexesTask.doRun(DownloadIndexesTask.java:45) >> at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:139) >> at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:342) >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) >> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) >> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:619) >> Caused by: java.net.SocketTimeoutException: Read timed out >> at java.net.SocketInputStream.socketRead0(Native Method) >> at java.net.SocketInputStream.read(SocketInputStream.java:129) >> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) >> at java.io.BufferedInputStream.read(BufferedInputStream.java:237) >> at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78) >> at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106) >> at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116) >> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413) >> at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973) >> at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735) >> at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098) >> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) >> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) >> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) >> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) >> at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:483) >> ... 19 more >> >> We can reach central through the same proxy on a desktop machine, so I don't think it's an issue with the proxy. More likely a config issue somewhere locally. >> >> Not sure what to try next, or what other information would be helpful in debugging. >> >> Thanks in advance. >> >> Matthew Jaskula >> Engineer >> NYSE Technologies >> 100 Wall Street, 3rd Floor >> New York, New York 10005 >> United States >> t +1.212.510.3629 >> mjaskula@... >> NYSE Euronext >> Powering the Exchanging World >> www.nyse.com/technologies >> >> >> Visit our website at http://www.nyse.com >> >> **************************************************** >> >> Note: The information contained in this message and any attachment >> to it is privileged, confidential and protected from disclosure. If the >> reader of this message is not the intended recipient, or an employee >> or agent responsible for delivering this message to the intended >> recipient, you are hereby notified that any dissemination, >> distribution or copying of this communication is strictly prohibited. >> If you have received this communication in error, please notify the >> sender immediately by replying to the message, and please delete >> it from your system. Thank you. NYSE Euronext, Inc. >> >> > > > Visit our website at http://www.nyse.com > > **************************************************** > > Note: The information contained in this message and any attachment > to it is privileged, confidential and protected from disclosure. If the > reader of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify the > sender immediately by replying to the message, and please delete > it from your system. Thank you. NYSE Euronext, Inc. > > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: RE: Problem reaching central behind corporate proxy
by Rich Seddon
::
Rate this Message:
Is there any chance that someone can check the corporate proxy logs to
see if Maven is reaching the proxy at all, and if so why it isn't being allowed through? Rich On Oct 23, 2009, at 10:27 AM, Matthew Jaskula wrote: > Thanks for the quick reply Brian. It's not only the index, it just > seemed like a good way to test. Here's an example of what we are > seeing from a build: > > Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom > Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > GroupId: org.apache.maven.plugins > ArtifactId: maven-clean-plugin > Version: 2.2 > > Reason: Unable to download the artifact from any repository > > org.apache.maven.plugins:maven-clean-plugin:pom:2.2 > > from the specified remote repositories: > group-mirror (http://gambit/nexus/content/groups/public-eng/) > > > I can download the index through the proxy, in firefox, from s3, so > I don't think it is the proxy blocking, at least not in that way. > What else can I try? > > Matthew Jaskula > Engineer > NYSE Technologies > 100 Wall Street, 3rd Floor > New York, New York 10005 > United States > t +1.212.510.3629 > mjaskula@... > NYSE Euronext > Powering the Exchanging World > www.nyse.com/technologies > ________________________________________ > From: Brian Fox [brianf@...] > Sent: Friday, October 23, 2009 11:24 AM > To: Matthew Jaskula > Cc: nexus-user > Subject: Re: Problem reaching central behind corporate proxy > > Is it just the index that isn't working or everyting? The index is > actually stored on s3, so central does a redirect. If your proxy > doesn't allow s3 or follow redirects, that could explain the index > issue you now see. > > On Fri, Oct 23, 2009 at 11:16 AM, Matthew Jaskula <mjaskula@...> > wrote: >> Hi all, I tried searching but couldn't find an answer to this issue. >> >> We've recently moved our nexus server behind the corporate web >> proxy and can no longer communicate with central. We configured our >> proxy under Server -> Default HTTP Proxy Settings, our proxy does >> not use authentication. We are getting the following error when >> trying to download indexes. >> >> 2009-10-22 14:45:21 WARN [pool-1-thread-3] - >> o.s.n.i.IndexerMana~:default - Cannot fetch remote index: >> org.sonatype.nexus.proxy.StorageException: Tranport error while >> executing GET method >> at >> org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod >> (CommonsHttpClientRemoteStorage.java:512) >> at >> org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.retrieveItem >> (CommonsHttpClientRemoteStorage.java:133) >> at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve >> (DefaultIndexerManager.java:699) >> at >> org.sonatype.nexus.index.updater.DefaultIndexUpdater.loadIndexDirectory >> (DefaultIndexUpdater.java:178) >> at >> org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex >> (DefaultIndexUpdater.java:103) >> at >> org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex >> (DefaultIndexerManager.java:731) >> at >> org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository >> (DefaultIndexerManager.java:603) >> at >> org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex >> (DefaultIndexerManager.java:570) >> at >> org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryGroupIndex >> (DefaultIndexerManager.java:549) >> at >> org.sonatype.nexus.DefaultNexus.downloadRepositoryGroupIndex >> (DefaultNexus.java:1352) >> at org.sonatype.nexus.tasks.DownloadIndexesTask.doRun >> (DownloadIndexesTask.java:45) >> at org.sonatype.nexus.scheduling.AbstractNexusTask.call >> (AbstractNexusTask.java:139) >> at org.sonatype.scheduling.DefaultScheduledTask.call >> (DefaultScheduledTask.java:342) >> at java.util.concurrent.FutureTask$Sync.innerRun >> (FutureTask.java:303) >> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >> at java.util.concurrent.ScheduledThreadPoolExecutor >> $ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) >> at java.util.concurrent.ScheduledThreadPoolExecutor >> $ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) >> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask >> (ThreadPoolExecutor.java:886) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:619) >> Caused by: java.net.SocketTimeoutException: Read timed out >> at java.net.SocketInputStream.socketRead0(Native Method) >> at java.net.SocketInputStream.read(SocketInputStream.java:129) >> at java.io.BufferedInputStream.fill(BufferedInputStream.java: >> 218) >> at java.io.BufferedInputStream.read(BufferedInputStream.java: >> 237) >> at org.apache.commons.httpclient.HttpParser.readRawLine >> (HttpParser.java:78) >> at org.apache.commons.httpclient.HttpParser.readLine >> (HttpParser.java:106) >> at org.apache.commons.httpclient.HttpConnection.readLine >> (HttpConnection.java:1116) >> at >> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager >> $HttpConnectionAdapter.readLine >> (MultiThreadedHttpConnectionManager.java:1413) >> at org.apache.commons.httpclient.HttpMethodBase.readStatusLine >> (HttpMethodBase.java:1973) >> at org.apache.commons.httpclient.HttpMethodBase.readResponse >> (HttpMethodBase.java:1735) >> at org.apache.commons.httpclient.HttpMethodBase.execute >> (HttpMethodBase.java:1098) >> at >> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry >> (HttpMethodDirector.java:398) >> at >> org.apache.commons.httpclient.HttpMethodDirector.executeMethod >> (HttpMethodDirector.java:171) >> at org.apache.commons.httpclient.HttpClient.executeMethod >> (HttpClient.java:397) >> at org.apache.commons.httpclient.HttpClient.executeMethod >> (HttpClient.java:346) >> at >> org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod >> (CommonsHttpClientRemoteStorage.java:483) >> ... 19 more >> >> We can reach central through the same proxy on a desktop machine, >> so I don't think it's an issue with the proxy. More likely a config >> issue somewhere locally. >> >> Not sure what to try next, or what other information would be >> helpful in debugging. >> >> Thanks in advance. >> >> Matthew Jaskula >> Engineer >> NYSE Technologies >> 100 Wall Street, 3rd Floor >> New York, New York 10005 >> United States >> t +1.212.510.3629 >> mjaskula@... >> NYSE Euronext >> Powering the Exchanging World >> www.nyse.com/technologies >> >> >> Visit our website at http://www.nyse.com >> >> **************************************************** >> >> Note: The information contained in this message and any attachment >> to it is privileged, confidential and protected from disclosure. >> If the >> reader of this message is not the intended recipient, or an employee >> or agent responsible for delivering this message to the intended >> recipient, you are hereby notified that any dissemination, >> distribution or copying of this communication is strictly prohibited. >> If you have received this communication in error, please notify the >> sender immediately by replying to the message, and please delete >> it from your system. Thank you. NYSE Euronext, Inc. >> >> > > > Visit our website at http://www.nyse.com > > **************************************************** > > Note: The information contained in this message and any attachment > to it is privileged, confidential and protected from disclosure. If > the > reader of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify the > sender immediately by replying to the message, and please delete > it from your system. Thank you. NYSE Euronext, Inc. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nexus-user-unsubscribe@... > For additional commands, e-mail: nexus-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
RE: Problem reaching central behind corporate proxy
by Matthew Jaskula
::
Rate this Message:
All,
Thanks for all the help so far. It seems that we actually had two problems here, accessing artifacts on Nexus from maven clients (as shown in the previous message, below), and downloading indexes from public repos. The problem between the Nexus and the client was a configuration error caused by a recent migration and has been solved. The problem accessing the indexes remains open. I will begin the dialogue with our proxy administrators and see if we can find the problem on their end. Thanks. Matthew Jaskula Engineer NYSE Technologies 100 Wall Street, 3rd Floor New York, New York 10005 United States t +1.212.510.3629 mjaskula@... NYSE Euronext Powering the Exchanging World www.nyse.com/technologies ________________________________________ From: Matthew Jaskula Sent: Friday, October 23, 2009 1:27 PM To: Brian Fox Cc: nexus-user Subject: [nexus-user] RE: Problem reaching central behind corporate proxy Thanks for the quick reply Brian. It's not only the index, it just seemed like a good way to test. Here's an example of what we are seeing from a build: Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom Downloading: http://gambit/nexus/content/groups/public-eng//org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-clean-plugin Version: 2.2 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-clean-plugin:pom:2.2 from the specified remote repositories: group-mirror (http://gambit/nexus/content/groups/public-eng/) I can download the index through the proxy, in firefox, from s3, so I don't think it is the proxy blocking, at least not in that way. What else can I try? Matthew Jaskula Engineer NYSE Technologies 100 Wall Street, 3rd Floor New York, New York 10005 United States t +1.212.510.3629 mjaskula@... NYSE Euronext Powering the Exchanging World www.nyse.com/technologies ________________________________________ From: Brian Fox [brianf@...] Sent: Friday, October 23, 2009 11:24 AM To: Matthew Jaskula Cc: nexus-user Subject: Re: Problem reaching central behind corporate proxy Is it just the index that isn't working or everyting? The index is actually stored on s3, so central does a redirect. If your proxy doesn't allow s3 or follow redirects, that could explain the index issue you now see. On Fri, Oct 23, 2009 at 11:16 AM, Matthew Jaskula <mjaskula@...> wrote: > Hi all, I tried searching but couldn't find an answer to this issue. > > We've recently moved our nexus server behind the corporate web proxy and can no longer communicate with central. We configured our proxy under Server -> Default HTTP Proxy Settings, our proxy does not use authentication. We are getting the following error when trying to download indexes. > > 2009-10-22 14:45:21 WARN [pool-1-thread-3] - o.s.n.i.IndexerMana~:default - Cannot fetch remote index: > org.sonatype.nexus.proxy.StorageException: Tranport error while executing GET method > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:512) > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.retrieveItem(CommonsHttpClientRemoteStorage.java:133) > at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:699) > at org.sonatype.nexus.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:178) > at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:103) > at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:731) > at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:603) > at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:570) > at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryGroupIndex(DefaultIndexerManager.java:549) > at org.sonatype.nexus.DefaultNexus.downloadRepositoryGroupIndex(DefaultNexus.java:1352) > at org.sonatype.nexus.tasks.DownloadIndexesTask.doRun(DownloadIndexesTask.java:45) > at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:139) > at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:342) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) > at java.io.BufferedInputStream.read(BufferedInputStream.java:237) > at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78) > at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106) > at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413) > at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973) > at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735) > at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.executeMethod(CommonsHttpClientRemoteStorage.java:483) > ... 19 more > > We can reach central through the same proxy on a desktop machine, so I don't think it's an issue with the proxy. More likely a config issue somewhere locally. > > Not sure what to try next, or what other information would be helpful in debugging. > > Thanks in advance. > > Matthew Jaskula > Engineer > NYSE Technologies > 100 Wall Street, 3rd Floor > New York, New York 10005 > United States > t +1.212.510.3629 > mjaskula@... > NYSE Euronext > Powering the Exchanging World > www.nyse.com/technologies > > > Visit our website at http://www.nyse.com > > **************************************************** > > Note: The information contained in this message and any attachment > to it is privileged, confidential and protected from disclosure. If the > reader of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify the > sender immediately by replying to the message, and please delete > it from your system. Thank you. NYSE Euronext, Inc. > > Visit our website at http://www.nyse.com **************************************************** Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... Visit our website at http://www.nyse.com **************************************************** Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
