Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (nike.apache.org: domain of dr.louis.smith@gmail.com
 designates 209.85.161.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=IdJ8vdtDPAHc2b5LTTVift46It3a2cIkfA90pqRyNudftgBIOSPwh24UDHcLV+RSvQ
         H6xE7mZ+9UjA5ds9g7FHKEtW34i3MgTIlYGb6KUewA7Da/uvxSq6kq8eBeV53dp6kwQz
         S2ncETiGbfkq7iCVr2zKFTXMjWgLy487wkGH8=
MIME-Version: 1.0
Date: Thu, 5 May 2011 09:24:32 -0400
Message-ID: <BANLkTincmXg2UDg70xyDJFvr_e6-p-QaNw@mail.gmail.com>
Subject: Third Re-installation of Geronimo to fix error
From: Louis Smith <dr.louis.smith@gmail.com>
To: users@continuum.apache.org, users@geronimo.apache.org
Content-Type: multipart/alternative; boundary=00151747698035bf2504a2874b9a

--00151747698035bf2504a2874b9a
Content-Type: text/plain; charset=ISO-8859-1

At this point, I'm quite suspicious.  I have gotten the 3rd report from my
tech leads that they have had to re-install geronimo again to fix crashes
from Archiva and Continuum.

The environments are different - one on windows, 2 on linux.  Same issue -
the server will start throwing 500 errors to the end users of Continuum
and/or Archiva; looking at the logs shows failure to connect to the
underlying mysql database - with "invalid credentials" being the culprit.

The server will neither stop from shutdown, nor will it restart.  Startup
fails on deployment of the first product - again with the database
connection pool refusing to connect to the database with mysql throwing the
underlying bad account credentials back up the chain to the server.

Stop has to be a kill.  Fortunately, we have the documentation on setting
the flag to get past the MQ startup lock, so that isn't an issue.


This time, I was on site at one of the clients, and I noticed that the
startup log showed that the attempt was being made to start the archiva car
- but the failure showed the attempt to use the continuum credentials
('app'@'localhost' - not 'archiva'@'localost').  We checked the dbpool
plans, and the 3 of them (jdbc_archiva, jdbc_continuum, jdbc_users) were all
correct, with the correct accounts and credentials.


So we did a fast reinstall of Geronimo, re-created the dbpools with same
credentials (app/app, archiva/archiva), redeployed the same war files with
the same plans - and it came right back up.

We have saved the application and security settings, so we deploy no-start,
flash the files, start the apps. All come right back, connect to the
database and ldap, and everything is right where we got kicked out..

Anyone else experience the 500 errors against the database?

Geronimo 2.2.1
Archiva 1.3.4
Continuum 1.3.7
MySql 5 (various)

Windows Vista Ultimate 64 and RHEL 4.6

-- 
Dr. Louis Smith, ThD
Chief Technology Officer, Kyra InfoTech
Colonel, Commemorative Air Force

--00151747698035bf2504a2874b9a--