Re: [VOTE] JK 1.2.14.1
I don't know if I'm in position to vote about this, but I have been running more than a week with production servers using 1.2.14 (not .1). No problems (I have 12 sites using various tomcat versions, most of them are low-volume, however). I would say this is stable. Ari S. - Original Message - From: jean-frederic clere [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Sent: Wednesday, July 13, 2005 7:32 PM Subject: Re: [VOTE] JK 1.2.14.1 [x] Stable -- good build [ ] Alpha -- something serious is wrong: what is it? Please test and vote. Cheers Jean-Frederic - 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]
Re: PayPal Notification: Upgrade your information
Sir/Madam, We could not understand what do you want to say. Please write in details and in english language pls. Thanks and rgds., GUL. [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: fitchburg arum inhuman cancellate lighthearted hausdorff lexicography sirius carl groan conrad imperial bloop earthy decontrolling epitaxial charta escheat intoxicant ahead tenney - How much free photo storage do you get? Store your friends n family photos for FREE with Yahoo! Photos. http://in.photos.yahoo.com
DO NOT REPLY [Bug 35735] New: - Classloader often does not seperate Webapp Classpaths
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=35735. 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=35735 Summary: Classloader often does not seperate Webapp Classpaths Product: Tomcat 5 Version: 5.5.7 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hi, we use TC 5.5.7 with 5 WebApps which have ususally the same classes, but are complettly seperated by directories. Think of it as Production-, Beta- and Developer-WebApps. From time to time, we restart TC . If we do, and the dev webapp is first who is accesed and for this loads it classes, these classes are also used in the production web. for 95% of the used classes in this three apps, code and class methodes are the same, as the jsps are the same too. Our Production web does not reload classes in the classpath for speed reasons. The dev app does reload the classes. We used TC3 before we switched to TC5 and TC3 did NEVER show this behaviour. What do you need from our server to investigate this? -- 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 35735] - Classloader often does not seperate Webapp Classpaths
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=35735. 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=35735 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 14:51 --- Please post on tomcat-user instead. -- 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 35745] New: - Realm JDBCRealm userTable userRoleTable not real parameters?
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=35745. 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=35745 Summary: Realm JDBCRealm userTable userRoleTable not real parameters? Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When implementing container managed security in server.xml using JDBCRealm (and perhaps the JNDI JDBC based realm?) this works Realm className=org.apache.catalina.realm.JDBCRealm debug=99 connectionName=javauser connectionPassword=javadude connectionURL=jdbc:mysql://localhost:3306/trainingdb driverName=com.mysql.jdbc.Driver userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name / But this does not Realm className=org.apache.catalina.realm.JDBCRealm debug=99 connectionName=javauser connectionPassword=javadude connectionURL=jdbc:mysql://localhost:3306/trainingdb driverName=com.mysql.jdbc.Driver userTable=MYTABLENAME userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name / The Tomcat log files were helpful in that they indicated my table name was not found in the database - but it was there. On a hunch I renamed my existing legacy tables (in test) to match your examples and the container managed security worked. It appears the Tomcat implementation has hard-coded these table-name and column-name values somewhere in the j_security_implementation. This of course defeats the whole point of providing these parameters to users in the first place. Note that published authors, aside from your web-site, are touting the flexibility of the Tomcat implementation to reference existing client (legacy) USER and USER-ROLE table names already existing and used by other applications. I spent several days trying to get my existing table names to work without success and I'm not a 'newbie'. I never saw any published examples in books where anyone actually used names aside from the default example, so perhaps this simply has not be tested. It is the only explanation I have for it not working without digging into the Tomcat source code implementation of container managed security. Great product, by the way, really. Tomcat is fantastic - and free -- 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]
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net AprEndpoint.java
remm2005/07/14 10:45:25 Modified:util/java/org/apache/tomcat/util/net AprEndpoint.java Log: - Cosmetic change. Set socket to 0. Revision ChangesPath 1.63 +1 -0 jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/AprEndpoint.java Index: AprEndpoint.java === RCS file: /home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/AprEndpoint.java,v retrieving revision 1.62 retrieving revision 1.63 diff -u -r1.62 -r1.63 --- AprEndpoint.java 8 Jul 2005 15:43:23 - 1.62 +++ AprEndpoint.java 14 Jul 2005 17:45:25 - 1.63 @@ -666,6 +666,7 @@ serverSockPool = 0; // Close server socket Socket.close(serverSock); +serverSock = 0; sslContext = 0; // Close all APR memory pools and resources Pool.destroy(rootPool); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow (logging)
Bill, so far all I've gotten out of FINE logging is a lot of these: Jul 14, 2005 1:44:36 PM org.apache.jk.common.MsgAjp processHeader FINE: Received 560 18 We have been monitoring the server, and even though I got no SEVERE messages, it appears to have hung as before. Am I excluding SEVERE logging messages when I specify FINE as logging such as this? (I'm quite positive this is an inclusive logging setting) org.apache.jk.common.MsgAjp.level = FINEST org.apache.jk.server.JkMain.level = FINEST I any case, I have yet to catch the mod_jk in the act of doing a buffer overflow since changing the logging parameters. Thanks for any help you can give, Collin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32361] - [daemon] Installation failed
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=32361. 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=32361 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 21:20 --- It used to work with my j2sdk 1.4.2. Now I have the same problem after I upgraded to j2sdk 1.4.2_08 on my Windows XP professional. The following is the output when running tomcat5.exe from a command window: [2005-07-14 12:00:00] [349 prunsrv.c] [error] The system cannot find the file specified. [2005-07-14 12:00:00] [1037 prunsrv.c] [error] Load configuration failed -- 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 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
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=35725. 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=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-14 21:04 --- Entity resolution is done at translation time (as required by the spec), so all entity definitions must be available then. Since you almost certainly don't want nbsp;, gt;, lt;, etc. to be resolved at translation time, you need to quote them in the source either in a CDATA section or as amp;nbsp;. -- 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 35746] New: - session manager should be immune to system clock time changes (solution provided)
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=35746.
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=35746
Summary: session manager should be immune to system clock time
changes (solution provided)
Product: Tomcat 5
Version: 5.0.30
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]
Hi,
The session manager should be able to age session by age, not by comparison to
system time stamp.
Here is a simple and working time tracker immune to time shifts.
It 'knows' it waited some amount of milliseconds. This cannot be hacked on any
OS. Given that, the time arrow is maintained and session can be aged normally,
even if system time changes on the server, which is more than probable on
appliances and embed system.
That would prevent http session to expire and logout user prematurely.
Note that upon the receiver update, 't2' is always the current time (now) and
't1' is usually the last 't2' is no shift was detected.
public void run() {
long t1 = -1;
while(true) {
try {
long t2 = System.currentTimeMillis();
//-- time shifting detection
long shift = 0;
if(t10) { //if not first loop
long expected = t1+intervalMillis;
shift = t2-expected;
if(shift timePositiveShiftTolerance) {
vlogger.warn(Time shifted in future by
more than positive tolerance:
shift=+shift+ ms, tolerance=+timePositiveShiftTolerance);
//fireTimeDriftEvent(expected, drift);
t1 = t2-intervalMillis;
} else if(shift timeNegativeShiftTolerance) {
vlogger.warn(Time shifted in past by
more than negative tolerance:
shift=+shift+ ms, tolerance=+timeNegativeShiftTolerance);
//fireTimeDriftEvent(expected, drift);
t1 = t2-intervalMillis;
} else {
shift = 0;
}
}
///
//someReceiver.update(t1, t2, shift);
///
t1 = t2;
Thread.sleep(intervalMillis);
} catch(IllegalArgumentException e) {
vlogger.warn(,e);
//no break.
} catch(InterruptedException e) {
break;
} catch(Exception e) {
vlogger.error(,e);
}
}
}
--
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 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
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=35725. 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=35725 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] -- 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: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow
I've enabled the logging per your suggestions, and not having heard back in a bit, I was hoping someone could clue in to why I get plenty of FINE messages for org.apache.jk.common.MsgAjp, but no longer get SEVERE messages. I'm also trying consistently crash mod_jk, but not having much luck, OpenCMS is the webapp invovled here, I haven't gotten any feed back from their dev list. Thanks, Collin Remy Maucherat wrote: Bill Barker wrote: The message is simply that you have a header value that is too big for the AJP/1.3 protocol to handle. If you enable DEBUG logging for org.apache.jk.common.MsgAjp, you should get a dump of the partial data that should include the name of the bad header. Given the line, it could be a monster header value, possibly a cookie (the size is 18KB, which is way over the AJP/1.3 capabilities). Rémy (with the neophyte AJP developer hat on) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Collin McClendon Sr. Microsoft Systems Engineer Digicon Corporation [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net AprEndpoint.java
jfclere 2005/07/14 15:35:21
Modified:util/java/org/apache/tomcat/util/net AprEndpoint.java
Log:
throw an exception if listen or bind fails.
Revision ChangesPath
1.64 +6 -2
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/AprEndpoint.java
Index: AprEndpoint.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/AprEndpoint.java,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- AprEndpoint.java 14 Jul 2005 17:45:25 - 1.63
+++ AprEndpoint.java 14 Jul 2005 22:35:21 - 1.64
@@ -511,9 +511,13 @@
serverSock = Socket.create(Socket.APR_INET, Socket.SOCK_STREAM,
Socket.APR_PROTO_TCP, rootPool);
// Bind the server socket
-Socket.bind(serverSock, inetAddress);
+int ret = Socket.bind(serverSock, inetAddress);
+if (ret != 0)
+ throw(new Exception(bind failed: + ret));
// Start listening on the server socket
-Socket.listen(serverSock, backlog);
+ret = Socket.listen(serverSock, backlog);
+if (ret != 0)
+ throw(new Exception(listen failed: + ret));
// Sendfile usage on systems which don't support it cause major
problems
if (useSendfile !Library.APR_HAS_SENDFILE) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem with request dispatcher
Hello,
i'm having a problem with calling a servlet
and dispatching to a jsp.
my example:
here is my simple html form:
html
body
form method=post action=test
Login input type=text name=login
Password input type=text name=password
input type=submit value=Envoyer
/form
/body
/html
Here's my processing servlet:
public class Test2 extends HttpServlet
{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException
{
System.err.println(test: doGet());
getServletContext().getRequestDispatcher(/index2.jsp).forward(request,
response);
return;
}
public void doPost(HttpServletRequest request, HttpServletResponse
response)
throws IOException, ServletException
{
System.err.println(test: doPost());
getServletContext().getRequestDispatcher(/index2.jsp).forward(request,
response);
return;
}
}
[/code
Here's index2.jsp code:
[code]
html
head
title/title
/head
body
test
/body
/html
The logs of the server Tomcat 5.5 on W2K and IE 6 with a single form submit:
test: doPost()
test: doGet()
When i remove doGet implementation from the servlet, there is only
test: doPost() log. So it's OK.
When the two methods are implemented, that doesn't work good.
When i remove getRequestDispatcher... line in the doPost() method, it works.
I don't understand.
it happens every time with this example.
Thanks for your help
Julien
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
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=35725. 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=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2005-07-15 02:41 --- I'm still unclear about something. - You said Entity resolution is done at translation time (as required by the spec),, could you provide us which spec and where( i.e. which section ) has this requirement ? - Current jasper can resolve some entities(lt;, gt;, quot;, amp;, apos; ). I'd like to know why. If what you said is correct, they should be also flagged as an error. Why I'm asking is that I'd like to know how to have Jasper recognize additional entities. ( adding something to jsp:root tag ? or something like that. ) - When I tried the syntax #D;, jasper seems to recognize it. (Note that according to HTML spec, this syntax is valid. ) Is this shure that this syntax is also runnable for jasper ? Why I'm asking these is that current jasper accepts some entities while it doesn't accept others so I'm wondering what is the threshold for jasper to accept/not accept entities. Thank you very much. . . -- 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 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
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=35725. 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=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-15 05:08 --- (In reply to comment #4) I'm still unclear about something. - You said Entity resolution is done at translation time (as required by the spec),, could you provide us which spec and where( i.e. which section ) has this requirement ? spec-quote spec=JSP version=2.0 section=6.2.3 The first step in processing a JSP document is to process it as an XML document, checking for well-formedness, processing entity resolution and, if applicable, performing validation as described in Section JSP.6.2.4. /spec-quote - Current jasper can resolve some entities(lt;, gt;, quot;, amp;, apos; ). I'd like to know why. If what you said is correct, they should be also flagged as an error. Why I'm asking is that I'd like to know how to have Jasper recognize additional entities. ( adding something to jsp:root tag ? or something like that. ) Doh, those are standard XML entities that all XML parsers recognize. Use them in (without escaping) your JSPX page, and you're toast ;-). Watch your browser choke on: jsp:root xmlns:jsp==http://java.sun.com/JSP/Page; version=2.0 jsp:output omit-xml-declaration=no doctype-root-element=html doctype-public=-//W3C//DTD XHTML 1.1//EN doctype-system=http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd/ html bodyHello lt;World/body /html /jsp:root - When I tried the syntax #D;, jasper seems to recognize it. (Note that according to HTML spec, this syntax is valid. ) Is this shure that this syntax is also runnable for jasper ? Again, a standard XML entity. Why I'm asking these is that current jasper accepts some entities while it doesn't accept others so I'm wondering what is the threshold for jasper to accept/not accept entities. It's really simple: Jasper accepts the standard XML entities, as well as those defined in the internal and/or external DTD of the source document. And, of course, DTD declarations buried in CDATA sections don't count (they are nothing more than text Strings at translation time). But you are really missing the point: You don't want Jasper to resolve the XHTML entities at translation time. Thank you very much. . . -- 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: mod_jk 1.2.10 and tomcat 5.5.9 buffer overflow
Collin McClendon [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I've enabled the logging per your suggestions, and not having heard back in a bit, I was hoping someone could clue in to why I get plenty of FINE messages for org.apache.jk.common.MsgAjp, but no longer get SEVERE messages. I'm also trying consistently crash mod_jk, but not having much luck, OpenCMS is the webapp invovled here, I haven't gotten any feed back from their dev list. You get plenty of FINE messages, since those are primarily for developers trying to understand the protocol traffic ;-). You haven't gotten SEVERE messages for the simple reason that none of them have been triggered. (as an aside, MsgAjp only currently logs at either SEVERE or FINE). As Remy mentions below, the most likely problems are with a 'Set-Cookie' header (with a ridiculously big cookie), or with a 'Location' header (from a sendRedirect with a ridiculously big query-string). Personally, I'm betting on the second (since the Response body was less than 8K). In any case, this is starting to border on [OT] for this list, and may be better continued on [EMAIL PROTECTED] Don't worry, both Remy an me lurk there ;-). Thanks, Collin Remy Maucherat wrote: Bill Barker wrote: The message is simply that you have a header value that is too big for the AJP/1.3 protocol to handle. If you enable DEBUG logging for org.apache.jk.common.MsgAjp, you should get a dump of the partial data that should include the name of the bad header. Given the line, it could be a monster header value, possibly a cookie (the size is 18KB, which is way over the AJP/1.3 capabilities). Rémy (with the neophyte AJP developer hat on) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Collin McClendon Sr. Microsoft Systems Engineer Digicon Corporation [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35725] - jasper throws org.apache.jasper.JasperException with XHTML document
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=35725. 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=35725 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- 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]
