Jive''s perform problem

lately,we test jive_messenger_2005-04-18 in our company.jive run on linux RH9,machine is PIII900,memory is 512M, we setup 300 user in share group.User is 20 online ,server is run normally.when user online more 50,server had stopped to response.i view debug xml in exodus.users’‘s state change quickly.i stop state change automatic in exodus and added java memory to 200M in messenger.sh.server run normally some time.it second stop to response 10 minute that user online is 20, when machine can’'t do any deploy. we want to do a application for user online 100~200.what necessary deploy is it?

it is error log and warn log.

2005.04.22 10:18:38 org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:139) Internal server error

java.lang.IllegalStateException: Entry was removed

at java.util.concurrent.ConcurrentHashMap$EntryIterator.getKey(ConcurrentHashMap.j ava:1156)

at org.jivesoftware.messenger.user.User$PropertiesEntrySet$1.remove(User.java:354)

at java.util.AbstractMap.remove(AbstractMap.java:278)

at org.jivesoftware.messenger.spi.PresenceManagerImpl.deleteLastUnavailablePresenc e(PresenceManagerImpl.java:179)

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

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

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

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

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

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:240)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)

2005.04.22 10:32:02 org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:114) Could not route packet

java.lang.IllegalArgumentException: No enum const class org.xmpp.packet.Presence$Type.invisible

at java.lang.Enum.valueOf(Enum.java:192)

at org.xmpp.packet.Presence$Type.valueOf(Presence.java:308)

at org.xmpp.packet.Presence.getType(Presence.java:93)

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

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

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

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:240)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)

2005.04.22 14:55:03 Closing no longer valid connection

java.net.SocketException: Socket closed

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)

at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)

at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)

at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)

at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191)

at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:111)

at java.io.BufferedWriter.write(BufferedWriter.java:212)

at java.io.Writer.write(Writer.java:126)

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

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

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

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

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

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

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

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

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:285)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)

i currently have checked debug xml in exodus,some user online state change too more,in “xa”,’’’‘available’’… there are broadcast to every share user,when user is more,the state info will more ton,it is will stop to response in server.before we can’'t solved it,whether server may modify it broadcast user states info that it is only sned ‘‘online’’ and ‘‘offline’’.other user state info prohibite it send to share user.why do it?

thanks.

The first issue is that one of the clients is trying to set an invalid presence type of “invisible”. That might be causing some of the stack traces in the logs. Also, can you test with the official 2.1.3 release? If you still see performance problems, let us know.

Regards,

Matt

Yes,it’‘s a client problem.exodus’’ state change is more at part of machine.it is make more state information to every share groups user.when user online is more,the info is more in server,it will server stop to response.now ,we turn off automatic state change in exodus,jive server is run good.

i think whether jive can have a kind of info filtrated function,it can’'t send junk info to very user when some info repeat to send to share group user.or admin console can control that user can login to server.