date:20081106

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

To whom it may concern,

keeplearning wrote:
 I am relatively new to Tomcat. I was looking at thread dumps which we took
 from Tomcat and I see lots of thread names. Now, I am not sure which
one is
 important to look at.
 Some of threads I see are as follows:

 http-8080-Processor15

These are the HTTP request processing threads running on port 8080. If
you also have a connector configured for HTTP to listen on, say, port
8090, then you'll have a set of threads called http-8090-ProcessorABC
where ABC is the thread number. You will see a whole bunch of these
threads, since Tomcat will start at most maxThreads (defined on the
Connector element in server.xml) threads. The default (for Tomcat 6.0)
is 40 threads max.

 TP-Processor1

Oddly enough, these are also request processing threads, but these are
for the AJP connector. I'm not sure why the AJP connector doesn't name
its threads similar to the HTTP ones (like ajp-8009-Processor1 or
something like that), but that's the case.

 WorkerThread(receive_transaction_complete_stage,0)

I have no idea what this might be. Check the stack trace to see what
it's doing, and that may give you your answer.

 Timer-4

This looks like it's a timer, probably from your application using the
JDK's TimerTask classes. See Sun's javadoc for java.util.Timer. I don't
believe Tomcat uses this internally.

 message-bus-1

I don't believe this is Tomcat-related.

Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTSkUACgkQ9CaO5/Lv0PD3ugCgob9RzV9u+8gZDFGaj1Gt3ocd
MK4AoKdGvFSqaoOEQGj0tGXB+fh+WpbB
=5oHo
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a cookie question of one Server with two tomcat server

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bon,

Bon wrote:
 In my environment there are two tomcat server runing with different 
 port in one server , and both two must set its own cookies into 
 client

Are you talking about JSESSIONID cookies, or some other ones?

 now, when I open a browser and browe both site and I can find two
 site write their own cookie into my computer, but when I logout from
 both two sites

How do you logout from these sites?

 (they will expire their own cookies)

How do they expire their cookies?

 with same browser, but the cookies of on site did not be removed,
 does anyone know what is it going on? and how can I solve this
 problem?

Are you observing the cookies being re-sent to the server after they
should have been expired, or are you seeing them listed in your
browser's active cookie list?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTS5oACgkQ9CaO5/Lv0PCbMQCdHj/qRoGswA1/gOf1FE4ULb/m
A5sAn1jPlSAVxOR9PPYRIGMoqWZ/+zOe
=/EoB
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Is it possible to hide tomcat resource from outside?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

einojah,

einojah wrote:
 I have an admin area in my application I want to secure. 
 I know I can define a security constraint to set a basic or digest
 authentication for a url pattern. 
 
 But, I don't want the /admin area to be shown outside at all.

What do you want the behavior to be when someone tries to access an
/admin URL from the outside?

 The basic
 authentication is extremely weak and digest auth. also doesn't provide
 enough security. 

Why won't digest auth provide enough security for you? Have you
considered form-based auth over SSL?

 Is it possible to hide an url pattern on the outside, but have it
 available when accessing from the server machine? 

There are ways to do this, but the best way depends on what you want to
actually happen when someone requests a URL from /admin. So, let me know
and I'll make a recommendation.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTSvIACgkQ9CaO5/Lv0PAc+gCfUEzxdRxYPsQ245n5HrmbBDuG
l8wAmwbmVsWda69cTUk3rTDitN0a6rrT
=ZFg4
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 6.0.19 when?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Søren,

[EMAIL PROTECTED] wrote:
 Do anyone know when Tomcat 6.0.19 will be released?
 
 I''m working on a enterprise project, where i need to change the 
 SessionName on my tomcat server (6.0.18).

Do you mean the name of the JSESSIONID cookie? That's what it sounds
like given the bug referenced below.

 I'we been looking on the bugbase for Tomcat 6, and according to this bug: 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=42419,
 it will be fixed in release 6.0.19.

I don't see any indication on that bug report that it

a) has been fixed
b) fix will be included for 6.0.19

This bug is over a year old, but it's good to see that there is renewed
interest in it. According to Mark Thomas, another patch is in the works
(no word on where one can take a look at it), but it is targeted at TC
5.5, not 6.0.

 Are there other possibilites to change the SessionName in the earlier 
 Tomcat versions, or do i have to wait for 6.0.19?

You may have to wait longer than that.

