Thomas wrote:
On 09/06/2014 01:41, Fred Toth wrote:
Hi Dan,
Yes, the rest of the log is correct, and yes, I am certain I have an
active session (I can see the cookie in my browser).
Then something is messed up in your configuration. I've just checked
this works and it does. You'll need to provide
I've been going down this trail.
Thanks again,
Fred
On 6/9/2014 1:03 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Fred,
On 6/9/14, 10:59 AM, Fred Toth wrote:
I'm confused. I thought (apparently mistakenly) that there was
always a session, but I must be wrong
Hi,
This feature is in the doc since at least tomcat 5. I'm using tomcat
7.0.47 and I just tried to add the user session id to the access log by
adding %S to the pattern attribute. However, it's not working. All I'm
getting is - in the log.
Is there some trick to this? I haven't found
Hi Dan,
Yes, the rest of the log is correct, and yes, I am certain I have an
active session (I can see the cookie in my browser).
Thanks,
Fred
On 6/8/2014 4:30 PM, Daniel Mikusa wrote:
On Jun 8, 2014 4:01 PM, Fred Toth ft...@synernet.com wrote:
Hi,
This feature is in the doc since
On 11/13/2012 2:57 AM, Konstantin Kolinko wrote:
It looks like it overrides the default mapping of this servlet. If I
add the above fragment to web.xml of the docs application, I get 404
in Tomcat 7, while in Tomcat 6 it works.
If I replace above with the following, it works in Tomcat 7:
, Fred Toth wrote:
Context docBase=/mnt/data_arch/DATA
Is your application mounted on an NFS share?
p
(hint: don't do that.)
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail
thread after I dig some more.
Thanks,
Fred
On 11/12/2012 2:27 PM, Fred Toth wrote:
Hi,
Sorry, just getting back to this after a delay.
I've added an AccessValve to my context and it, too, reports 404. So
this is more confirmation that my context has actually deployed (as
the logs report
On 11/12/2012 4:24 PM, Konstantin Kolinko wrote:
2012/11/13 Fred Toth ft...@synernet.com:
Hello again,
I've found my problem, sort of.
In this particular application, ever since tomcat 5, we've been remapping
the DefaultServlet url-pattern. Works fine in 5 and 6, but not in 7. Which
means
Hi,
I've got a struts2/spring app that's been running under tomcat 6 with no
problems.
I migrated it to 7 and I've hit a strange brick wall. On startup, the
logs show the app deploying, absolutely normally with no errors at all.
However, when I try to hit any URL within the app's context,
: Starting ProtocolHandler [ajp-bio-8009]
Nov 2, 2012 2:31:05 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7487 ms
On 11/2/2012 3:44 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred,
On 11/2/12 3:27 PM, Fred Toth wrote:
I've got a struts2
Hi all,
I had problems trying to get tomcat to forward to a struts2 action
from an error-page directive in web.xml. I was all set to run to
the list for help when I figured it out. I thought I'd post this anyway
in case it helps someone else.
I had error-page working in the simplest sense. If I
Hi all,
I'm lost in the woods.
Some time ago we built an application that required us to extend
the TC 5.5 DefaultServlet. All we did was point it to an external path
(outside the war file). It works great.
However, I now realize that I've somehow broken the welcome-file
mechanism for our
12 matches
Mail list logo
