After you replaced the keystore, you have to undo the effect of deleting the key-entry and locking the keystore which is persisted to config.xml. This is done by removing the gbean element under <module name="org.apache.geronimo
That did the trick. Do you mind explaining what this did?Steven Ashwill
From: Vamsavardhana Reddy [mailto:email@example.com]
Sent: Tuesday, April 22, 2008 12:32 PM
Subject: Re: Locked keystore, forgive me I'm just a newbieAfter replacing the geronimo-default keystore, edit var/config/config.xml and locate the following xml fragment:
Replace the above with:
and start the server.
Let us know if it helped.
On Tue, Apr 22, 2008 at 10:09 PM, Ashwill, Steve (Facilities & Services) <firstname.lastname@example.org> wrote:
I have managed to mess-up my keystore and now Geronimo(2.1) won't
start. I made the geronimo-default file editable and then I deleted the
entry within it.(Don't ask why, just for fun, I guess) Is there a way to
recover from this? I added the file itself back to the
var/security/keystores folder but now it tells me that the keystore is
locked. Am I hopeless or can I restore a few folders from the install
to get back to square one, but leave all the database pools intact or is
there an even better way to recover.