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
.framework/server-security-config/2.1/car"> which resets the keystorePassword and keyPasswords attributes to their default values.


On Tue, Apr 22, 2008 at 11:30 PM, Ashwill, Steve (Facilities & Services) <> wrote:
That did the trick.  Do you mind explaining what this did?
Steven Ashwill

From: Vamsavardhana Reddy []
Sent: Tuesday, April 22, 2008 12:32 PM
Subject: Re: Locked keystore, forgive me I'm just a newbie

After replacing the geronimo-default keystore, edit var/config/config.xml and locate the following xml fragment:

    <module name="org.apache.geronimo.framework/server-security-config/2.1/car">
        <gbean name="org.apache.geronimo.framework/server-security-config/2.1/car?ServiceModule=org.apache.geronimo.framework/server-security-config/2.1/car,j2eeType=Keystore,name=geronimo-default">
            <attribute name="keyPasswords"/>
            <attribute name="keystorePassword"/>

Replace the above with:
    <module name="org.apache.geronimo.framework/server-security-config/2.1/car"/>

and start the server.

Let us know if it helped.


On Tue, Apr 22, 2008 at 10:09 PM, Ashwill, Steve (Facilities & Services) <> 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.


Steven Ashwill