Out of Memory for 6.0 sp2

We received the following stack trace in the weblogic logs
weblogic.log
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <main> <system> <> <000216> <WebLogic Server started>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <Using effective
file descriptor limit of: '1024' open sockets/files.>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <Allocating: '3'
POSIX reader threads>
####<Nov 16, 2001 7:33:57 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <system> <> <101047>
<[WebAppServletContext(536060,console)] *.html: init>
####<Nov 16, 2001 7:33:57 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <system> <> <101047>
<[WebAppServletContext(536060,console)] *.html: Using standard I/O>
####<Nov 16, 2001 7:36:11 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <> <> <101047>
<[WebAppServletContext(2021663,DefaultWebApp_danvers)] /classes: init>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-69> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-69> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:55 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:38:51 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-27> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:46:40 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
####<Nov 18, 2001 7:47:05 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:08:40 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '12' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 9:09:01 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '12' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:45:30 AM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:14:01 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '3' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
####<Nov 19, 2001 1:54:36 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 16, 2001 7:19:11 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <ListenThread> <system> <> <000202> <ListenThread listening on
port 9009>
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <ListenThread> <system> <> <000202> <ListenThread listening on
port 9009>
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <main> <system> <> <000216> <WebLogic Server started>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-69> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-69> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:50 PM GMT> <Error> <Adapter> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:55 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:36:44 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:38:04 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '10' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:38:51 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-27> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:40:19 PM GMT> <Error> <RJVM> <danvers> <danvers>
<ExecuteThread: '7' for queue: 'default'> <> <> <000000> <Failure in
heartbeat trigger for RJVM: '-4587908185898992697C:164.179.193.100'>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:41:50 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-47> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:41:59 PM GMT> <Error> <Adapter> <danvers> <danvers>
<ExecuteThread: '4' for queue: 'default'> <system> <> <000000>
<OutOfMemoryError in Adapter>
####<Nov 18, 2001 7:42:11 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '4' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:42:21 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-17> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:42:30 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-17> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:44:46 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '6' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:45:18 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '7' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:45:27 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '14' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 7:45:48 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
####<Nov 18, 2001 7:45:56 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:46:22 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-77> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:46:27 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '13' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 7:46:40 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:47:05 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:47:22 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '9' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
####<Nov 18, 2001 7:51:55 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-79> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 8:14:57 PM GMT> <Error> <RJVM> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Failure in
heartbeat trigger for RJVM: '7929968200845233656C:164.179.193.100'>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:08:40 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '12' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:09:01 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '12' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:45:30 AM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:14:01 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '3' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:54:36 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 2:26:37 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
We are not using the server as a web server we are running a 3rd party
application in the server configured with 1/2 Gb of memory. My guess is
that they are not
releasing some resources but if you BEA folks can point me into some
direction
that would be helpful. The vendor says its a weblogic problem which I
doubt.

