Re: Google App Engine SOAP call SocketTimeoutException

[Deepak Singh]

Hi Aljaz,

 

I am still facing the same problem and app is running with problem.

 

Let us do something out of the box so that google puts an attention over the issue.

 

Thanks

Deepak

On Fri, Jun 1, 2012 at 2:35 PM, Aljaz Delakorda <dela...@gmail.com> wrote:

Hi Deepak,

Sorry to contact you in this way, but the Issue where you were discussing has been marked as obsolete.

I am having exact same Problem as you described here:
http://code.google.com/p/googleappengine/issues/detail?id=5927#c5

I am calling a soap service (via jax-ws) which uses UrlFetch internally. I become very often a SocketTimeotException while fetching the response... Did you find a way how to increase this Timeout? How did you solve the problem? I cannot find any solutions on the web...

I hope you can take a second to help me out.

Thank you for your time,
Best regards,
Aljaz Delakorda

--
Deepak Singh

[Michel Jonker]

Yes I have the same issue, I cannot find a way to increase the connect timeout through JAX-WS that is allowed by Google...

[Emanuele Ziglioli]

It times out for me at times on the local server. Haven't found a way to increase the socket timeout. Have tried:

    System.setProperty("sun.net.client.defaultConnectTimeout", "10000");

    System.setProperty("sun.net.client.defaultReadTimeout", "10000");

It makes no difference. Then have tried:

       ((BindingProvider) port).getRequestContext().put(BindingProviderProperties.REQUEST_TIMEOUT, 30);

 

but it says "BindingProviderProperties is not supported by Google App Engine's Java runtime environment".

But at least when testing locally, it works most of the time.

Instead, on GAE servers, it fails. Have tried catching any exception but can't even do that.

The call that fails is:

new javax.xml.ws.Service(java.net.URL wsdlDocumentLocation, QName serviceName) 

[Thiago Catoto]

Hi,

I'm pretty sure Appengine has the limit of 10s for UrlFetch (https://developers.google.com/appengine/docs/java/urlfetch/overview).

You may need to change the request to Task Queue if you have the need of longer requests, but it would get more complicated to handling the response to the SOAP "caller".

Hope it helps.

Best regards,

Thiago Catoto.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/DbLPCLSYVGoJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Takashi Matsuo]

For clarification, it used to be 10 secs, but now the maximum deadline of the urlfetch is 60 seconds for online requests, 600 seconds for offline requests(taskqueue and cron).

-- Takashi

--
Takashi Matsuo

[Thiago Catoto]

Thanks Takashi!

And sorry about the wrong info Emanuele...

[Deepak Singh]

Hi Takashi,

How can we increase the deadline in case of SOAP client ?

Thanks

Deepak

Deepak Singh

[Emanuele Ziglioli]

Yes! +1

is there a way to do it?

I'm also experiencing a different problem on the production server:

http://stackoverflow.com/questions/11643218/error-in-javax-xml-ws-service-initialization-on-app-engine 

Deepak, 
it sounds you found a workaround for issue 4910, it that's the case, could you share your solution? thanks

http://code.google.com/p/googleappengine/issues/detail?id=4910 

Deepak

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Takashi Matsuo

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Deepak Singh

[Emanuele Ziglioli]

Hi everyone,

After a lot of digging I've given up on GAE's implementation of jaxws.

Their implementation can't be found by the Factory classloader, period.

So I've picked the Force.com Web Services Connector and managed to make it work.

There were bugs in the code generation process, in the generated code, and also the GAE connector needed some fixes.

I'm tempted to created a project on GitHub to show what I've done.

This implementation is faster and also you can set the socket timeout!

Cheers,

Emanuele

[Phil]

Emmanuele, Could you more describe your solution?

I've a lot of problem with timeout exception and Jax-ws. I'm looking for new solution for substituing Jax-RS for calling web services.

Thanks

Deepak

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Takashi Matsuo

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Deepak Singh

[Emanuele Ziglioli]

Ok,

have you managed to generate any code with the SalesForce tool?

As I wrote, I did get an error but most of the code generated anyway. I'll post the command line options I used if I can find them.

The generated code contains three packages:

com.sforce.ws.transport

     GaeHttpTransport.java (this is not specific to any WSDL)

com.sforce.soap.types

     Many classes, mostly dependent on the WSDL, similar to the code generated by jaxws

com.sforce.soap.service.dataxmldistribution.... // followed by the URL of your WSDL

    Connector.java

    SoapConnection.java

This last package, as far as I recall, was the one that had some problems. I've attached Connector.java.

We've also made some proprietary changes to SoapConnection.

We're using the implementation in wsc-22.jar

Example of usage:

try {

      ConnectorConfig config = new ConnectorConfig();

      config.setTransport( GaeHttpTransport.class );

      config.setTraceMessage(true);

      config.setReadTimeout(7000);  // this is the important part

      SoapConnection connection = Connector.newConnection(config);

      String xmlres = connection.getXml( parameters );

}

catch (ConnectionException e) {

}

You really need to pass the first stage of code generation, don't worry about errors, see if anything at all has been generated, look at the command line options. Look at their source code and google for errors. Their source code shows more options that are not documented.

Hope that helps,

E.

[Phil]

Thanks Emmanuel. Am I able to consume other web services with Force.Com or only the one of SaleForce?

I'm little bit confused of what is possible with Force.com.

By the way, Could you tell me if you know how to globally change the timeout of URL fetching in Google App Engine?

Thanks a lot.

[Emanuele Ziglioli]

On Thursday, 27 September 2012 18:56:09 UTC+12, Phil wrote:

Thanks Emmanuel. Am I able to consume other web services with Force.Com or only the one of SaleForce?

Sure you can, any WSDL 

I'm little bit confused of what is possible with Force.com.

It's very much like jaxws, just simpler and faster, it sits on top of URLFetch 

 

By the way, Could you tell me if you know how to globally change the timeout of URL fetching in Google App Engine?

There's no way I know to change the timeout using jaxws. But you can using the salesforce code, see comments in the code I posted yesterday