BindingProviderProperties and JAXWSProperties not supported on GAE

1,778 views
Skip to first unread message

Deepak Singh

unread,
Oct 17, 2011, 11:10:03 AM10/17/11
to google-a...@googlegroups.com
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

Deepak Singh

unread,
Oct 18, 2011, 11:48:24 AM10/18/11
to google-a...@googlegroups.com
Resending... 

Pls let me know if i need to open an issue.

Thanks
Deepak

Deepak Singh

unread,
Oct 19, 2011, 10:40:16 AM10/19/11
to google-a...@googlegroups.com
I opened an issue 6148 for this feature request and workaround till date.

Thanks
Deepak

On Mon, Oct 17, 2011 at 8:40 PM, Deepak Singh <deepaks...@gmail.com> wrote:

Michel Jonker

unread,
Oct 28, 2011, 7:11:50 AM10/28/11
to Google App Engine
+1

If you have a workaround, please let me know.

Deepak Singh

unread,
Oct 28, 2011, 11:51:07 PM10/28/11
to google-a...@googlegroups.com
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.



--
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.


Brandon Wirtz

unread,
Oct 29, 2011, 4:36:00 AM10/29/11
to google-a...@googlegroups.com

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.

Michel Jonker

unread,
Nov 28, 2011, 6:58:27 AM11/28/11
to Google App Engine
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" <drak...@digerat.com> 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: google-a...@googlegroups.com
> [mailto:google-a...@googlegroups.com] On Behalf Of Deepak Singh
> Sent: Friday, October 28, 2011 8:51 PM
> To: google-a...@googlegroups.com
> 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 <michel.jon...@e-office.com>

> <mailto:google-appengine%2Bunsu...@googlegroups.com> .
> For more options, visit this group athttp://groups.google.com/group/google-appengine?hl=en.

Brandon Wirtz

unread,
Nov 28, 2011, 4:38:18 PM11/28/11
to google-a...@googlegroups.com
Fetch used to time out at 8 seconds on GAE, it is possible that the WDSL has
to be returned in the old 8 seconds. You could copy the WDSL somewhere
static, that would serve it faster.
Reply all
Reply to author
Forward
0 new messages