Please give the details of java parameters like heap size, ratios etc.
Look at the following link for various hotspot options.
http://java.sun.com/docs/hotspot/VMOptions.html.
You can try with -verbosegc option, which splits all gc statistics to
know whether heap size is runningout of some other problem.
Thread dump will helpful to analyze the problem.
ctrl+\ ( ctrl + backslash) for solaris, ctrl+Break for windows will
be give the thread dump.
--sreeni.
Larry Presswood <[email protected]> wrote in message news:<[email protected]>...
Yes this is true but was wandering if the stack trace could point to anything
in particular like the jdk bug in 1.3.x which will give outof memory after 400
or
so ejb creations. Also would have to run under optimizeit for days which is
not
entirely desirable in QA but will do if not other help can be found.
Dimitri Rakitine wrote:
You can always use OptimizeIt to see what leaks memory.
Larry Presswood <[email protected]> wrote:
We received the following stack trace in the weblogic logs
weblogic.log
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <main> <system> <> <000216> <WebLogic Server started>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <Using effective
file descriptor limit of: '1024' open sockets/files.>
####<Nov 16, 2001 7:33:30 PM GMT> <Info> <Posix Performance Pack>
<danvers> <danvers> <ListenThread> <system> <> <000000> <Allocating: '3'
POSIX reader threads>
####<Nov 16, 2001 7:33:57 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <system> <> <101047>
<[WebAppServletContext(536060,console)] *.html: init>
####<Nov 16, 2001 7:33:57 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <system> <> <101047>
<[WebAppServletContext(536060,console)] *.html: Using standard I/O>
####<Nov 16, 2001 7:36:11 PM GMT> <Info> <HTTP> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <> <> <101047>
<[WebAppServletContext(2021663,DefaultWebApp_danvers)] /classes: init>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-69> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-69> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:55 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:38:51 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-27> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:46:40 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
####<Nov 18, 2001 7:47:05 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:08:40 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '12' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 9:09:01 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '12' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:45:30 AM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:14:01 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '3' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
####<Nov 19, 2001 1:54:36 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 16, 2001 7:19:11 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <ListenThread> <system> <> <000202> <ListenThread listening on
port 9009>
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <ListenThread> <system> <> <000202> <ListenThread listening on
port 9009>
####<Nov 16, 2001 7:33:30 PM GMT> <Notice> <WebLogicServer> <danvers>
<danvers> <main> <system> <> <000216> <WebLogic Server started>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-69> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:19:17 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-69> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:50 PM GMT> <Error> <Adapter> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:35:55 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <>
<000000> <ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:36:44 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '11' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:38:04 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '10' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:38:51 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-27> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:40:19 PM GMT> <Error> <RJVM> <danvers> <danvers>
<ExecuteThread: '7' for queue: 'default'> <> <> <000000> <Failure in
heartbeat trigger for RJVM: '-4587908185898992697C:164.179.193.100'>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:41:50 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-47> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:41:59 PM GMT> <Error> <Adapter> <danvers> <danvers>
<ExecuteThread: '4' for queue: 'default'> <system> <> <000000>
<OutOfMemoryError in Adapter>
####<Nov 18, 2001 7:42:11 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '4' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:42:21 PM GMT> <Error> <Adapter> <danvers> <danvers>
<Thread-17> <system> <> <000000> <OutOfMemoryError in Adapter>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:42:30 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-17> <system> <> <000000> <Error in Dispatcher>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:44:46 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '6' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:45:18 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '7' for queue: 'default'> <system> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:45:27 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '14' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 7:45:48 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
####<Nov 18, 2001 7:45:56 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
####<Nov 18, 2001 7:46:22 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-77> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 7:46:27 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '13' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
####<Nov 18, 2001 7:46:40 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:47:05 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000>
<ExecuteRequest failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 7:47:22 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '9' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
####<Nov 18, 2001 7:51:55 PM GMT> <Error> <AdapterDispatcher> <danvers>
<danvers> <Thread-79> <system> <> <000000> <Error in Dispatcher>
####<Nov 18, 2001 8:14:57 PM GMT> <Error> <RJVM> <danvers> <danvers>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Failure in
heartbeat trigger for RJVM: '7929968200845233656C:164.179.193.100'>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:08:40 PM GMT> <Error> <Posix Performance Pack>
<danvers> <danvers> <ExecuteThread: '12' for queue: 'default'> <> <>
<000000> <Uncaught Throwable in processSockets>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 18, 2001 9:09:01 PM GMT> <Error> <Performance Pack> <danvers>
<danvers> <ExecuteThread: '12' for queue: 'default'> <> <> <000000>
<Muxer got error: null>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:45:30 AM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:14:01 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '3' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 1:54:36 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
java.lang.OutOfMemoryError
<<no stack trace available>>
####<Nov 19, 2001 2:26:37 PM GMT> <Error> <Kernel> <danvers> <danvers>
<ExecuteThread: '5' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
We are not using the server as a web server we are running a 3rd party
application in the server configured with 1/2 Gb of memory. My guess is
that they are not
releasing some resources but if you BEA folks can point me into some
direction
that would be helpful. The vendor says its a weblogic problem which I
doubt.--
Dimitri

Similar Messages

Playing video from a capture device - Out of memory for video buffers?

Hello guys, I'm having problems playing video from a video capture device when not using JMStudio. When I use JMStudio, the video plays real time with no problems, but when I use code taken from a java book which is a simple Media Player, I get the following error:
"Error is Error: Out of memory for video buffers."
My capture device is working and I don't know why i get this error when trying to watch the video feed from a program other than JMStudio. I also tried different code that has worked in the past with the same exact capture device and I still get the same error. Please help, I have no clue at this point. The code for the simple media player is below, it's taken out of the book "Java: How to Program (4th edition)":
Thanks in advance, I am very greatful
Miguel
device info: vfw:Microsoft WDM Image Capture (Win32):0
When I type the locator, I am typing vfw://0, I also tried just vfw://
and I get the same error.
// Fig. 22.1: SimplePlayer.java
// Opens and plays a media file from
// local computer, public URL, or an RTP session
// Java core packages
import java.awt.*;
import java.awt.event.*;
import java.io.*;
import java.net.*;
// Java extension packages
import javax.swing.*;
import javax.media.*;
public class SimplePlayer extends JFrame {
// Java media player
private Player player;
// visual content component
private Component visualMedia;
// controls component for media
private Component mediaControl;
// main container
private Container container;
// media file and media locations
private File mediaFile;
private URL fileURL;
// constructor for SimplePlayer
public SimplePlayer()
super( "Simple Java Media Player" );
container = getContentPane();
// panel containing buttons
JPanel buttonPanel = new JPanel();
container.add( buttonPanel, BorderLayout.NORTH );
// opening file from directory button
JButton openFile = new JButton( "Open File" );
buttonPanel.add( openFile );
// register an ActionListener for openFile events
openFile.addActionListener(
// anonymous inner class to handle openFile events
new ActionListener() {
// open and create player for file
public void actionPerformed( ActionEvent event )
mediaFile = getFile();
if ( mediaFile != null ) {
// obtain URL from file
try {
fileURL = mediaFile.toURL();
// file path unresolvable
catch ( MalformedURLException badURL ) {
badURL.printStackTrace();
showErrorMessage( "Bad URL" );
makePlayer( fileURL.toString() );
} // end actionPerformed
} // end ActionListener
); // end call to method addActionListener
// URL opening button
JButton openURL = new JButton( "Open Locator" );
buttonPanel.add( openURL );
// register an ActionListener for openURL events
openURL.addActionListener(
// anonymous inner class to handle openURL events
new ActionListener() {
// open and create player for media locator
public void actionPerformed( ActionEvent event )
String addressName = getMediaLocation();
if ( addressName != null )
makePlayer( addressName );
} // end ActionListener
); // end call to method addActionListener
// turn on lightweight rendering on players to enable
// better compatibility with lightweight GUI components
Manager.setHint( Manager.LIGHTWEIGHT_RENDERER,
Boolean.TRUE );
} // end SimplePlayer constructor
// utility method for pop-up error messages
public void showErrorMessage( String error )
JOptionPane.showMessageDialog( this, error, "Error",
JOptionPane.ERROR_MESSAGE );
// get file from computer
public File getFile()
JFileChooser fileChooser = new JFileChooser();
fileChooser.setFileSelectionMode(
JFileChooser.FILES_ONLY );
int result = fileChooser.showOpenDialog( this );
if ( result == JFileChooser.CANCEL_OPTION )
return null;
else
return fileChooser.getSelectedFile();
// get media location from user input
public String getMediaLocation()
String input = JOptionPane.showInputDialog(
this, "Enter URL" );
// if user presses OK with no input
if ( input != null && input.length() == 0 )
return null;
return input;
// create player using media's location
public void makePlayer( String mediaLocation )
// reset player and window if previous player exists
if ( player != null )
removePlayerComponents();
// location of media source
MediaLocator mediaLocator =
new MediaLocator( mediaLocation );
if ( mediaLocator == null ) {
showErrorMessage( "Error opening file" );
return;
// create a player from MediaLocator
try {
player = Manager.createPlayer( mediaLocator );
// register ControllerListener to handle Player events
player.addControllerListener(
new PlayerEventHandler() );
// call realize to enable rendering of player's media
player.realize();
// no player exists or format is unsupported
catch ( NoPlayerException noPlayerException ) {
noPlayerException.printStackTrace();
// file input error
catch ( IOException ioException ) {
ioException.printStackTrace();
} // end makePlayer method
// return player to system resources and
// reset media and controls
public void removePlayerComponents()
// remove previous video component if there is one
if ( visualMedia != null )
container.remove( visualMedia );
// remove previous media control if there is one
if ( mediaControl != null )
container.remove( mediaControl );
// stop player and return allocated resources
player.close();
// obtain visual media and player controls
public void getMediaComponents()
// get visual component from player
visualMedia = player.getVisualComponent();
// add visual component if present
if ( visualMedia != null )
container.add( visualMedia, BorderLayout.CENTER );
// get player control GUI
mediaControl = player.getControlPanelComponent();
// add controls component if present
if ( mediaControl != null )
container.add( mediaControl, BorderLayout.SOUTH );
} // end method getMediaComponents
// handler for player's ControllerEvents
private class PlayerEventHandler extends ControllerAdapter {
// prefetch media feed once player is realized
public void realizeComplete(
RealizeCompleteEvent realizeDoneEvent )
player.prefetch();
// player can start showing media after prefetching
public void prefetchComplete(
PrefetchCompleteEvent prefetchDoneEvent )
getMediaComponents();
// ensure valid layout of frame
validate();
// start playing media
player.start();
} // end prefetchComplete method
// if end of media, reset to beginning, stop play
public void endOfMedia( EndOfMediaEvent mediaEndEvent )
player.setMediaTime( new Time( 0 ) );
player.stop();
} // end PlayerEventHandler inner class
// execute application
public static void main( String args[] )
SimplePlayer testPlayer = new SimplePlayer();
testPlayer.setSize( 300, 300 );
testPlayer.setLocation( 300, 300 );
testPlayer.setDefaultCloseOperation( EXIT_ON_CLOSE );
testPlayer.setVisible( true );
} // end class SimplePlayer

somebody? anybody? I know there are some JMF professionals in here, any ideas?
I was reading the Sun documentation and it said something about increasing the JVM memory buffer or something? Well, i'm just clueless at this point.
Help a brotha out!

"General Error" and "Out of Memory" for only certain files?

I have Final Cut Express 4 on Mac OS X Leopard and it has been working fine, up until now.
For some reason, when I try to view two clips in the tab to the left of the screen to find sections of them to put into my project, I get a message that says, "General Error" and when I click okay it says, "Error: Out of Memory". They are both mp4 files, and are 242.9 MB and 294.2 MB, and I have viewed them both on Quicktime. I don't understand why it is saying that it is out of memory when I still have 7 GB left on my computer and it still lets me view and add other files into my sequence.
Can someone help me out and tell me how to fix this? I'd really appreciate advise!

MPEG-4 is not a format that works in FCE. You'll have to convert it to one of FCE's format. Without knowing details about what the original format is it's impossible to say what you should convert it to.

Why do I get out of memory for applications on start up Mac OS10.6.8 with Firefox 7.0.1?

Using Firefox 7.0.1 on a MacBook Pro with OS 10.6.8 and NO OTHER applications running, I am consistently getting the message that Your Mac OS X startup disk has no mor space for application memory. It is happening whenever I try to do something using Firefox or use any application now. I have deleted six applications in the app folder and that has made no difference. I see a note about iPhoto plugin 6. I have iPhoto 9 app.

Hi RJBP-
Here is a Support article on how to troubleshoot Firefox with high memory usage:
[[High memory usage]]
Hope that helps.

I tried to utilise iCloud with iPhoto. since then all that happens is that I end up with the timer wheel and eventually the mac runs out of memory for everything. How do I get iPhoto to work normally?

How do I reset the settings on iPhoto so that it forgets I wanted to use iCloud with iPhoto ?

iPhoto 6 and later: Rebuilding the iPhoto library

OUT OF MEMORY PLEASE HELP!!

I have a Mac book Pro with 120 Gigs of HD space and I have somewhere in the neighborhood of 30gigs memory just for Lightroom catalogs of all my clients. I am out of memory for storage, but need to a access my client catalogs periodically. What can I do???

holy bullet,
Not to be pedantic, but you're talking about
storage
NOT
memory here, as your subject line suggested. You might have 2Gb of memory in your computer, but your storage capacity is 120Gb (your hard disk drive).
As John said, you either need to buy an external hard drive with more capacity and move your catalog(s) there, or upgrade your internal hard drive. The latter option will probably cost you less money (per gigabyte of storage) and time, while giving you better growth options in the future. Recommendations I've seen suggest choosing an external drive that uses high-speed Firewire, rather than USB, for better performance and stability. John's suggestion of offloading the smaller client catalogs to the external drive sounds excellent.
If you do create a new catalog for a client, then import those photos, be sure to remove them from your main catalog so you don't chew up additional space needlessly (and cause confusion).
Good luck

How to fixe exception out of memory ?

Hello,i did a web application (asp.net/c#/crystal reports),i used more than 35 tableAdapter and when i'm trying report after some time i remark the memory increase more and more until i get Out Put memory Exception. how can i fix this problem ?
please help me

Hi ghilasdz,
Thank you for posting in MSDN forum.
Since this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
So I’m afraid that it is not the correct forum for this issue.
As you said that the exception out of memory for the crystal reports, I suggest you can post this issue directly to the
SAP Crystal Reports: http://scn.sap.com/community/crystal-reports/content?filterID=contentstatus%5bpublished%5d~objecttype~objecttype%5bthread%5d
, you will get better support for this issue.
In addition, I find a similar thread about the exception out of memory for the crystal reports on the
SAP Crystal Reports, maybe you will get some useful message.
http://scn.sap.com/thread/1888746
Thanks for your understanding.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SAX XMLReader out of Memory!

I've been stuck on this one for a few hours now, and can't seem to be able to resolve the issue. I'm trying to parse a 50MB+ file using the apache (or 1.4 built in) SAX parser and keep running out of memory. Here are some details:
- one big outer tag
- about 1000 smaller inner tags
- one value over 200K per inner tag
About 10 or so of the innter tags parse just fine, but on the 11th, "Out Of Memory" exception!
Has anyone seen this before? (Is anyone else crazy enough to try parsing such a large file?)

i parse 100MB+ on a regular basis.
1) Are you creating objects while you are parsing?
you should parse and use the information and get rid of the info.
2) What parser are you using...some SAX parser use a buffer to help improve speed for small xml doc, but -run out of memory- for large doc 20MB+.
3) are you saving everything??? the hold 50MB in local/global variables?

Out of memory error for large recordings:

Hi,
My workflow process takes input as a list. It loops through the workflow for all the items in the list. If my list contain 4 items, there will be 3*7= 21 steps when I invoke the process. I can able to check my recordings for debugging.
If I give 5 inputs, It takes around 5*7 = 35 steps in the workflow. If I try to play the recording, i see the error: java heap space: Out of memory exception. I changed my space to Xmx1024m in workbench.ini. I also did: java -Xms<initial heap size> -Xmx<maximum heap size> (Q1: do we need to restart the JBoss after we do the second step? ).
Q2: My system is Windows7 with 4GB RAM. I have liveCycle 8.2 with SP2. JBoss & MySql. Do I need to set this java RAM size in any of our JBoss server files?
Q3: Is there any file to set the maximum permissible steps for a process recording? If so, please let me know. It would be a great help.
Thanks,
Chaitanya

If the size of the documents you are adding as input are very large this could result in OOM errors so that is something to consider.
Some other things to try are as follows:
1. Increase memory allocated by JBoss by another 200 - 300 M as per the following documentation on the web:
http://help.adobe.com/en_US/livecycle/9.0/workbenchHelp/help.html?topic=000097&topic=00183 7
2. Read the following sections of the Workbench Help which can be found on the web and describes how to limit your recording storage space used: http://help.adobe.com/en_US/livecycle/9.0/workbenchHelp/help.html?topic=000097&topic=00106 0
I would suggest increasing your maxNumberOfRecordingEntries to about 200.
Heather

