java.lang.OutOfMemoryError: nativeGetNewTLA

Mon Apr 28 07:47:05 PDT 2008

What version jgroups is it?  I don't recognize the stack traces.

Jim

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Jon Masamitsu <Jon.Masamitsu at Sun.COM>

Date: Mon, 28 Apr 2008 07:45:11 
To:Keith Holdaway <Keith.Holdaway at sas.com>
Cc:"hotspot-gc-use at openjdk.java.net" <hotspot-gc-use at openjdk.java.net>
Subject: Re: java.lang.OutOfMemoryError: nativeGetNewTLA

Keith Holdaway wrote:
> Any ideas what this refers to?

I looked through the hotspot sources and didn't
find any references to nativeGetNewTLA.

> 
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.protocols.TP.bufferToMessage(TP.java:972)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:829)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> 2008-04-26 02:38:13,411 ERROR [org.jgroups.stack.DownHandler] DownHandler (NAKACK) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.protocols.pbcast.NAKACK.getDigestHighestDeliveredMsgs(NAKACK.java:935)
>         at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:422)
>         at org.jgroups.stack.DownHandler.run(Protocol.java:121)
> 2008-04-26 02:38:17,471 WARN  [org.jgroups.util.TimeScheduler] exception executing task org.jgroups.protocols.pbcast.STABLE$StableTask at 4130b93
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.protocols.pbcast.STABLE$StableTask.run(STABLE.java:783)
>         at org.jgroups.util.TimeScheduler$TaskWrapper.run(TimeScheduler.java:204)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> 2008-04-26 02:38:20,298 ERROR [org.jgroups.stack.UpHandler] UpHandler (VERIFY_SUSPECT) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:474)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.UpHandler.run(Protocol.java:60)
> 2008-04-26 02:38:20,298 ERROR [org.jgroups.stack.DownHandler] DownHandler (FD) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:503)
>         at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
>         at org.jgroups.protocols.FD.down(FD.java:339)
>         at org.jgroups.stack.DownHandler.run(Protocol.java:121)
> 2008-04-26 02:38:24,562 ERROR [org.jgroups.stack.DownHandler] DownHandler (UNICAST) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:503)
>         at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
>         at org.jgroups.protocols.UNICAST.down(UNICAST.java:391)
>         at org.jgroups.stack.DownHandler.run(Protocol.java:121)
> 2008-04-26 02:38:25,936 ERROR [org.jgroups.stack.UpHandler] UpHandler (AUTH) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:474)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.AUTH.up(AUTH.java:143)
>         at org.jgroups.stack.UpHandler.run(Protocol.java:60)
> 2008-04-26 02:38:35,854 ERROR [org.jgroups.stack.DownHandler] DownHandler (FD) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:503)
>         at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
>         at org.jgroups.protocols.FD.down(FD.java:339)
>         at org.jgroups.stack.DownHandler.run(Protocol.java:121)
> 2008-04-26 02:38:38,618 ERROR [org.jgroups.stack.UpHandler] UpHandler (UNICAST) caught exception
> java.lang.OutOfMemoryError: nativeGetNewTLA
>         at org.jgroups.util.Queue.addInternal(Queue.java:570)
>         at org.jgroups.util.Queue.add(Queue.java:143)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:474)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:259)
>         at org.jgroups.stack.UpHandler.run(Protocol.java:60)
> 
> Running in JBoss.
> 
> keith
> 
> Keith R Holdaway
> Java Development Technologies
> 
> SAS The Power to Know
> 
> Carpe Diem
> 
> 
> -----Original Message-----
> From: Keith Holdaway
> Sent: Saturday, April 26, 2008 10:28 AM
> To: 'Y.S.Ramakrishna at Sun.COM'
> Cc: hotspot-gc-use at openjdk.java.net
> Subject: Weak References
> 
> If we are seeing a huge build up of weak references:
> 
> sun/rmi/transport/WeakRef =>
>       1654973  1644293  10680       0      0 Total
>        794333   783888  10445       0      0 => com/sas/metadata/remote/MdObjectListImpl
>        194966   194966      0       0      0 => com/sas/metadata/remote/impl/PropertyImpl
>       192165   192165      0       0      0 => com/sas/services/information/metadata/OMRProperty
> 
> When does the GC algorithm decide to collect? Is there something that can be done programatically to collect earlier?
> 
> I assume GC will not collect until the weak references are "dead", i.e. the referents are available for GC since no strong refs are pointing at the referent?
> 
> Any guidance appreciated.
> 
> keith
> 
> Keith R Holdaway
> Java Development Technologies
> 
> SAS The Power to Know
> 
> Carpe Diem
> 
> 
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
_______________________________________________
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use