Once every day the server reports the following error and cannot recover (needs restart):
2008-03-10 22:36:50,855 ERROR [org.quartz.core.ErrorLogger] An error occured while firing trigger 'WatchedFolder.WatchedFolder:605'
org.quartz.JobPersistenceException: Couldn't select trigger state: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
MESSAGE: Connection reset by peer: socket write error
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65 )
at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedSt atement.java:1124)
at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPrepared Statement.java:676)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java: 1030)
at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeQuery( CachedPreparedStatement.java:76)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery (WrappedPreparedStatement.java:211)
at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTriggerState(StdJD BCDelegate.java:2317)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggerFired(JobStoreSup port.java:2778)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$37.execute(JobStoreSuppo rt.java:2757)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLoc k(JobStoreSupport.java:3662)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggerFired(JobStoreSup port.java:2751)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java: 313)
I have just reinstalled the server and imported the processes I had created earlier, but no custom setup within the "stomach of JBoss/LiveCycle".
Does anybody knwo what I can do to rectify/localise this error?
Extended periods of server inactivity when using JBoss
Application Server configured with MySQL (the JBoss
turnkey). The exception is raised by background
processing during internal database management. Its
presence is expected: Idle connection with the
database times out and causes the TCP/IP connection
to close. Exceptions typically occur after 8 hours or
more of inactivity in LiveCycle ES.
[Exceptions seen on JBoss/MySQL and start with:
java.sql.SQLException: No operations allowed after
connection closed. Connection was implicitly closed
due to underlying exception/error: ** BEGIN NESTED
MESSAGE: Communications link failure due to
underlying exception: **java.net.SocketException
The document also says
This exception does not
impact the LiveCycle ES
server processing and
can be ignored.
However, I also need to restart the server to get it working again.
We had a problem with LC ES on jboss with MySQL. I believe the problem was that after the server being idle for a while, the connection to MySQL could not be restored untill the server was restarted. This was reported to Adobe, and a patch was made. Try contacting Adobe support and ask for the patch. It may help you.