Change deprecated SET OPTION to SET to support newest MySQL 5.6 versions


In the newest MySQL 5.6 versions support for deprecated SET OPTION statement has been removed. One have to use just SET statement instead. As SET OPTION is deprecated long time ago, older MySQL versions should work with SET also (needs testing). One of the places to make this change is in User-Summary.jsp (possibly other places).

With the current MySQL 5.6 version and the latest JDBC driver User Summary is not returning any entries.




Daryl Herzmann
April 26, 2014, 11:02 AM

wroot, do you know where in the openfire code "SET OPTION" is being used?

April 26, 2014, 11:19 AM

I've asked Mike on the forums.

Tom Evans
April 26, 2014, 6:01 PM

I checked the Openfire sources and can confirm we do not explicitly invoke the deprecated MySQL "SET OPTION" syntax anywhere in the code base. Rather, this is called implicitly via the JDBC API (likely in this case via the java.sql.Statement.setFetchSize method), which is implemented in the MySQL JDBC driver that is maintained by the MySQL folks. I think the best we can do for our users is to stay current with the most recently released version of MySQL Connector/J (currently 5.1.30) with each new release of Openfire.

Daryl Herzmann
April 26, 2014, 6:05 PM

resolving as a duplicate of OF-697, can reopen if it is still valid. Thanks Tom

Tom Evans
April 26, 2014, 6:24 PM

I realize that we recently updated the JDBC client for OF-697. However, given the upcoming release, I will update the MySQL Connector/J (mysql.jar) again to the latest released version for good measure. Beyond that, there is little else to be done in Openfire, so will mark this ticket as resolved.



Guus der Kinderen



Expected Effort


Ignite Forum URL



Affects versions