First - I may have posted this to the wrong list, if so please let me know a more
appropriate place to post this.
I think there is a bug in the way Tomcat (or the JVM) handles class loading of
classes. The problem is this, I have a servlet (filter actually) that attempts to do
some XSLT
Hi,
I put 2 web apps on the same tomcat(under apache).
App1 is defualt and App2 isn't.
when tring reference App2 from App1 the page not fount.
in App1 I write: http//:App2IP/App2Name/test.jsp
and get the error - page not found.
-
Oren Deri
Cellular:
Henri,
To see if APR could run on AS/400, you just need to download the
Apache2.0alpha drop and build it. If the httpd could run properly than APR
works on AS/400!
Have fun!
Punky
- Original Message -
From: "GOMEZ Henri" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday,
To see if APR could run on AS/400, you just need to download the
Apache2.0alpha drop and build it. If the httpd could run
properly than APR works on AS/400!
I've take a look at APR and there is no reference to AS/400.
There is nothing related to OS/400 in config.guess.
AS/400 is a very
Robert,
this is a well known issue that is being worked on. Check back on the list
over the last couple of days for another discussion of this :-)
Kevin Jones
DevelopMentor
www.develop.com
-Original Message-
From: Robert Petersen [mailto:[EMAIL PROTECTED]]
Sent: 26 March 2001 11:20
Could you send us the pushlet code example.
I could help here (mod_jk) :-)
"Entre truands, les bnfices, a se partage, la rclusion, a
s'additionne."
-- Michel Audiard
-Original Message-
From: Jestin Jean-Francois
[mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 4:01 PM
To:
Hello,
I'm currently using apache 1.3.12(mod_jk) and tomcat 3.3-m2 under solaris 2.6 talking
ajp13
Everything works fine except that I encounter sometime an Internal Server Error if I
don't restart Apache each time I restart tomcat. Is there a fix for that problem ?
On the other hand I use a
Pilho Kim wrote:
Hi,
Retry with Apache 1.3.14 or 1.3.17
On Fri, 23 Mar 2001, Jim Yiu wrote:
Hi,
I am trying to compile the Tomcat-Apache plugin for Solaris and am
unsuccessful,, I
am trying
to follow the mod_jk faq but it does not explain what to do when there are compile
melaquias01/03/26 06:47:58
Modified:src/share/org/apache/tomcat/modules/session
SimpleSessionStore.java
Log:
Temporary(?) fix to stop crashes when creating a new Session in embedded use of
Jasper (i.e. as standalone JspServlet ). Problem may occur in other
This is a little bit offtopic for the tomcat-dev list so I'll answer
personally:
Apache 1.3.x ist a classic unix-fork apllication. To minimize the overhead
a park of processes is started at startuptime.
If running on Win32 these processes are mapped more or less on NT-Threads.
Apache 2.x is
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
From: Mel Martinez [EMAIL PROTECTED]
Subject: TC3.3 - building javadoc
To:
Currently, when you run the build script (for TC 3.3),
build.xml has 'dist' dependent on the 'javadoc'
target. The 'javadoc' target compiles javadoc pages
for org.apache.tomcat.core and
org.apache.tomcat.modules.*.
I dunno about you, but this seems insufficient for
'dist'. Shouldn't the
here are 2 articles speaking about the pushlet
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet-2.html
here is a very simple sample pushlet :
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
Hi,
I take a look at pushlet and find it very bad design.
Using opened http connections to do real-time job is
not realist.
In that case you keep an :
- one OS (job/thread)
- one ajp13 connection
- one tomcat thread.
Imagine if you got 256 concurrents connexions !
A better alternative will
As hinted at last week, I'd like to propose
refactoring some of the classes in Jasper to improve
the OO model a bit, make maintenance/extendability a
bit easier and hopefully help the performance a bit as
well for those of us using jasper as the JSP engine in
other servlet engines (other than
Hi,
I have two questions regarding mod_jk's way of dealing with Tomcat
going away.
(1)
Can mod_jk be extended safely to retry connecting for a certain
time instead of immediately reporting an Internal Server Error if
a Tomcat process is temporarily unavailable? I have modified the
function
Can someone confirm that request-time attribute values is not
implemented in the latest version of Jakarta?
Here's what I want to do:
foo:bar customer="%= customer.getID() %"/
But instead of customer id, what actually gets passed to
BarTag.setCustomer() is the string "%= customer.getID() %"
Hi
We have been using JServ now Tomcat for some years now and are quite happy
about it. But alas some of our customers want thier stuff running on Win NT
or Win 2000, so we have also been using the IIS redirector.
And we have found it pretty unsatisfactory that when the tomcat/java process
for
Hi Mel,
In my view, jasper is composed from at least 5 big components:
1. The jsp-java translator.
2. The java-class compiler
3. The Mangler ( managing name mappings )
4. Runtime - that should be completely independent of all other pieces,
since jasper-generated servlets should run without
This question should really be addressed to the TOMCAT-USER
list. TOMCAT-DEV is for discussions of the development of Tomcat itself.
On Sun, 25 Mar 2001, rajeev wrote:
Can someone confirm that request-time attribute values is not
implemented in the latest version of Jakarta?
Which version
--- Jestin Jean-Francois
[EMAIL PROTECTED] wrote:
here are 2 articles speaking about the pushlet
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet-2.html
here is a very simple sample pushlet :
{
public
Hello,
I'm attempting to use an alternative naming service with tomcat 4.x and
running into some difficulties.
This may be a result of my lack of understanding on how to go about this
but please read on...
I start tomcat 4 with both -nonaming and -Dcatalina.useNaming=false
added as parameters
- Original Message -
From: "T. Park" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 26, 2001 11:07 AM
Subject: How do I use a non-apache naming service with tomcat 4?
When tomcat starts up it fails in StandardContext with the reflection
error complaining about the
On Mon, 26 Mar 2001, Remy Maucherat wrote:
- Original Message -
From: "T. Park" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 26, 2001 11:07 AM
Subject: How do I use a non-apache naming service with tomcat 4?
When tomcat starts up it fails in StandardContext
craigmcc01/03/26 12:02:17
Modified:catalina/src/share/org/apache/catalina/connector
HttpRequestBase.java
Log:
Correct the implementation of HttpServletRequest.isUserInRole() so that it
properly respects role name aliases defined with security-role-ref.
craigmcc01/03/26 12:04:41
Modified:tester/src/bin tester.xml
tester/web/WEB-INF web.xml
Added: tester/src/tester/org/apache/tester Authentication03.java
Log:
Add a new unit test to validate correct behavior of isUserInRole() for
three circumstances:
*
Temporary(?) fix to stop crashes when creating a new Session in
embedded use of Jasper (i.e. as standalone JspServlet ). Problem may
occur in other situations as well, I'm not sure.
Problem: When
SimpleSessionStore.SimpleSessionManager.getNewSession() is called (as a
result of a
craigmcc01/03/26 12:50:48
Modified:webapps/examples/jsp/security/protected index.jsp
Log:
Explicitly identify the destination of the form submit, so that this page
works correctly when used in a form-based login environment.
Revision ChangesPath
1.2 +1 -1
Jan,
Henri Gomez is working on a patch to solve this very problem
as we speak --
he is setting it up so that the mod_jk plugin will detect that
TC has died,
and will attempt to open new connections.
Hopefully, that will be testable within a week or two...
-Dan
Just sent to list ;)
Henri (+ Larry),
Looks about ready for more general testing. I like the new
ajp13_operation. Two things:
1) l. 672 (op-recoverable = JK_FALSE).
I believe that should be outside of the if statement (i.e. immediately after
the connection_tcp_send_message). The whole thing becomes
Henri (+ Larry),
Looks about ready for more general testing. I like the new
ajp13_operation. Two things:
1) l. 672 (op-recoverable = JK_FALSE).
I'll check that.
I believe that should be outside of the if statement (i.e.
immediately after
the connection_tcp_send_message). The whole thing
I don't anticipate a TC3.3 Milestone 3 this week. Maybe
next week. I'm okay to commit it since there will some
time before TC 3.3 Beta 1. We can review then whether
it is working well enough to be kept for Beta 1.
Larry
-Original Message-
From: Dan Milstein [mailto:[EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 1:08 PM
To: [EMAIL PROTECTED]
Subject: Re: TC3.3 Proposal: Refactoring org.apache.jasper.servlet
Hi Mel,
In my view, jasper is composed from at least 5 big components:
1.
According to the STATUS.html(which doesn't seem to be up to date) no one seems
to have volunteered for the JDBC-Session store. If that is truly the case I
would like to volunteer for that part.
Thanks, Bip
Looks about ready for more general testing. I like the new
ajp13_operation. Two things:
1) l. 648 (op-recoverable = JK_FALSE).
I set op-recoverable to JK_FALSE just after
detected upload mode (dropped var)
Find included the latest .c since I miss diff cmd
under W2K rigth now.
Where
I have helped work on a fix for this on 4.0 (which supports the
javax.servlet.ServletRequest.setCharacterEncoding() method). Tomcat 3.x
does not support the new servlet 2.3 methods, so I did not look at fixing
it in Tomcat.
However, I have an easy to use object (included) which is able to
1. In general the Java SecurityManager implemenation in Tomcat 4
and Jasper has significant improvements and is much cleaner.
True. The SecurityManager in 3.3 is working fine for now ( Glenn is also
the main author for the 3.x sandboxing ), with all watchdog passing - but
a refactoring will
More info.
I pulled the routines I needed out of my 'big everything' jar file and
I can now get my jndi stuff to
work with tomcat4.
The problemi is that I still need to get the other stuff in that jar
file to play nice with tomcat.
but, for now, the problem looks to be in my camp.
Thanks for the
craigmcc01/03/26 16:04:23
Modified:catalina STATUS.html
Log:
Add Bip Thelin as a volunteer to work on the JDBC-based Store implementation.
Revision ChangesPath
1.5 +2 -2 jakarta-tomcat-4.0/catalina/STATUS.html
Index: STATUS.html
On Mon, 26 Mar 2001, Bip Thelin wrote:
According to the STATUS.html(which doesn't seem to be up to date) no one seems
to have volunteered for the JDBC-Session store. If that is truly the case I
would like to volunteer for that part.
Thanks, Bip
That is the case currently, so I
--- [EMAIL PROTECTED] wrote:
Temporary(?) fix to stop crashes when creating a
new Session in
embedded use of Jasper (i.e. as standalone
JspServlet ). Problem may
occur in other situations as well, I'm not sure.
I looked at that and I couldn't reproduce it - are
you sure you
However, this does point to the need for default
behavior of tomcat session generation code (or any
interceptor or module code) in the absence of expected
configuration info in server.xml.
That's a good point, but I'm wondering how could it be implemented.
The whole idea of modules is that
On Mon, 26 Mar 2001, Steve Downey wrote:
1. The jsp-java translator.
2. The java-class compiler
3. The Mangler ( managing name mappings )
4. Runtime - that should be completely independent of all
other pieces,
since jasper-generated servlets should run without jasper ( as
Guys,
I've isolated the cause of the problem down to the inclusion of the javax.naming
package in my 'big everything' jar.
If I remove the javax.naming package from the jar file, then all works well, if
not, we get that wierd 'signature' problem with createNamingContext.
(with or without
Guys,
I've isolated the cause of the problem down to the inclusion of the
javax.naming
package in my 'big everything' jar.
If I remove the javax.naming package from the jar file, then all works
well, if
not, we get that wierd 'signature' problem with createNamingContext.
(with or without
craigmcc01/03/26 17:54:20
Modified:catalina/docs/dev classloaders.html
catalina/src/share/org/apache/catalina/startup
Bootstrap.java
Log:
Rearrange the order in which repositories are added to each of the
standard class loader so that the
Hi Remy,
I'm running tomcat 4 beta 1.
I'll download tonight's latest build and see how I fare with that.
Thanks so much for the support!
-Thom
p.s. is there a b2 drop in the near future - I'm trying to focus my
integration efforts on the nearest milestone build.
Remy Maucherat wrote:
Thom,
From: "T. Park" [EMAIL PROTECTED]
Subject: Multi-byte character support.
Date: Mon, 26 Mar 2001 10:32:31 -0800
Message-ID: [EMAIL PROTECTED]
Tomcat 3.2[.1] doesn't seem to like static html pages (or servlets for
that matter) that offer multi-byte (non-latin) characters.
Tomcat 3.2.2b2
Hello,
I agree the idea of the pushlet is a bit confusing because it uses http (a non real
time protocol) to do pseudo real-time job,
but real-time is always more "hungry" than other technology (think about streaming !!
).
On the other hand having pseudo real-time monitoring over standard http
I agree the idea of the pushlet is a bit confusing because it
uses http (a non real time protocol) to do pseudo real-time job,
but real-time is always more "hungry" than other technology
(think about streaming !! ).
On the other hand having pseudo real-time monitoring over
standard http is
Here is the patch I'll commit if there is
no objection
jk_util.patch
51 matches
Mail list logo
