| Author |
Message
|
| shubham_rajput |
 Posted: Tue Mar 13, 2018 1:26 am Post subject: How to stop broker recording Standard system log |
 |
|
Novice
Joined: 29 Aug 2017
Posts: 13
|
Hi all,
I am having a flow with HTTPS input node configured. Every 5 sec the flow receives request and Broker record standard system log at workpath\components\broker_name\integration_server_uuid\console.txt file in windows.
Since every 5 sec the log gets populated the size gets upto 120 MB within 5 min. Therefore I want to stop the broker to record standard system log.
I have tried the following commands in IIB Console but still the standard system log in console.txt gets populated:
| Code: |
| mqsichangetrace MB8BROKER -u -e default -l none |
| Code: |
| mqsichangetrace BrokerA -t -b -l none |
Is there some command which can stop broker to record standard system log?
Please help out guys  |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Tue Mar 13, 2018 2:05 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
Hi...I could be wrong but I don't think there is a standard way to switch off the already redirected stdout/stderr in broker.
What exact info is getting logged at the moment? In case if you have some sort of tracing/trace nodes in the flow it is worth getting those to log the trace details to some other file for which you can then put archiving mechanisms in place.
Last edited by abhi_thri on Tue Mar 13, 2018 5:36 am; edited 2 times in total |
|
| Back to top |
|
|
| shubham_rajput |
| Posted: Tue Mar 13, 2018 2:14 am Post subject: |
|
|
Novice
Joined: 29 Aug 2017
Posts: 13
|
Hi there is no Trace node included in the flow.
The standard log that is getting logged in console.txt is generally the certificates and client,server handshake details log since HTTPS input node is used in the flow to receive the request. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 13, 2018 5:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shubham_rajput wrote: |
| The standard log that is getting logged in console.txt is generally the certificates and client,server handshake details log since HTTPS input node is used in the flow to receive the request. |
On Windows, the broker writes log entries as Windows events. On Linux, it sends log events to the syslog daemon process.
Whatever's writing to that text file isn't an OOTB IBM component.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shubham_rajput |
| Posted: Tue Mar 13, 2018 5:24 am Post subject: |
|
|
Novice
Joined: 29 Aug 2017
Posts: 13
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 13, 2018 5:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Things you learn. 
Going to be awkward when we move to 9.0.0.8
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Tue Mar 13, 2018 5:50 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
|
| Back to top |
|
|
| shubham_rajput |
| Posted: Tue Mar 13, 2018 9:25 pm Post subject: |
|
|
Novice
Joined: 29 Aug 2017
Posts: 13
|
Hi Abhi
Thanks for your reply.
From your reply I remembered that Indeed I had added Environment Variable in my local system:
| Quote: |
| IBM_JAVA_OPTIONS=-Djavax.net.debug=true |
I just deleted that.
Since the log was still getting generated even though I restarted the broker, I restarted the system since changing environment variables requires system restart sometimes.
After restarting the system I restarted the broker again and now no standard log are getting logged in console.txt.
Thanks a lot for your help. |
|
| Back to top |
|
|
|
|
