Yes I sent them 2 posts ago.
However, here they are again :
In our server.xml:
##
In our workers.properties:
workers.apache_log=/usr/local/apache/logs
workers.tomcat_home=/usr/local/tomcat
workers.java_home=/usr/local/java
ps=/
worker.list=ajp13
worker.ajp13.type
have we seen your connector config, and your apache forwarding setup (JK
i assume)?
Nicolas Schwartz wrote:
As I said it happens even on GET requests and very small urls on our side.
Since it is a get request, we do see the parameter in the apache log,
but we can't get it with the getParame
As I said it happens even on GET requests and very small urls on our side.
Since it is a get request, we do see the parameter in the apache log, but we
can't get it with the getParameter() method.
The parameter is lost somewhere between the connector and tomcat I think.
Nicolas
Yashwanth CP a
Hi,
We are facing a similar issue ( missing parameters intermittently ). Our
setup has relatively huge post requests , ( < 4KB) , and about 100-200
parallel connections on a tomcat that has 512MB memory.Some of the
parameters just become null randomly. Our guess is ,it is related to size of
post r
Hi !
Here is the configuration we have:
In our server.xml:
##
In our workers.properties:
#parametrage de mod_jk
workers.apache_log=/usr/local/apache/logs
workers.tomcat_home=/usr/local/tomcat
workers.java_home=/usr/local/java
ps=/
worker.list=ajp13
worker.ajp13
in mod_jk.conf for apache, we have the following lines:
# define the channel
JkSet channel.socket:localhost:8009.port 8009
JkSet channel.socket:localhost:8009.host 127.0.0.1
# define the worker
JkSet ajp13:localhost:8009.channel channel.socket:localhost:8009
JkUriSet group ajp
Nicolas Schwartz wrote:
>
> I thought it might come from the connector ...
> Did you already try to change it ?
> Which version are you using ?
>
Interesting point Nicolas, to be honest with you... I don't know a lot about
connectors. I went to the Server.xml file in Tomcat and found the follo
I thought it might come from the connector ...
Did you already try to change it ?
Which version are you using ?
Nicolas
lmelendez a écrit :
Nicolas Schwartz wrote:
It occurs on GET requests, maybe on POST ones but we don't know.
The value of the parameter is not long, neither is the value.
It
Nicolas Schwartz wrote:
>
> It occurs on GET requests, maybe on POST ones but we don't know.
> The value of the parameter is not long, neither is the value.
> It appears to occur "randomly"
>
Exact same thing in our case. We have seen it in GET requests, not entirely
sure about POSTs. We use s
rache wrote:
Parameter values are set in the jsp either as hardcoded
links(http://j.jsp?param=value) or as hidden parameters. When the program
enters the doGet() or doPost() method of a servlet and check for the
parameter, its null.
String pvalue = req.getParameter("param");
This happens interm
Hi,
We are facing the same problem.
Sometimes the parameters don't get to tomcat.
We've seen this by monitoring our plateform through a servlet simply returning
the value of a parameter.
We are also using apache+tomcat
apache-2.0.54
jakarta-tomcat-5.5.9
It occurs on GET requests, maybe on POS
(i can't see a previous thread for this, new mail setup, so apologies if
I'm restating.)
Are you using GET or POST?
And how many parameters are you submitting?
And are there any particularly long bits of data in the parameters?
lmelendez wrote:
Hi Rache,
Well, we are seeing the problem. Ou
Hi Rache,
Well, we are seeing the problem. Our web application seems to *drop*
parameters for some requests and we still don't know what it is. We have
enabled Valves and Filters and it looks like the parameters never make it to
tomcat.
The problem is intermitent and we cannot reproduce it at w
Parameters are either set this way:
1. from the page itself:
2. from building xmls which are then integrated into the page itself which a
user can click on for links:
href="../servlet/tpservlet?transactiontype=sessionProfileActionBean&ACTIVITY_
Erm. ok. Where does the redirectURL variable come from? Unless it has
parameters encoded into it that will be your problem.
Also, be a bit wary in using the RequestDumperValve with non-ascii
charset data as it can corrupt some parameters:
http://marc.theaimsgroup.com/?l=tomcat-user&m=112530311
This is how the code redirects:
if (redirectURL.toUpperCase().startsWith("/SERVLET"))
{
// routing to another request to the servlet...
response.sendRedirect(request.getContextPath() +
redirectURL);
}
Rache,
Tools like ieHTTPHeaders and LiveHTTPHeaders will also help you determine
what the browser actually sends to the server, including any redirects
caused by 302 response codes.
HTH,
Jon
> Rache,
>
>> But this usually occur after redirects.
>
> This is what I was going to ask about: if you
Rache,
> But this usually occur after redirects.
This is what I was going to ask about: if you fail to put all the
important parameters into the redirect, then you will lose them. For
example, if you have a form handler that accepts 5 request parameters,
you cannot simply say:
response.sendRedir
t;Ben Souther" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Friday, July 28, 2006 9:21 PM
Subject: Re: Missing Request Parameters
> Since all webapps rely on request parameters, I'd say this would be a
> huge bug if it were one. So huge that it would render
That's what I was thinking - that it couldn't have been a bug :) I'm quite
new to Tomcat but I know it coundn't have been one since many are using it.
I don't have any code access now since codebase is at the office. But this
usually occur after redirects.
Most of the pages (servlets and those ur
Since all webapps rely on request parameters, I'd say this would be a
huge bug if it were one. So huge that it would render Tomcat unusable
for any commercial grade application. Such a bug would fill this list
with hundreds or thousands of complaints.
Since we're not seeing those complaints, it'
21 matches
Mail list logo
