Modify

Opened 15 years ago

Last modified 12 years ago

#6308 new defect

Always getting "Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" in client

Reported by: anonymous Owned by: osimons
Priority: high Component: XmlRpcPlugin
Severity: normal Keywords:
Cc: lidaobing@… Trac Release: 0.11

Description

We always get the following exception in our Java XmlRpcClient.

Could it be that you download the DTD in the server implementation? Could you disable this?

(because of spam control I had to change the url to <SAMVE URL>)

ERROR  xxx.cms.infoportal.service.TracSyncServlet ?(sync:?) 08.12.2009 12:17:35  org.apache.xmlrpc.client.XmlRpcClientException: Failed to read servers
 response: Server returned HTTP response code: 503 for URL: <SAME URL>
org.apache.xmlrpc.client.XmlRpcClientException: Failed to read servers response: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml
1/DTD/xhtml1-strict.dtd
        at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:179)
        at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:145)
        at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:94)
        at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:44)
        at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:53)
        at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
        at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
        at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
        at xxx.cms.infoportal.service.TracSyncServlet.getTracTickets(Unknown Source)
        at xxx.cms.infoportal.service.TracSyncServlet.sync(Unknown Source)
        at xxx.cms.infoportal.service.TracSyncServlet$1.run(Unknown Source)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: <SAME URL>
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:175)
        ... 12 more

Attachments (0)

Change History (2)

comment:1 Changed 14 years ago by anonymous

Cc: lidaobing@… added; anonymous removed

comment:2 Changed 14 years ago by osimons

Are you running RPC from latest trunk? Earlier the plugin (and the underlying method implementations from Trac core) would raise TracError a lot - this error in regular Trac response handling will return a HTML error page. The DTD your client tries to fetch is likely coded into the Trac xhtml template.

Latest version of TracRPC (trunk) should not return any such pages, and in case of errors it will return proper faults/errors adapted to the protocol or in worst case return a text/plain response.

Please check again and let mw know how it works out.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain osimons.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.