History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: QB-1615
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Steve Luo
Reporter: Alexey Shumkin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Traymonitor on Linux Fedora 17 gives an error "Parse response failed" after a build failure

Created: 01/May/13 02:31 AM   Updated: 31/May/13 07:10 AM
Component/s: None
Affects Version/s: 5.0.16
Fix Version/s: 5.0.18

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
Server Information
System Date and Time 2013-04-18 20:13:24
Operating System Linux 2.6.33.7-co-0.7.9, i386
JVM OpenJDK Client VM 1.6.0_20, Sun Microsystems Inc.
QuickBuild Version 5.0.16 - Thu Apr 11 11:03:25 MSK 2013

client:
$ uname -a
Linux ashu.dyn1.rarus.ru 3.7.9-101.fc17.x86_64 #1 SMP Mon Feb 18 22:04:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ java -version
java version "1.7.0_17"
OpenJDK Runtime Environment (fedora-2.3.8.3.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)


 Description  « Hide
After a build failure a notification occurred '"Parse response failed / The response from server contains error and can't be parsed!"

from ~/.qbmonitor/traymonitor.log:
...
2013-04-18 20:11:02,717 ERROR - Parse document failed!
org.dom4j.DocumentException: Error on line 131 of document : Character reference "&# Nested exception: Character reference "&#
        at org.dom4j.io.SAXReader.read(SAXReader.java:482)
        at org.dom4j.DocumentHelper.parseText(DocumentHelper.java:278)
        at com.pmease.quickbuild.monitor.notifier.NotificationHandler.getBuilds(NotificationHandler.java:185)
        at com.pmease.quickbuild.monitor.notifier.NotificationHandler.run(NotificationHandler.java:86)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:722)
Nested exception:
org.xml.sax.SAXParseException; lineNumber: 131; columnNumber: 89; Character reference "&#
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
        at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
        at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
        at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388)
        at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanCharReferenceValue(XMLScanner.java:1272)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2986)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
        at org.dom4j.io.SAXReader.read(SAXReader.java:465)
        at org.dom4j.DocumentHelper.parseText(DocumentHelper.java:278)
        at com.pmease.quickbuild.monitor.notifier.NotificationHandler.getBuilds(NotificationHandler.java:185)
        at com.pmease.quickbuild.monitor.notifier.NotificationHandler.run(NotificationHandler.java:86)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:722)
...

restarting traymonitor does not vanish the error

 All   Comments   Work Log   Change History      Sort Order:
[ Permlink | « Hide ]
Alexey Shumkin [06/May/13 07:56 PM]
Excuse me, why this issue is absent in a list of related issues of 5.0.18 version in QB http://build.pmease.com/build/2369/jira ?

[ Permlink | « Hide ]
Steve Luo [07/May/13 03:24 AM]
Sorry, because there was some problems when updating the issue you created before (QB-1609) due to our very old JIRA instance, and this one is a clone. We relied on our QuickBuild JIRA plugin and haven't had this issue link to our release notes manually. Now, I linked it to our release notes already.

The issue (QB-1609 old one or this one QB-1615) should have been fixed in 5.0.18, so you can upgrade to the latest now.

[ Permlink | « Hide ]
Alexey Shumkin [31/May/13 07:10 AM]
Confirmed fixed


Powered by Atlassian JIRA™ the Professional Issue Tracker. (Standard Edition, Version: 3.7.4-#189) - Bug/feature request - Contact Administrators