Hi,

The time out occurs much faster than 60 seconds, it triggers in 7
seconds, according to this log:

28-nov-2011 12:46:08 com.simservices.simcardmanager.TelenorClient
changeSimStatus
FINE: start change status of 89460800000105350112 to Activate
28-nov-2011 12:46:15 com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: /simblokkeer
javax.xml.ws.WebServiceException: Failed to access the WSDL at:
https://serviceportal.telenorconnexion.com/api/SubscriptionManagement?WSDL.
It failed with:
        Timeout while fetching: 
https://serviceportal.telenorconnexion.com/api/SubscriptionManagement?WSDL.
        at
com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:
151)

I can only conclude that something other than the mentioned 60 seconds
is causing this time.
A browser fetch for the WSDL url takes 25 seconds...

I know I need to talk to the service provider, but still it is less
than 60 seconds.

Regards

Michel




On 29 okt, 09:36, "Brandon Wirtz" <[email protected]> wrote:
> The maximum execution time for any request on a front end instance is 60
> Seconds. This cannot be over-ridden
>
> You can break complex tasks in to chained tasks using multiple fetches.
>
> Do something that takes 50seconds
>
> Fetch stuff to do for the next 50 seconds
>
> Fetch stuff to do for another 50 seconds
>
>                 Report task complete.
>
> This works well with AJAX so that you can update that status every so often.
>
> If this won't work for you consider pushing your task to a back end instance
> and only check the status  from time to time.
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Deepak Singh
> Sent: Friday, October 28, 2011 8:51 PM
> To: [email protected]
> Subject: Re: [google-appengine] Re: BindingProviderProperties and
> JAXWSProperties not supported on GAE
>
> Nope. I dont have any workaround and am surprised that even no one from
> google has replied over this issue to let us know any workaround.
>
> On Fri, Oct 28, 2011 at 4:41 PM, Michel Jonker <[email protected]>
> wrote:
>
> +1
>
> If you have a workaround, please let me know.
>
> On Oct 17, 5:10 pm, Deepak Singh <[email protected]> wrote:
>
>
>
>
>
>
>
>
>
> > Hi,
>
> > I have JAXWS-2.1.6 client running on GAE 1.5.5
> > I need to increase the timeout to 60 sec as follows
>
> > import com.sun.xml.internal.ws.client.BindingProviderProperties;
> > import com.sun.xml.internal.ws.developer.JAXWSProperties;
>
> > Map<String, Object> context =
> > ((BindingProvider)tktPort).getRequestContext();
> > context.put(BindingProviderProperties.CONNECT_TIMEOUT, 60000);
> > context.put(JAXWSProperties.CONNECT_TIMEOUT, 60000);
>
> > But  BindingProviderProperties and JAXWSProperties are not supported on
> GAE
> > 1.5.5 still.
>
> > So Any idea how can i increase the timeout.
>
> > Also, Is there a way so that i can set a specific timeout for entire
> > application. I mean to say application specific connect timeout to be set
> on
> > GAE.
> > Is there a way to achieve this ?
>
> > Thanks
> > Deepak
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]
> <mailto:google-appengine%[email protected]> .
> For more options, visit this group 
> athttp://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 [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group 
> athttp://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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to