How do I find out the exact path of each and every file that LabVIEW finds and loads into memory for a given top level vi?

How do I find out the exact path of each and every file that LabVIEW finds and loads into memory for a given top level vi? There is probably a trivial, easy way to get this info, but I have not yet found it! Thanks..

Or if you want to grab all the paths programatically, try the attached VI.
Open the top level that you want all the paths from and close all others, then open the
attached and run it. It will return an array of all the VIs that the VI
in question uses, including vi.lib VIs. You can filter these as well if
you like.
Ed
Message Edited by Ed Dickens on 08-01-2005 07:01 PM
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Attachments:
Get all paths.vi ‏29 KB

"returning error page for JRun too busy or out of memory"

Hello,
I've got some trouble to update a ColdFusion linux based.
We have already tried to update from ASPB11-04 and ASPB11-14 but we always have the folloing erreor message :
"returning error page for JRun too busy or out of memory"
We really need a solution ASAP. Thanks!
Jeff

Can you share the exception and application logs having the error entries.
Regards,
Anit Kumar

Hyperion IR : Getting out of memory error while fetching data for whole year through web client (wrokspace)

Hi,
While fetching data though IR wen client from workspace for a year(all 12 months) I am getting error as ("Out of Memory .Advice : Close other applications or windows and try again").
If I am trying same through IR studio it does not give any output and show me same repoting front page.
If i am selecting periods till 8 months it is giving the required data in both IR web client and IR studio.
Could you please suggest how can we resolve this issue.
Thanks,
D.N.Rana

