Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Grouper upgrade 2.2.1 => 2.2.2 - "conflicting jar" - mysql

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Grouper upgrade 2.2.1 => 2.2.2 - "conflicting jar" - mysql

Chronological Thread 
  • From: Chris Hyzer <>
  • To: "Waldbieser, Carl" <>, Gouper Users List <>
  • Subject: RE: [grouper-users] Grouper upgrade 2.2.1 => 2.2.2 - "conflicting jar" - mysql
  • Date: Mon, 30 Nov 2015 12:26:38 -0500
  • Importance: normal

Copy the same jar to both folders  and see if it works.   Open a Jira if you think we need to address this


-------- Original message --------
From: "Waldbieser, Carl"
Date:11/30/2015 11:59 AM (GMT-05:00)
To: Gouper Users List
Subject: [grouper-users] Grouper upgrade 2.2.1 => 2.2.2 - "conflicting jar" - mysql

I ran the Grouper 2.2.2 upgrader to upgrade the Grouper api from 2.2.1 to 2.2.2.  Near the end of the upgrade, I got the message:

    There is a conflicting jar: ArrayList size: 2: [0]: /var/opt/internet2/grouper/grouper.apiBinary/lib/custom/mysql-connector-java-bin.jar
    [1]: /var/opt/internet2/grouper/grouper.apiBinary/lib/jdbcSamples/mysql-connector-java-bin.jar

    You should probably delete one of these files (oldest one?) or consult the Grouper team.
    Press <enter> to continue...

I ended up deleting the older file ([1] above).  Now, when I try to use gsh, I get a stack trace that indicates an issue with the database driver:

    Grouper error: Error finding database driver class from com.mysql.jdbc.Driver, perhaps you did not put the database driver jar in the lib/custom dir or lib dir, or you have the wrong driver listed: java.lang.RuntimeException: Problem loading class: com.mysql.jdbc.Driver

I am guessing this is some kind of library versioning issue?
I can still connect to the DB if I use command line mysql with the same credentials.

Carl Waldbieser
ITS Systems Programmer
Lafayette College

Archive powered by MHonArc 2.6.16.

Top of Page