In our Android Client, using OpenCMIS 0.10.0 and AtomPub binding, we see OpenCMIS attempt to reuse a TCP connection that the server has tried to close. In response to the Client trying to reuse a connection that it tried to close, the server correctly replies with a TCP RST. We then see the Android Client respond in different ways depending on what type of request it was attempting to send on the TCP connection.
Case 1: If the Client was trying to do a getChildren, OpenCMIS closes the connection that the server was trying to close, opens a new connection and uses that connection for the GetChildren request. The request succeeds and everyone is happy. Case 2: If the Client was trying to do a createDocument, OpenCMIS does NOT close the connection that the server was trying to close. It opens a new connection, but then unexpectedly closes it immediately after opening it. Is it confused and closing the wrong connection? At this point, there's no connection available for it to use. Eventually, OpenCMIS throws a "CmisConstraintException: Conflict". The request fails and nobody is happy. I have Wireshark captures that clearly show the above behaviors which I can make available. Is this a known issue? I didn't see anything in Jira that resembles it. Please let me know how I should proceed in getting this resolved. Thanks! ... Brian ... Xerox Corporation Palo Alto, California
