I understand that, but the problem ist that when I am logging an issue that
happens only with Jersey, they will reply that it propably is a Jersey
issue. so what to do? Maybe it is easier if you log the issue so they
understand that you already checked that it is not Jersey's fault?
From: Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
Sent: Donnerstag, 24. September 2009 11:01
To: users_at_jersey.dev.java.net
Subject: Re: [Jersey] Getting nuts with hangs in Client API
On Sep 8, 2009, at 9:48 AM, Markus KARG wrote:
Paul,
thank you for your tips and have nice holidays! Just came back from a great
short trip to Vienna, so if you don't know where to go to. ;-)
:-)
The idea with a 10 minutes sleep didn't help. :-(
Changing to Grizzly works well (but one really must give the package to scan
or Jersey will tell you that
"C:\C:\jersey-archive-1.0.3.1\lib\jsr311-api-1.0.jar, is not a jar file")!
:-)
Ug, that looks like a silly windows bug. We will investigate.
So I assume that there is a bug in the http server used internally by
Jersey, and there is a bug in Jersey's ClassPath scanner (it seems to add
another C:\ to each JAR if not giving a package to scan).
For my presentation, this should work. But maybe you like to have a look
into the the above items after your holidays? :-)
OK.
I have wasted way too much time with the LW HTTP server and its issues! In
my experience it is not stable on windows. I can only suggest logging an
issue against the JDK.
Paul.