| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| trigger monitor issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqmart |
 Posted: Sat Dec 06, 2003 5:06 pm Post subject: trigger monitor issue |
 |
|
Newbie
Joined: 06 Dec 2003
Posts: 2
|
| I have a local queue triggered to run a process with a korn shell script ( script is custom wrapper that pulls data from the queue). When trigger monitor service is running under MUSR_MQADMIN id the trigger msg is sent to the dead letter queue with the error: MQFB_APPL_CANNOT_BE_STARTED. When I stop the service and run the trigger monitor in a dos window ( under different login id ) the korn shell script works just fine. Note: using MKS Toolkit software to allow korn shell to work in Windows environment. Does anyone know why script is successfully kicked off by MQ when trm is running under one ID but not with the service and ID: MUSR_MQADMIN. OS is W2K and MQ is version 5.3 CSD 4. Please assist. Thanks ! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Dec 07, 2003 6:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mqmart wrote: |
| Does anyone know why script is successfully kicked off by MQ when trm is running under one ID but not with the service and ID |
Umm, because it's running under a different ID.
This means that all of these things are different (and more): - Security context (file, registry, network permissions are different)
- Environment (classpath, path, etc.)
- MQ permissions
- Working directory
- etc
.
So it could be that your service ID doesn't have permissions to execute your program. It could be that your service id doesn't have permissions to the files your program needs to start up. It could be that your service ID doesn't have the right things set up on the PATH or CLASSPATH in the environment it's running under. It could be that your service ID doesn't have the necessary permissions on the MQ objects you're accessing (although if you're really running as MUSER_MQADMIN, that's not likely). It could be that your program is running in a different working directory than you expect, and thus it can't find things it needs to.
Or it could be any combination of all of these, and other things as well.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmart |
| Posted: Mon Dec 08, 2003 8:52 am Post subject: [SOLVED] trigger issue |
|
|
Newbie
Joined: 06 Dec 2003
Posts: 2
|
| Thanks for the feedback. I failed to restart the server after installing MKS so the environment variables ( although present in PATH ) were not set. Reboot fixed the issue. |
|
| 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
|
|
|
|
