As detailed in this thread http://www.igniterealtime.org/community/message/176057 there seems to be a memory/CPU problem in the GaduGadu transport.
I can see the following thread which seems to belong to the jggapi eating lots of CPU cycles and memory
“Thread-859” daemon prio=10 tid=0x0891b400 nid=0x79fc runnable [0xc7fa7000…0xc7fa7f30]
java.lang.Thread.State: RUNNABLE
at java.util.Arrays.copyOf(Unknown Source)
at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source)
at java.lang.AbstractStringBuilder.append(Unknown Source)
at java.lang.StringBuilder.append(Unknown Source)
at pl.mn.communicator.packet.HexDump.hexDump(HexDump.java:60)
at pl.mn.communicator.packet.HexDump.hexDump(HexDump.java:30)
at pl.mn.communicator.packet.GGUtils.prettyBytesToString(GGUtils.java:31)
at pl.mn.communicator.packet.handlers.PacketChain.sendToChain(PacketChain.java:74)
at pl.mn.communicator.DefaultConnectionService$ConnectionThread.decodePacket(Defau ltConnectionService.java:412)
at pl.mn.communicator.DefaultConnectionService$ConnectionThread.handleInput(Defaul tConnectionService.java:361)
at pl.mn.communicator.DefaultConnectionService$ConnectionThread.run(DefaultConnect ionService.java:337)
Anyone else experiencing this?