-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSE Logs - Error while closing the output stream in order to commit response #126
Comments
|
|
|
|
|
Update Jan 9, 2023
After all, probably this is a configuration issue? And because seems like this is applied to both tomcat and jetty, maybe this is servlet level config? Example of SSE client code (so don't need to start KPM each time for testing): import EventSource from "eventsource";
let source = new EventSource("http://localhost:8080/plugins/killbill-osgi-logger");
// let source = new EventSource("http://localhost:8080/jooby1apps/sse");
source.addEventListener('message', function(e) { console.log("Message: ", e); }, false);
source.addEventListener('open', function(e) { console.log("Open: ", JSON.stringify(e, null, 2)); }, false);
source.addEventListener('error', (e) => {
console.log("An error occurred while attempting to connect: " + JSON.stringify(e, null, 2));
}); |
Update Jan 10, 2023When continue debugging, I opened jersey code and found this in // Happens when the client closed connection before receiving the full response.
// This is OK and not interesting in vast majority of the cases
// hence the log level set to FINE to make sure it does not flood the log unnecessarily
// (especially for clients disconnecting from SSE listening, which is very common). In Jetty, most of the time, calling |
This is a follow up issue based on silence SSE logs issue. This problem showing up when:
killbill
running withkpm
andlogger
plugin installed.http://127.0.0.1/plugins/killbill-osgi-logger
) consumed by KAUI (or any SSE client)Note that running killbill with jetty vs tomcat will produce slightly different error messages, and both tomcat and jetty throws different Exception in different times. But exception message always started by
ServerRuntime$Responder - Error while closing the output stream in order to commit response
on both of them.When googling for specifics error (like
java.lang.IllegalStateException: s=OPEN,api=BLOCKED,sc=false,e=null
) some says it is jetty problem, and fixed long ago.Last Update:
Jan 10, 2023
Jan 9, 2023.
Tomcat (8.5.82)
killbill and KAUI deployed as described in getting started guide.
NullPointerException: null
Full stacktrace here.
ArrayIndexOutOfBoundsException
Full stacktrace here.
InvalidMarkException: null
Full stacktrace here.
Jetty
Killbill run using
mvn jetty:run
command, while KAUI deployed in tomcat following the getting started guide.IllegalStateException (
s=OPEN,api=BLOCKED,sc=false,e=null
ors=CLOSING,api=BLOCKED,sc=false,e=null
)Full stacktrace here.
IllegalArgumentException: setContentLength(0) when already written 628
Full stacktrace here.
The text was updated successfully, but these errors were encountered: