> The problem is that I have the same behaviour when I simply
> reload my page in
> the same Browser instance, jumping from one Tomcat instance
> to the other as if
> no javax.servlet.http.HttpSession was defined (jsessionid).
I haven't used JK2, but I know how this works with JK(1) and I think
> I've got JK2 running to connect IIS and Tomcat. Two issues
> bother me at the moment.
>
> 1. When JK2 is started the corresponding log file
> ($CATALINA_HOME/log/jk2.log in my case)
> is created. However, it's more or less empty (just a few
> cryptic characters) but still
> consumes 1024KB.
Baldur Norddahl wrote:
> We have a setup with multiple tomcat4 servers and a single apache2
> acting as a front for them.
Do you really need multiple tomcat instances running? Perhaps you could
have a single tomcat running multiple web applications?
If so, you can specify multiple Host elements
Mark Palmer wrote:
> I guessed as much. The thing is, I can see that the browser
> is just never
> getting the JSESSIONID cookies when accessing via Apache.
>
> If you access directly to Tomcat the JSESSIONID cookies come
> no problem.
>
> I just don't get it - this implies that mod_jk2 is str
Jose Euclides da Silva Junior wrote:
> if any servlet generate a cookie object ( during http connection,
> of course), so it will always store this cookie on the client
> side ( the user' browser) , which called the servlet
>( of course). Is it right? If yes, what happens if the browser
> doesn
Jake Robb writes:
> So, given that I haven't changed the root context definition,
> why doesn't my
> index.jsp page work? I moved the old stuff out, and put mine
> in, and Tomcat
> says it can't find the file.
I don't know. Have you tried starting from a working configuration, and
making minim
Jake Robb writes:
> Do I have to use the manager app to do something to set up my context, or
> can I just create the web.xml file? Do I even need a web.xml file if I'm
> not using a servlet?
I'm pretty sure you need a web.xml file for any web application.
> Does anyone out there have Tomcat 4.1
Hi Jake,
> Does this work when going to Tomcat directly (say to port 8080, if you've
> got a HTTP connector listening to that port) rather than going through a
> native web server? If you don't have an HTTP connector configured in
> Tomcat, you might want to add one to help in debugging the situa
i, if any? That section is also
blank.
If I could find this information anywhere, I'd be delighted to modify the
documentation and submit a patch. But I don't know how to find the
information online, and I'm currently too busy on other mat
/v2.0.
> 2/
>
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4
> .1.18/src/
>
>
> Regards,
>
>
> PQ
>
> "This Guy Thinks He Knows Everything"
> "This Guy Thinks He Knows What He Is Doing"
>
> -Original Mess
The jakarta-tomcat-connector source tarball is available in the same place
as the Tomcat tarball:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.18/src/
It does seem odd that the TC 4.1 releases are under jakarta-tomcat-4.0... I
guess it's just one of those mysteries.
Compiling
> > The notion of binding a Connection to a particular Thread using a
> > ThreadLocal is a pretty good idea.
> I do not agree.
Well, OK.
> > The big advantage to my mind is that you
> > can use the Connection from any level of the call tree
> without passing it
> > around as a parameter. What
Reynir Hübner asked:
> > Seems to me that this is the simple question of 'global
> > variables' or 'passing parameters' style of coding. The
> > 'global variables' approach seems some what less object
> > orientated in my opinion (Coming from a 4GL background where
> > I was haunted by global v
On this subject, PaulE wrote:
> Seems to me that this is the simple question of 'global variables' or
> 'passing parameters' style of coding. The 'global variables'
> approach seems some what less object orientated in my opinion (Coming
> from a 4GL background where I was haunted by global variab
> > If the connection is available for more than one request
> > depends on the way the container handles threads. If each
> > request is a new Thread you will win nothing.
> > Instead you will loose performace as each request
> > would create a new connection to the database.
>
> Yes that is t
Josh G wrote:
> Hi, I was wondering if there's a simple way to have one
> instance of tomcat
> run two different applications, each on the root of a
> different port? Ie I'd
> like to run a test application on 8080, and a development app
> on 8081 or
> some such, preferrably without two tomcat i
You can also modify $JTC/jk/native2/build.xml -- change
to
(of course if you're not using linux you should change a different one of
the linkOpt elements. Or change them all, that works too.)
Cheers,
-bn
> -Original Message-
> From: Dom [mailto:dombat@;free.fr]
> Sent: Wednesday
Denis Haskin wrote:
>
> We found that we had to do 2 things:
>
> 1) Make sure that mod_jk was loaded into Apache *before* mod_rewrite,
> which meant moving the loading of mod_jk from mod_jk.conf to Apache's
> httpd.conf, and we listed it in the LoadModule and AddModule lists
> *before* mod_rewri
ase as yet.
Cheers,
Brett Neumeier
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
19 matches
Mail list logo
