powered by Jive Software

Today I saw this log in error section in my server

What is going on here. Most of the lines here are in red.

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:113)

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:103)

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

at org.jivesoftware.messenger.SessionManager$ClientSessionListener.onConnectionClo se(SessionManager.java:1227)

at org.jivesoftware.messenger.net.SocketConnection.notifyCloseListeners(SocketConn ection.java:316)

at org.jivesoftware.messenger.net.SocketConnection.close(SocketConnection.java:235 )

at org.jivesoftware.messenger.net.SocketConnection.deliver(SocketConnection.java:2 62)

at org.jivesoftware.messenger.net.SocketPacketWriteHandler.process(SocketPacketWri teHandler.java:79)

at org.jivesoftware.messenger.spi.PacketDelivererImpl.deliver(PacketDelivererImpl. java:48)

at org.jivesoftware.messenger.handler.IQHandler.process(IQHandler.java:50)

at org.jivesoftware.messenger.IQRouter.handle(IQRouter.java:213)

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

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

at org.jivesoftware.messenger.net.SocketReader.processIQ(SocketReader.java:258)

at org.jivesoftware.messenger.net.ClientSocketReader.processIQ(ClientSocketReader. java:43)

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

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

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

Hey deepak,

The java.net.ConnectException: Connection refused: connect[/i] error means that there is a connectivity problem. It seems that your server was able to reach the remote server but it failed to establish a connection on the server-to-server port. Check that the remote xmpp server is running, that port 5269 (or the one is being used for s2s) is opened in the firewall and that the server is listening in that port.

Regards,

– Gato

Hi,

as you are not using s2s I wonder if one user has a user with a jid like usernname@mrecord-dc in his roster. May I ask if mrecord-dc matches your xmpp.domain?

LG

mrecord-dc is another machine in our network and few days back i tried to move jive messenger server to that machine.

I see following data in warning section. Is that affecting my server’'s performance?

Thanks

2006.04.20 06:41:53 Connection 0 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 06:41:53 Connection 1 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 06:41:53 Connection 2 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 06:41:53 Connection 3 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 06:41:53 Connection 4 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 06:42:44 Cache: vcardCache – object with key p_anish is too large to fit in cache. Size is 705243

2006.04.20 06:43:35 Cache: vcardCache – object with key q_chetant is too large to fit in cache. Size is 2816731

2006.04.20 06:44:17 Cache: vcardCache – object with key t_rupaliw is too large to fit in cache. Size is 705243

2006.04.20 06:45:06 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 06:47:25 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 06:51:11 Cache: vcardCache – object with key q_chetant is too large to fit in cache. Size is 2816731

2006.04.20 06:51:23 Connection 0 had warnings: java.sql.SQLWarning: [SQLServer 2000 Driver for JDBC]Database changed to Messenger

2006.04.20 07:10:31 Cache: vcardCache – object with key t_lalitd is too large to fit in cache. Size is 705243

2006.04.20 07:17:18 Cache: vcardCache – object with key t_jijoa is too large to fit in cache. Size is 2816731

2006.04.20 07:23:40 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 07:24:05 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 07:47:07 Cache: vcardCache – object with key q_chetant is too large to fit in cache. Size is 2816731

2006.04.20 07:47:08 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 07:52:18 Closing no longer valid connection

org.jivesoftware.messenger.net.SocketConnection@f09653 socket: Socket[addr=/192.168.1.210,port=3606,localport=5222] session: org.jivesoftware.messenger.ClientSession@11d2cdb status: 3 address: s_vaishali@serv125/MRecord Messenger id: f5df38de presence:

java.net.SocketException: Connection reset by peer: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(Unknown Source)

at java.net.SocketOutputStream.write(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(Unknown Source)

at sun.nio.cs.StreamEncoder.flush(Unknown Source)

at java.io.OutputStreamWriter.flush(Unknown Source)

at java.io.BufferedWriter.flush(Unknown Source)

at org.jivesoftware.messenger.net.SocketConnection.validate(SocketConnection.java: 93)

at org.jivesoftware.messenger.SessionManager.isActiveRoute(SessionManager.java:748 )

at org.jivesoftware.messenger.handler.IQAuthHandler.login(IQAuthHandler.java:191)

at org.jivesoftware.messenger.handler.IQAuthHandler.handleIQ(IQAuthHandler.java:14 1)

at org.jivesoftware.messenger.handler.IQHandler.process(IQHandler.java:48)

at org.jivesoftware.messenger.IQRouter.handle(IQRouter.java:213)

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

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

at org.jivesoftware.messenger.net.SocketReader.processIQ(SocketReader.java:258)

at org.jivesoftware.messenger.net.ClientSocketReader.processIQ(ClientSocketReader. java:43)

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

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

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

2006.04.20 07:52:53 Cache: vcardCache – object with key s_nimesh is too large to fit in cache. Size is 2816731

2006.04.20 08:19:19 Cache: vcardCache – object with key q_chetant is too large to fit in cache. Size is 2816731

2006.04.20 08:19:37 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

2006.04.20 08:27:58 Cache: vcardCache – object with key s_nimesh is too large to fit in cache. Size is 2816731

2006.04.20 08:35:56 Cache: vcardCache – object with key t_lalitd is too large to fit in cache. Size is 705243

2006.04.20 08:41:43 Cache: vcardCache – object with key t_manishap is too large to fit in cache. Size is 705243

Hi,

this is still "Jive Messenger, Version: 2.2.2 " ?

The only thing which makes me wonder is the vcardCache issue. Do you have vCards with 2 MB size? Retrieving and sending them to the clients will take some time, and as they are not cached the server must query the database every time one of these vCards is requested.

Also with Wifi 2.6.2 it is afaik not possible to configure the vCard cache size, but an upcoming version will have this option.

LG

Hey LG,

The size and expiration time of caches in Wildfire can be configured. We need to create a KB document that specifies how to do it since there is no explicit way to do it from the admin console. However, future versions of Wildfire will provide a user friendly way to do it.

For now you have to create new system properties in the admin console and set the required value: These are the names of the properties that you can define and configure.

cache.vcardCache.size

cache.vcardCache.expirationTime

cache.userCache.size

cache.userCache.expirationTime

cache.remoteUsersCache.size

cache.remoteUsersCache.expirationTime

cache.username2roster.size

cache.username2roster.expirationTime

cache.group.size

cache.group.expirationTime

cache.userGroup.size

cache.userGroup.expirationTime

cache.listsCache.size

cache.listsCache.expirationTime

cache.multicast.size

cache.multicast.expirationTime

cache.offlinemessage.size

cache.offlinemessage.expirationTime

cache.pop3.size

cache.pop3.expirationTime

cache.fileTransfer.size

cache.fileTransfer.expirationTime

cache.ldap.size

cache.ldap.expirationTime

The *.size properties define the max size in bytes the cache may be. The *.expirationTime defines the default max lifetime of the cache, in milliseconds.

Regards,

– Gato

Hi,

cache.vcardCache.size should also work with JM 2.2.2, but I have no idea about the initial value. And if you increase it you will also need more memory. So maybe you better check why the vcards are so large. Did one upload a 2 MB photo?

LG

Hello it2000

Yes … Few guys uploaded large filesize photos… I will restrict the photo size in my Messenger client’'s next update. What max filesize should I allow to upload? What is ur suggestion?

Thanks

Hi Deepak,

see http://www.jivesoftware.org/community/thread.jspa?threadID=19315 for details.

A size of 8k and 32x32 - 96x96 pixels is what the Experimental JEP’'s suggest.

LG