| Author |
Message
|
| kayhansefat |
 Posted: Tue Mar 20, 2007 2:01 am Post subject: /var directory fills up quite quickly |
 |
|
Acolyte
Joined: 18 Oct 2006
Posts: 65
|
My /var directory seems to be continually written to and on a number of occasions has reached 100% causing me to have to clear out some log files. It seems to always be filled up with a certain "stdout" file which seems to be linked to the current broker.
I have noticed that within the directory:
/var/mqsi/components/WBRK6_DEFAULT_BROKER
the are a number of sub directories, the most recent being:
ec0f38fe-1001-000-0080-c6f0c37f60aa
Within here the stdout file seems to be written to every 5 or so seconds and is currently about 270mb in size. I actually done a /dev/null on the file yesterday so it is growing quite fast. There is only one flow deployed on the broker at the moment which hasnt had anything passed through it in about 24 hours.
Is this normal to have to monitor these files and clear them out? Is there a way to limit how often this log is being written to? Thanks. |
|
| Back to top |
|
 |
| jsware |
| Posted: Tue Mar 20, 2007 5:29 am Post subject: Re: /var directory fills up quite quickly |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| kayhansefat wrote: |
I have noticed that within the directory:
/var/mqsi/components/WBRK6_DEFAULT_BROKER
the are a number of sub directories, the most recent being:
ec0f38fe-1001-000-0080-c6f0c37f60aa
|
On my production installation of WBIMB v5 running on AIX, we don't have a /var/mqsi/components directory. A search on google for this directory only give me two hits:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/topic/com.ibm.etools.mft.eb.doc/au16534_.htm
discusses HTTP connections to a URL that does not match an HTTPInput node and
http://www.redbooks.ibm.com/redbooks/pdfs/sg247283.pdf which discusses managing resources in WMB.
Do either of these help you? Have you got any HTTP clients trying to connect to a URL on your message broker which does not match an HTTPInput node?
Try creating a flow with an HTTPInput node with the URL of /* (this should catch all invalid URLs I think) and dump the content to a trace node. You might be able to find our the source of the connection that way.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 20, 2007 6:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm sure components is new in v6.
First thing is to make sure that excessive tracing isn't enabled.
Then make sure that you haven't written any Java code or C code that is writing to stdout.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Mar 20, 2007 7:28 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
our /var/mqsi/components is only 15 MB large, altough we have plenty of flows running.
Like Jeff says, there might be tracing enabled.
What also is possible, is that some flow is running in a infinite loop. We also had this once, then those files get indeed very large. |
|
| Back to top |
|
|
| kayhansefat |
| Posted: Wed Mar 21, 2007 5:02 am Post subject: |
|
|
Acolyte
Joined: 18 Oct 2006
Posts: 65
|
Yep sorted. Some Java code was writing to it.
Many thanks. |
|
| Back to top |
|
|
|
|