Unfortunately, this particular issue is unlikely to be fixed quickly,
because any solution results in a proprietary solution that violates the
servlet specification (the servlet spec mandates the name of the cookie,
which is why it's hard-coded).

 And last but not least - when will Tomcat 6.0.19 be released?

They generally come when the come. If you're interested in getting the
next release out more quickly, perhaps you could volunteer to fix some bugs?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTTeMACgkQ9CaO5/Lv0PA/CwCgwoiCc19zFYsEbl8UbAhhh+Nl
BMQAmwTF+SBrtOfbJa2PWHg5Gwg7GO5d
=hpkJ
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Convenient web application configuration.

2008-11-06 Thread Jason Cipriani

My end solution ended up being to modify
$CATALINA_ROOT/conf/context.xml and put the JNDI data source
definition there. While I agree that modifying global server files is
less than ideal it is by far the simplest solution: It's only one
resource element that has to be added, it requires no modification to
deployment scripts, and solves the problem of site-specific data
source.

I left non site-specific servlet context configuration in each
servlet's web.xml.

Then, I moved site-specific servlet context parameters into the
database. This ended up working out really nicely for a number of
reasons.

Everything is much more convenient now. Thanks for all your advice.

Jason


On Tue, Nov 4, 2008 at 5:15 PM, Christopher Schultz
[EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Jason,

 Jason Cipriani wrote:
 I'm developing with Eclipse but could configure custom build steps
 with ant. This solution would remove most of the inconvenience, but I
 would still have to make 4 separate WARs available for distribution.
 Not *too* big of a deal but I'd rather just distribute a single
 archive.

 If you need a different web.xml file for each machine, they you will, by
 definition, require a different WAR for each machine. There's really
 nothing you can do about that.

 Another option would be to configure your application using something
 other than web.xml but then you've just moved the problem to another
 file.

 We use a file in the user's home directory (called .ant.properties) that
 includes machine-specific environmental information. To deploy, we grab
 the source from CVS and run ant install which does everything,
 including merging the machine-specific configuration into the WAR and
 deploying it. We have a small number of production machines, so this
 isn't a big deal for us. If we had a large number, we'd just further
 script the process by allowing the WAR creation to be parameterized by,
 say, command-line switches (which they really are, since you can define
 any ant property right on the command-line).

 Hope that helps,
 - -chris

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkkQyYEACgkQ9CaO5/Lv0PBzXQCdH4lqz0vHbGOChbEJIihowz50
 2lsAoK6obiLTx09nSb7+8taZxxITlpjM
 =GAv3
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 6.0.19 when?

Christopher Schultz schrieb:
 Søren,
 
 [EMAIL PROTECTED] wrote:
 Do anyone know when Tomcat 6.0.19 will be released?
 
 I''m working on a enterprise project, where i need to change the 
 SessionName on my tomcat server (6.0.18).
 
 Do you mean the name of the JSESSIONID cookie? That's what it sounds
 like given the bug referenced below.
 
 I'we been looking on the bugbase for Tomcat 6, and according to this bug: 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=42419,
 it will be fixed in release 6.0.19.
 
 I don't see any indication on that bug report that it
 
 a) has been fixed
 b) fix will be included for 6.0.19

I think he is actually talking about

https://issues.apache.org/bugzilla/show_bug.cgi?id=45951

which will be part of 6.0.19.

Regards,

Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Convenient web application configuration.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jason,

Jason Cipriani wrote:
 My end solution ended up being to modify
 $CATALINA_ROOT/conf/context.xml and put the JNDI data source
 definition there.

Yikes! You should /definitely/ not do that. Doing so will make that JNDI
data source available (separately, I might add) to all deployed
applications. You'd be better off putting it in server.xml, since nobody
really ever looks for anything in the server-wide context.xml. I believe
you will be adding confusion at the least and a management nightmare at
the worst.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTbmgACgkQ9CaO5/Lv0PBg4gCgpjHTTBCbQDvesDsgYh7ork8i
11YAn2d/Hx2erPtBGBdxrkVjLwAY97Wr
=4mqt
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Convenient web application configuration.

2008-11-06 Thread Jason Cipriani

Hmm, well, there are no other web applications, the server is
dedicated to this one. If there *were* other web applications, they
would likely be using the same data source anyways -- and in that case
it's certainly handy to be able to set the data source for multiple
web apps by maintaining just a single entry in one of Tomcat's
configuration files. Also, for now, I did name the resource something
unique to the web application, I'm not worried about conflicts. As for
management, simple instructions insert this into context.xml on new
server setup seems to be working out well.

I can't think of any way that's more convenient. IMHO, if the choice
is writing custom deployment scripts and having to maintain and run
those to deploy the web app (and centrally maintaining separate copies
of configuration files so they can be distributed with the deployment
scripts rather than letting other developers maintain their own), and
describe to other developers how those work vs. adding an entry to
context.xml once and using Tomcat manager to deploy things, it seems
that the former ends up being more confusing and hard to manage.

To be honest I can't think of a single compelling reason not to do it
this way, or any reason at all other than the fact that I have to
explain to developers that when setting up a new system, they must
modify Tomcat configuration files, and I don't see that as a big deal.
I could be missing something, but everything is working great and is
incredibly easy to manage now that I've made this change. That seems
positive.

