Thanks David,
This is definitely something that I haven't come across before. What I did notice in the wrapper.log is this exception (which is related to the JDBC MySQL database connection:
INFO | jvm 1 | 2009/02/25 13:01:33 | java.net.SocketException: Broken pipe
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.socketWrite0(Native Method)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2692)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2621)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1552)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.Connection.execSQL(Connection.java:2994)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.obtainLock(StdRowLockSemaphore.java:137)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreCMT.doRecoverMisfires(JobStoreCMT.java:1337)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2449)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:2468)
Looking at this MySQL thread:
http://forums.mysql.com/read.php?39,42763,42763#msg-42763
It seems in general that this problem is caused by a discrepancy in the MySQL configuration.
I noticed in your lams.properties that you are using the mysql-connector-java-5.1.7-bin.jar jdbc library instead of the packaged mysql-connector-java-3.1.12-bin.jar is there a reason for this?
What version of MySQL are you using and how did you install it? Have any configurations been made on the MySQL server? And is there anything else apart from LAMS using this MySQL instance?
Thanks
Luke
Posted by Luke Foxton
