Soldato
OK this might be lacking in some details, simply because I don't know all of them. I have a DOM in XML format, the length of the String that makes up the DOM is 89,424,168, less than the theoretical limit of the length of a string (2,147,483,647)
This XML is a Jasper report exported to XML format, I am trying to serialize this XML and add it to my response XML (client->server architecture).
The problem is the response XML (which includes the serialized DOM) has been truncated, so the client has issues reading it.
Is there a limit to how much can be serialized? For info serializing is done by a org.apache.xml.serialize.XMLSerializer, it looks like it can throw an IOException which stupidly is being caught but not dealt with! (I didn't write this) I have however added an IOException breakpoint caught and uncaught to Eclipse and that isn't triggered.
EDIT: Ok seems there is a "java.net.SocketException: Broken pipe" when sending the response from the Server, so the client is closing the connection before the server has finished responding!
This XML is a Jasper report exported to XML format, I am trying to serialize this XML and add it to my response XML (client->server architecture).
The problem is the response XML (which includes the serialized DOM) has been truncated, so the client has issues reading it.
Is there a limit to how much can be serialized? For info serializing is done by a org.apache.xml.serialize.XMLSerializer, it looks like it can throw an IOException which stupidly is being caught but not dealt with! (I didn't write this) I have however added an IOException breakpoint caught and uncaught to Eclipse and that isn't triggered.
EDIT: Ok seems there is a "java.net.SocketException: Broken pipe" when sending the response from the Server, so the client is closing the connection before the server has finished responding!
Last edited: