file.PersistenceManager: Could not rebuild the queue from th

[thoennes]

Hello,

since we are testing the new JBoss 3.2 branch to be used in production, we would like to get an explanation how the following situation could occur:

[Fri Dec 12 06:00:15.932 CET 2003] [ERROR] [org.jboss.mq.pm.file.PersistenceManager] Starting failed
org.jboss.mq.SpyJMSException: Could not rebuild the queue from the queue's tranaction log.; - nested throwable: (java.io.EOFException)
at org.jboss.mq.pm.file.MessageLog.throwJMSException(MessageLog.java:277)
at org.jboss.mq.pm.file.MessageLog.restore(MessageLog.java:114)
at org.jboss.mq.pm.file.PersistenceManager.restoreTransactions(PersistenceManager.java:264)
at org.jboss.mq.pm.file.PersistenceManager.startService(PersistenceManager.java:187)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
at $Proxy11.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:392)
[...]
at org.jboss.Main.boot(Main.java:150)
at org.jboss.Main$1.run(Main.java:388)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2165)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2634)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:734)
at java.io.ObjectInputStream.(ObjectInputStream.java:253)
at org.jboss.mq.pm.file.MessageLog.restoreMessageFromFile(MessageLog.java:263)
at org.jboss.mq.pm.file.MessageLog.restore(MessageLog.java:98)
... 69 more

From the "Caused by ... EOFException" and the stacktrace below I assume that the
corresponding message stored in a file had been truncated somehow. But I could not seen any errors during the previous shutdown of the server.

Are there any known issues that persistent messages are incompletely saved on shutdown,
perhaps some buffer flushing issue?

Thanks, Joerg

[adrian.brock]

I wouldn't recommend using the file persistence manager in production.
It is only there for backwards compatibility with jboss-2.4

I'm certainly not actively maintaining it.

Regards,
Adrian

[thoennes]

Adrian,

my collegue Raphael already tried to use JDBC persistence, but there was some problem with PostgreSQL that prevented us from using it.

But I do not find the Forums thread which dealt with that topic; I think he talked to you about that.

Please, could you confirm that there are no (known) problems using JDBC PostgreSQL as persistence manager for JBoss 3.2.3?

Thanks, Jörg

[adrian.brock]

I cannot confirm that, since I haven't tried it.

Somebody provided an example configuration for 3.2.2
it can be found in docs/examples/jms

Regards,
Adrian