We are using 1.1-M4 release when we stumbled across what seems to be a
similar problem (stack trace below). The thread basically blocks
indefinitely. If it is the same problem is there a fix for the v1.1.6.
We are currently in the process of upgrading to the latest stable
1.1.X version.
"Observant.Dispatcher" daemon prio=6 tid=0x036f5800 nid=0x122c
runnable [0x0453f000..0x0453fc94]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
- locked <0x227fc9a0> (a java.io.BufferedInputStream)
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:
323)
at
com
.noelios
.restlet.ext.httpclient.HttpMethodCall.sendRequest(HttpMethodCall.java:
285)
at
com
.noelios
.restlet.http.HttpClientConverter.commit(HttpClientConverter.java:101)
at
com.noelios.restlet.http.HttpClientHelper.handle(HttpClientHelper.java:
79)
at org.restlet.Client.handle(Client.java:134)
at org.restlet.Uniform.handle(Uniform.java:95)
at
au
.com
.observant
.ringocore
.clientapi
.http
.HttpRingoCoreDispatcherClient.post(HttpRingoCoreDispatcherClient.java:
115)
at
au
.com
.observant
.ringocore
.clientapi
.http
.HttpRingoCoreDispatcherClient.post(HttpRingoCoreDispatcherClient.java:
102)
at
au
.com
.observant
.ringocore
.dispatcher
.dequeue.ZoneDequeueStrategy.dequeue(ZoneDequeueStrategy.java:78)
at
au
.com
.observant
.ringocore
.dispatcher
.dequeue.DispatcherQueueConsumer.process(DispatcherQueueConsumer.java:
197)
at
au
.com
.observant
.ringocore
.dispatcher.dequeue.DispatcherService.run(DispatcherService.java:245)
at java.lang.Thread.run(Unknown Source)
cheers
</jima>
On 08/10/2009, at 9:06 PM, Evgeny Shepelyuk wrote:
> Hello,
> I'm using JDK6 and restlet 2.0m3 / 2.0m5.
> Yes, i have found this issue during debug. The parameters are set, but
> getHelper().getXXX doesn't return parameters, i've used while creating
> client.
> Instead it returns zero.
>
> My code looks like
>
> Client client = new Client(Protocol.HTTP);
>
> Context ctx = new Context();
> ctx.getParameters().add("readTimeout", "5000");
>
> client.setContext(ctx);
> client.setConnectTimeout("5000");
>
> And regarding to some internal app limitations i can't create client
> with
> context passed as constructor argument.
> So it should be processed in the order i've shown above.
>
>
>> Hi Evgeny,
>>
>> Looking at the code in SVN trunk, we do set the property, but only if
>> Java >
>> 1.5:
>>
>> // These properties can only be used with Java 1.5 and
>> upper
>> // releases
>> int majorVersionNumber =
>> SystemUtils.getJavaMajorVersion();
>> int minorVersionNumber =
>> SystemUtils.getJavaMinorVersion();
>> if ((majorVersionNumber > 1)
>> || ((majorVersionNumber == 1) &&
>> (minorVersionNumber
>>> =
>> 5))) {
>> this.connection.setConnectTimeout(getHelper()
>> .getConnectTimeout());
>> this.connection.setReadTimeout(getHelper().getReadTimeout());
>> }
>>
>> Which version are you using? Could you debug the Restlet code to
>> see if
>> it
>> steps into this section (see
>> org.restlet.ext.net.internal.HttpUrlConnectionCall's constructor).
>>
>> Best regards,
>> Jerome Louvel
>> --
>> Restlet ~ Founder and Lead developer ~ http://www.restlet.org
>> Noelios Technologies ~ Co-founder ~ http://www.noelios.com
>>
>>
>>
>> -----Message d'origine-----
>> De : news [mailto:n...@ger.gmane.org] De la part de Evgeny Shepelyuk
>> Envoyé : mercredi 7 octobre 2009 14:56
>> À : discuss@restlet.tigris.org
>> Objet : UrlConneciton based HTTP client tiimeouts
>>
>> Hello,
>>
>> While trying to set connection timeouts for HTTP client based based
>> on
>> org.restlet.ext.net extension
>> i've noticed that connectTimeout is not taken into acctount
>> parameter id
>> not set into underlying conneciton)
>> when performing request
>>
>> I've used 2.0m3 and 2.0m5 versions of Restlet.
>>
>
>
> --
> Regards,
> Evgeny Shepelyuk
>
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2404882
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2407845
