DO NOT REPLY [Bug 39699] - simple deploy failed in cluster (distributable flag)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39699. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39699 --- Additional Comments From [EMAIL PROTECTED] 2006-06-03 07:39 --- (In reply to comment #16) please attach a test case, that way we can get the facts and fix it more promptly. sorry, but what do you mean with a 'test case'? You can reproduce the problem with the server.xml in my first post (a simple cluster configuration is sufficient (SimpleTcpCluster line only is sufficient) and try to deploy with html manager or copy a war to your webapps (with autodeploy enabled of course). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the mod_jk 1.2.16 release?
Mladen Turk wants to add some small changes. After that we will do some testing again and then release. Any input from your side about intermediate test results on trunk will be highly appreciated. Most important changes until now: - fixed bug, that disabled workers never will leave error state - added piped mod_jk logging for Apache 1.3 - fixed log file corruptions - Additional attribute distance to express preferences between balanced workers of an lb - Additional parameter jvm_route to be configure several workers for the same tomcat target, e.g. to use them in differently configured lb workers. - Better behaviour of lb in settings which use domains and after error recovery - small performance improvements - code simplifications in lb worker The new atributes are already documented in the xml documentation contained in subversion. Rainer David Rees wrote: There was a thread in late March (http://marc.theaimsgroup.com/?t=11425956601r=1w=2) which looked like was going to lead to a new release of mod_jk which would fix a number of outstanding bugs, but I never saw that 1.2.16 was tagged for testing. I'm willing to test once 1.2.16 is tagged as my servers are affected by some of the known bugs in 1.2.15. Will the head of SVN planned on being tagged for 1.2.16? I can pull that and use that for testing in the meantime. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39711] New: - WebappLoader checkInterval documentation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39711. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39711 Summary: WebappLoader checkInterval documentation Product: Tomcat 5 Version: 5.5.17 Platform: All OS/Version: other Status: NEW Severity: trivial Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The context Loader was apparently refactored many moons ago to move the checkInterval into a common backgroundProcessorDelay located in ContainerBase. The documentation still mentions the presence of checkInterval in WebappLoader. http://tomcat.apache.org/tomcat-5.5-doc/config/loader.html All the resources bundles in o.a.c.loader also still store the (standard|webapp)Loader messages. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39699] - simple deploy failed in cluster (distributable flag)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39699. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39699 --- Additional Comments From [EMAIL PROTECTED] 2006-06-03 15:42 --- test case, meaning maybe a zip containing your config files, any modifications that you have made two tomcat, ie, added in log4j etc. ie, can you get us detailed instructions on how to exactly reproduce your problem. just saying that deploy an app and it breaks, it simply not sufficient, as our apps are deploying. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 38048] - Classloader leak caused by EL evaluation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=38048. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=38048 --- Additional Comments From [EMAIL PROTECTED] 2006-06-03 17:58 --- Sun AS/Glassfish used commons-el in past (=8.2) versions, exhibiting exactly this problem. This was fixed using a simple patch, manually releasing cached classes on webapp shutdown. See description of bug and solution here: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6390584 In later versions (=9.0) commons-el was dropped altogether (quite wise). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
