| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 4 matches |
| Author |
Message |
 Topic: Possible memory leak from WMB API? |
richhall88
Replies: 10
Views: 6399
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 05, 2014 11:25 am Subject: Re: Possible memory leak from WMB API? |
ExecutionGroupProxy eg = ExecutionGroupProxy.getLocalInstance();
Instead of using the administration (CMP) API for this purpose, you could use the lightweight getExecutionGroup().getName() me ... |
| Topic: Possible memory leak from WMB API? |
richhall88
Replies: 10
Views: 6399
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 05, 2014 10:52 am Subject: Possible memory leak from WMB API? |
OK, did you also remove the lines where you connected to the BrokerProxy?
Nope. Don't have reference to this class in my code. |
| Topic: Possible memory leak from WMB API? |
richhall88
Replies: 10
Views: 6399
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 05, 2014 10:18 am Subject: Re: Possible memory leak from WMB API? |
ExecutionGroupProxy eg = ExecutionGroupProxy.getLocalInstance();
I'm not surprised. Seems your flow was trying to administer itself.
Hi Esa, not sure what you mean. All I wanted in my code ... |
| Topic: Possible memory leak from WMB API? |
richhall88
Replies: 10
Views: 6399
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 05, 2014 7:32 am Subject: Possible memory leak from WMB API? |
Hi folks,
I have experienced this resource problem such as: outOfMemoryError, or Resource temporarily unavailable in my message flow. I have tried to play around with the heapsize, but no luck. ... |
|
|
|
