Does anyone know how to stop jetty from zapping the
/roller-weblogger-webapp/target/derby-system each time its started?
Its painful (and a waste of time) having to renter all the weblog
details on each subsequent re-start.
For some reason jetty is unable to reload itself without some kind of
memory/file issues.
WARN 2012-01-12 15:51:00,088 JPAThreadManagerImpl:registerLease -
Error obtaining lease, assuming race condition.
<openjpa-2.0.1-r422266:989424 fatal general error>
org.apache.openjpa.persistence.PersistenceException:
java.net.SocketException : Error opening socket to server localhost on
port 3223 with message : Too many open files
at
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4832)
at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4792)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.retainConnection(JDBCStoreManager.java:252)
at
org.apache.openjpa.kernel.DelegatingStoreManager.retainConnection(DelegatingStoreManager.java:164)
at
org.apache.openjpa.kernel.BrokerImpl.retainConnection(BrokerImpl.java:3914)
at
org.apache.openjpa.kernel.BrokerImpl.beginStoreManagerTransaction(BrokerImpl.java:1400)
at
org.apache.openjpa.kernel.BrokerImpl.beginInternal(BrokerImpl.java:1337)
at org.apache.openjpa.kernel.BrokerImpl.begin(BrokerImpl.java:1326)
at
org.apache.openjpa.kernel.DelegatingBroker.begin(DelegatingBroker.java:917)
at
org.apache.openjpa.persistence.EntityManagerImpl.begin(EntityManagerImpl.java:555)
at
org.apache.roller.weblogger.business.jpa.JPAPersistenceStrategy.getEntityManager(JPAPersistenceStrategy.java:227)
at
org.apache.roller.weblogger.business.jpa.JPAPersistenceStrategy.getNamedUpdate(JPAPersistenceStrategy.java:286)
at
org.apache.roller.weblogger.business.jpa.JPAThreadManagerImpl.registerLease(JPAThreadManagerImpl.java:112)
at
org.apache.roller.weblogger.business.runnable.RollerTaskWithLeasing.run(RollerTaskWithLeasing.java:59)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.derby.client.am.DisconnectException:
java.net.SocketException : Error opening socket to server localhost on
port 3223 with message : Too many open files
at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
at org.apache.derby.client.am.Connection.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at
org.apache.openjpa.jdbc.schema.SimpleDriverDataSource.getConnection(SimpleDriverDataSource.java:96)
at
org.apache.openjpa.jdbc.schema.SimpleDriverDataSource.getConnection(SimpleDriverDataSource.java:91)
at
org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:139)
at
org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:112)
at
org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:139)
at
org.apache.openjpa.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:325)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:978)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:963)
just unusable........
Cheers Greg.
