Open GoogleCodeExporter opened 9 years ago
This is stupid! I just lost 3 hours trying to figure out what was wrong on my
EC2 server. The reason is that opensocial.jar's logging.properties is read
first on that specific EC2 configuration, but not on my test environment. The
logging flood caused my EC2 server to almost hang.
This is a huge anti-pattern! You should NOT set logging for all classes on your
lib, if you expect others to include your lib on their projects (specially if
this is a 1.0 lib).
Please, fix this. It is as simple as removing this file from the jar generation
script.
Note: Tomcat startup with ALL logging=load of 0.98, after removing ALL
logging=load of 0.02
Original comment by mangini
on 12 Nov 2010 at 8:33
Original issue reported on code.google.com by
Daniel.D...@gmail.com
on 20 Apr 2010 at 12:14