aspose file tools*
The moose likes Swing / AWT / SWT and the fly likes Stack Overflow Error - URGENT Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Swing / AWT / SWT
Bookmark "Stack Overflow Error - URGENT" Watch "Stack Overflow Error - URGENT" New topic
Author

Stack Overflow Error - URGENT

Tanmay Agarwal
Greenhorn

Joined: May 01, 2006
Posts: 1
Problem Scenario :

We have a J2EE application, which has a front end developed in Java Swing with usage of heavy graphics & managed by the weblogic server. There are several application details in the Hash-Maps containing with nested Hash-Maps & Hash maps contains the Serializable Java Value Objects. These serializable Java Objects contains values which are Java Primitive Types as well as Other Java Value Objects. When the client launches the application & tries to read these Hash-Maps from the server, the Stack Over Flow Exception as given below occurs. This has started occurring from a few days only.



Stack Trace :

java.lang.StackOverflowError
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1812)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.util.HashMap.writeObject(HashMap.java:798)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)

Can you suggest something in this regard? This is VERY URGENT !!



Regards
Tanmay Agarwal
agarwal.tanmay@gmail.com
Kamesh Loganathan
Greenhorn

Joined: Jan 21, 2006
Posts: 20
Hi,
I am not sure why this is happening in your application but in genral this happens in swing when there is a dead lock. Since swing is event driven, if for some reason there is an event that triggers another and that inturn triggers the first one, then you end up with Stack overflow exception. Hope this helps.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Stack Overflow Error - URGENT
 
Similar Threads
Urgent !
Urgent
NotSerializableException Problem
Error during saving session into database
Session Management in Websphere 3.5