This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes I/O and Streams and the fly likes Saxon 9, java.net.ConnectException: Connection timed out: connect error Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » I/O and Streams
Bookmark "Saxon 9, java.net.ConnectException: Connection timed out: connect error" Watch "Saxon 9, java.net.ConnectException: Connection timed out: connect error" New topic
Author

Saxon 9, java.net.ConnectException: Connection timed out: connect error

Don Blodgett
Ranch Hand

Joined: Jan 09, 2006
Posts: 61
I am using Saxon 9.1 to transform an XML document and get, inconsistently, the following error I have found that by disabling the firewall I am able to run the same code without issues most of the time, I still get the error from time to time (much more rarely though). I have tried to disable "use XSI schema location" feature in an attempt to ignore lookups of the namespace URI (based on Michael Key's comment Here), but I still get the error. I need to be able to prevent this without having to resort to taking down the firewall. Has anyone else had this issue, if so how did you manage to resolve it?

Any help is greatly appreciated.
Don Blodgett
Ranch Hand

Joined: Jan 09, 2006
Posts: 61
Is there some way I can determine what Saxon is trying to connect to, I looked through the XML and XSLT, but there is nothing that would indicate that there is anything to connect to. The only URIs in the document are namespace URIs and it should not be trying to connect to those as they are just namespaces.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18570
    
    8

Doesn't your firewall tell you? If it's blocking requests then it should be logging those blocked requests so the administrator can see who is doing "bad things", or at least you should be able to configure it to do so.
 
GeeCON Prague 2014
 
subject: Saxon 9, java.net.ConnectException: Connection timed out: connect error