Its simply a wrapping of the exception resulting from a reflected call that is not a subclass of java.lang.Exception. Its possible that this is an exception marshalled back to a client and that the OOM is occuring on the server.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sebastian Hauer Sent: Monday, January 26, 2004 1:53 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] OOM wrapped in UndeclaredThrowable Hi, Today we saw this exception log in one of our environments running jboss 3.0.8: ---------------------------- 12:39:55,861 WARN [ClientConsumer] Could not send messages to a receiver. java.lang.reflect.UndeclaredThrowableException: java.lang.OutOfMemoryError <<no stack trace available>> 12:39:55,861 ERROR [JMSDestinationManager] The connection to client ID:91 failed. 12:39:55,924 ERROR [SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.AcknowledgementRequestMsg896683[msgType: m_acknowledge, msgID: 4449, error: null] javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:317) at org.jboss.mq.server.JMSDestinationManager.acknowledge(JMSDestinationMana ger.java:520) at org.jboss.mq.server.JMSDestinationManager.acknowledge(JMSDestinationMana ger.java:504) at org.jboss.mq.server.JMSServerInterceptorSupport.acknowledge(JMSServerInt erceptorSupport.java:197) at org.jboss.mq.server.TracingInterceptor.acknowledge(TracingInterceptor.ja va:404) at org.jboss.mq.server.JMSServerInvoker.acknowledge(JMSServerInvoker.java:1 99) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketMa nagerHandler.java:81) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java :355) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:376) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecuto r.java:732) at java.lang.Thread.run(Thread.java:479) ---------------------------- 1. We are wondering how it is possible that an OOM ends up inside a UndeclaredThrowableException. 2. Is it somehow possible that an OOM originating on a remote client results in such a stack trace? Any help or insite is appreciated, thanks, ---------------------------------------- Sebastian Hauer Software Engineering [EMAIL PROTECTED] Sakonnet Technology 594 Broadway Suite 1008 New York, NY 10012 www.sknt.com +1 917 237 3831 direct +1 212 343 3103 fax ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
