| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to inhibit System.out logs on get failure |
« View previous topic :: View next topic » |
| Author |
Message
|
| martin |
 Posted: Fri Aug 10, 2001 6:49 am Post subject: |
 |
|
Novice
Joined: 09 Aug 2001
Posts: 17
Location: Charlotte, NC
|
I have a MQSeries 5.2 NT Java application where the user depends on the system out screen for various purposes. The program also contains a loop that is doing a get on a queue. It is required to be a NO_WAIT get
to facilitate thread interrupts and has only a slight pause between gets.
As you can imagine, the System out screen becomes unusable due to the volume of messages like:
MQJE001: Completion Code 2, Reason 2033
Catching MQExceptions has not effect on the logging on this message.
Is there a way to stop, filter, or redirect this unwanted System.out output? Alternatively, is there a way to configure the unsatisfied get to not get a message?
thanks for any ideas, |
|
| Back to top |
|
 |
| kolban |
| Posted: Fri Aug 10, 2001 6:59 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
The public static field of MQException called "log" specifies where MQSeries logged messages are delivered. By default, this is System.out.err.
If you set this to null, no logging will occur:
for example:
MQException.log = null;
|
|
| Back to top |
|
|
| unichigid |
| Posted: Fri Jul 08, 2005 10:57 am Post subject: Need to know, where did u set that MQException.log = null. |
|
|
Novice
Joined: 22 Mar 2005
Posts: 17
|
[quote="martin"]I have a MQSeries 5.2 NT Java application where the user depends on the system out screen for various purposes. The program also contains a loop that is doing a get on a queue. It is required to be a NO_WAIT get
to facilitate thread interrupts and has only a slight pause between gets.
As you can imagine, the System out screen becomes unusable due to the volume of messages like:
MQJE001: Completion Code 2, Reason 2033
Catching MQExceptions has not effect on the logging on this message.
Is there a way to stop, filter, or redirect this unwanted System.out output? Alternatively, is there a way to configure the unsatisfied get to not get a message?
thanks for any ideas,[/quote]
Can you please let me know where did you set that MQException.log = null.
Thanks,
Ravi |
|
| Back to top |
|
|
| unichigid |
| Posted: Fri Jul 08, 2005 11:01 am Post subject: Hey ! can you let me know, how did you solve this problem. |
|
|
Novice
Joined: 22 Mar 2005
Posts: 17
|
Hi,
Can you kindly let me know, how did you solve this problem, coz even I am getting the same unwanted messages in my eclipse console.
Also, I am guessing it shouldn't cause any problem to my working components of WBI. Is that right ? If not what is the best solution to prevent any further problems.
Ravi
479-685-5983 |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jul 08, 2005 12:23 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Can you please let me know where did you set that MQException.log = null. |
That should be inside the program.
Do you have access to the source code of the application which is spitting out the errors in the STDOUT ? |
|
| Back to top |
|
|
| fergus |
| Posted: Thu Apr 20, 2006 3:28 am Post subject: |
|
|
Newbie
Joined: 20 Apr 2006
Posts: 3
|
You can also disable the " MQJE001: Completion Code 2, Reason 2033" trace by excluding the reason code using the method
| Code: |
| MQException.logExclude() |
as follows:
| Code: |
| MQException.logExclude(MQException.MQRC_NO_MSG_AVAILABLE); |
|
|
| 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
|
|
|
|