Jason


On Thu, Nov 6, 2008 at 5:23 PM, Christopher Schultz
[EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Jason,

 Jason Cipriani wrote:
 My end solution ended up being to modify
 $CATALINA_ROOT/conf/context.xml and put the JNDI data source
 definition there.

 Yikes! You should /definitely/ not do that. Doing so will make that JNDI
 data source available (separately, I might add) to all deployed
 applications. You'd be better off putting it in server.xml, since nobody
 really ever looks for anything in the server-wide context.xml. I believe
 you will be adding confusion at the least and a management nightmare at
 the worst.

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkkTbmgACgkQ9CaO5/Lv0PBg4gCgpjHTTBCbQDvesDsgYh7ork8i
 11YAn2d/Hx2erPtBGBdxrkVjLwAY97Wr
 =4mqt
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

ISAPI_REDIRECT issue

2008-11-06 Thread Paul Pree

Hi All

Apologies in advance if I'm not getting this right - I'm a newbie to the
list.

I have an issue using ISAPI_REDIRECT through IIS to Tomcat.

For most Windows users the redirection works fine, but for users with
large group memberships (approx 70+) they are not redirected and nothing
is logged in the ISAPI log.

I've been working with Microsoft and from the IIS side all appears well.

They believe it is an HTTP Header size issue.

 

Environment:

Windows 2003 32 bit

Tomcat 5.5.25

Java JDK 1.5.0_16

ISAPI Redirect v 1.2.26 (Precompiled DLL for win32)

I believe that the HTTP header is fixed at 8k. Can anyone give me a tip
on how this can be increased? I've seen reference to it being possible,
but just not how. Is it a parameter I set in Tomcat on the 8009
connector? Is it something I can set in the uri properties file (I think
not)? Do I need to download the source and adjust it in there and build
my own DLL?

 

Any tips gratefully received!!!

Thanks

Paul

Re: ISAPI_REDIRECT issue

Paul Pree schrieb:
 Hi All
 
 Apologies in advance if I'm not getting this right - I'm a newbie to the
 list.
 
 I have an issue using ISAPI_REDIRECT through IIS to Tomcat.
 
 For most Windows users the redirection works fine, but for users with
 large group memberships (approx 70+) they are not redirected and nothing
 is logged in the ISAPI log.
 
 I've been working with Microsoft and from the IIS side all appears well.
 
 They believe it is an HTTP Header size issue.
 
  
 
 Environment:
 
 Windows 2003 32 bit
 
 Tomcat 5.5.25
 
 Java JDK 1.5.0_16
 
 ISAPI Redirect v 1.2.26 (Precompiled DLL for win32)
 
 I believe that the HTTP header is fixed at 8k. Can anyone give me a tip
 on how this can be increased? I've seen reference to it being possible,
 but just not how. Is it a parameter I set in Tomcat on the 8009
 connector? Is it something I can set in the uri properties file (I think
 not)? Do I need to download the source and adjust it in there and build
 my own DLL?

First we should check, whether it is really a header size issue. We
should be able to verify that by logging a failing request done by one
of those users with log_level trace. Please do not log a lot of
requests, because trace log level produces very much output. Especially
it logs the packets which get send to the backend, so we can see,
whether the headers are to big.

I hope you have a system, where you can do such a test?

Regards,

Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: ISAPI_REDIRECT issue

2008-11-06 Thread Paul Pree

Thanks Rainer
I've attached a log recorded during one of these failing connects for
TestUser. We stopped IIS, set logging to trace, cleared the log, started
IIS, attempted one connect, then stopped.

Unfortunately I don't have direct access to the failing site, but have
been trying to resolve this for some time now so hopefully have already
collected anything that might assist in pinpointing the problem.
Note that we copied the Windows account of a failing user, then started
stripping Windows groups. The starting point was over 150 groups. When
that user was dropped to 69 it started working. Adding back another
group brought back the failure. Other users with up to 90 groups could
connect, but some with 50 could not. Group complexity (maybe even name
length) definitely has an impact so it's not necessarily 'death at 70'
but each test users has a working number that fails with the addition of
one.
Regards
Paul 
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED] 
Sent: Friday, 7 November 2008 9:46 AM
To: Tomcat Users List
Subject: Re: ISAPI_REDIRECT issue

Paul Pree schrieb:
 Hi All
 
 Apologies in advance if I'm not getting this right - I'm a newbie to
the
 list.
 
 I have an issue using ISAPI_REDIRECT through IIS to Tomcat.
 
 For most Windows users the redirection works fine, but for users with
 large group memberships (approx 70+) they are not redirected and
nothing
 is logged in the ISAPI log.
 
 I've been working with Microsoft and from the IIS side all appears
