C# 同一服务器上的WCF服务之间响应缓慢
我在C# 同一服务器上的WCF服务之间响应缓慢,c#,wcf,enterprise-library,C#,Wcf,Enterprise Library,我在UAT环境中遇到了一个非常奇怪的问题。我有两个彼此通信的WCF服务。在较高的层次上,我的web应用程序与业务层通信,并从业务层将wcf请求传递给事务层,事务层处理所有请求并返回响应。我面临的问题是,事务层接收业务层发送的请求大约需要1分钟。有WCF服务部署在同一台服务器上,并且此应用程序设置在生产环境中运行良好,因此我不确定发生了什么 示例: Web前端向业务层发送wcf请求,以获取所有广告的列表。 业务层执行一些安全检查(我已从示例中删除),然后通过另一个WCF请求将请求传递到事务层。但是
UAT
环境中遇到了一个非常奇怪的问题。我有两个彼此通信的WCF
服务。在较高的层次上,我的web应用程序与业务层通信,并从业务层将wcf请求传递给事务层,事务层处理所有请求并返回响应。我面临的问题是,事务层接收业务层发送的请求大约需要1分钟。有WCF
服务部署在同一台服务器上,并且此应用程序设置在生产环境中运行良好,因此我不确定发生了什么
示例:
Web前端向业务层发送wcf请求,以获取所有广告的列表。
业务层执行一些安全检查(我已从示例中删除),然后通过另一个WCF请求将请求传递到事务层。但是事务层需要1分钟来接收这个请求
业务层:
public partial class AdsManagementService : IAdsManagementService
{
public ListAdvertisementResponse ListAdvertisement(ListAdvertisementRequest request)
{
LogManager.Write("Initiated AdsManagement.AdsManagentService.ListAdvertisement()", LogCategory.Trace.ToString());
var response = new ListAdvertisementResponse();
response.Advertisements = new List<Advertisement>();
LogManager.Write("Authentication token validated in AdsManagement.AdsManagentService.ListAdvertisement()", LogCategory.Event.ToString());
var client = new AdService.AdsManagementServiceClient();
try
{
response = client.ListAdvertisement(request);
LogManager.Write("response received by AdsManagement.AdsManagentService.ListAdvertisement()", LogCategory.Event.ToString());
}
finally
{
try
{
client.Close();
}
catch (Exception ex)
{
LogManager.ExceptionHandler(ex);
}
}
}
}
我设法弄明白了。IIS中的WCF应用程序被设置为多进程应用程序池,这似乎造成了问题。更改此选项后,所有WCF服务都使用单个流程应用程序池,日志文件现在创建在单个文件中,不再有延迟 这种情况是每次都发生还是只在第一次查询中发生?它是间歇性发生的。我在白天随机测试了它,有时它会立即响应,有时需要1分钟。我们的服务在UAT环境中“睡着”,而没有人使用它们。把他们叫醒要花很多时间。我不认为这是。。。可能每5-10分钟发生一次
public ListAdvertisementResponse ListAdvertisement(ListAdvertisementRequest request)
{
LogManager.Write("BEGIN - ListAdvertisement", LogCategory.Event);
var response = new ListAdvertisementResponse();
try
{
response.Advertisements = new List<AdvertisementType>();
var ads = AdvertisementDataContextInstance.Advertisements;
foreach (var ad in ads)
{
AdvertisementType advertisement = ConvertToAdvertisementType(ad);
string filePath = AdFilePath + @"\" + ad.Code;
if (Directory.Exists(filePath))
{
string[] files = Directory.GetFiles(filePath);
foreach (string file in files)
{
advertisement.Files.Add(file);
}
}
response.Advertisements.Add(advertisement);
}
}
catch (Exception ex)
{
response.ErrorAction = ResponseActionEnum.GeneralException;
response.ErrorDetails = ex.Message;
response.ErrorMessage = "Unable to list advertisements.";
}
LogManager.Write("END - ListAdvertisement", LogCategory.Event);
return response;
}
**Timestamp: 2/04/2013 9:23:08 AM**
Thread Name:
Category: Trace
Severity: Information
Message: Initiated AdsManagement.AdsManagentService.ListAdvertisement()
**Timestamp: 2/04/2013 9:23:08 AM**
Thread Name:
Category: Event
Severity: Information
Message: Authentication token validated in AdsManagement.AdsManagentService.ListAdvertisement()
**Timestamp: 2/04/2013 9:24:02 AM**
Thread Name:
Category: Event
Severity: Information
Message: Response received by AdsManagement.AdsManagentService.ListAdvertisement()
**Timestamp: 2/04/2013 9:24:02 AM**
Thread Name:
Category: Trace
Severity: Information
Message: Completed AdsManagement.AdsManagentService.ListAdvertisement()
**TRANSACTION LAYER LOG TRACE**
**2/04/2013 9:24:02 AM** - BEGIN - ListAdvertisement
**2/04/2013 9:24:02 AM** - BEGIN - ConvertToAdvertisementType
2/04/2013 9:24:02 AM - END - ConvertToAdvertisementType
2/04/2013 9:24:02 AM - BEGIN - ConvertToAdvertisementType
2/04/2013 9:24:02 AM - END - ConvertToAdvertisementType
2/04/2013 9:24:02 AM - BEGIN - ConvertToAdvertisementType
2/04/2013 9:24:02 AM - END - ConvertToAdvertisementType
**2/04/2013 9:24:02 AM** - END - ListAdvertisement
As you can see, there is roughly a 1 minute delay before the Transaction layer receives the request. I have no idea what is causing this. I think it might be the logging system (Microsoft.Practices.EnterpriseLibrary.Logging). I've noticed that it creates a separate log file almost every time it receives a request, almost as if the original log file is being kept open which stops it from writing to that file. Perhaps there is a 1 minute timeout on the logging before it decides to create a new log file and write to that?
I have the following log files in the logging directory for today's date: Every time I send a new request to the Transaction Layer, there is a 1min delay and then it creates a new log file:
RTITraceGeneral.log 02/04/2013 9:20 AM
RTIEvent.log 02/04/2013 9:20 AM
c9d64c18-80d9-4993-b167-2070190fce51RTITraceGeneral.log 02/04/2013 9:20 AM
a7acf427-a919-4fe4-9832-d186e9e28c0cRTIEvent.log 02/04/2013 9:24 AM
8e35dbdc-3c94-4e93-866a-3affcbf5f082RTITraceGeneral.log 02/04/2013 9:24 AM