Bugzilla – Full Text Bug Listing
|Summary:||Corrupt derby.jar during install of GridShib 0.5.1 onto Shib 1.3c|
|Product:||GridShib||Reporter:||Kyle Peacock <email@example.com>|
|Component:||Shibboleth IdP Plugin||Assignee:||Tom Scavo <firstname.lastname@example.org>|
|Severity:||normal||CC:||email@example.com, firstname.lastname@example.org, email@example.com|
Similar to bug 4955 (http://bugzilla.globus.org/globus/show_bug.cgi?id=4955), but the problematic IdP version is 1.3c instead. gridshib-db-test runs normally and exits after completing its task with no errors. However, the Certificate Registry can not be accessed. Instead of the appropriate page, a Shibboleth error page displays with the message "Database error." shib-error.log gives the following error: 2007-01-24 13:31:34,975 ERROR - Unable to obtain a new connection for jdbc:derby:/usr/local/shibboleth-idp/etc/gridshib-idp/certificate-registry-db: No suitable driver 2007-01-24 13:31:34,976 ERROR - Database error: No suitable driver The problem in this case is in derby.jar. Instead of getting the full derby.jar, an empty derby.jar is getting installed instead. The workaround in this case is to delete the derby.jar in $SHIB_DIST$/custom/lib and to then to run "./ant install" again. If the WAR does not automatically get expanded into the webapps/ directory, get rid of the shibboleth-idp/ webapp directory and restart tomcat.