Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B550811D65 for ; Tue, 10 Jun 2014 19:36:23 +0000 (UTC) Received: (qmail 64196 invoked by uid 500); 10 Jun 2014 19:36:18 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 64032 invoked by uid 500); 10 Jun 2014 19:36:18 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 64021 invoked by uid 99); 10 Jun 2014 19:36:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jun 2014 19:36:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates 212.85.38.231 as permitted sender) Received: from [212.85.38.231] (HELO tor.combios.es) (212.85.38.231) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jun 2014 19:36:13 +0000 Received: from [192.168.245.129] (montserrat.wissensbank.com [212.85.37.175]) (Authenticated sender: andre.warnier@ice-sa.com) by tor.combios.es (Postfix) with ESMTPA id EC8283C26CB for ; Tue, 10 Jun 2014 21:36:16 +0200 (CEST) Message-ID: <53975E12.8060100@ice-sa.com> Date: Tue, 10 Jun 2014 21:35:46 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Working mod_jk related to loglevel with wildfly? References: <5396F07A.2070109@stoas.nl> <53971182.5010306@ice-sa.com> <53972440.5080209@ice-sa.com> <53973507.3090409@yahoo.com> In-Reply-To: <53973507.3090409@yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Mark Eggers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 6/10/2014 8:29 AM, Andr� Warnier wrote: >> Andr� Warnier wrote: >>> Martin Stolk wrote: >>>> >>>> Hello, >>>> >>>> We are migrating our applications from tomcat to wildfly. We >>>> are using mod_= jk (1.2.40) to connect apache to the wildfly >>>> ajp port. >>>> >>>> When using tomcat there are no problems, but with wilfdly >>>> there is a strang= e behavior in our application. >>> It is a bit of a puzzle then, why you are asking for help here. >>> Would "http://wildfly.org/gethelp/" not be a better place to >>> start ? >>> >>>> Our application is written in java (wicket) and when entering a >>>> search form= every field fills with a semi-colon after entering >>>> the find button. When i= set the JkLogLevel to trace or debug >>>> the problems remains but less frequen= tly and not in every >>>> form. I also tried different ForwardURI** JkOptions, but that >>>> make no difference. >>> I can't think of a reason off-hand why this should ever make any >>> difference. It would seem that the first thing to look at, is >>> what this "Find" button in the form really does. Is it just a >>> "submit" button, or does it call something (some javascript >>> perhaps) ? Does the

send a POST, or a GET request ? >>> >>>> Can anyone help me where to find a solution? >>>> >> Ok, I'll bite again. As I understand the issue, you have the >> following schema : >> >> B + BA <-HTTP-> A + M <-AJP-> E + EA >> >> where : >> >> - B is the browser - BA is the "application" in the browser. That >> can be pure HTML, or HTML + javascript, or a Java Applet, or >> whatever - A is the Apache httpd front-end - M is the mod_jk >> module running inside Apache httpd - E is the Servlet Engine >> (Tomcat or Wildfly) - EA is the java application running inside of >> E >> >> and we assume that the only element which varies is E, which is >> either Tomcat or Wildfly. >> >> You say that when E is Tomcat, everything works fine. But when E >> is Wildfly, strange things happen. >> >> Given that B + BA are the same and would send the same HTTP >> requests in both cases to A, - there is no reason why A would do >> anything different when E is Wildfly, than when E is Tomcat. A >> does not even know which Servlet Engine E is being used. - there is >> no reason why M would do anything different when E is Wildfly, >> than when E is Tomcat. M does not even know which Servlet Engine E >> is being used. It just knows that it is talking to an AJP connector >> of a webserver, and that it needs to "translate" the HTTP request, >> to an AJP request, before forwarding it. >> >> The only impact that I can think of, of changing the mod_jk >> loglevel, is to make mod_jk perhaps a little bit slower, because >> it has to log more. (But we should be talking of at most >> milliseconds here). >> >> So, on the face of it, logically, I would think that if there is a >> problem when E is Wildfly, the problem must be with Wildfly, or >> with how Wildfly is running the EA application. >> >> Or else, our premise is wrong, and BA is not exactly the same in >> both cases, and does not send exactly the same thing to A. But >> since BA "comes from" E + EA originally, that would also mean that >> the problem is with Wildfly + the EA application. >> >> So I would still go to the Wildfly support list, present the same >> case as you did above, and ask them if they have a clue as to what >> may be happening. > > > To extend Andr�'s excellent examination . . . . > > It would be nice if you could remove A + M from the equation. In other > words: > > B + BA <-HTTP-> E + EA > > Then vary E (Wildfly or Tomcat). > > If both work, then the issue might be with Firefly's AJP configuration > (or its AJP implementation). > > If Firefly does not work, then the issue might be with Firefly's > configuration (or Firefly and Wicket). > > If neither work, then that's a puzzle. > > . . . . just my (coffee-less) 2 cents Now wait, Firefly ? Is that linked to the coffee-less state ? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org