well.
 
 They believe it is an HTTP Header size issue.
 
  
 
 Environment:
 
 Windows 2003 32 bit
 
 Tomcat 5.5.25
 
 Java JDK 1.5.0_16
 
 ISAPI Redirect v 1.2.26 (Precompiled DLL for win32)
 
 I believe that the HTTP header is fixed at 8k. Can anyone give me a
tip
 on how this can be increased? I've seen reference to it being
possible,
 but just not how. Is it a parameter I set in Tomcat on the 8009
 connector? Is it something I can set in the uri properties file (I
think
 not)? Do I need to download the source and adjust it in there and
build
 my own DLL?

First we should check, whether it is really a header size issue. We
should be able to verify that by logging a failing request done by one
of those users with log_level trace. Please do not log a lot of
requests, because trace log level produces very much output. Especially
it logs the packets which get send to the backend, so we can see,
whether the headers are to big.

I hope you have a system, where you can do such a test?

Regards,

Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a cookie question of one Server with two tomcat server

Hi Christopher,

I'm not sure what's difference of JSESSIONID cookies and
javax.servlet.http.Cookie,
I think they are the same thing right? or some other difference details
what I don't know.

when a client user click logout link from the main site web page,
the logout link is main site's logout Servlet URL, and the logout
Servlet will do something as following:
1. set the cookies maxAge to 0 and add them into response again.
cookie.setMaxAge(0);
response.addCookie(cookie);
2. set the session to invalidate
request.getSession().invalidate();
3. response.sendRedirect(redirectTo); redirectTo is the URL of second
site's logout link.
then the client browser will redirect to second site's logout URL, and
it is a Struts Action,
and this logout Action will do something as following:
1. set the session to invalidate
2. set the cookie maxAge to 0 and add them into response again.
cookies[i].setMaxAge(0);
response.addCookie(cookies[i]);
3. forward to a logout default display page.
4. direct to main site some page by form submit in default logout
display page.

then done this logout process,
and I found the cookie of main site was be removed but the second site
did not!
when I use the same browser instance to visit second site's logout, and
the cookies
of second site still did not be removed! but, if I open a new browser
and to visit
the second site's logout then the cookies of second could be removed!

I need give user a single link to finish the main and second site's
logout,
so I try to do what I did, but it did not work like what I want!
do I do something wrong and can you give me some idea to do that or some
other
useful information.

Thank you for your help~
Bon

Christopher Schultz-2 wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bon,

Bon wrote:
In my environment there are two tomcat server runing with different
port in one server , and both two must set its own cookies into
client

Are you talking about JSESSIONID cookies, or some other ones?

now, when I open a browser and browe both site and I can find two
site write their own cookie into my computer, but when I logout from
both two sites

How do you logout from these sites?

(they will expire their own cookies)

How do they expire their cookies?

with same browser, but the cookies of on site did not be removed,
does anyone know what is it going on? and how can I solve this
problem?

Are you observing the cookies being re-sent to the server after they
should have been expired, or are you seeing them listed in your
browser's active cookie list?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTS5oACgkQ9CaO5/Lv0PCbMQCdHj/qRoGswA1/gOf1FE4ULb/m
A5sAn1jPlSAVxOR9PPYRIGMoqWZ/+zOe
=/EoB
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
View this message in context:
http://www.nabble.com/a-cookie-question-of-one-Server-with-two-tomcat-server-tp20355052p20373498.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ISAPI_REDIRECT issue

The attachment did not make it through. If it is to big for this list,
you can send to me directly, but we should keep the discussion on the list.

Regards,

Rainer

