Hi I tried to run a Spring JPA application in glassfish server the application is up and running but everytime a DB query is getting accessed the below warning is displayed in the logs:
javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.pool.resizer
Error while Resizing pool MediaTrackPool. Exception : WEB9031: WebappClassLoader unable to load resource [com.mysql.jdbc.SQLError], because it has not yet been started, or was already stopped.
Though there is no problem with the app running but everytime the warning is displayed. Can some one help me in getting rid of the same.
Related
Laravel Version: 5.7.28
PHP Version: 7.2.15
Database Driver & Version: MariaDB 10.2.23
I am struggling with a bug on my production server using Horizon.
ErrorException: Warning: PDO::prepare(): MySQL server has gone away
[internal] in unserialize
You can see a stack trace of the error here: https://sentry.io/share/issue/b105b7946b524a9e841f56f44445ea14/
As far as I can tell, this error should be caught by the Laravel framework. I'm not sure why it's not being caught and turned into a QueryException which would then trigger the reconnection and/or killing the worker.
See: https://github.com/laravel/framework/blob/9fb420cc29a7dd5de5051f09c523ffc3ea01b969/src/Illuminate/Database/Connection.php#L663
And then: https://github.com/laravel/framework/blob/9fb420cc29a7dd5de5051f09c523ffc3ea01b969/src/Illuminate/Database/Connection.php#L735
My understanding is that any Exception should be caught and then re-thrown as a QueryException, which would then be properly caught by the framework and then reconnected to the database.
This is an occasional error so it's difficult to reproduce; I've tried to manually throw a similar error but it is caught properly and handled properly.
Any general guidance on why this error might be different in production and ideas on how I can isolate the error would be appreciated.
In case anyone else runs into this, the current theory is that Sentry is catching errors that are still being handled properly by the framework.
Essentially, the job still completes correctly, because MySQL connection errors are handled automatically by the framework. However, Sentry still catches an error in that error handling process, though the reason is currently unknown.
For reference, see this discussion on Github:
https://github.com/laravel/horizon/issues/583
We have spring-boot batch task application that is hosted on pcf and deployed via spring-cloud-dataflow(scdf).
After we have connected it to app-dynamics agent it start to report crash every 5 minutes with the following resolution:
But there is no any exceprion within application and there is no crashes.
In logs I can see plain app execution.
I was thinking that there is some problems with app health check configuration on pcf. So I have added health check, but problem still exists and I have no idea already what is wrong there.
Does anyone know how to fix this or have any ideas on why it can happen ?
Let me know if you need any additional info.Thx
#SabbyAnandan
We are using SCDF(1.3.0) and PCF(1.2)
There is nothing in SCDF logs.
I suppose that is plain PCF issue that is reporting crash when there was no crashes/exception at all.
I have started getting errors after switching my queue driver in my Laravel app from 'database' to 'sqs'. The error is following:
Method __PHP_Incomplete_Class::handle() does not exist
I have not done any other changes besides switching the queue driver.
I have found the error. The reason is that I have accidentally connected the app to the queue of another app. And because the second app does not have the job classes from the first app it has thrown errors.
I get this error sometimes when trying to save things to Parse or to fetch data from it.
This is not constant and appear once in a while making the operation to fail.
I have contacted Parse for that. Here is their answer:
Starting on 4/28/2016, apps that have not migrated their database may see a "428" error code if the request cannot be handled by the remaining shared pool of resources. If you see this error in your logs, we highly recommend migrating the database for your app without delay.
Means this happens because of starting this date all apps are on low priority but those who started DB migration. So, Migration of the DB should resolve that.
i have a server with a bunch of tomcat, springs applications, and i can´t load a particular one that uses quartz. The main problem is that i can´t find an error anywhere that tells me what went wrong. And the same application runs fine in the test server, which uses de samde 1.6 jdk, tomcat 5.5. The only difference is that the productions server is in debian lenny, the test server in Centos. I only get a HTTP Status 404: requested resource not available.
Nothing usefull in catalina.out, configured log4j using this tutorial: http://tomcat.apache.org/tomcat-5.5-doc/logging.html , but can´t find any error there either. So i was wondering where can i get a hint of the problem ? tomcat starts succesfully and the other applications load without any problem.
Thank you very much
tail -f the catalina.out when you load the application, even it fails you still should able to see the output of tomcat trying to load the classes.
You might want to adjust to log level to info to see that tho.
*with 404 error, you could also try check the apache log, if you are using mod jk or proxy linking them.