The JDBC driver will have a fully-qualified name, there are multiple JDBC drivers for the same database, different types.
Just a version of 5.5 is not enough to determine compatibility, but, at a wild guess, it sounds like something related to MySQL, which isn't supported anyway.
To really know compatibility, anyone would need to know the actual name of the jar file, class used to initiate connection, stated version of JDBC driver, if not obvious from file name, and JDBC driver type, usually 2 or 4.
Usually if the agent is run in DEBUG mode, it will tell you to skip a particular class to stop the Unknown SQL metrics from appearing, but further work in the code would be required to actually get SQL metrics out as we know them.
And then an idea can be raised to request full support for the driver.