Closed GoogleCodeExporter closed 9 years ago
Hi Matthias, changing the logging to commons logging is not desirable for
tomcat 6+. At first I used java util logging and changed it with issue #35 (Use
same logging system as Tomcat).
I asume you have no possibility to move on to tomcat6?
I can imagine creating a separate branch for tomcat 5.5 compatibility and a
separate jar/release for it, though I have to say that now that tomcat7 is
coming I'm not so motivated about putting effort in creating support for 5.5.
Would it be worth for you to get a separate branch/jar/release for this change,
or can you just use your custom build for now?
Cheers,
Martin
Original comment by martin.grotzke
on 25 Sep 2010 at 1:56
Hi Martin,
thanks for your feedback. Sadly Tomcat 6 is not available for me, cause
deployment infrastructure is managed by our resevered siteops team. ;-)
Did a custom build of msm two weeks ago, works like a charme. I guess no
special release is needed if there are no other users requesting support for
Tomcat 5.
Bye4now,
Matthias
Original comment by turbobr...@gmx.net
on 25 Sep 2010 at 5:37
Alright, so I'll close this for now. If you want to get notified about new
releases just subscribe to the mailing list:
http://groups.google.com/group/memcached-session-manager
Cheers,
Martin
Original comment by martin.grotzke
on 26 Sep 2010 at 11:30
We're still on 5.5 (RHEL5) at my employer as well. However, it seems to work
fine if I just copy the tomcat-juli jar from JPackage's Tomcat 6.
Original comment by goo...@gnifty.net
on 21 Dec 2010 at 8:33
Original issue reported on code.google.com by
turbobr...@gmx.net
on 15 Sep 2010 at 8:18Attachments: