|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Background trigger problem |
« View previous topic :: View next topic » |
Author |
Message
|
AlainB |
Posted: Tue Sep 09, 2003 5:58 am Post subject: Background trigger problem |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
Hi all,
We are having a strange problem on a windows NT queue manager. We have a queue, which is triggered on first message to start an application.
This doesn't work : the application is not started.
If we run the trigger monitor in foreground (so not from the MQSeries Services), it's running fine : the trigger monitor starts our application.
We've changed the process definition to start a batch file : when running in background, the trigger monitor doesn't start our application, but if we ask it to start notepad, the batch file starts notepad successfully.
From all of these, we assume it's right problems. The MQSeries service is started with the system account, so the trigger monitor too (?).
The System account has all rights (full control) on the files and directories it needs to access ... but that doesn't work
So, giving we have absolutely no error generated in the DLQ, no particular message in the AMQERRx.LOG files, how can we solve that ?
Alain B _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
RogerLacroix |
Posted: Tue Sep 09, 2003 9:07 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
Yup, you are right but you are wrong. I recently went through great pains to get a GUI program to trigger correctly.
You are right because it "appears" that notepad did not start but in actual fact, notepad was triggered but it is running under the MUSR_MQADMIN UserID. Hence you cannot see notepad.
If you bring-up Windows' "Task Manager", click the "Processes" tab, double click on the name column to sort them, then you will see "x" notepads running. Don't be surprised if you see 20 of them running.
It is extremely compilcated to get a triggered (by NT Service) Windows GUI program to operate in the "current" logged on user's address space.
On the other hand, if your GUI Windows program, starts, processing messages then ends without needing user interaction then just create a standard MQ Process definition and you will be fine.
later
Roger... _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
 |
AlainB |
Posted: Wed Sep 10, 2003 3:43 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2002 Posts: 79 Location: Belgium
|
It seems I've badly explained the problem ... the notepad application starts, in background (so not on the desktop, but present in the task manager).
But my application, which should read the MQ queue, doesn't even start. My program is not a GUI one, it's just something reading the queue and sending the message somewhere thru an home-based middleware. _________________ Alain Buret
Visit http://www.fosdem.org |
|
Back to top |
|
 |
RogerLacroix |
Posted: Wed Sep 10, 2003 8:37 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
When you run your program from the command prompt, does it work?
Do you have any dependencies?
- Do you pass input arguments to it?
- Does your program expect / require to be run from a particular directory?
Check your program to see if you are reading a properties or ini file but the full path is not specified.
later
Roger... _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|