Issue Cause :
Sometimes this is due to excessive data which brings the size of the BQY file up around one gigabyte uncompressed in size (for processing may take twice as actual RAM, plus the memory space space for the plugin, and the typical memory limit on a 32-bit system is 2 gigabytes).
Solution :
To avoid excessive BQY size exceeding memory availability:
Ensure that your computer has at least 2Gb of free RAM before he runs IR Studio.
Put a limit to the number of rows that can be pulled down: Right click on Request label of Query section and put a value in Return First xxx Rows (and check the check box).
Do not pull down more than 750 MB of data (remember it may be duplicated while processing).
Place limits or aggregations in Query section (as opposed to Result section) to limit data entering the BQY.

Importing Word docs from RH for Word X5 - out of memory error

I've tried a few times to import 537 Word docs (2,974) from a
RH for Word project (RH X5 for Word, CHM output) into a new RH HTML
5 project. Each time, RH HTML "hangs" and I've seen "out of memory"
at least once at the very end. The original RH for Word project has
conditional build tags defined, but only one tag has been assigned
to one topic, so far. We've never been able to build an index in
this RH for Word project (it's mostly blank), but we've built a
search and contents without problems.
Is an error related to Word? Is it a bug that was fixed for
version 6? Is it somehow related to this fix:
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb401651&sliceId=1?
If it's a known bug that was fixed with a later version, then
it would further help me build a case for converting to RH 7, with
the end result of converting the whole thing eventually to RH HTML.
Thanks,
Jim

I don't do much import but if you are trying to import 537
documents in one go, nothing would surprise me. Have you tried one
at a time or a small batch at a time?
The bug you point to arose in 6 and was fixed so it is not
relevant.
My guess is it is down to memory and that most PCs would
baulk at 537 documents in one go.

Out of Memory - Indesign 2.02 for Windows

Hello.
Probably been asked before but how do you resolve the "out of memory" (clipping path) problem when you are using InDesign for Windows? - see that there is a fix for Mac but can't find one for Windows 7 - is there a downloadable update available?
Regards,
Harvey

Bob.
Thanks for that - expect that I will have to bite the bullet and upgrade - just got used to using the older version and because of limited time commitments, didn't want to spend ages having to learn to use a new programme all over again!
Regards,
Harvey

Problem: Out-of-memory condition? : waiting for an available stack

Hello,
I'm evaluating jrockit and trying to run in ita java application that I normally
run with the Sun JVM on WinXP.
After a few seconds I get the message "Out-of-memory condition? : waiting for
an available stack".
I'm running it on an Intel machine, WindowsXP 392Mb RAM.
I have played with different GC options, heap, stack size, native/thinthreads
but it always stops around the same point. When I turn -Xverbose:codegen on I
can see that it's trying to compile a method in my own security manager. The message
is something like that:
[codegen] 500 84732 5169 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[codegen] 500 84732 5170 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[codegen] 500 84732 5171 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[JRockit]Out-of-memory condition? : waiting for an available stack
It looks as though it's in a loop.
This is the code for this method (the super class of the containing class is SecurityManager):
public void checkRead(String fileName, Object context) {
try {
if(context==null) {
super.checkRead(fileName);
} else {
super.checkRead(fileName, context);
} catch (SecurityException ex1) {
// If a file in the persistent storage is accessed we need to consider additional
MAC/DAC possibilities
ServiceDomainIdentifier sdi;
sdi=ServiceDomainIdentifierManager.getInstance().get(fileName);
FileSystem filesys=(sdi==null)?null:sdi.getFileSystem();
if(filesys!=null && !filesys.checkReadPermission(fileName)) {
throw ex1;
I also use many native methods in different libraries.
Any ideas?
Thanks,
Sibelius

Hello Staffan,
Thanks for the info. I had v1.4.1_05 and I have now installed v1.4.2_03.
Unfortunately, the error still happened at the same point in the code, although
much earlier on, but this time no message was displayed. It was just stuck there.
However, I changed the code a little bit (I put the catch block in another private
function) and now everything works. I'm writing the different snippets down. Perhaps
it would be interesting to find out why it behaves this way.
So, can you tell why this code won't works?
public void checkRead(String fileName, Object context) {
try {
if(context==null) {
super.checkRead(fileName);
} else {
super.checkRead(fileName, context);
} catch (SecurityException ex1) {
ServiceDomainIdentifier sdi;
sdi=ServiceDomainIdentifierManager.getInstance().get(fileName);
FileSystem filesys=(sdi==null)?null:sdi.getFileSystem();
if(filesys!=null && !filesys.checkReadPermission(fileName)) {
throw ex1;
But if I write it like following, it works!
public void checkRead(String fileName, Object context) {
try {
if(context==null) {
super.checkRead(fileName);
} else {
super.checkRead(fileName, context);
} catch (SecurityException ex1) {
myFunction(fileName,ex1);
private void myFunction(tring fileName, SecurityException ex1) {
ServiceDomainIdentifier sdi;
sdi=ServiceDomainIdentifierManager.getInstance().get(fileName);
FileSystem filesys=(sdi==null)?null:sdi.getFileSystem();
if(filesys!=null && !filesys.checkReadPermission(fileName)) {
throw ex1;
Thank you!
Sibelius
Staffan Larsen <[email protected]> wrote:
You didn't mention which version of JRockit this happens with (java
-version). I would suggest you upgrade to JRockit 1.4.2 if you haven't
already.
Regards,
/Staffan
Sibelius Segala wrote:
Hello,
I'm evaluating jrockit and trying to run in ita java application thatI normally
run with the Sun JVM on WinXP.
After a few seconds I get the message "Out-of-memory condition? : waitingfor
an available stack".
I'm running it on an Intel machine, WindowsXP 392Mb RAM.
I have played with different GC options, heap, stack size, native/thinthreads
but it always stops around the same point. When I turn -Xverbose:codegenon I
can see that it's trying to compile a method in my own security manager.The message
is something like that:
[codegen] 500 84732 5169 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[codegen] 500 84732 5170 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[codegen] 500 84732 5171 de.irt.mhp.security.MySecurityManager.checkRead(Ljava.lang.String;Ljava.lang.Object;)V:
7583.59 ms
[JRockit]Out-of-memory condition? : waiting for an available stack
It looks as though it's in a loop.
This is the code for this method (the super class of the containingclass is SecurityManager):
public void checkRead(String fileName, Object context) {
try {
if(context==null) {
super.checkRead(fileName);
} else {
super.checkRead(fileName, context);
} catch (SecurityException ex1) {
// If a file in the persistent storage is accessed we need toconsider additional
MAC/DAC possibilities
ServiceDomainIdentifier sdi;
sdi=ServiceDomainIdentifierManager.getInstance().get(fileName);
FileSystem filesys=(sdi==null)?null:sdi.getFileSystem();
if(filesys!=null && !filesys.checkReadPermission(fileName)) {
throw ex1;
I also use many native methods in different libraries.
Any ideas?
Thanks,
Sibelius

Out of Memory for 6.0 sp2

Similar Messages

Maybe you are looking for