rschlege's Profile

Recent activity

Subscribe to this feed

rschlege reported a problem in Sonatype on January 20, 2009 14:55:

SSL problem when accessing the jsr144 repository
I am using the jsr144 Maven repository with this configuration:

This used to work. But when I try to access https://jsr144-public.dev.java.net/ossj/jsr144/oss_cbe_party_ri/1.5/oss_cbe_party_ri-1.5.jar it's not stored in the proxy.

(Note: the jsr144 repository was a workaround and doesn't support browsing, but allows to access the jar's directly)

The log reports:
INFO | jvm 1 | 2009/01/20 15:33:00 | 2009-01-20 15:33:00,535 INFO [org.apache.commons.httpclient.HttpMethodDirector] - I/O exception (javax.net.ssl.SSLException) caught when processing request: java.security.ProviderException: Could not obtain session
INFO | jvm 1 | 2009/01/20 15:33:00 | 2009-01-20 15:33:00,535 INFO [org.apache.commons.httpclient.HttpMethodDirector] - Retrying request
INFO | jvm 1 | 2009/01/20 15:33:05 | 2009-01-20 15:33:05,073 WARN [org.apache.commons.httpclient.HttpMethodBase] - Cookie rejected: "$Version=0; JSESSIONID=A7205677043546B3D05431A5E1252F51; $Path=/servlets". Illegal path attribute "/servlets". Path of origin: "/"
rschlege replied on October 09, 2008 15:01 to the problem "Very bad performance for large artifacts" in Sonatype:

Added a respective sub-task: http://issues.sonatype.org/browse/NEX...

Do you think this solves the problem? Mark it as solved
rschlege replied on October 07, 2008 11:38 to the problem "Very bad performance for large artifacts" in Sonatype:

Tried now nexus with jetty 6.1.12.rc2 which fixes JETTY-681
Result: better performance (around factor 2), but still quite slow compared to solaris installation.

Do you think this solves the problem? Mark it as solved
rschlege replied on October 01, 2008 15:52 to the problem "Very bad performance for large artifacts" in Sonatype:

Not sure if this could have something to do with it: http://jira.codehaus.org/browse/JETTY...
(nexus is using jetty 6.1.11)

One more interesting point: when using my private Notebook as a client connecting to the nexus webapp, the speed is fine! Thus seems only to be a problem if windows is on both sides, and only in special cases. Very strange...

Do you think this solves the problem? Mark it as solved
rschlege replied on September 24, 2008 17:14 to the problem "Very bad performance for large artifacts" in Sonatype:

Tried now on my Win XP box at home and on that one it runs just fine! I'll try to find out which tool interferes with Nexus and post it here if I have the solution.

Do you think this solves the problem? Mark it as solved
rschlege replied on September 24, 2008 13:19 to the problem "Very bad performance for large artifacts" in Sonatype:

That was my thought initially as well, but then I tried over http from the webapp folder and that's very fast, no problem. And additionally, there is no CPU usage which might indicate virus scanner or anything! Tried also from my local machine to my neighbours to avoid any firewall and that's very slow as well! It really must be something about Windows I believe, especially because it's fine if I run nexus on Solaris and stream over the same network.

Did you try with windows?

Do you think this solves the problem? Mark it as solved
A comment on the problem "Very bad performance for large artifacts" in Sonatype:

When using localhost I don't see the problem either, only from a different machine (see below or issue 812) – rschlege, on September 24, 2008 11:29
A comment on the problem "Very bad performance for large artifacts" in Sonatype:

Is 192.168.101.21 your own machine? If yes, could you please try from a different machine?
When I login on the machine where nexus is running and use the own IP it's very fast as well, only from a different machine it's really slow! – rschlege, on September 24, 2008 11:28
rschlege replied on September 18, 2008 12:23 to the problem "Very bad performance for large artifacts" in Sonatype:

At least it seams to take some thinking now... :-)

Do you think this solves the problem? Mark it as solved
rschlege replied on September 18, 2008 06:56 to the problem "Very bad performance for large artifacts" in Sonatype:

Did now the same Tamas did -> placed the artifact into the webapp folder and downloaded it from there http://nexusserver:8081/nexus/large-a...
Speed: 5.3MB/s

Do you think this solves the problem? Mark it as solved
rschlege replied on September 18, 2008 06:35 to the problem "Very bad performance for large artifacts" in Sonatype:

Tried now also with
java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

Exactly the same bad performance!

Could it be somehow because of M$?

Note: I realize the performance is bad in general, not only for large artifacts. When downloading one with 300KB it takes long enough for the browser to display the bandwith with 230KB/s.

Do you think this solves the problem? Mark it as solved
rschlege replied on September 18, 2008 06:27 to the problem "Very bad performance for large artifacts" in Sonatype:

java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Just checked Task manager: doesn't show any change while downloading other than 1% CPU usage for java.exe for just the blink of an eye.

Machine:
Windows Server 2003 Standard Edition
Intel Core 2 Duo 2.4GHz
2GB RAM

Change in wrapper.conf:
# Maximum Java Heap Size (in MB) wrapper.java.maxmemory=256

Do you think this solves the problem? Mark it as solved
rschlege replied on September 17, 2008 15:52 to the problem "Very bad performance for large artifacts" in Sonatype:

Alright, installed XAMPP now and configured it to use the nexus working directory. After that I navigated to the large artifact, and guess what, I didn't even see it downloading because it was so fast.
To be sure, I deleted the Browser cache and tried again -> less than 1 second!

Any ideas?

Thanks

Do you think this solves the problem? Mark it as solved
rschlege replied on September 17, 2008 15:36 to the problem "Very bad performance for large artifacts" in Sonatype:

Thanks for your answer.

Didn't try apache, but I have also an MS IIS instance running. That one provides pretty much the same bandwith over http like file:/// does.

Anyway, I think Nexus is quite fast in looking up the artifact, but has problems streaming it over the network. Hard to believe that 260KB/s is the maximum commons http manages to stream over a 100Mbps network. btw.: CPU usage on the server is at 1% while streaming.

Would you expect Apache httpd less performant than IIS?

Do you think this solves the problem? Mark it as solved
rschlege replied on September 17, 2008 15:03 to the problem "Very bad performance for large artifacts" in Sonatype:

Just compared download performance with a Browser:
- through the nexus url: ~260KB/s and falling to 130KB/s
- through the file url: ~4.7MB/s

both are on the same server!
Any idea?

Do you think this solves the problem? Mark it as solved
rschlege replied on September 17, 2008 14:40 to the problem "Very bad performance for large artifacts" in Sonatype:

Thanks for the quick answer!

I Just did this a second time:
- checked if it is in the nexus cache
- mvn clean my project
- moved my local repository to ~/.m2/repository_old
- mvn install
--> it took 22 seconds again for the large artifact!

Do you think this solves the problem? Mark it as solved
rschlege reported a problem in Sonatype on September 17, 2008 13:59:

Very bad performance for large artifacts
Since using Nexus I noticed mvn install is very slow compared to direct connections, Even if I have to define several repositories it's still faster than using the repository group from nexus. wouldn't be a problem if it was just a few %, but think about this:
5MB Artifact download through http://nexusserver:8081/nexus/content.... : ~22sec
5MB Artifact download through file:///\\nexusserver\contents_share\... : ~1sec

rschlege's dashboard

About me

Recent activity