Unexpected end of file after null
This error occurs when the "Enable Mock HTTP Log" in the HTTP Settings preference page in enabled. com.eviware.soapui.impl.wsdl.mock.DispatchException: org.apache.xmlbeans.XmlException: error:...
Forum Discussion
Its a little strange. It works on the first transaction after SOAP UI is started then fails on subsequent transactions.
I have seen the "end of file" error before when multiple "Mock Response Steps" were open on the same port and the flag was disabled. The first response would succeed and the second would fail with the error. I assumed at the time that each response step started a temporary mock service on the port but all responses were queued on the first service that started. Thus, when the first response completed and shut it service down, the second service had no response prepared for the second incoming request. But I didn't have the time to check the source code so I switched to using the "Mock Service".
However, the "Mock Service" also fails when the flag has been set so my assumption has to change. I imagine that the code that is writing the transaction to the log is closing or cleaning up something that it shouldn't be.
I have seen the "end of file" error before when multiple "Mock Response Steps" were open on the same port and the flag was disabled. The first response would succeed and the second would fail with the error. I assumed at the time that each response step started a temporary mock service on the port but all responses were queued on the first service that started. Thus, when the first response completed and shut it service down, the second service had no response prepared for the second incoming request. But I didn't have the time to check the source code so I switched to using the "Mock Service".
However, the "Mock Service" also fails when the flag has been set so my assumption has to change. I imagine that the code that is writing the transaction to the log is closing or cleaning up something that it shouldn't be.