Paul Pree schrieb:
 Thanks Rainer
 I've attached a log recorded during one of these failing connects for
 TestUser. We stopped IIS, set logging to trace, cleared the log, started
 IIS, attempted one connect, then stopped.
 
 Unfortunately I don't have direct access to the failing site, but have
 been trying to resolve this for some time now so hopefully have already
 collected anything that might assist in pinpointing the problem.
 Note that we copied the Windows account of a failing user, then started
 stripping Windows groups. The starting point was over 150 groups. When
 that user was dropped to 69 it started working. Adding back another
 group brought back the failure. Other users with up to 90 groups could
 connect, but some with 50 could not. Group complexity (maybe even name
 length) definitely has an impact so it's not necessarily 'death at 70'
 but each test users has a working number that fails with the addition of
 one.
 Regards
 Paul 
 -Original Message-
 From: Rainer Jung [mailto:[EMAIL PROTECTED] 
 Sent: Friday, 7 November 2008 9:46 AM
 To: Tomcat Users List
 Subject: Re: ISAPI_REDIRECT issue
 
 Paul Pree schrieb:
 Hi All

 Apologies in advance if I'm not getting this right - I'm a newbie to
 the
 list.

 I have an issue using ISAPI_REDIRECT through IIS to Tomcat.

 For most Windows users the redirection works fine, but for users with
 large group memberships (approx 70+) they are not redirected and
 nothing
 is logged in the ISAPI log.

 I've been working with Microsoft and from the IIS side all appears
 well.
 They believe it is an HTTP Header size issue.

  

 Environment:

 Windows 2003 32 bit

 Tomcat 5.5.25

 Java JDK 1.5.0_16

 ISAPI Redirect v 1.2.26 (Precompiled DLL for win32)

 I believe that the HTTP header is fixed at 8k. Can anyone give me a
 tip
 on how this can be increased? I've seen reference to it being
 possible,
 but just not how. Is it a parameter I set in Tomcat on the 8009
 connector? Is it something I can set in the uri properties file (I
 think
 not)? Do I need to download the source and adjust it in there and
 build
 my own DLL?
 
 First we should check, whether it is really a header size issue. We
 should be able to verify that by logging a failing request done by one
 of those users with log_level trace. Please do not log a lot of
 requests, because trace log level produces very much output. Especially
 it logs the packets which get send to the backend, so we can see,
 whether the headers are to big.
 
 I hope you have a system, where you can do such a test?
 
 Regards,
 
 Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ISAPI_REDIRECT issue

Paul Pree schrieb:
 Thanks Rainer
 I've attached a log recorded during one of these failing connects for
 TestUser. We stopped IIS, set logging to trace, cleared the log, started
 IIS, attempted one connect, then stopped.
 
 Unfortunately I don't have direct access to the failing site, but have
 been trying to resolve this for some time now so hopefully have already
 collected anything that might assist in pinpointing the problem.
 Note that we copied the Windows account of a failing user, then started
 stripping Windows groups. The starting point was over 150 groups. When
 that user was dropped to 69 it started working. Adding back another
 group brought back the failure. Other users with up to 90 groups could
 connect, but some with 50 could not. Group complexity (maybe even name
 length) definitely has an impact so it's not necessarily 'death at 70'
 but each test users has a working number that fails with the addition of
 one.

Yes, it looks like a header size problem.

Look at the description of max_packet_size on

http://tomcat.apache.org/connectors-doc/reference/workers.html

You can set it to some bigger value than the default. We don't know
though, how much you actually need (try and error). Be careful to also
adjust the Connector in server.xml as described in the docs page.

Remark: your isapi redirector is version 1.2.25 (that's what the log
file says). I would recommend updating to 1.2.26, or even 1.2.27 (though
that version was just released on Monday).

Let us know, if max_packet_size plus packetSize fixes your problem.

Regards,

Rainer


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

migrating from Tomcat 5.5.x to Tomcat 6.0.x

2008-11-06 Thread rajesh202023


Hi,

I want to replace Tomcat 5.5.x running in my system with Tomcat 6.0.x. I
want to do this in a manner such that the applications that are running on
Tomcat 5 do not need to be modified in any manner to run on Tomcat 6.
I have gone through the Tomcat homepage and noticed that there are some
difference in the directory structure and some other stuff, between the
6.0.x and 5.5.x release.

I want to know what all and where should I change after I install Tomcat 6,
so that I am able to run the existant applications without any issues.

Please help, as I am new to Tomcat in general.

Thanks in advance...

Raj
-- 
View this message in context: 
http://www.nabble.com/migrating-from-Tomcat-5.5.x-to-Tomcat-6.0.x-tp20374253p20374253.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Where to get the exact source code of tomcat6.exe and tomcat6w.exe

2008-11-06 Thread Bill Barker


Jack Cai [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Hi,

 I see that tomcat6.exe and tomcat6w.exe is precompiled and is presented as
 is in Tomcat source code tree. Where can I find the exact source code for
 this two EXE? I'm aware of the Apache Commons procrun project, but I'm not
 sure whether tomcat6.exe and tomcat6w.exe are created from the latest
 procrun source code. And modification required?

 I appreciate if someone can shed some light on this. Thanks!


Pretty much all of the procrun developers are also Tomcat developers.  As a 
result, the latest version of tomcat6?.exe should be from the source of the 
latest version of Commons-Daemon procrun.

 -Jack Cai
 




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a cookie question of one Server with two tomcat server

2008-11-06 Thread Caldarale, Charles R

 From: Bon [mailto:[EMAIL PROTECTED]
 Subject: Re: a cookie question of one Server with two tomcat server

 I'm not sure what's difference of JSESSIONID cookies and
 javax.servlet.http.Cookie,

JSESSIONID is the specific cookie called out by the servlet spec to be used for 
tracking sessions between client and server.  Instances of 
javx.servlet.http.Cookie can be any cookie you care to use, not just 
JSESSIONID.  The servlet container (Tomcat, for our purposes) is responsible 
for managing JSESSIONID, but a webapp can return any number of cookies to the 
client for whatever purpose it chooses.

 1. set the cookies maxAge to 0

What cookie are your referring to?  JSESSIONID or one of your own?

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SSL setup help

2008-11-06 Thread Bill Barker

The entry 
keystoreFile=${/usr/local/jre1.6.0_06/bin/keystore.key}/.keystore is 
almost certainly wrong.  For this to work, you would have to start Tomcat 
with the weird 
entry -D/usr/local/jre1.6.0_06/bin/keystore.key=/path/to/my/keystore/keys.
Tomcat does variable substitution when parsing the various config xml files 
based on System properties when it sees something like ${variable}. (This is 
a Tomcat-specific feature, so you can't count on porting it to another 
container).

Michael A. Tucker [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I'm trying to setup SSL on a web app that I have running on a server.  I
 created my keystore.key file and then uncommented this section in my
 server.xml file:

 Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true
maxThreads=150 scheme=https secure=true
 
 keystoreFile=${/usr/local/jre1.6.0_06/bin/keystore.key}/.keystore 
 keystorePass=changeit
clientAuth=false sslProtocol=TLS

 Now when I go to https://localhost:8443/ I get failed to connect page
 load error.  I think I'm not doing something wrong in the server.xml
 file, but I'm not sure what.  I already have another program running on
 443 so could that interfere?  I also don't know what APR means in the
 SSL doc.
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.6 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iD8DBQFJEbv2iSj9VAB3NO8RAkyLAJ0ZhVqiOz0cKuZILoYMYQTjojD8awCfXjHY
 pI7vAxr3JZan3Mq87uzrhMU=
 =8iED
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a cookie question of one Server with two tomcat server

Hi Caldarale

I just set my own cookies's maxAge to 0, if I also set the JSESSIONID to
0 maybe could be solve my problem right? I'll try it.

thank you for your answer.
Bon

Caldarale, Charles R wrote:

From: Bon [mailto:[EMAIL PROTECTED]
Subject: Re: a cookie question of one Server with two tomcat server

I'm not sure what's difference of JSESSIONID cookies and
javax.servlet.http.Cookie,

JSESSIONID is the specific cookie called out by the servlet spec to be
used for tracking sessions between client and server. Instances of
javx.servlet.http.Cookie can be any cookie you care to use, not just
JSESSIONID. The servlet container (Tomcat, for our purposes) is
responsible for managing JSESSIONID, but a webapp can return any number of
cookies to the client for whatever purpose it chooses.

1. set the cookies maxAge to 0

What cookie are your referring to? JSESSIONID or one of your own?

- Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
View this message in context:
http://www.nabble.com/a-cookie-question-of-one-Server-with-two-tomcat-server-tp20355052p20374522.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Deployment Web App on Debian

2008-11-06 Thread Zaki Akhmad

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hello all,

I am having difficulty while deploying my web application on Debian.
FYI, I am using Debian Testing.

Before I deploy on Debian, I had successfully deployed on Windows. I
just copy one folder of my web application folder to
C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\mywebapp

Do some little configuration, restart the tomcat, voila! It works on
http://localhost:8080/mywebapp

But how do I do it on Debian GNU/Linux?

- --
Zaki Akhmad


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkkTwjIACgkQT4k8JfIMt5fw5ACeMZQXkW0RUQXSOV4hqwhzQc+P
fpgAnje/rgMHC/f1vPfDjnkWrsrV1HFF
=hbKI
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a cookie question of one Server with two tomcat server

Hi Caldarale,

I'm so naive.
I've try to set the JSESSIONID's max-age to 0, and my second site still
did not expire its own cookie
from client.
I guess that is a issue about client or because I can check the second
site's cookie from Server side
and logging each cookie's value to make sure what cookie I've set
max-age to 0, but the cookies in
client also stay here...

does anybody can give me some idea, some information, and what should I
do right now :-((

best regards,
Bon

Bon wrote:

Hi Caldarale

I just set my own cookies's maxAge to 0, if I also set the JSESSIONID
to 0 maybe could be solve my problem right? I'll try it.

thank you for your answer.
Bon

Caldarale, Charles R wrote:

From: Bon [mailto:[EMAIL PROTECTED]
Subject: Re: a cookie question of one Server with two tomcat server

I'm not sure what's difference of JSESSIONID cookies and
javax.servlet.http.Cookie,

JSESSIONID is the specific cookie called out by the servlet spec to be
used for tracking sessions between client and server. Instances of
javx.servlet.http.Cookie can be any cookie you care to use, not just
JSESSIONID. The servlet container (Tomcat, for our purposes) is
responsible for managing JSESSIONID, but a webapp can return any number
of cookies to the client for whatever purpose it chooses.

1. set the cookies maxAge to 0

What cookie are your referring to? JSESSIONID or one of your own?

- Chuck

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
View this message in context:
http://www.nabble.com/a-cookie-question-of-one-Server-with-two-tomcat-server-tp20355052p20375287.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Problem]Tomcat 6.x with Active Directory on Windows Server 2003

2008-11-06 Thread Vickey


I am trying to authenticate web users with Active Directory on Windows Server
2003 R2 with sp2 and tomcat 6.18, but get an HTTP Status 403 - Access to
the requested resource has been denied error, don't know why, my steps and
configuration as below and post as attachment:

1. create test group and user in Active Directory:
domain name: test
domain controller host: 172.20.2.13
TestGroup: a global security group
testuser1, tomcat: member of TestGroup
screen capture is available in attachment

2. ${catalina.home}/conf/server.xml: 

Server ..
..
Engine name=Catalina defaultHost=localhost
  !-- have to comment this out to use ldap authentication realm
  Realm className=org.apache.catalina.realm.UserDatabaseRealm
resourceName=UserDatabase/
  --
  
  !--I have also tried to put the ldap realm here, but not work
yet--  

  Host name=localhost  appBase=webapps
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false

   !--ad integration--
   !--the servers are all in my local network, can't access them
from internet--   
   Realm 
className=org.apache.catalina.realm.JNDIRealm 
debug=99
connectionURL=ldap://172.20.2.13:389;
connectionName=[EMAIL PROTECTED]
connectionPassword=tomcat1
authentication=simple
referrals=follow
userRoleName=member
userBase=DC=test
userSearch=(sAMAccountName={0})
userSubtree=true
roleBase=DC=test
roleName=TestGroup
roleSubtree=true
roleSearch=(member={0})
/

  /Host   
/Engine
..
/Server http://www.nabble.com/file/p20375746/ad.jpg 

3. create test web application, and modify the web.xml:
web-app xmlns=http://java.sun.com/xml/ns/javaee;
   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;
   version=2.5

  display-namead test/display-name
  descriptionad test/description

  !--ad integration-- 
  security-constraint
   web-resource-collection
   web-resource-nameAuthenticated area/web-resource-name
   url-pattern/session.jsp/url-pattern
   url-pattern*.xml/url-pattern
   !--more url patterns and http methods here--
   http-methodDELETE/http-method
   http-methodGET/http-method
   http-methodHEAD/http-method
   http-methodPOST/http-method
   http-methodPUT/http-method
   /web-resource-collection

   !--more web resource collection nodes here--
   auth-constraint
   role-nameTestGroup/role-name
   !--more role name nodes here--
   /auth-constraint
   
   /security-constraint

   login-config
  auth-methodFORM/auth-method
  role-nameTestGroup/role-name
  form-login-config
   form-login-page/login.jsp/form-login-page
  form-error-page/error.jsp/form-error-page
  /form-login-config
/login-config

security-role
descriptionad test group/description
role-nameTestGroup/role-name
/security-role

!--I have also try another login method
login-config  
  auth-methodBASIC/auth-method
/login-config
--
/web-app

4. problem description: 
when resources in Authenticated area defined above are accessed, login.jsp
will appear, if wrong username/password is entered, error.jsp will appear,
but after correct user/password is entered, I can still get error message as
below:

HTTP Status 403 - Access to the requested resource has been denied



type Status report

message Access to the requested resource has been denied

description Access to the specified resource (Access to the requested
resource has been denied) has been forbidden.




Apache Tomcat/6.0.18 

no exception or error is thrown in the console

5. after log4j is configured to debug on tomcat, errors are found in the
debug log:
 DEBUG http-8080-1 org.apache.catalina.authenticator.AuthenticatorBase - 
Failed authenticate() test
 DEBUG http-8080-1 org.apache.catalina.authenticator.AuthenticatorBase - 
Failed authenticate() test
..

 DEBUG http-8080-1 org.apache.catalina.authenticator.FormAuthenticator -
Authenticating username 'testuser1'
 DEBUG http-8080-1 org.apache.catalina.authenticator.FormAuthenticator -
Authenticating username 'testuser1'
 DEBUG http-8080-1 org.apache.catalina.authenticator.FormAuthenticator -
Authentication of 'testuser1' was successful
 DEBUG http-8080-1 org.apache.catalina.authenticator.FormAuthenticator -
Authentication of 'testuser1' was successful
 DEBUG http-8080-1

Vedr.: Re: Tomcat 6.0.19 when?

2008-11-06 Thread sje

Hi Rainer!


Yes! That's correct - i referenced the wrong bugnumber :)





Rainer Jung [EMAIL PROTECTED] 
06-11-2008 21:16
Besvar venligst til
Tomcat Users List users@tomcat.apache.org


Til
Tomcat Users List users@tomcat.apache.org
cc

Emne
Re: Tomcat 6.0.19 when?






Christopher Schultz schrieb:
 Søren,
 
 [EMAIL PROTECTED] wrote:
 Do anyone know when Tomcat 6.0.19 will be released?
 
 I''m working on a enterprise project, where i need to change the 
 SessionName on my tomcat server (6.0.18).
 
 Do you mean the name of the JSESSIONID cookie? That's what it sounds
 like given the bug referenced below.
 
 I'we been looking on the bugbase for Tomcat 6, and according to this 
bug: 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=42419,
 it will be fixed in release 6.0.19.
 
 I don't see any indication on that bug report that it
 
 a) has been fixed
 b) fix will be included for 6.0.19

I think he is actually talking about

https://issues.apache.org/bugzilla/show_bug.cgi?id=45951

which will be part of 6.0.19.

Regards,

Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


ETa4aF48ddYFvyOJ7LMCtvWOmSVFIEOPvWwEmq9lJWf0LZmw==

Re: Deployment Web App on Debian

2008-11-06 Thread Youssef Mohammed

There shouldn't be any difference if you have same same version of tomcat
(recall java in platform independent).
You should look at your logs and see why it fails. If could be for example
that you don't have your database setup or jdbc drivers is done added the
classpath.
You should also deploy a WAR not the webbapp folder (though it sometimes
works both ways).

Regards, Youssef


On Fri, Nov 7, 2008 at 6:21 AM, Zaki Akhmad [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1


 Hello all,

 I am having difficulty while deploying my web application on Debian.
 FYI, I am using Debian Testing.

 Before I deploy on Debian, I had successfully deployed on Windows. I
 just copy one folder of my web application folder to
 C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\mywebapp

 Do some little configuration, restart the tomcat, voila! It works on
 http://localhost:8080/mywebapp

 But how do I do it on Debian GNU/Linux?

 - --
 Zaki Akhmad


 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: http://getfiregpg.org

 iEYEARECAAYFAkkTwjIACgkQT4k8JfIMt5fw5ACeMZQXkW0RUQXSOV4hqwhzQc+P
 fpgAnje/rgMHC/f1vPfDjnkWrsrV1HFF
 =hbKI
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Problem Deploying Web App on Debian's Tomcat

2008-11-06 Thread Zaki Akhmad

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello all,

I am having difficulty while deploying my web application on Debian.
FYI, I am using Debian Testing.

Before I deploy on Debian, I had successfully deployed on Windows. I
just copy one folder of my web application folder to
C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\mywebapp

Do some little configuration, restart the tomcat, voila! It works on
http://localhost:8080/mywebapp

But how do I do it on Debian GNU/Linux?

- --
Zaki Akhmad


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkkT7TsACgkQT4k8JfIMt5dejwCdGAemc69mts2XSbYdpjObDi9P
3dgAnA9gZemQ2mcuKlJ6fDXgQeHYV7y/
=12Ap
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Problem]Tomcat 6.x with Active Directory on Windows Server 2003

2008-11-06 Thread Vickey


another thing, authentication on IIS and Active Directory with the same users
and groups is successfully passed.
-- 
View this message in context: 
http://www.nabble.com/-Problem-Tomcat-6.x-with-Active-Directory-on-Windows-Server-2003-tp20375746p20375888.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Deployment Web App on Debian

2008-11-06 Thread Leon Rosenberg

you should also check which java version is installed.
If its not suns - remove it.

Leon

On Fri, Nov 7, 2008 at 8:22 AM, Youssef Mohammed
[EMAIL PROTECTED] wrote:
 There shouldn't be any difference if you have same same version of tomcat
 (recall java in platform independent).
 You should look at your logs and see why it fails. If could be for example
 that you don't have your database setup or jdbc drivers is done added the
 classpath.
 You should also deploy a WAR not the webbapp folder (though it sometimes
 works both ways).

 Regards, Youssef


 On Fri, Nov 7, 2008 at 6:21 AM, Zaki Akhmad [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1


 Hello all,

 I am having difficulty while deploying my web application on Debian.
 FYI, I am using Debian Testing.

 Before I deploy on Debian, I had successfully deployed on Windows. I
 just copy one folder of my web application folder to
 C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\mywebapp

 Do some little configuration, restart the tomcat, voila! It works on
 http://localhost:8080/mywebapp

 But how do I do it on Debian GNU/Linux?

 - --
 Zaki Akhmad


 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: http://getfiregpg.org

 iEYEARECAAYFAkkTwjIACgkQT4k8JfIMt5fw5ACeMZQXkW0RUQXSOV4hqwhzQc+P
 fpgAnje/rgMHC/f1vPfDjnkWrsrV1HFF
 =hbKI
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a cookie question of one Server with two tomcat server