MQSeries.net :: View topic - Delayed startup time on C# triggering application

Sudhir123 · Posted: Mon Jan 07, 2013 4:17 pm Post subject:

I have a C# triggering application with triggering threshold depth of 1. I am referencing the amqmdnet.dll (file version - 1.0.0.3, product version - 7.0.1.6) in my C# app. The C# application processes a messages on the queue within 3-4 sec when executed from the command prompt. However there is a startup delay of 8-9 sec when the application is triggered from the MQ trigger monitor. I have tried several things to figure out what's going on without any success. Below is the configuration:

WebSphere MQ v7.0.1.6
CMVC level: p701-106-110725
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Windows
Mode: 32-bit
O/S: Windows Ver 6.1 (7) Server Enterprise x64 Edition, Build 7601: SP1

C# Console application with build target X86 using .Net 3.5 (VS 2008) running on a 64 bit Windows 2008.

Here is what IBM had to say about it :

, it consistently takes 9 seconds from the point that the trigger
monitor issues the system command (to run it) to the actual execution of
the program, where it put out its first trace statement. The 9 seconds
is the time it must take for the system create a session for the program
complete with the .Net CLR, application code and load of non-managed
libraries. I suspect the faster load times when the program is run
directly from the command line are due to cacheing features within
Windows, that are not available when a .Net application is started
programmatically using the "system" api.

Any help would be appreciated. This is a production issue and I need to get this resolved ASAP.

Thanks!