EAServer 6.3 OutofMemory

Chris,

I'm using the NFR release of Powerbuilder from ISUG which is
11.5, build 3127. I'm trying to make sure we're in position
to upgrade from Powerbuilder 11.0.1 before we purchase the
upgrade. EAServer version is 6.3 developer edition (again,
to be upgraded to Advanced once we know it will work for
us). This is all running on Windows XP Pro SP2.

As for EAServer, I have not made any configuration changes
to EAServer except to define connection caches. I have been
able to successfully deploy objects to that EAServer with
this configuration BUT not past a certain number of objects.
It seems to me like there is a memory leak. I've even
encountered a few instances where when I run my application
after deployment I get an OutOfMemory condition in EAServer.

Any thoughts or suggestions?

Thanks,
Shawn

Post by Chris Pollach
Hi Shawn;
I am using EAS 6.3 with PB 11.5.1 and 12 Classic and
able to deploy with no problems.
I have two machines .. but, both of these are 4 G - one XP
and the other Vista.
What version of PB are you using?
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
frustrated!!! >

I've been trying to put together an upgrade of our
EASErver system to get it up to EAServer 6.3 but I can't
deploy more than a few objects without getting
OutOfMemory errors. I'm attaching my log file in hopes
that this will shed some light on the problem.
I understand that compared to pre version-6 EAServers,
EAServer now compiles Powerbuilder objects into java
(right?). I just upgraded the RAM on my laptop to 2GB
and I had assumed this would give me the memory I needed
to do my deployments. It looks like I was wrong!
Does anyone have any suggestions on what I need to do to
be able to deploy objects from PB 11.5 to EAServer 6.3
and have it be successful rather than failing on

OutOfMemory errors? >

Note attached log file.
Thanks,
Shawn

Chris Pollach

2009-09-15 14:36:08 UTC

FWIW: You can apply the PB 11.5.1 maintenance release (build 4011). It is
available for a free download at www.sybase.com.

Post by unknown
Chris,
I'm using the NFR release of Powerbuilder from ISUG which is
11.5, build 3127. I'm trying to make sure we're in position
to upgrade from Powerbuilder 11.0.1 before we purchase the
upgrade. EAServer version is 6.3 developer edition (again,
to be upgraded to Advanced once we know it will work for
us). This is all running on Windows XP Pro SP2.
As for EAServer, I have not made any configuration changes
to EAServer except to define connection caches. I have been
able to successfully deploy objects to that EAServer with
this configuration BUT not past a certain number of objects.
It seems to me like there is a memory leak. I've even
encountered a few instances where when I run my application
after deployment I get an OutOfMemory condition in EAServer.
Any thoughts or suggestions?
Thanks,
Shawn

OutOfMemory errors? >

Note attached log file.
Thanks,
Shawn

unknown

2009-09-15 16:06:50 UTC

EAServer 6.3.0.06 Developer Edition
Powerbuilder 11.5.1 Build 4566

Same Error:

Displayed in EAServer console windw:
Deploying Package: xxxxxxx...
Exception in thread "TaskScheduler:ExecuteThread"
java.lang.OutofMemoryError: PermGen space
Exception in thread "RMI RenewClean[192.168.1.101:1282]"
java.lang.OutofMemoryError: PermGen space

The only thing special about my objects is that they all are
built off of an ancestor. When I deploy, I choose the
Collapse Class Hierarchy. I don't know why that suddenly
would make a difference but I thought it worth mentioning.

Any other ideas? I'ver never had any problems like this in
past versions of EAServer. I really have no idea where to
look to fix this. My only option will be to abandon the
upgrade and report that it's not stable for our needs.

Shawn

Post by Chris Pollach
FWIW: You can apply the PB 11.5.1 maintenance release
(build 4011). It is available for a free download at
www.sybase.com.

Post by unknown
I'm using the NFR release of Powerbuilder from ISUG
which is 11.5, build 3127. I'm trying to make sure
we're in position to upgrade from Powerbuilder 11.0.1
before we purchase the upgrade. EAServer version is 6.3
developer edition (again, to be upgraded to Advanced
once we know it will work for us). This is all running

on Windows XP Pro SP2. >

Post by unknown
As for EAServer, I have not made any configuration
changes to EAServer except to define connection caches.
I have been able to successfully deploy objects to that
EAServer with this configuration BUT not past a certain
number of objects. It seems to me like there is a memory
leak. I've even encountered a few instances where when
I run my application after deployment I get an

OutOfMemory condition in EAServer. >

Post by unknown
Any thoughts or suggestions?
Thanks,
Shawn

Post by Chris Pollach
Hi Shawn;
I am using EAS 6.3 with PB 11.5.1 and 12 Classic

and >> able to deploy with no problems.

Post by Chris Pollach
I have two machines .. but, both of these are 4 G - one

XP >> and the other Vista.

Post by Chris Pollach
What version of PB are you using?
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
frustrated!!! >

I've been trying to put together an upgrade of our
EASErver system to get it up to EAServer 6.3 but I

can't >> > deploy more than a few objects without getting

OutOfMemory errors. I'm attaching my log file in

hopes >> > that this will shed some light on the problem.

