Error while firing WatchedFolder trigger

[kc]

Hi all,



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 **



java.net.SocketException

MESSAGE: Connection reset by peer: socket write error



STACKTRACE:



java.net.SocketException: Connection reset by peer: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)

at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)

at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2692)

at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2621)

at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1552)

at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1124)

at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.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(StdJDBCDelegate.java:2317)

at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggerFired(JobStoreSupport.java:2778)

at org.quartz.impl.jdbcjobstore.JobStoreSupport$37.execute(JobStoreSupport.java:2757)

at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3662)

at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggerFired(JobStoreSupport.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?



Sincerely

Kim

[kc]

Can it really be true that nobody knows anything about this problem?



The problem seems strange to me that this problem occurs - as I can only find one watched folder endpoint in the Administration UI - and the error occurs even if I have disabled this endpoint.



Any suggestions to what I can do to chase the nature of this error?



Thanks in advance



Sincerely

Kim

[Former Community Member]

From the LiveCycle ES Error Code Reference



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

EXCEPTION

**com.mysql.jdbc.CommunicationsException

MESSAGE: Communications link failure due to

underlying exception: **java.net.SocketException

MESSAGE: Software]



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.



Sincerely,

Nick

[Former Community Member]

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.