Org.xml.sax.saxparseexception premature end of file web service

Home New Browse Search [? Bug - org. Summary: org. Note You need to log in before you can comment on or make changes to this bug. Comment 9 rodrigorsantos UTC. Comment 10 rodrigorsantos UTC. Comment 18 dheffelfinger UTC. Comment 22 rmatous UTC.

Comment 23 rmatous UTC. P1 blocker vote. Attachments stacktrace 6. Add an attachment proposed patch, testcase, etc. It seems that it happens even with new installation with a fresh userdir.

Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta.

New post summary designs on greatest hits now, everywhere else eventually. Related 0. Hot Network Questions. Maybe I misunderstood your original post, but it looked like you were saying that Sonic's web stack is not being used and that you wrote a custom service for the web request.

Most peculiar thing is this was working correctly couple of months back. Are you suggesting that if we use sonic's web stack, the web service call will be sucessful? I think it should work. I don't recall any issues with Web Services that use chunked encoding but this is normally specified by the client, not the server. My point was more this:.

SDM is just a deployment mechanism. As long as the environment is the same, it should not matter how it was deployed. So, this is unlikely to be an SDM issue but I would check:. Archive of former Progress Community Discussions. Web service call - getting soap fault "Premature end of Posted by smahanta on Aug Moreover, I would like to use tcpmon to capture packets.

How to do that with a sonic service? Please help.