powered by Jive Software

Sometimes Spark replaces characters with ��

In Spark it look like two squares. It accures randomly and rarely. Random lithuanian (probably those double-byte) chars are replaced with two squares. It happens when first message comes, all subsequent messages looks fine.

This started to happen with 2.5.8 Beta 1 if i remember right, not so long before. And Openfire is the same latest stable version.

Oct 11, 2007 8:22:28 AM org.jivesoftware.spark.util.log.Log error

SEVERE:

java.net.UnknownHostException: www.igniterealtime.org

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.(Unknown Source)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocke t(DefaultProtocolSocketFactory.java:79)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocke t(DefaultProtocolSocketFactory.java:121)

at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:704)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDir ector.java:384)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirect or.java:170)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)

at org.jivesoftware.sparkimpl.updater.CheckUpdates.isNewBuildAvailableFromJivesoft ware(CheckUpdates.java:150)

at org.jivesoftware.sparkimpl.updater.CheckUpdates.newBuildAvailable(CheckUpdates. java:94)

at org.jivesoftware.sparkimpl.updater.CheckUpdates.checkForUpdate(CheckUpdates.jav a:391)

at org.jivesoftware.MainWindow$11.finished(MainWindow.java:558)

at org.jivesoftware.spark.util.SwingWorker$2$1.run(SwingWorker.java:136)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

This started to happen more often to me. Anybody else seeing this with 2.5.8 Beta 1? My coworker with 2.5.7 hasnt seen such behaviour.

Also at home messages in russian are showing wrong (ICQ transport), though maybe this can be Gateway issue, but i havent seen such before.

So far this is happening only if you arent looking in chat window or this is new chat. Last time i was chating with someone, went away and then my pc (Windows XP) has locked up. When i unlocked it i saw new message which had those symbols instead of correct char.

So, this is 1-st high priority issue for 2.5.8 for me.

>So, this is 1-st high priority issue for 2.5.8 for me.

its not spark issue, only Openfire 3.3.3 and 3.4.1 with any clients http://papir.kiev.ua/square.jpg

victorae wrote:

its not spark issue, only Openfire 3.3.3 and 3.4.1 with any clients http://papir.kiev.ua/square.jpg

well, i dont know your case, but for us it’s only started happening with Spark 2.5.8 beta 1, server is 3.3.3 for a very long time, and my coworker with 2.5.7 have nefver seen such problems

>server is 3.3.3 for a very long time, and my coworker with 2.5.7 have nefver seen such problems

90% russian admins OF use 3.3.2 version , because of these squares in words

Dont know about differences between lithuanian and russian chars (assume should be both unicode).

At work we use Exodus as main client. Only two of us use Spark. So maybe this could be related to Exodus. But as i said it only happens to me with 2.5.8 Beta 1.

At home i use Openfire 3.4.0 and Spark 2.5.8 Beta 1 with IM Gateway (ICQ mainly). I have some contacts who are writing in russian and i havent ever seen such problem with them.

squares in Psi, Miranda, Pandion, Spark - may be this not client problem

Hi Oleg,

could you try to reproduce this with Openfire 3.3.2 and Spark 2.5.8-b1 to make sure that this is really a Spark issue?

LG

No, i cant. At work it’s 3.3.3 and i dont want to test with it. And this is happening only to me with Spark 2.5.8. Also it happens only few times per day, so it would be hard to reproduce. At home i use Openfire 3.4.0 and Spark 2.5.8, but i dont chat in lithuanian, i only have some contacts who are chating in russian (through IM Gateway - ICQ), but i never seen such problem with them. So there is no point to revert to 3.3.2 at home.

3.3.3 and letter , open on sender and recipient XML console ( i’m check on Psi and Pandion) .

in outgoing messages in XML console not squares, in incomming via XML Console - squares.

on OF 3.3.2 never see squares in messages.

Have found such error in Openfire logs:

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

at java.lang.Thread.run(Thread.java:619)

Nested exception:

org.xml.sax.SAXParseException: Character reference “�” is an invalid XML character.

at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseExcep tion(ErrorHandlerWrapper.java:195)

at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHan dlerWrapper.java:174)

at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorRe porter.java:388)

at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner. java:1411)

at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanCharReferenceValue(XMLSc anner.java:1295)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragment ContentDriver.next(XMLDocumentFragmentScannerImpl.java:3009)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocument ScannerImpl.java:645)

at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocu mentScannerImpl.java:140)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocu ment(XMLDocumentFragmentScannerImpl.java:508)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Config uration.java:807)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Config uration.java:737)

at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXP arser.java:1205)

at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXPa rserImpl.java:522)

at org.dom4j.io.SAXReader.read(SAXReader.java:465)

at org.dom4j.io.SAXReader.read(SAXReader.java:365)

Seems to be Openfire (MINA) issue.