I copied the offending 'jar' file to a zip file and ran "unzip -t" to test the integrity. Sure enough, their is ONE class with a bad checksum. That's why jlink was throwing a bad CRC exception on that one jar file.
Sadly, 'jar' program does NOT have an integrity check command (Sun, if you're reading, please take note!!!) or the vendor might have found the problem before shipping a jar with a bad class in it....
