|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
CONFIGURATION OF A JAVA PLUGIN NODE |
« View previous topic :: View next topic » |
Author |
Message
|
danielaphex |
Posted: Mon Jan 19, 2004 3:22 am Post subject: CONFIGURATION OF A JAVA PLUGIN NODE |
|
|
Apprentice
Joined: 07 Apr 2003 Posts: 28
|
Hi to everyone,
I would like to ask to whom it may concern the following questions related with Java PlugIn Nodes:
1) We are working on an AIX server (where the broker runs). Where do we can find the standard output of the Java program produced by the command System.out.println("")?
2) Is it mandatory to define any variable on AIX machine to allow this output display to be seen?
3) Is it necessarty to restart the broker each time a deployment is made, over the execution group which the plugin belongs to, even if any change over the plug-in node were produced?
I hope somebody could help me.
Thanks in advance, |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jan 19, 2004 5:49 am Post subject: Re: CONFIGURATION OF A JAVA PLUGIN NODE |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
danielaphex wrote: |
1) We are working on an AIX server (where the broker runs). Where do we can find the standard output of the Java program produced by the command System.out.println("")?
|
If System.out.println goes anywhere on any platform, it might show up in a usertrace. But I don't know that it will show up anywhere. At all. Well, I suppose it might also show up in the std out in the shell that is running the broker process - which I don't think you can redirect.
danielaphex wrote: |
2) Is it mandatory to define any variable on AIX machine to allow this output display to be seen? |
Again, to the best of my knowledge, there's nothing you can do to make this visible. Write to your own debug file instead, or use the API to put stuff to the System log (MBService.logInformation etc.)
danielaphex wrote: |
3) Is it necessarty to restart the broker each time a deployment is made, over the execution group which the plugin belongs to, even if any change over the plug-in node were produced? |
I don't know. I suspect so. Have you tried it? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
danielaphex |
Posted: Tue Jan 20, 2004 1:34 am Post subject: |
|
|
Apprentice
Joined: 07 Apr 2003 Posts: 28
|
danielaphex wrote:
Quote: |
3) Is it necessarty to restart the broker each time a deployment is made, over the execution group which the plugin belongs to, even if any change over the plug-in node were produced? |
JeffLowrey wrote:
Quote: |
I don't know. I suspect so. Have you tried it? |
Yes, I have just tried and either my broker configuration is not the standard one or it is really of this way.
But, nevertheless, I think It is not the rigth way to work, is not it?
Thanks, anyway, for your help.
Cheers |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Jan 20, 2004 6:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
danielaphex wrote: |
Yes, I have just tried and either my broker configuration is not the standard one or it is really of this way.
But, nevertheless, I think It is not the rigth way to work, is not it? |
Just to be clear, you only need to restart the broker if you have changed the jar (or lil) file for the plug-in. You don't need to restart the broker after a normal deployment. I'm reasonably certain that merely restarting an execution group process will NOT reload a redeployed plug-in.
But I could be wrong on that.  _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|