Mass closing of all bugs resoved during 2.6.0 and 2.6.1
Wolf P. May 3, 2011 at 8:27 AM
Edited
theres no workaround for this, smack has to catch the unexpected format
since smack is responsible for the parsing of the packet
im not going to implement a workaround for faulty behaviour, caused by a specific server
dont use integrated databes
-------
i added a catch-block to the "supposed-error" in spark, see how that works out
wroot May 3, 2011 at 3:30 AM
Can we have a workaround to this? This was working with earlier builds of Spark. As we know that fixing bugs in Openfire can take ages, literally. Using embedded database in production is not a good choice, but many users don't have resources or skills to have a separate database.
Wolf P. May 2, 2011 at 7:23 PM
this seems to happen when using the integrated database in openfire
Since the work was done on adding indication if user don't have access to a room i can't see any room if i browse a conference server.