Hello,
does anybody have some news about this ?
I have tested with the latest snapshot [2.0 Snapshot (2010-02-09)], but 
with no luck.
Should I create an entry in the bug tracking system ?

Regards,
Laurent.

Le 03/02/2010 14:53, Laurent Rustuel a écrit :
> Hello,
> Still trying to update>  2.0 M6, I used the latest snapshot.
> When I return an empty representation with an Identifier set, I can not
> be found in the client side (object is null)
> See attached file for an eclipse project to reproduce.
>
> Also, since the upgrade, I show in the logs that the port is -1, and I
> don't think it is
> a configuration problem from my application (the same showed the correct
> port in log previously)
>
> INFO: 2010-02-03      14:43:42        127.0.0.1       -       -       -1      
> GET     /test/resource
> someKey=someValue     204     0       0       31      http://localhost:8182
> Restlet-Framework/2.0snapshot -
>
> instead of
> INFO: 2010-02-03      14:47:12        127.0.0.1       -       -       8182    
> GET     /test/resource
> someKey=someValue     200     0       -       31      http://localhost:8182   
> Restlet-Framework/2.0m6 -
>
> Finally, I still got the following, in the server side log, when a
> client connects :
> FIN: Error while reading an HTTP message. Closing the connection.
> java.net.SocketException: Connection reset
>       at java.net.SocketInputStream.read(SocketInputStream.java:168)
>       at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>       at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
>       at
> org.restlet.engine.http.connector.ServerConnection.readMessage(ServerConnection.java:156)
>       at
> org.restlet.engine.http.connector.Connection.readMessages(Connection.java:795)
>       at
> org.restlet.engine.http.connector.ControllerTask$2.run(ControllerTask.java:94)
>       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)
>
> Does the fix available in the snapshot should correct this behavior also
> or it is not related ?
>
> I hope it helps, fell free to ask for more informations if needed.
> Regards,
> Laurent.


-- 
Laurent Rustuel,
Alten contractor for Genesys, an Alcatel-Lucent Company

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2446708

Reply via email to