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
HTTP Status 500 - Could not roll back Hibernate transaction #161
Comments
I am going to try installing Oracle JDK and swap over the env vars to see if it makes any difference. |
Swapping to Oracle JDK did not resolve the issue. Any ideas? I was looking into the settings in the DataSource.groovy file but it seems like the validationQuery should be keeping the session alive. Not sure if anyone else has experience this issue? |
Hi!
maybe "autoReconnect=true" works for you? I personally have a long-running instance of streama that has been running for approx 12 weeks without restart, and I don't have that issue... EDIT: I am now seeing that the grails production datasource has a validityQuery that it runs ever 15000 ms. see this block:
but this only gets executed if you actually run the application in production mode. Did you make sure to run as run-war, not run-app? or even better: deploy to tomcat? |
When I ran it with "./grailsw run-war -Dgrails.env=production" it seems to be working correctly now, forcing the production environment seems to have resolved the issue as far as I can tell. Even though running without that command told me it was compiling the production version. Weird but now it has run for over 24 hours with zero issues (never did that before). TL;DR: Use "./grailsw run-war -Dgrails.env=production" |
After the server has been up for 12+ hours something seems to break, is there a requirement to run Oracle's Java or does Streama support OpenJDK? My server setup is currently Ubuntu 14.04.4 x64 and I'm currently utilizing OpenJDK 1.7.0_95 to run Streama. Everything works initially as far as I can tell but this has been a consistent issue where Tomcat will always start returning the following:
The text was updated successfully, but these errors were encountered: