Glassfish server logs driver#
For example, if you are running the version 9.3 of PostgreSQL, make sure you have the driver in your /glassfish/lib directory.
Glassfish server logs install#
Make sure you install the correct version of the driver. it most likely means that it is the JDBC driver incompatibility that’s preventing the timer from working correctly. Įxception Description: Could not deserialize object from byte array. Internal Exception: java.io.StreamCorruptedException: invalid stream header. If you are seeing the following in your server.log.įollowed by an Exception stack trace with these lines in it: (See Dataverse Application Timers for details.) If these scheduled jobs are not running on your server, this may be the result of the incompatibility between the version of PostgreSQL database you are using, and PostgreSQL JDBC driver in use by your instance of Glassfish. # will restart glassfish if it's stopped comment out the `start-domain` command at the endĭV_DIR=$/bin/asadmin start-domainĭataverse relies on EJB timers to perform scheduled tasks: harvesting from remote servers, updating the local OAI sets and running metadata exports. # access to the database (local sockets, or appropriate environmental variables). # assumes this script is being run as root, and that the postgres user had passwordless # EBJ timers sometimes cause problems utility to clear generated directories and database rows (See the comments in the script for more information) Aside from the configuration values that need to be changed to reflect your environment (the Glassfish directory, name of the database, etc.) the script relies on the database being configured in a certain way for access. Note that it may or may not work on your system, so it is provided as an example only, downloadable here. The shell script below performs the steps above. Delete all the rows from the EJB_TIMER_TBL table in the database.Remove the generated and osgi-cache directories.We don’t know what’s causing this issue, but here’s a known workaround: Sometimes the Dataverse application fails to deploy, or Glassfish fails to restart once the application is deployed, with the following error message: “remote failure: Error occurred during deployment: Exception while loading the app : EJB Timer Service is not available. Deployment fails, “EJB Timer Service not available” ¶
0 kommentar(er)
