| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| how can I configure the memory of the message flow using |
« View previous topic :: View next topic » |
| Author |
Message
|
| lcl3977 |
 Posted: Thu Jul 06, 2006 12:34 am Post subject: how can I configure the memory of the message flow using |
 |
|
Apprentice
Joined: 04 Jul 2006
Posts: 27
|
how can I configure the memory of the message flow using in WMB?
can somebody help me?
I use mqsichangeproperties ,but I can't find the right parameter.
When I put one 100MB message to queue.the WMB can't process it.and the message flow use about 1000mb memory.and then release it fastly.
I thank maybe the memory of this message flow used is not enough.
but out server has 16GB memory.
... |
|
| Back to top |
|
 |
| TheBigEasy |
| Posted: Thu Jul 06, 2006 2:21 am Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Hi lcl3977
I suggest you search for 'Resolving problems with performance' in the Infocenter.
Much of the allocation you can do is platform specfic.
Cheers |
|
| Back to top |
|
|
| lcl3977 |
| Posted: Thu Jul 06, 2006 7:56 pm Post subject: |
|
|
Apprentice
Joined: 04 Jul 2006
Posts: 27
|
TheBigEasy,thank you for you replay.
I had searched it in InfoCenter .but I can't find the right way.... |
|
| Back to top |
|
|
| TheBigEasy |
| Posted: Fri Jul 07, 2006 2:53 am Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Hi lcl3977
What platform are you running on?
Best wishes |
|
| Back to top |
|
|
| TheBigEasy |
| Posted: Fri Jul 07, 2006 3:00 am Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Extract for you
You experience configuration problems with a large number of components
Scenario: You are experiencing configuration problems with a large number of components.
Explanation: If you are running WebSphere Message Broker with a large number of configured components, the memory footprint of the broker processes (particularly the DataFlowEngine) might exceed their memory limits. In particular, the user process limit might be exceeded, or the address space limit might be reached. You might encounter problems, such as the BIP2106E error message, when running a broker with:
A large number of message flows
Multiple databases
Very large input or output messages
Solution: Use tools that are specific to your operating system to check the maximum size of the failing process, then check for any user limits (if applicable) or computer limits on process size.
Use the ulimit command to check user limits on Linux or UNIX systems and increase if needed.
There is a hard limit on each operating system for the maximum process size, beyond which failure is inevitable:
Operating system Maximum process size
Windows
2 GB
Solaris
About 3.75 GB
HP-UX
About 3 GB, depending on kernel settings
AIX (32 bit system)
2 GB
z/OS
2 GB
Increasing user limits beyond these values will not make any difference. If your broker processes regularly reach these sizes, consider spreading your message flows across more execution groups to reduce the size of each one below these limits.
On AIX, WebSphere Message Broker limits DataFlowEngines to two 256 MB memory segments, that is, 512 MB. Normally DataFlowEngine processes do not require more than 512 MB of the AIX address space, so the DataFlowEngine executable file is linked so as to have a default address space of two segments. However, it is possible to extend the size of the AIX address space available to the DataFlowEngine process by increasing the number of 256 MB memory segments available to it. You can patch the DataFlowEngine to use more memory segments using the following shell command:
/usr/bin/echo '\0100\0\0\0'|dd of=executable_file_name bs=4 count=1 seek=19
conv=notrunc
This creates a version of the DataFlowEngine that uses four segments (that is, 1 GB).
Alternatively, on AIX 5.1 and above, you can achieve the same result by using the ldedit command:
ldedit -b maxdata:0x40000000 DataFlowEngine
The application of fix pack maintenance replaces the existing DataFlowEngine, so if you have used the above process, repeat it after every fix pack installation.
The technique described above overrides only the soft limit and not the hard limit. If your broker processes regularly reach these sizes, consider spreading your message flows across more execution groups to reduce the size of each one to be below these limits. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jul 07, 2006 3:07 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
|
| 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
|
|
|
|
