DB integration problem

Openfire Openfire Support
1

I’‘m having the same problem with 3.0.1 and 3.1.0 is I presume I’'m doing something wrong.

My setting are :-

(XMPPServer.java:147)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.java:88)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

2

Just had the exact same problem with the most current version, but on a Debian server. Spent two hours trying different combinations of all the different things mentioned here on the forums, but alas, no luck. I also got the OperationNotSupportedException a lot when trying to log into the admin panel.

I suspect there might be a simple error in the configuration file. Maybe someone could post his/her complete working wildfire.conf for comparison.

But anyway, for me this would have been a temporary solution anyway, and I kind of decided to do it right from the start now and write my own AuthProvider - hopefully with more success.

3

I would recommend resetting the conf file to the default and then using the setup tool to set the JDBC values. Once you get that working, you can customize the user provider.

Regards,

Matt

4

I don’'t know enough about Java to know if this is the reason, but there is a difference in JBDCUserProvider amd the auth and ldap versions :-

public JDBCUserProvider() {

// Load the JDBC driver and connection string.

String jdbcDriver = JiveGlobals.getXMLProperty(“jdbcProvider.jdbcDriver.className”);

public JDBCGroupProvider() {

// Load the JDBC driver and connection string.

String jdbcDriver = JiveGlobals.getXMLProperty(“jdbcProvider.driver”);

public JDBCAuthProvider() {

// Load the JDBC driver and connection string.

String jdbcDriver = JiveGlobals.getXMLProperty(“jdbcProvider.driver”);

is the xml parse not going to the 3rd level ?

5

I just checked the 3.1 code and JDBCUserProvider has the code:

// Load the JDBC driver and connection string.

String jdbcDriver = JiveGlobals.getXMLProperty(“jdbcProvider.driver”);

So, I think this is a bug that’‘s already fixed in 3.1. I’'ve personally done testing of the JDBC provider code under 3.1 so it might be the best bet.

Regards,

Matt

6

Cheers Matt,

Using last nights build and the following wildfire.xml everything appears to work.