I am observing openfire memleak after upgrading to 3.10.3. When I took a heap dump after taking one single chat (closed the MUC session), I observed that openfire is still holding those xmpp messages belong to that chat. This is confirmed with 2nd chat also (the xmpp messages for both chats are in memory).
This behaviour is very obvious in the server with full load in 3 hours.
Are there any configuration?
Any one have idea?
Environment:
Openfire 3.10.3
Smack 3.3.0
The xmpp messages after chat end:
MESSAGE_SEQUENCE_ID 7
user1 is now available
PARTICIPANT_VISIBILITY PUBLIC
PRESENCE available
FROM user1
VISIBILE 0
MESSAGE_SEQUENCE_ID 8
user2 is now available
PARTICIPANT_VISIBILITY PUBLIC
PRESENCE available
FROM user2
TYPE 3
VISIBILE 0
TRANSPORT_TYPE MUC_MESSAGE
MESSAGE_SEQUENCE_ID 9
IS_TYPING
user2
MESSAGE_SEQUENCE_ID 10
hi
user2
MESSAGE_SEQUENCE_ID 11
IS_TYPING true
user2
MESSAGE_SEQUENCE_ID 12
hello
user2
MESSAGE_SEQUENCE_ID 13
ACK_PACKET (hi)
FROM user1
TRANSPORT_TYPE MUC_ACK
MESSAGE_SEQUENCE_ID 14
ACK_PACKET (hello)
FROM user1
TRANSPORT_TYPE MUC_ACK
MESSAGE_SEQUENCE_ID 15
IS_TYPING
user1
MESSAGE_SEQUENCE_ID 16
123
user1
MESSAGE_SEQUENCE_ID 17
IS_TYPING
FROM user1
MESSAGE_SEQUENCE_ID 18
ACK_PACKET
ACK_MSG_ID node0
FROM user2 (123)
TRANSPORT_TYPE MUC_ACK
MESSAGE_SEQUENCE_ID 19
456
user1
MESSAGE_SEQUENCE_ID 20
ACK_PACKET
FROM user2 (456)
MESSAGE_SEQUENCE_ID 21
IS_TYPING
FROM user2
MESSAGE_SEQUENCE_ID 22
bye
user2
MESSAGE_SEQUENCE_ID 23
ACK_PACKET
FROM user1 (bye)
MESSAGE_SEQUENCE_ID 24
user1 is now unavailable
PRESENCE unavailable
TYPE 3
VISIBILE 0
TRANSPORT_TYPE MUC_MESSAGE