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


Le jeudi 26 juillet 2012 07:26:55 UTC+2, Emanuele Ziglioli a écrit :
>
> 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
>
> On Thursday, 26 July 2012 09:14:38 UTC+12, Emanuele Ziglioli wrote:
>>
>> 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 
>>
>>
>>
>> On Thursday, 26 July 2012 04:12:59 UTC+12, Deepak Singh wrote:
>>>
>>> Hi Takashi,
>>>
>>> How can we increase the deadline in case of SOAP client ?
>>>
>>> Thanks
>>> Deepak
>>>
>>> On Wed, Jul 25, 2012 at 7:50 PM, Thiago Catoto 
>>> <[email protected]<javascript:>
>>> > wrote:
>>>
>>>> Thanks Takashi!
>>>>
>>>> And sorry about the wrong info Emanuele...
>>>>
>>>> On Wed, Jul 25, 2012 at 11:01 AM, Takashi Matsuo 
>>>> <[email protected]<javascript:>
>>>> > wrote:
>>>>
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>> On Wed, Jul 25, 2012 at 10:36 PM, Thiago Catoto 
>>>>> <[email protected]<javascript:>
>>>>> > wrote:
>>>>>
>>>>>> 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.
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 24, 2012 at 10:13 PM, Emanuele Ziglioli <
>>>>>> [email protected] <javascript:>> wrote:
>>>>>>
>>>>>>> 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) 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, 21 June 2012 21:49:28 UTC+12, Michel Jonker wrote:
>>>>>>>>
>>>>>>>> Yes I have the same issue, I cannot find a way to increase the 
>>>>>>>> connect timeout through JAX-WS that is allowed by Google...
>>>>>>>>
>>>>>>>> On Friday, June 1, 2012 11:32:20 AM UTC+2, Deepak Singh wrote:
>>>>>>>>>
>>>>>>>>> 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 
>>>>>>>>> <[email protected]<javascript:>
>>>>>>>>> > 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<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
>>>>>>>>>
>>>>>>>>  -- 
>>>>>>> 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 
>>>>>>> [email protected]<javascript:>
>>>>>>> .
>>>>>>> To unsubscribe from this group, send email to 
>>>>>>> [email protected] <javascript:>.
>>>>>>> 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 
>>>>>> [email protected]<javascript:>
>>>>>> .
>>>>>> To unsubscribe from this group, send email to 
>>>>>> [email protected] <javascript:>.
>>>>>> 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 
>>>>> [email protected]<javascript:>
>>>>> .
>>>>> To unsubscribe from this group, send email to 
>>>>> [email protected] <javascript:>.
>>>>> 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 
>>>> [email protected]<javascript:>
>>>> .
>>>> To unsubscribe from this group, send email to 
>>>> [email protected] <javascript:>.
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/google-appengine?hl=en.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Deepak Singh
>>>  
>>

-- 
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/-/6lCN-KrCAU0J.
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