| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| using trigger on MQseries 5.3 for inviking java prog. |
« View previous topic :: View next topic » |
| Author |
Message
|
| geniemani |
 Posted: Wed May 07, 2003 5:45 am Post subject: using trigger on MQseries 5.3 for inviking java prog. |
 |
|
Newbie
Joined: 05 May 2003
Posts: 8
|
hi,
it is said that the trigger option in queues can be used for
invoking a specific java file which will process the incoming message....
how to go about this... since i dont want a java file to be polling continuously to the queue ... would be gr8 if the same would be invoked
on every incoming msg...
thnx
_________________
visit http://www.geniemani.com |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed May 07, 2003 6:14 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Yes you can do that.
You have to set the trigger on the queue....
define a process and run the trigger monitor. For detailed instructions refer o the manuals
Chapter 14 in Application Programming guide.
GOOD LUCK
-------
Venny |
|
| Back to top |
|
|
| Martin Rusoff |
| Posted: Sun May 18, 2003 11:08 am Post subject: Triggering and some alternatives |
|
|
Newbie
Joined: 24 Jun 2002
Posts: 2
Location: Columbus Ohio
|
In general, triggering java programs works fine, but with a couple of caveats...
-- Java startup tends to be a bit slow and resource intensive (a couple at the same time is awful.
-- There are some bugs that may cause you to have to run the java code with the JIT turned off, particularly with MQSeries 5.3 and AIX JVMs prior to 1.4 (we haven't tested 1.4 as we are running a pre-5 version of AIX and cannot.
-- It really doesn't take any resources to speak of to have your application wait on the get (which is a specifiable parameter. If the rest of the application needs to keep running while waiting, you can make it a thread... There are seomk significant advantages to the latter approach, such as being able to listen to more than one queue or be able to notice that you haven't had messages for a while.
We usually have a shell script that kicks off the java program and also logs the fact that it kicked off, when it terminated and handles redirecting the STDIO and STDERR to the right places (a log) and then scans the logfile for errors and emails if we found any. This also can provide a smarter way to disable the trigger by having the script check for a file like "TRIGGER_NAME.disable". This way it can be enabled and disabled be a program, say part of your installation script for production changes WITHOUT fiddling with the MQSeries configuration in production.
-Mrrtin Rusoff, Info-Scape Ltd. |
|
| 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
|
|
|
|
