[openjms-developer] [ openjms-Bugs-1381708 ] Problem starting OpenJMS server and Persisting Messages

SourceForge.net

2005-12-16 10:18:43 UTC

Bugs item #1381708, was opened at 2005-12-16 02:21
Message generated for change (Settings changed) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1381708&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: persistence

Group: v0.7.6.1
Status: Closed
Resolution: Invalid

Priority: 5
Submitted By: pmukhi (pmukhi)

Assigned to: Tim Anderson (tanderson)

Summary: Problem starting OpenJMS server and Persisting Messages

Initial Comment:
Hi,
While trying to start the OpenJMS server
(using ./openjms.sh start), I got the following error:
Using
OPENJMS_HOME: /home/systemcare/adc/OpenJMS/openjms-
0.7.6.1

Using JAVA_HOME: /opt/j2sdk1.4.2

Using
CLASSPATH: :/home/systemcare/adc/OpenJMS/openjms-
0.7.6.1/lib/openjms-0.7.6.1.jar

:/home/systemcare/adc/OpenJMS/openjms-
0.7.6.1/lib/openjms-0.7.6.1.jar

OpenJMS 0.7.6.1

The OpenJMS Group. (C) 1999-2004. All rights reserved.

http://openjms.sourceforge.net

org.exolab.jms.server.ServerException:
org.exolab.jms.persistence.PersistenceException:
org.exolab.core.foundation.FailedToCreateDatabaseExcept
ion: Failed to create database openjms
b/cjava.io.StreamCorruptedException: unexpected EOF in
middle of data block

at
org.exolab.core.database.recman.PageManagedDatabase.<in
it>(PageManagedDatabase.java:118)

at
org.exolab.jms.persistence.ObjectAdapter.<init>
(ObjectAdapter.java:218)

at
org.exolab.jms.persistence.DatabaseService.createJdbmAd
apter(DatabaseService.java:258)

at
org.exolab.jms.persistence.DatabaseService.<init>
(DatabaseService.java:166)

at
org.exolab.jms.persistence.DatabaseService.instance
(DatabaseService.java:115)

at
org.exolab.jms.server.JmsServer.registerServices
(JmsServer.java:274)

at org.exolab.jms.server.JmsServer.init
(JmsServer.java:185)

at org.exolab.jms.server.JmsServer.main
(JmsServer.java:229)

As per the error message, there was an "unexpected EOF
in middle of data block". This is the first time since
this problem has occured, so I wanted to know, how an
EOF character was inserted in the data.
[The problem was resolved by deleting the openjms.db,
openjms.lg and openjms.lock files]

Also, the attached openjms.lg contains
a "PersistenceException". (apparently this is solved
by an upgrade to OpenJMS version 0.7.7-alpha-2.
Currently I am using openjms-0.7.6.1.jar). Are the
above two errors related?

Would be great if anyone can provide some information
on the above.

Thanks.

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)

Date: 2005-12-16 21:18

Message:
Logged In: YES
user_id=557161

The JDBM database has become corrupted. This database is no
longer supported, replaced in 0.7.7 with Derby.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1381708&group_id=54559