Support Forum

[michaelneale]

We are running track studio on a weblogic 6.1 server.
Track studio seems to be using a lot of memory and killing the weblogic server due to out of memory errors. Things were working fun upto a point, but once you start running a few filters, it slows down and then crashes.

Any ideas?

[admin]

We are running track studio on a weblogic 6.1 server.
Track studio seems to be using a lot of memory and killing the weblogic server due to out of memory errors. Things were working fun upto a point, but once you start running a few filters, it slows down and then crashes.

Any ideas?

Please try to use -Xmx option to increase memory size to 384 or even 512 MB. We know about this problem and next version should require less memory.

PS. How many tasks/users do you have ?

[michaelneale]

Unfortunately the box we are running it on doesnt really have enough real memory, and that is the real problem. We have run a few applications on it, and normally it is fine.

256 is not much memory, but it should be enough, but track studio must aggresively cache things by the look of it, cause it isnt really that much data on its own.

I guess it would be a nice idea in future if a track studio installation could have its caching tuned so as to not use up too much memory if required (but at the cost of more database hits). For instance, we have a fairly serious sun box running the databases we use, but the weblogic box is its poor cousin (!). In such a case the database server can handle more load... but I guess track studio has the advantage that it can use lower end databases and still scale reasonably well.

Do you have a timeframe for when the memory issues will be addressed? I ask because I think adding more memory will only delay the problem, and in any case it will steal resources from the other apps running on the same server.

[michaelneale]

Is this a problem with other application servers or is it weblogic specific?

We have tomcat available to use, would we be better off using it on that server?

[admin]

Unfortunately the box we are running it on doesnt really have enough real memory, and that is the real problem. We have run a few applications on it, and normally it is fine.

256 is not much memory, but it should be enough, but track studio must aggresively cache things by the look of it, cause it isnt really that much data on its own.

I guess it would be a nice idea in future if a track studio installation could have its caching tuned so as to not use up too much memory if required (but at the cost of more database hits). For instance, we have a fairly serious sun box running the databases we use, but the weblogic box is its poor cousin (!). In such a case the database server can handle more load... but I guess track studio has the advantage that it can use lower end databases and still scale reasonably well.

Do you have a timeframe for when the memory issues will be addressed? I ask because I think adding more memory will only delay the problem, and in any case it will steal resources from the other apps running on the same server.

Weblogic is quite memory-expensive application, so its require more memory than Tomcat or Jetty, for example. For better cache management we plan to wrap our query cache with JCS cache, so cache settings should be easy configurable. This issue should be resolved early september.

Even if you have not enought physical memory - please add more swap space or/and switch to Jetty, for example.

PS. We run our hosted service on P4 box with 512 MB memory with -Xmx768 (but it never require more than 500 MB). This instance handle 1500 users, approx 8000 tasks and 25000 messages.
Also this box handler corporate email, proxy, DNS, etc.

[michaelneale]

We added an extra 512Meg memory (bringing total to 768 Meg) and we still get weblogic crashing when there is reasonable activity on track studio.
It doesnt appear to just be memory, there could be something else that is killing weblogic. Has anyone else run track studio 2.7 successfully on weblogic 6.1 ?

[admin]

We added an extra 512Meg memory (bringing total to 768 Meg) and we still get weblogic crashing when there is reasonable activity on track studio.
It doesnt appear to just be memory, there could be something else that is killing weblogic. Has anyone else run track studio 2.7 successfully on weblogic 6.1 ?

When we use early TrackStudio releases under Weblogic 6.1 and sun jdk under linux - weblogic crash periodically (several times a day) under load.
This bug does not exists with JDK 1.4 and under Windows.

Please check this post: http://forum.java.sun.com/thread.jsp?fo ... &trange=15

But, as far as I remember 6.1 does not support, so you need upgrade to 7.0.

TrackStudio + JDK 1.4 + Weblogic 7.0 has no problems.

PS. This this bug with -hotspot optimization in JDK 1.3.1. When I write to sun, they suggest enable debug log, find method that cause bug and disable hotspot compilation for them. But no luck, only change to 1.4 help us.

[admin]

We added an extra 512Meg memory (bringing total to 768 Meg) and we still get weblogic crashing when there is reasonable activity on track studio.
It doesnt appear to just be memory, there could be something else that is killing weblogic. Has anyone else run track studio 2.7 successfully on weblogic 6.1 ?

Another useful links:
http://www.tek-tips.com/gviewthread.cfm ... qid/342414

http://edocs.bea.com/wls/certifications ... ris27.html

http://forum.sun.com/thread.jsp?forum=9&thread=9363

I suggest you contact BEA or sun about this problem