|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Broker usage of /tmp on AIX |
« View previous topic :: View next topic » |
Author |
Message
|
pfarrel |
Posted: Mon Jul 23, 2007 6:34 am Post subject: Broker usage of /tmp on AIX |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
I am running WMB ( Websphere Message Broker ) version 6.0.0.4 on AIX. We have noticed that it seems to be using a lot of space in the /tmp folder. When the broker is down, /tmp shows 4 percent used. When the broker is up, /tmp shows 63 percent used. In looking at the files we see that there are a number of files in /tmp/IBMRAC that are created when the broker is started, but they all have length of zero. Apart from that, I can't see where the /tmp space is going. Any ideas ? |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jul 23, 2007 6:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
/tmp/IBMRAC should be Rational Agent Controller, not Broker.
Presumably you won't be running RAC on Production, so this is not really an issue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
pfarrel |
Posted: Mon Jul 23, 2007 6:54 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
This problem is occurring on my production system.
I have put a question into IBM on this, and here is what they have told me:
A customer might notice that there appears to be a reduction in free
space available on the /tmp filesystem while his V6 Broker is running.
No unexplainable files can be seen when using "ls" or "du", but the
effect is clearly visible using "df".
When the Broker or Configuration Manager starts, the Java runtime unzips
JAR files into a temporary directory, the Java TMPDIR directory. This
results in six jar_cache files with a combined size of about 10.5Mb -
for each Execution Group. On Linux, UNIX and z/OS systems, the TMPDIR is
usually /tmp; on Windows systems, it is C:\Documents and
Settings\IBM_USER\Local Settings\Temp. If this directory is not large
enough to hold the JAR files, the Broker or Configuration Manager will
not start.
It is not possible to avoid the creation of these files, but it is
possible to specify their location by setting the environment variable
MQSIJVERBOSE=-Djava.io.tmpdir=desired_path. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jul 23, 2007 6:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Well, I guess you've solved your problem, then.
But again, I hope you aren't running RAC on your production server. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
pfarrel |
Posted: Mon Jul 23, 2007 7:09 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
I am not running RAC on my production system. In fact, it is not installed. Strangely enough I am getting all these zero length files created in /tmp/IBMRAC when the broker starts however. They have strange names, here is one of them:
UUID-1184947091-901836-440201729-2036406003
All the names are similar to this.
I'm assuming that this is not a problem, and is normal. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jul 23, 2007 7:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
They're possibly socket/IPC files for Broker components to talk to RAC with.
Named Pipes, as it were. _________________ 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
|
|
|
|