API is working on TOMCAT, But failing on Weblogic about cloning HOT 11 CLOSED

If the process is dying, it might be it is cloning a native object or runs out 
of memory or out of stack (in linux i noticed out of stack can sometimes crash 
the jvm). Can you enable debug (cloner.setdebug) and have a look on what gets 
cloned? And maybe also increase thread stack space.

I could not able to find cloner.setdebug method in the API, can you please 
suggest

Well, I did not turned debuger on, but I saw a fatal error in SSL exception in 
the Logger. This only happens after we introduce this Clonner bit. When we 
comment this clone bit we do not have any issue, running properly. 

Hi Kostas,
         Just want to tell you, I have a Hibernate Object which has child Objects and for some of the Child Object there is a link to Parent Object, will there be any circular reference problems occur.

Cloner is aware of cyclic dependencies and will work fine with those. For the 
debugging, there should be a method "dump cloned" or so, will have a look soon

can you please try cloner.setDumpCloned(true) and have a look at the console? 
Even the console on your dev box will do, provided you clone exactly the same 
objects. If you notice it cloning file handlers, streams, hibernate proxies, 
web server proxies etc, then probably you need to cloner.dontClone(class)

Also can you paste the source code of the class(es) you clone? Is it just a few 
or many classes?

I think you are looking another API, because I could not able to find the 
cloner.setDumpCloned(true).

How are you instantiating cloner?

import com.rits.cloning.Cloner

Cloner cloner = new Cloner()
c.deepClone(<Object>)

cloner.setDumpCloned(true) should do, doesn't it work?