3.0.0 to 3.0.1 upgrade

I just upgraded from 3.0.0 to 3.0.1 and some of my users s2s contacts aren’'t showing as online after 20-30minutes of waiting. The users from other servers are online, and my users can exchange messages with other users. What causes this so I can be mindful of it for the next upgrade?

Also, is there some doucmentation for how to upgrade Wildfire so next time it’'s not such a (easy) stab in the dark? Is it just: Copy the conf, copy the db if necessary and copy the ssl keys if necessary and restart?

That’‘s what I do, mostly. I didn’'t have to copy the DB (since I use an external MySQL database), and I also copied my plugins.

Maybe this is related http://www.jivesoftware.org/community/thread.jspa?threadID=20869&tstart=0

I think JS.com is using 3.0.1. At first i thought it was a Spark issue. But i’'m not sure. Havent tested enough with Psi. What clients are you using?

Is this true for a particular group of S2S contacts in your cases? I’‘m running 3.0.1, and I’‘ve just added my wildfire account to my rosters on jabber.org and jivesoftware.com. It was already on my gmail roster. I logged off and in a couple of times, but I don’'t seem to have any problems.

I’'m using our in-house client for the wildfire account, Google Talk for the gmail account and Gaim for the other two accounts.

Guus wrote:

I logged off and in a couple of times, but I don’'t seem to have any problems.

I dont have problems with presences at login. Gmail contact becomes offline after a while (maybe same 20-30 mins).

My clients were still running. I’‘ve had no problems since my last post. I’‘ve changed all presences to ‘‘available’’ (they were dnd and away) and I’'ll have another look in half an hour.

It has been more than half an hour: no problems so far. What’‘s needed to reproduce this bug? All our users log in using connection managers and we’'re using DNS SRV records.

Message was edited by: Guus

Wait a sec - might have made a mistake… I’'ll update in another half hour.

Nothing so far. I’‘ve enabled the debug of our client. It doesn’'t report any unexpected packets.

When I look at my server sessions in the webadmin, I notice that I’‘ve almost always got a gmail session. Other sessions seem to time-out and disappear, only to resurface when they’‘re needed (I’'m the only user on this server now, so traffic is ultra-light).

There’‘s another thing that’‘s different between S2S servers. I enabled my debug logs, and entries for the gmail server differ from those for jivesoftware.com or jabber.org. Not sure if it’'s related.

Jabber and JiveSoftware leave messages like these:


2006.07.19 11:15:46 Logging off jabber.org on org.jivesoftware.wildfire.net.SocketConnection@35d56bbe socket: Socket[addr=/208.245.212.98,port=48138,localport=5269] session: org.jivesoftware.wildfire.server.IncomingServerSession@7991ba7 status: 1 address: jabber.org id: 726bc16d

2006.07.19 11:18:36 Logging off jivesoftware.com on org.jivesoftware.wildfire.net.SocketConnection@8ca1ada socket: Socket[addr=/63.246.20.123,port=52363,localport=5269] session: org.jivesoftware.wildfire.server.IncomingServerSession@54e674d6 status: -1 address: jivesoftware.com id: 35dba8b9


Google Talk on the other hand leaves stacktraces:


2006.07.19 11:13:36 Finishing Outgoing Server Reader. Closing session: org.jivesoftware.wildfire.server.OutgoingServerSession@6f0c29fe status: -1 address: gmail.com id: 201E05189B68B6ED

java.net.SocketException: Socket closed

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:129)

at org.jivesoftware.wildfire.net.ServerTrafficCounter$InputStreamWrapper.read(Serv erTrafficCounter.java:183)

at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)

at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)

at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)

at java.io.InputStreamReader.read(InputStreamReader.java:167)

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:320)

at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)

at org.dom4j.io.XMPPPacketReader.parseDocument(XMPPPacketReader.java:303)

at org.jivesoftware.wildfire.server.OutgoingServerSocketReader$1.run(OutgoingServe rSocketReader.java:91)