DO NOT REPLY [Bug 23962] New: - Out of memory error when serializing bad classes.

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23962>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23962

Out of memory error when serializing bad classes.

           Summary: Out of memory error when serializing bad classes.
           Product: Axis
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: luke_sleeman@hotmail.com


You can cause the BeanService seriliser into a loop that will cause out of
memory errors, by tring to send a class like:

public class StupidClass
{
	public StupidClass getInstance()
	{
		return new StupidClass();
	}
}

The end result of trying to send this class is an Tomcat 500 error with a root
cause of java.lang.OutOfMemoryError .  While axis cannot deal with Classes like
StupidClass, the out of memory error is less than helpfull in trying to diagnose
what went wrong.  Something more along the lines of:

Error while serilizing StupidClass:  Maximum tree depth exceeded while calling
getInstance()

would be helpfull