search

aucd29 / cloning

Automatically exported from code.google.com/p/cloning
Other
0 stars 0 forks source link

Conflict with Cloning jar and Log4j jar. #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

I am using an web-application where i am using the cloning jar in cache 
implementation. Here i am facing an issue like after few minutes of 
transactions the log is not generating and throwing an error:--

log4j:ERROR Could not close 
org.apache.log4j.helpers.CountingQuietWriter@10c8abcd
java.io.IOException: Bad file descriptor

But if i remove the cloning jar, log is working fine. So the cloning jar is 
having a conflict with the log4j jar.

The log4j is working with all other third party jars except this cloning jar.

Can you tell me if this is a bug with the cloning jar? 

The jar versions which i am using are:-

Cloning--1.7.4
log4j--1.2.9

Original issue reported on code.google.com by debrajpa...@gmail.com on 12 Dec 2013 at 1:47

GoogleCodeExporter commented 9 years ago 
Cloner will deep clone all instances, including Logging classes. You probably 
want to configure cloner to not clone them: cloner.registerImmutable(... Logger 
classes ...)

Original comment by kostas.k...@googlemail.com on 16 Dec 2013 at 9:20

GoogleCodeExporter commented 9 years ago 
Hi.. Thanks for the reply. It solved the issue :)

Original comment by debrajpa...@gmail.com on 23 Dec 2013 at 2:59

GoogleCodeExporter commented 9 years ago

Original comment by kostas.k...@googlemail.com on 23 Dec 2013 at 3:01