Lifetime very slow after upgrade to 8.0.0.12

Lifetime very slow after upgrade to 8.0.0.12

  
Hello,

last week, after performing an upgrade from version 8.0.0.3 to 8.0.0.12 (Platform Server and Integration Studio) and 8.0.0.15 (Service Studio) my access to Lifetime has become incredibly slow and I have some errors in Service Center like the following:

Error Detail

Back to Log 

Id: 

70c7b720-4441-444f-9887-ce0708e01057 

Time of Log: 

2013-10-14 13:40:58 

eSpace: 

LifeTimeEngine 

Tenant: 

ServiceCenter 

User: 

Session Id: 

No session 

Server: 

TN001-AP002 

Module: 

Web Reference 

Message: 

The request failed with HTTP status 504: Gateway Timeout. 

Stack: 

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at ssLifeTimeCore.WRefPlatformServices.WRefPlatformServices_v8_0_0.Server_GetStatus(String inWSUsername, Boolean inWSUsernameSpecified, String inWSPassword, Boolean inWSPasswordSpecified, WORCCS_EnvironmentReportRecord& outWSEnvironmentReport)
-Env-
eSpaceVer: 2 (Id=34, PubId=30, CompiledWith=8.0.0.12)
RequestUrl: http://127.0.0.1/LifeTimeEngine/_TimerHandler.asmx (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/LifeTimeEngine-1-130262221872116000
FilePath: D:\...\PS\running\LifeTimeEngine.8824075\
Locale: en-US
DateFormat: dd/MM/yyyy
PID: 3884 ('w3wp', Started='10/14/2013 11:02:35 AM', Priv=105Mb, Virt=769Mb)
TID: 12
Thread Name: 
.NET: 2.0.50727.5472 

Since there's a timeout message and performed a network verification and the speed looks fine. I also didn't detect any packet losses.
Is there anyone else facing a similar issue?

Thanks in advance.

Marcus Santos
We have been using Lifetime for a while and have mainly problems on the synchronization part.
Justin James has advised everybody to upgrade to 8.0.1.25, because of fixes included regarding lifetime.

Regards Eric de Bruin
I'd say wait a week and go to 8.0.1.27... there's a fix in there that in our environment reduced CPU use on our SQL Server from 60% at peak hours to 20%. :D

J.Ja