Errors after upgrading to 2.2

Openfire Openfire Support
1

Hi, I had a running instance of Jive Messenger that I upgraded today to 2.2. Since then, everything stopped working and I am only getting the strack trace below on the error logs. I use no s2s and no external components. Where should I look at?

Thank you

Matheus

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.(Unknown Source)

at javax.net.DefaultSocketFactory.createSocket(Unknown Source)

at org.jivesoftware.messenger.server.ServerDialback.createOutgoingSession(ServerDi alback.java:130)

at org.jivesoftware.messenger.server.OutgoingServerSession.authenticateDomain(Outg oingServerSession.java:157)

at org.jivesoftware.messenger.spi.RoutingTableImpl.getRoutes(RoutingTableImpl.java :133)

at org.jivesoftware.messenger.roster.Roster.broadcastPresence(Roster.java:444)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.broadcastUpdate(Presen ceUpdateHandler.java:239)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:90)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:141)

at org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:87)

at org.jivesoftware.messenger.PresenceRouter.route(PresenceRouter.java:60)

at org.jivesoftware.messenger.PacketRouter.route(PacketRouter.java:73)

at org.jivesoftware.messenger.net.SocketReader.processPresence(SocketReader.java:3 01)

at org.jivesoftware.messenger.net.ClientSocketReader.processPresence(ClientSocketR eader.java:49)

at org.jivesoftware.messenger.net.SocketReader.readStream(SocketReader.java:208)

at org.jivesoftware.messenger.net.SocketReader.run(SocketReader.java:111)

at java.lang.Thread.run(Unknown Source)

2

Hey matheus,

It seems that you have in your roster (i.e. contact list) contacts whose domain does not match your server hostname. Therefore, when you become available the server is trying to connect to a remote server named “my.host.name” to get the presence of your contact.

In other words, if you are not using server-2-server then make sure that all the contacts in the users rosters have the same domain of your server’'s hostname. E.g. if your server hostname is myserver.com then make sure that all your contacts are of the form @my.host.name.

You may want to stop the server, perform an update on jiveRoster table and then restart the server again.

Regards,

– Gato