|
Home > Archive > WebSphere Application Server > September 2005 > OutOfMemory attempting to get Onames with queryNames()
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
OutOfMemory attempting to get Onames with queryNames()
|
|
|
| I have a client application written in Java that attempts to connect to a WebSphere server. Once connected the client calls to get all the Onames, configs & stats from the server. In one instance, this client is connecting to a deployment manager OK, bu
t then is getting an OutOfMemory exception when it asks for the Onames. It works if we connect to the individual servers in the cell, but not the deployment manager.
Is it possible that there are so many objects that we are really running out of memory? Or maybe there's some circular condition in the objects that's causing this?
Here's the stack trace of the exception:
java.lang.OutOfMemoryError
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:610)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:579)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.queryNames(SOAPConnectorClient.java:381)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:321)
at $Proxy0.queryNames(Unknown Source)
at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:87)
at com.firehunter.agent.websphere.WebSphereCoordinator.getOnames(WebSphereCoordinator.java:199)
at com.firehunter.agent.websphere.WebSphereCoordinator.runCoordinator(WebSphereCoordinator.java:163)
at com.firehunter.agent.websphere.WebSphereCoordinator.main(WebSphereCoordinator.java:48)
Exception in thread "main"
**
| |
| Ken Hygh 2005-09-26, 6:04 pm |
| jeff.kehoe@indicative.com wrote:
>I have a client application written in Java that attempts to connect to a WebSphere server. Once connected the client calls to get all the Onames, configs & stats from the server. In one instance, this client is connecting to a deployment manager OK, b
ut then is getting an OutOfMemory exception when it asks for the Onames. It works if we connect to the individual servers in the cell, but not the deployment manager.
>
>Is it possible that there are so many objects that we are really running out of memory? Or maybe there's some circular condition in the objects that's causing this?
>
>Here's the stack trace of the exception:
>
>java.lang.OutOfMemoryError
> at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:610)
> at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:579)
> at com.ibm.ws.management.connector.soap.SOAPConnectorClient.queryNames(SOAPConnectorClient.java:381)
> at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:321)
> at $Proxy0.queryNames(Unknown Source)
> at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:87)
> at com.firehunter.agent.websphere.WebSphereCoordinator.getOnames(WebSphereCoordinator.java:199)
> at com.firehunter.agent.websphere.WebSphereCoordinator.runCoordinator(WebSphereCoordinator.java:163)
> at com.firehunter.agent.websphere.WebSphereCoordinator.main(WebSphereCoordinator.java:48)
>Exception in thread "main"
>**
>
>
>
Try setting your -Xmx higher. I've connected to a dmgr and dumped all
the names without a problem.
Ken
| |
|
| We tried setting -Xmx to 1024, same results.
The server has 3.5 Gig RAM, VM page file size for all hard drives set to 2046.
| |
| Ken Hygh 2005-09-26, 6:04 pm |
| jeff.kehoe@indicative.com wrote:
>We tried setting -Xmx to 1024, same results.
>
>The server has 3.5 Gig RAM, VM page file size for all hard drives set to 2046.
>
>
>
OK, let's try another tack...make sure you're using the JVM that comes
with WebSphere when executing this.
Ken
| |
|
| Ken,
Thanks for your help. We'll give that a try. We are currently running on Windows 2003 with the following java:
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
We've run this version successfully with WebSphere Deployment Managers elsewhere.
Are you aware of any known problems with it?
| |
| Ken Hygh 2005-09-27, 7:59 am |
| jeff.kehoe@indicative.com wrote:
>Ken,
>
>Thanks for your help. We'll give that a try. We are currently running on Windows 2003 with the following java:
>
>java version "1.4.2_08"
>Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
>Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
>
>We've run this version successfully with WebSphere Deployment Managers elsewhere.
>
>Are you aware of any known problems with it?
>
>
Not aware of any, just trying to see if there's some difference between
whatever it is that I'm running - WAS 6 - vs. what you're running.
Ken
|
|
|
|
|