Timeouts When using the Enlighten service
Posted on: Tue, 08/26/2008 - 08:33
Is there a way to set a limit for the timeouts in the Enlighten service? In other words, is there a way to ask it to raise an exception if there is no response for more than 2 minutes? The way I have it now is that I kill the process manually each time I find there is no response.
Thank you,
h.
Trackback URL for this post:
http://www.opencalais.com/trackback/5591
I'm doing a http post for SOAP and the exception i'm getting is as follows:
java.net.UnknownHostException: http://api.opencalais.com/enlighten/
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 java.net.Socket.(Unknown Source)
at com.til.soap.PostXML.main(PostXML.java:20)
Can any one help me getting by pass this. When I ping http://api.opencalais.com/, i'm getting time outs as following:
C:\>ping api.opencalais.com
Pinging proxylb-calais.mashery.com [75.101.136.33] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 75.101.136.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Thanks.
Hi,
Can you send us a sample of your code so we can see what is the problem? And specific document that causes this problem? You can send it also to questions@opencalais.com.
What exact sample code did you use from the www.opencalais.com web site?
Thanks,
Ofer
What platform or programming language are you using?
Maybe it would make more sense to specify a timeout on network/socket level?
Because what you basically ask for is "hey, just let me know if your not able to respond", which is a bit of an antagonism.
Thank you for your reply. I am using a Java SOAP client and NetBeans. I used the tutorial that was posted on Calais gallery.
You should propably take a look at the generated classes for the web service and see if you can find a timeout option there. Its generally good practice to handle this case and create a user message or reschedule the request. Remember, it could be anything to cause this, so it must not necessarily be a calais problem.