I can't see any reasons why these services should wait 20! hours so I put 2 hours max as in other services. I guess it was entered
by error once and copied many (only in the content compoment)
Fixed at revision: 762329
Thanks
Jacques
From: "Enrique Ruiz - DiSiD" <
[hidden email]>
>
> No, just to be sure it is not a bug ... normally the services that have the
> timeout setted are 7200ms not 72000ms.
>
>
> BJ Freeman wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> is this giving you a problem?
>> which service is not working?
>>
>> eruiz. DiSiD Technologies sent the following on 4/4/2009 8:32 AM:
>>> Hi,
>>>
>>> Why the content services (applications/content/servicedef/services.xml)
>>> have
>>> a timeout so high: 72000?
>>>
>>> Thanks
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (MingW32)
>> Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org>>
>> iD8DBQFJ14CHrP3NbaWWqE4RAm5jAJ0UZscUQaGUMdNgDh1HdN4xm4y42wCgo9Co
>> /ecu9cE4NAr4SdMRpne6zCM=
>> =pvyH
>> -----END PGP SIGNATURE-----
>>
>>
>
> --
> View this message in context:
http://www.nabble.com/Content-services-timeout-tp22884634p22902379.html> Sent from the OFBiz - User mailing list archive at Nabble.com.
>
Locked