I understand that compared to pre version-6 EAServers

, >> > EAServer now compiles Powerbuilder objects into
java >> > (right?). I just upgraded the RAM on my laptop
to 2GB >> > and I had assumed this would give me the
memory I needed >> > to do my deployments. It looks like
I was wrong! >> >

Does anyone have any suggestions on what I need to do

to >> > be able to deploy objects from PB 11.5 to EAServer
6.3 >> > and have it be successful rather than failing on

Post by Chris Pollach
OutOfMemory errors? >

Note attached log file.
Thanks,
Shawn

Chris Pollach

2009-09-15 18:13:24 UTC

Now .. EAS keeps a copy of the PBVM in a sub-folder of itself. What I do on
a development machine (especially for EBF and MR upgrade support) to make
sure that EAS uses the same version of the VM is ...

1) Rename the PowerBuilder folder under EAS to PowerBuilder_xx for example
(ie path: C:\Program Files\Sybase\EAServer6\PowerBuilder)
2) Make sure that the development PB's runtime is in the System Path
(ie: C:\Program Files\Sybase\Shared\PowerBuilder)
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com

Post by unknown
EAServer 6.3.0.06 Developer Edition
Powerbuilder 11.5.1 Build 4566
Deploying Package: xxxxxxx...
Exception in thread "TaskScheduler:ExecuteThread"
java.lang.OutofMemoryError: PermGen space
Exception in thread "RMI RenewClean[192.168.1.101:1282]"
java.lang.OutofMemoryError: PermGen space
The only thing special about my objects is that they all are
built off of an ancestor. When I deploy, I choose the
Collapse Class Hierarchy. I don't know why that suddenly
would make a difference but I thought it worth mentioning.
Any other ideas? I'ver never had any problems like this in
past versions of EAServer. I really have no idea where to
look to fix this. My only option will be to abandon the
upgrade and report that it's not stable for our needs.
Shawn

Post by Chris Pollach
FWIW: You can apply the PB 11.5.1 maintenance release
(build 4011). It is available for a free download at
www.sybase.com.

on Windows XP Pro SP2. >

OutOfMemory condition in EAServer. >

Post by unknown
Any thoughts or suggestions?
Thanks,
Shawn

Post by Chris Pollach
Hi Shawn;
I am using EAS 6.3 with PB 11.5.1 and 12 Classic

and >> able to deploy with no problems.

Post by Chris Pollach
I have two machines .. but, both of these are 4 G - one

XP >> and the other Vista.

Post by Chris Pollach
What version of PB are you using?
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
frustrated!!! >

I've been trying to put together an upgrade of our
EASErver system to get it up to EAServer 6.3 but I

can't >> > deploy more than a few objects without getting

OutOfMemory errors. I'm attaching my log file in

hopes >> > that this will shed some light on the problem.

I understand that compared to pre version-6 EAServers

Does anyone have any suggestions on what I need to do

to >> > be able to deploy objects from PB 11.5 to EAServer
6.3 >> > and have it be successful rather than failing on

Post by Chris Pollach
OutOfMemory errors? >

Note attached log file.
Thanks,
Shawn

Mark Maslow

2009-09-15 21:04:16 UTC

PermGen space is where objects end up after being passed over several
times by the garbage collector, because references to them are retained
over a relatively long period of time.

First off, there are two JVM parameters that control the amount of
PermGen space available for the JVM, initial and maximum. For example:

-XX:PermSize=64m
-XX:MaxPermSize=128m

I belive the defaults are lower than that (depends on what JVM you are
using). One thing you can do is try configuring the JVM to use more
space. You'll have to refer to the docs as to just how to do that for
EAServer.

If you have plenty of space configured, and are still running out, that
would probably indicate a memory leak. Since you are never creating
Java objects directly, I believe the only option you have is to work
with Sybase TS.

Mark Maslow

2009-09-16 04:28:07 UTC

Oh - now that I looked at the log entries you posted, I see that it's the
classloader that is hitting the limit. Classes are not generally garbage
collected, nor would one generally want them to be in production, so they
almost always end up in the permanent generation - and there doesn't seem to
be enough room there to get everything loaded.

If increasing MaxPermSize doesn't solve it, it is really a problem for
Sybase TS to sort out. If you get any definitive answers, I'm sure others
will be interested to hear them.

unknown

2009-09-16 15:33:10 UTC

Chris and Mark,

Thank you for the guidance. I have more pressing matters to
tend to for the next few days. When I have the available
time again, I'll jump back on this problem and see if your
suggestions help to resolve it. I'll post what I can in the
days ahead.

Thanks!
Shawn

Post by Mark Maslow
Oh - now that I looked at the log entries you posted, I
see that it's the classloader that is hitting the limit.
Classes are not generally garbage collected, nor would
one generally want them to be in production, so they
almost always end up in the permanent generation - and
there doesn't seem to be enough room there to get
everything loaded.
If increasing MaxPermSize doesn't solve it, it is really a
problem for Sybase TS to sort out. If you get any
definitive answers, I'm sure others will be interested to
hear them.

Millard F. Brown III[Team Sybase]

2009-09-18 16:39:43 UTC