5.5, WebdavServlet and getResources

[Tore Halset]

Hello.

I am upgrading my WebdavServlet subclass to tomcat-5.5. I used to  
override getResources() to return a custom DirContext, but  
getResources are gone in version 5.5. How can I provide a custom  
DirContext?


Regards,
 - Tore.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: PLEASE REMOVE ME FROM THE MAILING LIST

[Java Pro]

Alassane Top wrote:



  

To unsubscribe, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Session Problems with Firefox

[Michael Andreas Omerou]

Hello,

I have some problems with session management when our application runsin
Firefox.

Basically, what happens is that after I set in the session some
attributes/beans which are needed down the application, I check in all JSPs
and servlets that an old session is still there by using 
if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));

}

With IE all works fine, however with Firefox, it seems that the session is
re-initialised whenever the client/browser requests a new page.  I checked
this by printing the session id in the log on each page and with IE it does
not change, while with Firefox it changes.  

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: context error

[Warren Pace]

> 
> From: "jacky" <[EMAIL PROTECTED]>
> Date: 2006/02/14 Tue PM 08:32:56 EST
> To: "Tomcat Users List" , 
>   <[EMAIL PROTECTED]>
> Subject: Re: context error
> 
> hi, Mike,
>Do you mean put all directories together? 
> No, we need to separate them. So, any other suggestions about this problem?
> 
>  Best Regards.
>jacky  
> 
Could you send us your server.xml with and without the added context?  I see 
you're using 4.1.  What OS and what JVM are you using?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with hosting web application on tomcat / error 404 for an exists file

[Legolas Woodland]

Hi
Thank you for reading my post.
I have a web application which i developed and works well on my tomcat 5.5.9
Now i purchase a hosting plane with tomcat 5.5.9 it is on linux and have 
cpanel.
they said that i should upload all contents of my war file into http_doc 
folder , so i did
I used ftp to upload them all , now that i try to access my web site it 
return



 HTTP Status 404 - /index.jsp


meanwhile index.jsp in under that www folder.
I test the server by uploading an html file to make sure that i put 
content of war file in correct place. nad it works ok with HTML file.

can some one help me about this problem ?


Thanks

Re: Tomcat and client certificates

[Luis Henrique]

Hi

I have followed all the instructions on this discussion, and i´m still
getting the error:

HTTP Status 400 - No client certificate chain in this request

Does the user cert that i´m using need to be "trusted" by cert of tomcat sever?


I´m using Apache Tomcat/5.5.15, on Win Xp Pro SP2

I have generated the 2 certs like described on:
http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html

The acess to https://localhost:8443 works fine
But the access to the restricted area https://localhost:8443/teste
return the error:
HTTP Status 400 - No client certificate chain in this request

If i use the BASIC auth, it works, but with CLIENT-CERT it did not

Is there anything wrong with my configuration?

This are my configuration:

server.xml :
...


...




tomcat-users.xml :

  ...
  
   



web.xml:


http://java.sun.com/dtd/web-app_2_3.dtd";>



Bug 12218

  Test web app for bug 12218.




App
/index.htm


cert


CONFIDENTIAL




  CLIENT-CERT



  cert




Thanks for your help

Luis

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Problems with Firefox

[Michael Andreas Omerou]

Further to my below email I have put in some code to check the HTTP headers
in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of FireFox but not
in the case of IE could be the cause of my problems.

Michael



>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 11:27
>To: users@tomcat.apache.org
>Subject: Session Problems with Firefox
>
>Hello,
>
>I have some problems with session management when our 
>application runsin Firefox.
>
>Basically, what happens is that after I set in the session 
>some attributes/beans which are needed down the application, I 
>check in all JSPs and servlets that an old session is still 
>there by using 
>   if (request.getSession(false)==null){
> 
>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>
>}
>
>With IE all works fine, however with Firefox, it seems that 
>the session is re-initialised whenever the client/browser 
>requests a new page.  I checked this by printing the session 
>id in the log on each page and with IE it does not change, 
>while with Firefox it changes.  
>
>I checked my firefox settings for cookies and all look ok.
>
>Anybody has a clue of what I might be doing wrong?
>
>Regards,
>Michael
>
>
>-
>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: JNDIRealm and how to extract user info

[Crompton, SY \(Shirley\)]

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:06
To: Crompton, SY (Shirley)
Subject: failure notice


Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
Sorry, only subscribers may post. If you are a subscriber, check to be sure you 
are sending from your subscribed address. (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 30844 invoked by uid 99); 15 Feb 2006 11:05:42 -
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2006 03:05:42 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [148.79.80.138] (HELO mserv7.dl.ac.uk) (148.79.80.138)
Hi

I have set up JNDIRealm to authenticate my user against our company's active 
directory using the basic auth mode.  But I need to use the user name to get 
access mode via a local database.  Could any one advice on how to extract the 
user name from Tomcat 5.5?  Many thanks

Shirley




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

classloader issue?

[Rik Claesen]

hi,

I'm having a problem with Tomcat 5 with the security manager activated:
"javassist.NotFoundException: java.lang.Object
javassist.ClassPool.get(ClassPool.java:374)
org.apache.hivemind.service.impl.CtClassSource.getCtClass(CtClassSource.java:52)
org.apache.hivemind.service.impl.CtClassSource.newClass(CtClassSource.java:62) 
 ..."


It looks like someone in the javassist.jar cannot find java.lang.Object in 
the rt.jar


Can it be, that when the security manager is activated, a classloader used 
by javassist cannot find the classes in rt.jar due to security restrictions?


Do I have to move the javassist.jar to another location? if so where?

This simple thing is driving me nuts because all works fine when the 
security manager is not active.


My eternal gratitude for the one who can help me.
Rik



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5 Deply Multi-Servlet

[Stefano . Massera]

Hi,
i upgrade recently my tomcat from 4.1 to 5.5.
I have some problem on deploy.
My application is made of about 200 servlet.

In the old tomcat version i specify a  element in server.xml and
all works in the right way.

In the new version this configuration doesn't works.

I try to modify the web.xml in folder WEB-INF.
The question is: in file web.xml i have to specify all the 200 servlet
by element  and 
or is there a smarter way to do that?

sTe


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: classloader issue?

[Boris Unckel]

Hi,

> Do I have to move the javassist.jar to another location? if so where?
Where is the javassist.jar now? In your web application (WEB-INF/lib)?

Boris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

password protection

[Zohar Amir]

Hello,
I'm using tomcat 5.5.15 on Win XP.
I have a servlet that is deployed on a certain context. I would like anyone 
trying to use that servlet use a username-password. how do I do this?

What if I need to protect a jsp that is part of the servlet?
Thanks,
Zohar. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: App will work on localhost but blank on client PC.

[David Smith]

Take a look at server.xml and specifically the  element 
corresponding to port 8447. Does it have an attribute named address set 
to "127.0.0.1" ?  If so, remove that attribute and restart tomcat.  
Setting the address attribute to 127.0.0.1 specifically binds tomcat to 
the localhost adapter and you'll never be able to connect to it from any 
other client.


-- David

Alexander Alekseev wrote:

Server is 192.168.2.100, client is 192.168.2.X

We tried using http://192.168.2.100:8447/ from the client, and the blank
problem first cropped up.

Now, instead of http://localhost:8447/ we tried http://192.168.2.100:8447/
from the server itself, and it also comes up blank.



-Original Message-
From: Mike Sabroff [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 14, 2006 9:55 AM

To: Tomcat Users List
Subject: Re: App will work on localhost but blank on client PC.

  
How does localhost resolve in that scenario...why not use the hostname 
or ip address







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  



--
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Setting up a parallel test environment on the same machine as main server

[Tim Lucia]

I believe you need to have a virtual host in Tomcat for each one on Apache.
I also believe that the name of the workers is irrelevant, as is the IP
address over which they communicate -- as long as the servers are bound to
the right address(es).  All differentiation takes place on the host header
only.

The https part (having to use Ips) is unfamiliar to me (I have one site on
my server running secure, and that works fine.)

Someone else feel free to jump in here and correct me if I am wrong.

Tim

> > So, you should have two virtual hosts (by name) in both 
> server.xml and 
> > httpd.conf.  Not sure how to solve the https problem -- 
> never tried to 
> > myself.
> 
> This is where I get lost.  I currently have two virtual hosts 
> on apache 
> pointing at the same virtual host on tomcat ALL with 
> different names - so 
> this doesn't square with what you are saying  of there being 
> a one to one 
> mapping.
> 
> This server is running linux, with two ethernet cards. On the 
> WAN side (which 
> is what you can see) my ISP allocated via dhcp a single IP 
> address.  That is 
> the www.chandlerfamily.org.uk address. On the lan side, I can 
> allocate 
> multiple IP addresses to the card in a set of "psuedo 
> devices", so at the 
> moment it has address 192.168.0.20 and 192.168.0.30, 31, 32 
> and 39.  Each of 
> these is given separate names such as roo.home, appserv.home, 
> webmail.home 
> money.home and test.home by a nameserver also running on that machine
> 
> On apache I have a number of virtual hosts set up (but 
> because of the https 
> problem they MUST be differenciated by ip address).  At the 
> moment I have the 
> virtual hosts www.chandlerfamily.org.uk and money.home 
> directing traffic to 
> tomcat on the host appserv.home (the home page you saw was 
> being generated in 
> a java application).
> 
> I want to add a tomcat host to serve java applications to an 
> apache virtual 
> host running on test.home.  If I understand you correctly you 
> would advocate 
> creating additional  elements of my server.xml file 
> with names of 
> www.chandlerfamily.org.uk and test.home (I presume I have to 
> keep default 
> host of appserv.home just so that tomcat knows which ip 
> address to listen 
> on).  If I do that how do I pick up traffic to money.home? 
> add another  
> statement with repeated contexts?
> 
> 
> 
> -- 
> Alan Chandler
> http://www.chandlerfamily.org.uk
> Open Source. It's the difference between trust and antitrust.
> 
> -
> 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: classloader issue?

[Rik Claesen]

Thnx Boris, I forgot to mention it.
The assist.jar is currently located in the WEB-INF/lib.
and ...this is working fine as long as the security manager is not active.

Rik



From: "Boris Unckel" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" 
To: "Tomcat Users List" 
Subject: Re: classloader issue?
Date: Wed, 15 Feb 2006 13:28:41 +0100 (MET)

Hi,

> Do I have to move the javassist.jar to another location? if so where?
Where is the javassist.jar now? In your web application (WEB-INF/lib)?

Boris

-
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: password protection

[David Delbecq]

Zohar Amir a écrit :

> Hello,
> I'm using tomcat 5.5.15 on Win XP.
> I have a servlet that is deployed on a certain context. I would like
> anyone trying to use that servlet use a username-password. how do I do
> this?

set a security-constrain in WEB-INF/web.xml

> What if I need to protect a jsp that is part of the servlet?

You mean to prevent direct loading of a jsp included by your servlet?
Same thing, add a security-constraint to the url of your jsp.

> Thanks,
> Zohar.
> -
> 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: password protection

[Zohar Amir]

Thanks,
Where can I find info on how exactly to do this? maybe an example...?
- Original Message - 
From: "David Delbecq" <[EMAIL PROTECTED]>

To: "Tomcat Users List" 
Sent: Wednesday, February 15, 2006 2:52 PM
Subject: Re: password protection



Zohar Amir a écrit :


Hello,
I'm using tomcat 5.5.15 on Win XP.
I have a servlet that is deployed on a certain context. I would like
anyone trying to use that servlet use a username-password. how do I do
this?


set a security-constrain in WEB-INF/web.xml


What if I need to protect a jsp that is part of the servlet?


You mean to prevent direct loading of a jsp included by your servlet?
Same thing, add a security-constraint to the url of your jsp.


Thanks,
Zohar.
-
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]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: password protection

[David Delbecq]

http://www.onjava.com/pub/a/onjava/2001/07/24/tomcat.html
http://www.cafesoft.com/products/cams/tomcat-security.html

for other ones, use favorite search engine.

Zohar Amir a écrit :

> Thanks,
> Where can I find info on how exactly to do this? maybe an example...?
> - Original Message - From: "David Delbecq" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" 
> Sent: Wednesday, February 15, 2006 2:52 PM
> Subject: Re: password protection
>
>
>> Zohar Amir a écrit :
>>
>>> Hello,
>>> I'm using tomcat 5.5.15 on Win XP.
>>> I have a servlet that is deployed on a certain context. I would like
>>> anyone trying to use that servlet use a username-password. how do I do
>>> this?
>>
>>
>> set a security-constrain in WEB-INF/web.xml
>>
>>> What if I need to protect a jsp that is part of the servlet?
>>
>>
>> You mean to prevent direct loading of a jsp included by your servlet?
>> Same thing, add a security-constraint to the url of your jsp.
>>
>>> Thanks,
>>> Zohar.
>>> -
>>> 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]
>>
>>
>
> -
> 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]

Performance issues with tomcat 5

[Leon Rosenberg]

Hi,

has someone ever estimated the max possible load for tomcat? We are
suffering from very odd behaviour, as long as tomcat/machine is under
certain load it works very well, but then it just "breaks a magical
limit" and the performance breaks down.
Tomcat or the JVM are starting to leak memory (we are running with
mx800M, and are normally at 600+ free memory, but then it goes to
zero). Tomcat begins to throw absolutely ununderstandable exceptions,
like beans not present in scope which are normally there, socket/pipe
errors, unable to deliver 5xx or 4xx error pages and so on. Busy
threads are going high, from 10-20 to some hundreds.

We are running with jdk1.4.2_04, tomcat 5.0.25, linux kernel 2.6.8
(debian) 32 bit on different hardware, intel or opteron 1-2
processors, 32 and 64 bit processors (up to 4 virtual processors). No
tomcat clustering, no app. server. Our loadbalancing is based on CPU
Idle time, so the amount of traffic on each machine is different,
faster machines serving 4 times more then slower. The faster machines
are serving 100-150 requests per second in normal, and approx. 300-400
requests per second in peak times. Avg. request duration is <15 ms in
normal times (the servlet execution, not counting the jsp transmission
afterwards) and 100-200 under high load.

We need some serious performance benchmarks, but those are hard to
find (most people talk about absolutely irrelevant things like
database tuning)...
Any good links?

TIA
Leon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.15 Clustering ?

[David Avenante]

Yes MULTICAST is enabled i see that by too fact :

first,
ifconfig eth0 :

eth0  Link encap:Ethernet  HWaddr 00:13:D4:45:A6:3F
  inet addr:192.168.2.102  Bcast:192.168.2.255  Mask:255.255.255.0
  UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST  MTU:1500
Metric:1
  RX packets:264493 errors:0 dropped:0 overruns:0 frame:0
  TX packets:292063 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:98079150 (93.5 Mb)  TX bytes:41007393 (39.1 Mb)

ALLMULTI and MULTICAST is enabled on two serveur interface.

second,

as you see in my first post tcpdump track the UDP messages send between
server.


For sticky_session=true i' m not agree with you.
In the connector documentation (see
http://tomcat.apache.org/connectors-doc/config/workers.html)
=> Set sticky_session to *False* when Tomcat is using a Session Manager
which can persist session data across multiple instances of Tomcat
It' s my situation.

So i' m alway in the trouble by thanks a lot for the verification ;)


On 2/15/06, Peter Rossbach <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> 1)  Clustering need sticky_session=true and is only design for
> failover (see servlet spec).
> 2)  Are your sure that MULTICAST is enabled at eth0?
>
> regards
> Peter
> [EMAIL PROTECTED]
>
>
>
> Am 15.02.2006 um 02:26 schrieb David Avenante:
>
> > Hi,
> >
> > I' ve try to use Tomcat 5.5.15 in cluster mod. And after some work on
> > configuration and test
> > i seems to be on limit of my all possibilities ;)
> >
> > I try to use two tomcat in cluster with apache web server and
> > mod_jk as
> > connector.
> >
> > my Apache configuration look like :
> >
> >
> > # workers.properties
> >
> > ps=/
> >
> > # List the workers name
> > worker.list=loadbalancer
> >
> > # 
> > # First worker
> > # 
> > worker.node01.port=8009
> > worker.node01.host=agnes
> > worker.node01.type=ajp13
> > worker.node01.lbfactor=1
> > #worker.node01.domain=cluster1
> > # 
> > # Second worker
> > # 
> > worker.node02.port=9009
> > worker.node02.host=ovea-inspiron
> > worker.node02.type=ajp13
> > worker.node02.lbfactor=1
> > #worker.node02.domain=cluster1
> > # --
> > # Load Balancer worker
> > # --
> > worker.loadbalancer.type=lb
> > worker.loadbalancer.sticky_session=false
> > worker.loadbalancer.balanced_workers=node01,node02
> >
> > As you can see i use two server ('agnes' IP : 192.168.2.102 and
> > 'ovea-inspiron' IP : 192.168.2.103)
> > I' ve coded a little aplication who read un file and create a
> > sessions if
> > session not exist.
> >
> > If i use the system in mod load balancing (with no cluster mod
> > activate)
> > all is great (my config is of course
> > worker.loadbalancer.sticky_session=true
> > )
> >
> > So system run with session affinitu but the two server are
> > accessible ;)
> >
> > Now i try to configure as cluster mode with session replication
> > (my config is now worker.loadbalancer.sticky_session=3Dfalse)
> >
> > I configure my to server.xml like that :
> > agnes (IP : 192.168.2.102)
> >
> > 
> >   
> >  >type="org.apache.catalina.UserDatabase"
> >description="User database that can be updated
> > and saved"
> >factory="
> > org.apache.catalina.users.MemoryUserDatabaseFactory"
> >pathname="conf/tomcat-users.xml" />
> >
> >   
> >
> >   
> >  >   maxThreads="150" minSpareThreads="25"
> >   maxSpareThreads="75"
> >   enableLookups="false" redirectPort="8443"
> > acceptCount="100"
> >   connectionTimeout="2"
> > disableUploadTimeout="true"
> > />
> >
> >  >   redirectPort="8443" protocol="AJP/1.3" />
> >
> >  > jvmRoute="node01" >
> >
> >>resourceName="UserDatabase" />
> >
> >>unpackWARs="true" autoDeploy="true"
> >xmlValidation="false" xmlNamespaceAware="false">
> >   > className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
> >   doClusterLog="true"
> >   clusterLogName="clusterlog"
> >   manager.className="
> > org.apache.catalina.cluster.session.DeltaManager"
> >   manager.expireSessionsOnShutdown="false"
> >   manager.notifyListenersOnReplication="true"
> >   manager.notifySessionListenersOnReplication="true"
> >   manager.sendAllSessions="true"
> >   manager.sendAllSessionsSize="500"
> >   manager.sendAllSessionsWaitTime="20">
> >
> >  >  mcastBindAddress="192.168.2.102"
> >  mcastAddr="224.0.0.1"
> >  mcastPort="45564"
> >  mcastFrequency="1000"
> >  

Read-Only Context with Tomcat + Hibernate

[Abraham Fdez]

Hi all,

 

I’m making a Web application with Apache + Tomcat + Mod_Jk + Hibernate +
Postgresql. I need that hibernate binds factory to JNDI but when I do that
it gives me and error that context is read-only.

 

Is there any method to implement this or any config tag that makes context
writable?.

 

Thanks all,

 

 


  

Abraham Fernández Álvarez


Dpto. de Informática 
FNAC ESPAÑA S.A. 
Parque Empresarial La Finca
Pº de la Finca, bloque 11 2ª Planta
28223 Pozuelo de Alarcón (Madrid) 
* +34 91 7689211
7 +34 91 7689225 

* [EMAIL PROTECTED]  

* http://www.fnac.es 

 

 

 

 

 

 

 

 

 

 

 

Re: Read-Only Context with Tomcat + Hibernate

[Kenevel]

Abraham Fdez wrote:
> I'm making a Web application with Apache + Tomcat + Mod_Jk +
> Hibernate + Postgresql. I need that hibernate binds factory to JNDI
> but when I do that it gives me and error that context is read-only.

>From memory Tomcat has a JNDI context that is read-only, but which can
accept values bound to it in the configuration files. So you can set up a
data-source in the conf/Catalina/localhost/yourcontext.xml file and bind
this to a JNDI name. This is then available to be read (only).

There will be docs on this but it looks something like this:





Incidentally, Spring is a superb way of integrating a Java webapp and
Hibernate

Mike

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can't get caseSensitive="false" to work

[David Kerber]

Nobody has any suggestions on this?  I still can't get it to go.

Thnaks!
Dave

David Kerber wrote:

I read the thread from last week about case-sensitivity, and did some 
additional googling when it didn't work, but still can't get my Tomcat 
5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for 
the context path.  That is a problem for my users, because we migrated 
them from SilverStream, which is NOT case-sensitive in the context 
path.  I have tried the following Context entries.  Note the entry in 
both the  field, and the  entry (I found that one 
via google).  I have tried these entries eash separately, and 
together, and still cannot get my context path to be 
case-INsensitive.  I don't care if things are case sensitive once they 
get into the app, but would really like to get the context path to not 
matter.


This is in my server.xml, because I can't get the context path to work 
in context.xml:


docBase="e:\TomcatClients\WebSiraCommon\webapps\SiteData" debug="0"
reloadable="true" autoDeploy="true" unpackWARs="true" 
crossContext="false" caseSensitive="false">


 

And yes, I know about the security warning about being non 
case-sensitive on Windows!  I also know that this context path setup 
is not the usual way of doing things; it's because I need to keep the 
path the same after the migration to Tomcat.


Thanks!
Dave



-
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: Can't get caseSensitive="false" to work

[Bob Faist]

I know that it works in conf/context.xml.  Can you just setup a minimal
config in the context.xml file?




WEB-INF/web.xml

 

According to the docs, the server.xml is not recommended place to put
 setup.

http://tomcat.apache.org/tomcat-5.5-doc/config/context.html



-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 8:49 AM
To: Tomcat Users List
Subject: Re: Can't get caseSensitive="false" to work

Nobody has any suggestions on this?  I still can't get it to go.

Thnaks!
Dave

David Kerber wrote:

> I read the thread from last week about case-sensitivity, and did some 
> additional googling when it didn't work, but still can't get my Tomcat
> 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for

> the context path.  That is a problem for my users, because we migrated

> them from SilverStream, which is NOT case-sensitive in the context 
> path.  I have tried the following Context entries.  Note the entry in 
> both the  field, and the  entry (I found that one 
> via google).  I have tried these entries eash separately, and 
> together, and still cannot get my context path to be case-INsensitive.

> I don't care if things are case sensitive once they get into the app, 
> but would really like to get the context path to not matter.
>
> This is in my server.xml, because I can't get the context path to work

> in context.xml:
>
>  docBase="e:\TomcatClients\WebSiraCommon\webapps\SiteData" debug="0"
> reloadable="true" autoDeploy="true" unpackWARs="true" 
> crossContext="false" caseSensitive="false">
> 
>  
>
> And yes, I know about the security warning about being non 
> case-sensitive on Windows!  I also know that this context path setup 
> is not the usual way of doing things; it's because I need to keep the 
> path the same after the migration to Tomcat.
>
> Thanks!
> Dave
>
>
>
> -
> 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]


**
Confidentiality Notice
The information contained in this e-mail is confidential and intended for
use only by the person(s) or organization listed in the address. If you have
received this communication in error, please contact the sender at O'Neil &
Associates, Inc., immediately. Any copying, dissemination, or distribution
of this communication, other than by the intended recipient, is strictly
prohibited.
**


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Apache / mod_jk / Multiples instances of Tomcat

[Farid Izem]

Hi all,

I'm currently trying to build a Apache load balancings against multiples
instances of Tomcat.

On my host, i have three instances of Tomcat (ie using CATALINA_BASE
variable), each listening on differents ports for AJP Connector.
On the same server, i have an Apache using Mod_jk.

Is it possible to configure load balancing across the three instances of
Tomcat using mod_jk ?

Morever, in the worker.properties, i don't known how to configure
worker.tomcat_home as it is different for each instance of Tomcat ?

Any help would be appreciate, Any Internet Links ..

Kind Regards,

Farid

Re: Tomcat 5.5.15 Clustering ?

[Filip Hanik - Dev Lists]

>1)Clustering need sticky_session=true and is only design for 
failover (see servlet spec).


Not true for Tomcat, using replicationMode="pooled" and 
waitForAck="true", you can do round robin non sticky load balancing as 
long as you don't have more than one thread accessing the session at any 
point in time.


>INFO: Manager [/cluster-1.0-SNAPSHOT]: skipping state transfer. No 
members active in cluster group.


yes, your multicast isn't working, or it should have said that you had a 
member.
Take a look at the bottom of the page and run the MCaster test included 
in a super old version of Tomcat 4 clustering.

http://people.apache.org/~fhanik/

On multihomed hosts, it can get a little tricky to get multicasting 
working and you might have to setup some routes to help. Check with your 
sysadmin.


Filip



Peter Rossbach wrote:

Hey,

1)Clustering need sticky_session=true and is only design for 
failover (see servlet spec).

2)Are your sure that MULTICAST is enabled at eth0?

regards
Peter
[EMAIL PROTECTED]



Am 15.02.2006 um 02:26 schrieb David Avenante:


Hi,

I' ve try to use Tomcat 5.5.15 in cluster mod. And after some work on
configuration and test
i seems to be on limit of my all possibilities ;)

I try to use two tomcat in cluster with apache web server and mod_jk as
connector.

my Apache configuration look like :


# workers.properties

ps=/

# List the workers name
worker.list=loadbalancer

# 
# First worker
# 
worker.node01.port=8009
worker.node01.host=agnes
worker.node01.type=ajp13
worker.node01.lbfactor=1
#worker.node01.domain=cluster1
# 
# Second worker
# 
worker.node02.port=9009
worker.node02.host=ovea-inspiron
worker.node02.type=ajp13
worker.node02.lbfactor=1
#worker.node02.domain=cluster1
# --
# Load Balancer worker
# --
worker.loadbalancer.type=lb
worker.loadbalancer.sticky_session=false
worker.loadbalancer.balanced_workers=node01,node02

As you can see i use two server ('agnes' IP : 192.168.2.102 and
'ovea-inspiron' IP : 192.168.2.103)
I' ve coded a little aplication who read un file and create a 
sessions if

session not exist.

If i use the system in mod load balancing (with no cluster mod activate)
all is great (my config is of course 
worker.loadbalancer.sticky_session=true

)

So system run with session affinitu but the two server are accessible ;)

Now i try to configure as cluster mode with session replication
(my config is now worker.loadbalancer.sticky_session=3Dfalse)

I configure my to server.xml like that :
agnes (IP : 192.168.2.102)


  
   description="User database that can be updated and 
saved"

   factory="
org.apache.catalina.users.MemoryUserDatabaseFactory"
   pathname="conf/tomcat-users.xml" />

  

  
  connectionTimeout="2" 
disableUploadTimeout="true"

/>





  

  
 className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"

  doClusterLog="true"
  clusterLogName="clusterlog"
  manager.className="
org.apache.catalina.cluster.session.DeltaManager"
  manager.expireSessionsOnShutdown="false"
  manager.notifyListenersOnReplication="true"
  manager.notifySessionListenersOnReplication="true"
  manager.sendAllSessions="true"
  manager.sendAllSessionsSize="500"
  manager.sendAllSessionsWaitTime="20">







  

  



ovea-inspiron (IP : 192.168.2.103)


  

  

  

connectionTimeout="2" 
disableUploadTimeout="true"

/>

   

   
 

 

 className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"

  doClusterLog="true"
  clusterLogName="clusterlog"
  manager.className="
org.apache.catalina.cluster.session.DeltaManager"
  manager.expireSessionsOnShutdown="false"
  manager.notifyListenersOnReplication="true"
  manager.notifySessionListenersOnReplication="true"
  manager.sendAllSessions="true"
  manager.sendAllSessionsSize="500"
  manager.sendAllSessionsWaitTime="20">







  

  



I'm user linux so i've compiled my kernel with multicat kernel option
I add the rout like rooute add -host 224.0.0.1 dev eth0

N.B : why 224.0.0.1 => 
http://www.iana.org/assignments/multicast-addresses


So route is :
ALL-SYSTEMS.MCA * 255.255.255.255 UH0  00 eth0
192.168.2.0 *  255.255.255.0 U  0  
00

eth0
loopback*   255.0.0.0U  0  0
 0 lo
default .  0.0.0.0   UG0  0
   0 eth0

now i start the two tomcat with the same application in webapp 
directo

Re: Tomcat 5.5.15 Clustering ?

[Peter Rossbach]

Am 15.02.2006 um 15:11 schrieb Filip Hanik - Dev Lists:

>1)Clustering need sticky_session=true and is only design for  
failover (see servlet spec).


Not true for Tomcat, using replicationMode="pooled" and  
waitForAck="true", you can do round robin non sticky load balancing  
as long as you don't have more than one thread accessing the  
session at any point in time.


OK, yes, for special application we support it, but normaly  
sticky_session is true. See Servlet Spec (SRV 7.7).


Peter

>INFO: Manager [/cluster-1.0-SNAPSHOT]: skipping state transfer. No  
members active in cluster group.


yes, your multicast isn't working, or it should have said that you  
had a member.
Take a look at the bottom of the page and run the MCaster test  
included in a super old version of Tomcat 4 clustering.

http://people.apache.org/~fhanik/

On multihomed hosts, it can get a little tricky to get multicasting  
working and you might have to setup some routes to help. Check with  
your sysadmin.



Filip



Peter Rossbach wrote:

Hey,

1)Clustering need sticky_session=true and is only design for  
failover (see servlet spec).

2)Are your sure that MULTICAST is enabled at eth0?

regards
Peter
[EMAIL PROTECTED]



Am 15.02.2006 um 02:26 schrieb David Avenante:


Hi,

I' ve try to use Tomcat 5.5.15 in cluster mod. And after some  
work on

configuration and test
i seems to be on limit of my all possibilities ;)

I try to use two tomcat in cluster with apache web server and  
mod_jk as

connector.

my Apache configuration look like :


# workers.properties

ps=/

# List the workers name
worker.list=loadbalancer

# 
# First worker
# 
worker.node01.port=8009
worker.node01.host=agnes
worker.node01.type=ajp13
worker.node01.lbfactor=1
#worker.node01.domain=cluster1
# 
# Second worker
# 
worker.node02.port=9009
worker.node02.host=ovea-inspiron
worker.node02.type=ajp13
worker.node02.lbfactor=1
#worker.node02.domain=cluster1
# --
# Load Balancer worker
# --
worker.loadbalancer.type=lb
worker.loadbalancer.sticky_session=false
worker.loadbalancer.balanced_workers=node01,node02

As you can see i use two server ('agnes' IP : 192.168.2.102 and
'ovea-inspiron' IP : 192.168.2.103)
I' ve coded a little aplication who read un file and create a  
sessions if

session not exist.

If i use the system in mod load balancing (with no cluster mod  
activate)
all is great (my config is of course  
worker.loadbalancer.sticky_session=true

)

So system run with session affinitu but the two server are  
accessible ;)


Now i try to configure as cluster mode with session replication
(my config is now worker.loadbalancer.sticky_session=3Dfalse)

I configure my to server.xml like that :
agnes (IP : 192.168.2.102)


  
   description="User database that can be updated  
and saved"

   factory="
org.apache.catalina.users.MemoryUserDatabaseFactory"
   pathname="conf/tomcat-users.xml" />

  

  
  connectionTimeout="2"  
disableUploadTimeout="true"

/>



jvmRoute="node01" >


  

  
 className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"

  doClusterLog="true"
  clusterLogName="clusterlog"
  manager.className="
org.apache.catalina.cluster.session.DeltaManager"
  manager.expireSessionsOnShutdown="false"
  manager.notifyListenersOnReplication="true"
  manager.notifySessionListenersOnReplication="true"
  manager.sendAllSessions="true"
  manager.sendAllSessionsSize="500"
  manager.sendAllSessionsWaitTime="20">







  

  



ovea-inspiron (IP : 192.168.2.103)


  
 description="User database that can be  
updated and

saved"
 factory="
org.apache.catalina.users.MemoryUserDatabaseFactory"
 pathname="conf/tomcat-users.xml" />
  

  

connectionTimeout="2"  
disableUploadTimeout="true"

/>

   

   jvmRoute="node02" >

 

 

 className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"

  doClusterLog="true"
  clusterLogName="clusterlog"
  manager.className="
org.apache.catalina.cluster.session.DeltaManager"
  manager.expireSessionsOnShutdown="false"
  manager.notifyListenersOnReplication="true"
  manager.notifySessionListenersOnReplication="true"
  manager.sendAllSessions="true"
  manager.sendAllSessionsSize="500"
  manager.sendAllSessionsWaitTime="20">







  

  



I'm user linux so i've compiled my kernel with multicat kernel  
option

I add the rout like rooute add -host 224.0.0.1 dev e

Re: Can't get caseSensitive="false" to work

[David Kerber]

Thanks for the response, but I still can't get it to go.  I set up 
another server with the  entries in the context.xml instead of 
in server.xml, so things are where the docs recomment, but still 
nothing.  I've put the caseSensitive="false" in both the one in /conf, 
and in META-INF with no luck. 

Are you sure it works in 5.5.12?  A couple of the posts I've seen while 
googling have implied that the last version this worked in was 5.5.9.  
That would really suck if correct!  If it matters, I'm running jdk 1.5.0_06.





David Kerber wrote:


Nobody has any suggestions on this?  I still can't get it to go.

Thnaks!
Dave

David Kerber wrote:

I read the thread from last week about case-sensitivity, and did some 
additional googling when it didn't work, but still can't get my 
Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be 
case-INsensitive for the context path.  That is a problem for my 
users, because we migrated them from SilverStream, which is NOT 
case-sensitive in the context path.  I have tried the following 
Context entries.  Note the entry in both the  field, and the 
 entry (I found that one via google).  I have tried these 
entries eash separately, and together, and still cannot get my 
context path to be case-INsensitive.  I don't care if things are case 
sensitive once they get into the app, but would really like to get 
the context path to not matter.


This is in my server.xml, because I can't get the context path to 
work in context.xml:


docBase="e:\TomcatClients\WebSiraCommon\webapps\SiteData" debug="0"
reloadable="true" autoDeploy="true" unpackWARs="true" 
crossContext="false" caseSensitive="false">


 

And yes, I know about the security warning about being non 
case-sensitive on Windows!  I also know that this context path setup 
is not the usual way of doing things; it's because I need to keep the 
path the same after the migration to Tomcat.


Thanks!
Dave






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.15 Clustering ?

[Peter Rossbach]

Can you test your config without the parameter mcastBindAddress="xx"?


Peter



Am 15.02.2006 um 14:35 schrieb David Avenante:


Yes MULTICAST is enabled i see that by too fact :

first,
ifconfig eth0 :

eth0  Link encap:Ethernet  HWaddr 00:13:D4:45:A6:3F
  inet addr:192.168.2.102  Bcast:192.168.2.255  Mask: 
255.255.255.0

  UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST  MTU:1500
Metric:1
  RX packets:264493 errors:0 dropped:0 overruns:0 frame:0
  TX packets:292063 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:98079150 (93.5 Mb)  TX bytes:41007393 (39.1 Mb)

ALLMULTI and MULTICAST is enabled on two serveur interface.

second,

as you see in my first post tcpdump track the UDP messages send  
between

server.


For sticky_session=true i' m not agree with you.
In the connector documentation (see
http://tomcat.apache.org/connectors-doc/config/workers.html)
=> Set sticky_session to *False* when Tomcat is using a Session  
Manager

which can persist session data across multiple instances of Tomcat
It' s my situation.

So i' m alway in the trouble by thanks a lot for the verification ;)


On 2/15/06, Peter Rossbach <[EMAIL PROTECTED]> wrote:


Hey,

1)  Clustering need sticky_session=true and is only design for
failover (see servlet spec).
2)  Are your sure that MULTICAST is enabled at eth0?

regards
Peter
[EMAIL PROTECTED]



Am 15.02.2006 um 02:26 schrieb David Avenante:


Hi,

I' ve try to use Tomcat 5.5.15 in cluster mod. And after some  
work on

configuration and test
i seems to be on limit of my all possibilities ;)

I try to use two tomcat in cluster with apache web server and
mod_jk as
connector.

my Apache configuration look like :


# workers.properties

ps=/

# List the workers name
worker.list=loadbalancer

# 
# First worker
# 
worker.node01.port=8009
worker.node01.host=agnes
worker.node01.type=ajp13
worker.node01.lbfactor=1
#worker.node01.domain=cluster1
# 
# Second worker
# 
worker.node02.port=9009
worker.node02.host=ovea-inspiron
worker.node02.type=ajp13
worker.node02.lbfactor=1
#worker.node02.domain=cluster1
# --
# Load Balancer worker
# --
worker.loadbalancer.type=lb
worker.loadbalancer.sticky_session=false
worker.loadbalancer.balanced_workers=node01,node02

As you can see i use two server ('agnes' IP : 192.168.2.102 and
'ovea-inspiron' IP : 192.168.2.103)
I' ve coded a little aplication who read un file and create a
sessions if
session not exist.

If i use the system in mod load balancing (with no cluster mod
activate)
all is great (my config is of course
worker.loadbalancer.sticky_session=true
)

So system run with session affinitu but the two server are
accessible ;)

Now i try to configure as cluster mode with session replication
(my config is now worker.loadbalancer.sticky_session=3Dfalse)

I configure my to server.xml like that :
agnes (IP : 192.168.2.102)


  


  

  






  

  
 







  

  



ovea-inspiron (IP : 192.168.2.103)


  

  

  

   

   

   jvmRoute="node02" >

 

 

 







  

  



I'm user linux so i've compiled my kernel with multicat kernel  
option

I add the rout like rooute add -host 224.0.0.1 dev eth0

N.B : why 224.0.0.1 => http://www.iana.org/assignments/multicast-
addresses

So route is :
ALL-SYSTEMS.MCA * 255.255.255.255 UH0  00 eth0
192.168.2.0 *  255.255.255.0 U  0
00
eth0
loopback*   255.0.0.0U  0  0
 0 lo
default .  0.0.0.0   UG
0  0
   0 eth0

now i start the two tomcat with the same application in webapp
directories
with tcpdump i verify the multicasting btewen my server .. so :

19:39:17.809978 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:18.546034 IP ovea-inspiron.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:18.814418 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564UDP,
length 56
19:39:19.790470 IP ovea-inspiron.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:19.818691 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:20.826650 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:20.943933 IP ovea-inspiron.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:21.806813 arp who-has . tell 192.168.2.102
19:39:21.806972 arp reply . is-at 00:04:e2:b6:65:0a (oui Unknown)
19:39:21.831048 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:22.164812 IP ovea-inspiron.45564 > all-systems.mcast.net.
45564:UDP,
length 56
19:39:22.835240 IP 192.168.2.102.45564 > all-systems.mcast.net.
45564:UDP,
length 56

So all semms to be OK but i've

Feb 14, 2006 6:33:26 PM
org.apache.catalina.cluste

webapp references, classloaders and GC (oh my)

[Tim Lucia]

I have a question about references held to my webapp from Tomcat.

I have observed the behavior below on both Red Had EL V.4, and on WinXP,
using Tomcat 5.5, and JDK 1.5.  I used JProfiler to trace the allocations.

Some background: The environment here is such that we have a shared sandbox
for QA, so developers are deploying (by copying some changed resource files,
which are processed by the servlets) directly into the WEB-INF/classes/...
area of the webapp.  This causes (intentionally) a reload of the context,
either by (and I have tried both ways) auto reloading (reload="true"), or by
manual reloading (/manager/html/reload?path=/).

What the profiler shows me is that my ServletContextListener gets reloaded
every time, and there is one per reload (each in its own classloader.)  This
is as expected.  When "enough" of them are loaded, GC runs (or if I run it
manually from the profiler), all but two or three are GC'd.  The three that
remain are allocated by:

1. org.apache.catalina.startup.Bootstrap -- On Tomcat startup
2. org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor -- on
auto-reload
3. org.apache.tomcat.util.net.AprEndpoint$Worker -
org.apache.catalina.manager.HTMLManagerServlet (/manager/html/reload)

While this does not cause PermGen problems for any one developer, it does
cause the shared database server to run out of connections, because each
developer has up to 3 "pools" (after GC, might be 8 or 10 before GC) per
Tomcat, and some have clusters which means 2 X n pools.  It appears, from
watching the connections at the server, that the connections remain as long
as one of the three references above remain.

I can see clearly from logging that the
ServletContextListener.contextInitialized() and
ServletContextListener.contextDestroyed() methods are called as expected,
however, the webapp is still not GC'd.  I have shown this to be the case
with a simple, 2-class webapp - one class implements ServletContextListener
(and does nothing whatsoever in its two methods), and the other extends
HttpServlet, looks up a JNDI resource, gets the DataSource, connects, and
reports the connection is good (or bad).

I took out all logging in the process, as that has been known (in the past
anyway) to cause PermGen "leaks".

I can mitigate things for the time being by reducing the size of the
developer pools and/or increasing the number of connections in the database,
but I would still like to understand what is going on.

Any ideas or insights would be appreciated.

Thanks,
Tim





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

 Anybody has an idea what could be causing what I describe in the below two
emails?

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 13:10
>To: 'Tomcat Users List'
>Subject: RE: Session Problems with Firefox
>
>Further to my below email I have put in some code to check the 
>HTTP headers in each case (IE and FireFox).
>
>These are:
>
>IE
>accept: */*
>accept-language: en-gb
>accept-encoding: gzip, deflate
>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
>SV1; .NET CLR 1.1.4322; InfoPath.1)
>host: localhost
>connection: Keep-Alive
>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>
>FireFox
>host: localhost
>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
>Gecko/20050919 Firefox/1.0.7
>accept:
>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
>0.8,image/png,*/*;q=0.5
>accept-language: en-gb,en;q=0.5
>accept-encoding: gzip,deflate
>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>keep-alive: 300
>connection: keep-alive
>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>cache-control: max-age=0
>
>
>I wonder whether the keep-alive which exists in the case of 
>FireFox but not in the case of IE could be the cause of my problems.
>
>Michael
>
>
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 11:27
>>To: users@tomcat.apache.org
>>Subject: Session Problems with Firefox
>>
>>Hello,
>>
>>I have some problems with session management when our application 
>>runsin Firefox.
>>
>>Basically, what happens is that after I set in the session some 
>>attributes/beans which are needed down the application, I 
>check in all 
>>JSPs and servlets that an old session is still there by using
>>  if (request.getSession(false)==null){
>> 
>>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>>
>>}
>>
>>With IE all works fine, however with Firefox, it seems that 
>the session 
>>is re-initialised whenever the client/browser requests a new page.  I 
>>checked this by printing the session id in the log on each page and 
>>with IE it does not change, while with Firefox it changes.
>>
>>I checked my firefox settings for cookies and all look ok.
>>
>>Anybody has a clue of what I might be doing wrong?
>>
>>Regards,
>>Michael
>>
>>
>>-
>>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]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Earnie Dyke]

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in the below two
emails?

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 13:10
>To: 'Tomcat Users List'
>Subject: RE: Session Problems with Firefox
>
>Further to my below email I have put in some code to check the 
>HTTP headers in each case (IE and FireFox).
>
>These are:
>
>IE
>accept: */*
>accept-language: en-gb
>accept-encoding: gzip, deflate
>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
>SV1; .NET CLR 1.1.4322; InfoPath.1)
>host: localhost
>connection: Keep-Alive
>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>
>FireFox
>host: localhost
>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
>Gecko/20050919 Firefox/1.0.7
>accept:
>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
>0.8,image/png,*/*;q=0.5
>accept-language: en-gb,en;q=0.5
>accept-encoding: gzip,deflate
>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>keep-alive: 300
>connection: keep-alive
>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>cache-control: max-age=0
>
>
>I wonder whether the keep-alive which exists in the case of 
>FireFox but not in the case of IE could be the cause of my problems.
>
>Michael
>
>
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 11:27
>>To: users@tomcat.apache.org
>>Subject: Session Problems with Firefox
>>
>>Hello,
>>
>>I have some problems with session management when our application 
>>runsin Firefox.
>>
>>Basically, what happens is that after I set in the session some 
>>attributes/beans which are needed down the application, I 
>check in all 
>>JSPs and servlets that an old session is still there by using
>>  if (request.getSession(false)==null){
>> 
>>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>>
>>}
>>
>>With IE all works fine, however with Firefox, it seems that 
>the session 
>>is re-initialised whenever the client/browser requests a new page.  I 
>>checked this by printing the session id in the log on each page and 
>>with IE it does not change, while with Firefox it changes.
>>
>>I checked my firefox settings for cookies and all look ok.
>>
>>Anybody has a clue of what I might be doing wrong?
>>
>>Regards,
>>Michael
>>
>>
>>-
>>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]
>


-
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: Tomcat 5.5.15 Clustering ?

[David Avenante]

Thank you very much for the toolkit ;)
My feeling was also on my multicast support.
But i' ve read more documentation for my Linux
and i think that my servers support MULTICAST like
explaned on my first message (compile kernel support
and add route + test with tcpdump)

So this toolkit seems confirme the fact that my servers support multicast.
When i test on agnes with target ovea-inspiron i've:

java -cp tomcat-replication.jar MCaster 224.0.0.1 45564 ovea-inspiron
Usage MCaster [address port message]
BEGIN TO RECEIVE
SENT:ovea-inspiron1
RECEIVED:ovea-inspiron1 FROM /192.168.2.102:45564
SENT:ovea-inspiron2
BEGIN TO RECEIVE
RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564
SENT:ovea-inspiron3
BEGIN TO RECEIVE
RECEIVED:(ftcp://192.168.2.102:400catalina FROM /192.168.2.102:45564
SENT:ovea-inspiron4
BEGIN TO RECEIVE
RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564

And when i test on ovea-inspiron with target agnes i've:
java -cp tomcat-replication.jar MCaster 224.0.0.1  45566
agnes
 Usage MCaster [address port message]
BEGIN TO RECEIVE
SENT:agnes1
RECEIVED:agnes1 FROM /192.168.2.103:45566
SENT:agnes2
BEGIN TO RECEIVE
RECEIVED:agnes2 FROM /192.168.2.103:45566
SENT:agnes3
BEGIN TO RECEIVE
RECEIVED:agnes3 FROM /192.168.2.103:45566
SENT:agnes4
BEGIN TO RECEIVE
RECEIVED:agnes4 FROM /192.168.2.103:45566
SENT:agnes5
BEGIN TO RECEIVE
RECEIVED:agnes5 FROM /192.168.2.103:45566
SENT:agnes6
BEGIN TO RECEIVE
RECEIVED:agnes6 FROM /192.168.2.103:45566
SENT:agnes7
BEGIN TO RECEIVE
RECEIVED:agnes7 FROM /192.168.2.103:45566

So it's not a multicast probleme but most a configuration probleme.
ovea-inspiron sent is ok but the received is empty ?
Some suggestion(s) ?

Thank's for the progress

On 2/15/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
>
> >1)Clustering need sticky_session=true and is only design for
> failover (see servlet spec).
>
> Not true for Tomcat, using replicationMode="pooled" and
> waitForAck="true", you can do round robin non sticky load balancing as
> long as you don't have more than one thread accessing the session at any
> point in time.
>
> >INFO: Manager [/cluster-1.0-SNAPSHOT]: skipping state transfer. No
> members active in cluster group.
>
> yes, your multicast isn't working, or it should have said that you had a
> member.
> Take a look at the bottom of the page and run the MCaster test included
> in a super old version of Tomcat 4 clustering.
> http://people.apache.org/~fhanik/
>
> On multihomed hosts, it can get a little tricky to get multicasting
> working and you might have to setup some routes to help. Check with your
> sysadmin.
>
> Filip
>
>
>
> Peter Rossbach wrote:
> > Hey,
> >
> > 1)Clustering need sticky_session=true and is only design for
> > failover (see servlet spec).
> > 2)Are your sure that MULTICAST is enabled at eth0?
> >
> > regards
> > Peter
> > [EMAIL PROTECTED]
> >
> >
> >
> > Am 15.02.2006 um 02:26 schrieb David Avenante:
> >
> >> Hi,
> >>
> >> I' ve try to use Tomcat 5.5.15 in cluster mod. And after some work on
> >> configuration and test
> >> i seems to be on limit of my all possibilities ;)
> >>
> >> I try to use two tomcat in cluster with apache web server and mod_jk as
> >> connector.
> >>
> >> my Apache configuration look like :
> >>
> >>
> >> # workers.properties
> >>
> >> ps=/
> >>
> >> # List the workers name
> >> worker.list=loadbalancer
> >>
> >> # 
> >> # First worker
> >> # 
> >> worker.node01.port=8009
> >> worker.node01.host=agnes
> >> worker.node01.type=ajp13
> >> worker.node01.lbfactor=1
> >> #worker.node01.domain=cluster1
> >> # 
> >> # Second worker
> >> # 
> >> worker.node02.port=9009
> >> worker.node02.host=ovea-inspiron
> >> worker.node02.type=ajp13
> >> worker.node02.lbfactor=1
> >> #worker.node02.domain=cluster1
> >> # --
> >> # Load Balancer worker
> >> # --
> >> worker.loadbalancer.type=lb
> >> worker.loadbalancer.sticky_session=false
> >> worker.loadbalancer.balanced_workers=node01,node02
> >>
> >> As you can see i use two server ('agnes' IP : 192.168.2.102 and
> >> 'ovea-inspiron' IP : 192.168.2.103)
> >> I' ve coded a little aplication who read un file and create a
> >> sessions if
> >> session not exist.
> >>
> >> If i use the system in mod load balancing (with no cluster mod
> activate)
> >> all is great (my config is of course
> >> worker.loadbalancer.sticky_session=true
> >> )
> >>
> >> So system run with session affinitu but the two server are accessible
> ;)
> >>
> >> Now i try to configure as cluster mode with session replication
> >> (my config is now worker.loadbalancer.sticky_session=3Dfalse)
> >>
> >> I configure my to server.xml like that :
> >> agnes (IP : 192.168.2.102)
> >>
> >> 
> >>   
> >>  >>type="org.apache.catalina.UserDatabase"
> >>description="User database that can be updated and
> >> saved"
> >> 

RE: Can't get caseSensitive="false" to work

[Bob Faist]

I'm using Tomcat 5.5.14 and jdk 1.5.0_06.
 

-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 9:44 AM
To: Tomcat Users List
Subject: Re: Can't get caseSensitive="false" to work

Thanks for the response, but I still can't get it to go.  I set up
another server with the  entries in the context.xml instead of
in server.xml, so things are where the docs recomment, but still
nothing.  I've put the caseSensitive="false" in both the one in /conf,
and in META-INF with no luck. 

Are you sure it works in 5.5.12?  A couple of the posts I've seen while
googling have implied that the last version this worked in was 5.5.9.  
That would really suck if correct!  If it matters, I'm running jdk
1.5.0_06.




David Kerber wrote:

> Nobody has any suggestions on this?  I still can't get it to go.
>
> Thnaks!
> Dave
>
> David Kerber wrote:
>
>> I read the thread from last week about case-sensitivity, and did some

>> additional googling when it didn't work, but still can't get my 
>> Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be 
>> case-INsensitive for the context path.  That is a problem for my 
>> users, because we migrated them from SilverStream, which is NOT 
>> case-sensitive in the context path.  I have tried the following 
>> Context entries.  Note the entry in both the  field, and the

>>  entry (I found that one via google).  I have tried these 
>> entries eash separately, and together, and still cannot get my 
>> context path to be case-INsensitive.  I don't care if things are case

>> sensitive once they get into the app, but would really like to get 
>> the context path to not matter.
>>
>> This is in my server.xml, because I can't get the context path to 
>> work in context.xml:
>>
>> > docBase="e:\TomcatClients\WebSiraCommon\webapps\SiteData" debug="0"
>> reloadable="true" autoDeploy="true" unpackWARs="true" 
>> crossContext="false" caseSensitive="false">
>> 
>>  
>>
>> And yes, I know about the security warning about being non 
>> case-sensitive on Windows!  I also know that this context path setup 
>> is not the usual way of doing things; it's because I need to keep the

>> path the same after the migration to Tomcat.
>>
>> Thanks!
>> Dave
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


**
Confidentiality Notice
The information contained in this e-mail is confidential and intended for
use only by the person(s) or organization listed in the address. If you have
received this communication in error, please contact the sender at O'Neil &
Associates, Inc., immediately. Any copying, dissemination, or distribution
of this communication, other than by the intended recipient, is strictly
prohibited.
**


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Apache / mod_jk / Multiples instances of Tomcat

[David Avenante]

You can see this URL http://www.paulkimbrel.com/?p=3

my configuration for me with one apache in front on two tomcat (for my
tests)
is :

after install mod_jk of course ;)

httpd.conf :
# Load mod_jk module
LoadModulejk_modulemodules/mod_jk.so
JkWorkersFile /etc/apache2/workers.properties
JkLogFile /var/log/apache2/mod_jk.log
JkLogLevelERROR
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkRequestLogFormat "%w %V %T"
JkMount /cluster-1.0-SNAPSHOT/app*  loadbalancer

workers.properties :

# workers.properties

ps=/

# List the workers name
worker.list=loadbalancer
# 
# First worker
# 
worker.node01.port=8009
worker.node01.host=agnes
worker.node01.type=ajp13
worker.node01.lbfactor=1
worker.node01.domain=cluster1
# 
# Second worker
# 
worker.node02.port=9009
worker.node02.host=ovea-inspiron
worker.node02.type=ajp13
worker.node02.lbfactor=1
worker.node02.domain=cluster1
# --
# Load Balancer worker
# --
worker.loadbalancer.type=lb
worker.loadbalancer.sticky_session=true
worker.loadbalancer.balanced_workers=node01,node02

as you can see in the list of worker only the loadbalancer worker is
present.
Be carreful in your server.xml to add jvmRoute with same name of worker.

 wrote:
>
> Hi all,
>
> I'm currently trying to build a Apache load balancings against multiples
> instances of Tomcat.
>
> On my host, i have three instances of Tomcat (ie using CATALINA_BASE
> variable), each listening on differents ports for AJP Connector.
> On the same server, i have an Apache using Mod_jk.
>
> Is it possible to configure load balancing across the three instances of
> Tomcat using mod_jk ?
>
> Morever, in the worker.properties, i don't known how to configure
> worker.tomcat_home as it is different for each instance of Tomcat ?
>
> Any help would be appreciate, Any Internet Links ..
>
> Kind Regards,
>
> Farid
>
>

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason that at then
end of loading each JSP firefox expires my session.  I use some meta tags
(, , ) and also set the corresponding header values using
response.setHeader but even if I remove them nothing changes.

Michael

>-Original Message-
>From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:10
>To: Tomcat Users List
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>Are you blocking cookies at the browser?
>
>Earnie!
>
>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 15, 2006 10:06 AM
>To: 'Tomcat Users List'
>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
> Anybody has an idea what could be causing what I describe in 
>the below two emails?
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 13:10
>>To: 'Tomcat Users List'
>>Subject: RE: Session Problems with Firefox
>>
>>Further to my below email I have put in some code to check the HTTP 
>>headers in each case (IE and FireFox).
>>
>>These are:
>>
>>IE
>>accept: */*
>>accept-language: en-gb
>>accept-encoding: gzip, deflate
>>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
>>.NET CLR 1.1.4322; InfoPath.1)
>>host: localhost
>>connection: Keep-Alive
>>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>>
>>FireFox
>>host: localhost
>>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
>>Gecko/20050919 Firefox/1.0.7
>>accept:
>>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>text/plain;q=
>>0.8,image/png,*/*;q=0.5
>>accept-language: en-gb,en;q=0.5
>>accept-encoding: gzip,deflate
>>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>keep-alive: 300
>>connection: keep-alive
>>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>>cache-control: max-age=0
>>
>>
>>I wonder whether the keep-alive which exists in the case of 
>FireFox but 
>>not in the case of IE could be the cause of my problems.
>>
>>Michael
>>
>>
>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 11:27
>>>To: users@tomcat.apache.org
>>>Subject: Session Problems with Firefox
>>>
>>>Hello,
>>>
>>>I have some problems with session management when our application 
>>>runsin Firefox.
>>>
>>>Basically, what happens is that after I set in the session some 
>>>attributes/beans which are needed down the application, I
>>check in all
>>>JSPs and servlets that an old session is still there by using
>>> if (request.getSession(false)==null){
>>> 
>>>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>>>
>>>}
>>>
>>>With IE all works fine, however with Firefox, it seems that
>>the session
>>>is re-initialised whenever the client/browser requests a new 
>page.  I 
>>>checked this by printing the session id in the log on each page and 
>>>with IE it does not change, while with Firefox it changes.
>>>
>>>I checked my firefox settings for cookies and all look ok.
>>>
>>>Anybody has a clue of what I might be doing wrong?
>>>
>>>Regards,
>>>Michael
>>>
>>>
>>>-
>>>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]
>>
>
>
>-
>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]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can't get caseSensitive="false" to work

[David Kerber]

Ok, thanks.  Obviously I'm missing something, then.  I'll keep digging...

Bob Faist wrote:


I'm using Tomcat 5.5.14 and jdk 1.5.0_06.


-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 9:44 AM

To: Tomcat Users List
Subject: Re: Can't get caseSensitive="false" to work

Thanks for the response, but I still can't get it to go.  I set up
another server with the  entries in the context.xml instead of
in server.xml, so things are where the docs recomment, but still
nothing.  I've put the caseSensitive="false" in both the one in /conf,
and in META-INF with no luck. 


Are you sure it works in 5.5.12?  A couple of the posts I've seen while
googling have implied that the last version this worked in was 5.5.9.  
That would really suck if correct!  If it matters, I'm running jdk

1.5.0_06.




David Kerber wrote:

 


Nobody has any suggestions on this?  I still can't get it to go.

Thnaks!
Dave

David Kerber wrote:

   


I read the thread from last week about case-sensitivity, and did some
 



 

additional googling when it didn't work, but still can't get my 
Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be 
case-INsensitive for the context path.  That is a problem for my 
users, because we migrated them from SilverStream, which is NOT 
case-sensitive in the context path.  I have tried the following 
Context entries.  Note the entry in both the  field, and the
 



 

 entry (I found that one via google).  I have tried these 
entries eash separately, and together, and still cannot get my 
context path to be case-INsensitive.  I don't care if things are case
 



 

sensitive once they get into the app, but would really like to get 
the context path to not matter.


This is in my server.xml, because I can't get the context path to 
work in context.xml:


   docBase="e:\TomcatClients\WebSiraCommon\webapps\SiteData" debug="0"
reloadable="true" autoDeploy="true" unpackWARs="true" 
crossContext="false" caseSensitive="false">

   


And yes, I know about the security warning about being non 
case-sensitive on Windows!  I also know that this context path setup 
is not the usual way of doing things; it's because I need to keep the
 



 


path the same after the migration to Tomcat.

Thanks!
Dave
 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Earnie Dyke]

The META tags should not have an effect on cookies. Firefox would not be the 
one that expires your session, Tomcat would. Do you have a session timeout 
specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason that at then
end of loading each JSP firefox expires my session.  I use some meta tags
(, , ) and also set the corresponding header values using
response.setHeader but even if I remove them nothing changes.

Michael

>-Original Message-
>From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:10
>To: Tomcat Users List
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>Are you blocking cookies at the browser?
>
>Earnie!
>
>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 15, 2006 10:06 AM
>To: 'Tomcat Users List'
>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
> Anybody has an idea what could be causing what I describe in 
>the below two emails?
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 13:10
>>To: 'Tomcat Users List'
>>Subject: RE: Session Problems with Firefox
>>
>>Further to my below email I have put in some code to check the HTTP 
>>headers in each case (IE and FireFox).
>>
>>These are:
>>
>>IE
>>accept: */*
>>accept-language: en-gb
>>accept-encoding: gzip, deflate
>>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
>>.NET CLR 1.1.4322; InfoPath.1)
>>host: localhost
>>connection: Keep-Alive
>>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>>
>>FireFox
>>host: localhost
>>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
>>Gecko/20050919 Firefox/1.0.7
>>accept:
>>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>text/plain;q=
>>0.8,image/png,*/*;q=0.5
>>accept-language: en-gb,en;q=0.5
>>accept-encoding: gzip,deflate
>>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>keep-alive: 300
>>connection: keep-alive
>>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>>cache-control: max-age=0
>>
>>
>>I wonder whether the keep-alive which exists in the case of 
>FireFox but 
>>not in the case of IE could be the cause of my problems.
>>
>>Michael
>>
>>
>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 11:27
>>>To: users@tomcat.apache.org
>>>Subject: Session Problems with Firefox
>>>
>>>Hello,
>>>
>>>I have some problems with session management when our application 
>>>runsin Firefox.
>>>
>>>Basically, what happens is that after I set in the session some 
>>>attributes/beans which are needed down the application, I
>>check in all
>>>JSPs and servlets that an old session is still there by using
>>> if (request.getSession(false)==null){
>>> 
>>>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>>>
>>>}
>>>
>>>With IE all works fine, however with Firefox, it seems that
>>the session
>>>is re-initialised whenever the client/browser requests a new 
>page.  I 
>>>checked this by printing the session id in the log on each page and 
>>>with IE it does not change, while with Firefox it changes.
>>>
>>>I checked my firefox settings for cookies and all look ok.
>>>
>>>Anybody has a clue of what I might be doing wrong?
>>>
>>>Regards,
>>>Michael
>>>
>>>
>>>-
>>>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]
>>
>
>
>-
>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]
>


-
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: Tomcat 5.5.15 Clustering ?

[Filip Hanik - Dev Lists]

It is a multicast problem, your second box is not receiving any 
multicast messages, only from itself.


To run this test properly, you will need to shutdown your tomcats, then 
run MCaster on both machines at the same time,
if both machines are not receiving messages from each other (like your 
example below) then you have a multicast problem


Filip


David Avenante wrote:

Thank you very much for the toolkit ;)
My feeling was also on my multicast support.
But i' ve read more documentation for my Linux
and i think that my servers support MULTICAST like
explaned on my first message (compile kernel support
and add route + test with tcpdump)

So this toolkit seems confirme the fact that my servers support multicast.
When i test on agnes with target ovea-inspiron i've:

java -cp tomcat-replication.jar MCaster 224.0.0.1 45564 ovea-inspiron
Usage MCaster [address port message]
BEGIN TO RECEIVE
SENT:ovea-inspiron1
RECEIVED:ovea-inspiron1 FROM /192.168.2.102:45564
SENT:ovea-inspiron2
BEGIN TO RECEIVE
RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564
SENT:ovea-inspiron3
BEGIN TO RECEIVE
RECEIVED:(ftcp://192.168.2.102:400catalina FROM /192.168.2.102:45564
SENT:ovea-inspiron4
BEGIN TO RECEIVE
RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564

And when i test on ovea-inspiron with target agnes i've:
java -cp tomcat-replication.jar MCaster 224.0.0.1  45566
agnes
 Usage MCaster [address port message]
BEGIN TO RECEIVE
SENT:agnes1
RECEIVED:agnes1 FROM /192.168.2.103:45566
SENT:agnes2
BEGIN TO RECEIVE
RECEIVED:agnes2 FROM /192.168.2.103:45566
SENT:agnes3
BEGIN TO RECEIVE
RECEIVED:agnes3 FROM /192.168.2.103:45566
SENT:agnes4
BEGIN TO RECEIVE
RECEIVED:agnes4 FROM /192.168.2.103:45566
SENT:agnes5
BEGIN TO RECEIVE
RECEIVED:agnes5 FROM /192.168.2.103:45566
SENT:agnes6
BEGIN TO RECEIVE
RECEIVED:agnes6 FROM /192.168.2.103:45566
SENT:agnes7
BEGIN TO RECEIVE
RECEIVED:agnes7 FROM /192.168.2.103:45566

So it's not a multicast probleme but most a configuration probleme.
ovea-inspiron sent is ok but the received is empty ?
Some suggestion(s) ?

Thank's for the progress

On 2/15/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
  

1)Clustering need sticky_session=true and is only design for
  

failover (see servlet spec).

Not true for Tomcat, using replicationMode="pooled" and
waitForAck="true", you can do round robin non sticky load balancing as
long as you don't have more than one thread accessing the session at any
point in time.



INFO: Manager [/cluster-1.0-SNAPSHOT]: skipping state transfer. No
  

members active in cluster group.

yes, your multicast isn't working, or it should have said that you had a
member.
Take a look at the bottom of the page and run the MCaster test included
in a super old version of Tomcat 4 clustering.
http://people.apache.org/~fhanik/

On multihomed hosts, it can get a little tricky to get multicasting
working and you might have to setup some routes to help. Check with your
sysadmin.

Filip



Peter Rossbach wrote:


Hey,

1)Clustering need sticky_session=true and is only design for
failover (see servlet spec).
2)Are your sure that MULTICAST is enabled at eth0?

regards
Peter
[EMAIL PROTECTED]



Am 15.02.2006 um 02:26 schrieb David Avenante:

  

Hi,

I' ve try to use Tomcat 5.5.15 in cluster mod. And after some work on
configuration and test
i seems to be on limit of my all possibilities ;)

I try to use two tomcat in cluster with apache web server and mod_jk as
connector.

my Apache configuration look like :


# workers.properties

ps=/

# List the workers name
worker.list=loadbalancer

# 
# First worker
# 
worker.node01.port=8009
worker.node01.host=agnes
worker.node01.type=ajp13
worker.node01.lbfactor=1
#worker.node01.domain=cluster1
# 
# Second worker
# 
worker.node02.port=9009
worker.node02.host=ovea-inspiron
worker.node02.type=ajp13
worker.node02.lbfactor=1
#worker.node02.domain=cluster1
# --
# Load Balancer worker
# --
worker.loadbalancer.type=lb
worker.loadbalancer.sticky_session=false
worker.loadbalancer.balanced_workers=node01,node02

As you can see i use two server ('agnes' IP : 192.168.2.102 and
'ovea-inspiron' IP : 192.168.2.103)
I' ve coded a little aplication who read un file and create a
sessions if
session not exist.

If i use the system in mod load balancing (with no cluster mod


activate)


all is great (my config is of course
worker.loadbalancer.sticky_session=true
)

So system run with session affinitu but the two server are accessible


;)


Now i try to configure as cluster mode with session replication
(my config is now worker.loadbalancer.sticky_session=3Dfalse)

I configure my to server.xml like that :
agnes (IP : 192.168.2.102)


  


  

  






  

  
 







  

  



ovea-inspiron (IP : 

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

It is 30 minutes.  If I do request.getSession().getMaxInactiveInterval() I
get 1800 (seconds I guess) which is the correct value for 30 minutes. 

Michael

>-Original Message-
>From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:25
>To: Tomcat Users List
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>The META tags should not have an effect on cookies. Firefox 
>would not be the one that expires your session, Tomcat would. 
>Do you have a session timeout specified in your application?
>
>Earnie!
>
>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 15, 2006 10:19 AM
>To: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
>Hi Earnie,
>
>Cookies are allowed at the browser.  It seems for some reason 
>that at then end of loading each JSP firefox expires my 
>session.  I use some meta tags (HTTP-EQUIV="Cache-Control" CONTENT="No-Cache">, HTTP-EQUIV="Pragma" CONTENT="No-Cache">, CONTENT="-1">) and also set the corresponding header values 
>using response.setHeader but even if I remove them nothing changes.
>
>Michael
>
>>-Original Message-
>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:10
>>To: Tomcat Users List
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>Are you blocking cookies at the browser?
>>
>>Earnie!
>>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: Wednesday, February 15, 2006 10:06 AM
>>To: 'Tomcat Users List'
>>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>
>> Anybody has an idea what could be causing what I describe in 
>the below 
>>two emails?
>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 13:10
>>>To: 'Tomcat Users List'
>>>Subject: RE: Session Problems with Firefox
>>>
>>>Further to my below email I have put in some code to check the HTTP 
>>>headers in each case (IE and FireFox).
>>>
>>>These are:
>>>
>>>IE
>>>accept: */*
>>>accept-language: en-gb
>>>accept-encoding: gzip, deflate
>>>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
>>>.NET CLR 1.1.4322; InfoPath.1)
>>>host: localhost
>>>connection: Keep-Alive
>>>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>>>
>>>FireFox
>>>host: localhost
>>>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; 
>rv:1.7.12)
>>>Gecko/20050919 Firefox/1.0.7
>>>accept:
>>>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>>text/plain;q=
>>>0.8,image/png,*/*;q=0.5
>>>accept-language: en-gb,en;q=0.5
>>>accept-encoding: gzip,deflate
>>>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>keep-alive: 300
>>>connection: keep-alive
>>>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>>>cache-control: max-age=0
>>>
>>>
>>>I wonder whether the keep-alive which exists in the case of
>>FireFox but
>>>not in the case of IE could be the cause of my problems.
>>>
>>>Michael
>>>
>>>
>>>
-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
>>>check in all
JSPs and servlets that an old session is still there by using
if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));

}

With IE all works fine, however with Firefox, it seems that
>>>the session
is re-initialised whenever the client/browser requests a new
>>page.  I
checked this by printing the session id in the log on each page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael



>-
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]
>>>
>>
>>
>>-
>>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: password protection

[Zohar Amir]

Thank you again,
I've set a security-constraint on the context (in the web.xml), and it works 
OK now.

What I'd like to know is:
1. Can I do it anywhere else other than the web.xml, so that the deployer 
can control this and not the developer?
2. Can I set it for a group of contexts, so that they will all be able to 
use request.getPricipal() and have the user name that logged in?



- Original Message - 
From: "David Delbecq" <[EMAIL PROTECTED]>

To: "Tomcat Users List" 
Sent: Wednesday, February 15, 2006 3:05 PM
Subject: Re: password protection



http://www.onjava.com/pub/a/onjava/2001/07/24/tomcat.html
http://www.cafesoft.com/products/cams/tomcat-security.html

for other ones, use favorite search engine.

Zohar Amir a écrit :


Thanks,
Where can I find info on how exactly to do this? maybe an example...?
- Original Message - From: "David Delbecq" <[EMAIL PROTECTED]>
To: "Tomcat Users List" 
Sent: Wednesday, February 15, 2006 2:52 PM
Subject: Re: password protection



Zohar Amir a écrit :


Hello,
I'm using tomcat 5.5.15 on Win XP.
I have a servlet that is deployed on a certain context. I would like
anyone trying to use that servlet use a username-password. how do I do
this?



set a security-constrain in WEB-INF/web.xml


What if I need to protect a jsp that is part of the servlet?



You mean to prevent direct loading of a jsp included by your servlet?
Same thing, add a security-constraint to the url of your jsp.


Thanks,
Zohar.
-
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]




-
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]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[alexandre.tastet]

Are you using SSL connection ?

-Message d'origine-
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
ache.org]De la part de Michael Andreas Omerou
Envoye : mercredi 15 fevrier 2006 16:34
A : 'Tomcat Users List'
Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


It is 30 minutes.  If I do request.getSession().getMaxInactiveInterval() I
get 1800 (seconds I guess) which is the correct value for 30 minutes. 

Michael

>-Original Message-
>From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:25
>To: Tomcat Users List
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>The META tags should not have an effect on cookies. Firefox 
>would not be the one that expires your session, Tomcat would. 
>Do you have a session timeout specified in your application?
>
>Earnie!
>
>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 15, 2006 10:19 AM
>To: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
>Hi Earnie,
>
>Cookies are allowed at the browser.  It seems for some reason 
>that at then end of loading each JSP firefox expires my 
>session.  I use some meta tags (HTTP-EQUIV="Cache-Control" CONTENT="No-Cache">, HTTP-EQUIV="Pragma" CONTENT="No-Cache">, CONTENT="-1">) and also set the corresponding header values 
>using response.setHeader but even if I remove them nothing changes.
>
>Michael
>
>>-Original Message-
>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:10
>>To: Tomcat Users List
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>Are you blocking cookies at the browser?
>>
>>Earnie!
>>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: Wednesday, February 15, 2006 10:06 AM
>>To: 'Tomcat Users List'
>>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>
>> Anybody has an idea what could be causing what I describe in 
>the below 
>>two emails?
>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 13:10
>>>To: 'Tomcat Users List'
>>>Subject: RE: Session Problems with Firefox
>>>
>>>Further to my below email I have put in some code to check the HTTP 
>>>headers in each case (IE and FireFox).
>>>
>>>These are:
>>>
>>>IE
>>>accept: */*
>>>accept-language: en-gb
>>>accept-encoding: gzip, deflate
>>>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
>>>.NET CLR 1.1.4322; InfoPath.1)
>>>host: localhost
>>>connection: Keep-Alive
>>>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>>>
>>>FireFox
>>>host: localhost
>>>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; 
>rv:1.7.12)
>>>Gecko/20050919 Firefox/1.0.7
>>>accept:
>>>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>>text/plain;q=
>>>0.8,image/png,*/*;q=0.5
>>>accept-language: en-gb,en;q=0.5
>>>accept-encoding: gzip,deflate
>>>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>>keep-alive: 300
>>>connection: keep-alive
>>>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>>>cache-control: max-age=0
>>>
>>>
>>>I wonder whether the keep-alive which exists in the case of
>>FireFox but
>>>not in the case of IE could be the cause of my problems.
>>>
>>>Michael
>>>
>>>
>>>
-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
>>>check in all
JSPs and servlets that an old session is still there by using
if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));

}

With IE all works fine, however with Firefox, it seems that
>>>the session
is re-initialised whenever the client/browser requests a new
>>page.  I
checked this by printing the session id in the log on each page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael



>-
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]
>>>
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>F

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

In principle,  one could try the below (a stand-alone jsp) which resides in
my application with a timeout of 30 minutes:

<[EMAIL PROTECTED] import="java.util.Enumeration,java.util.Date"
contentType="text/html"%>
<[EMAIL PROTECTED] pageEncoding="UTF-8"%>

JSP Page

<%

  Enumeration reqHeaderNames = request.getHeaderNames();
  String curHeaderName;
while (reqHeaderNames.hasMoreElements()){
curHeaderName=(String) reqHeaderNames.nextElement();
System.out.println(curHeaderName + ": " +
request.getHeader(curHeaderName));
}
  
  System.out.println("TestFirefox.jsp Session ID Value: "+
request.getSession(false).getId());
  
%>
TEST FIREFOX LOADED





The above creates a new session wheneven reloaded in Firefox while in IE it
keeps the same.

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:34
>To: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>It is 30 minutes.  If I do 
>request.getSession().getMaxInactiveInterval() I get 1800 
>(seconds I guess) which is the correct value for 30 minutes. 
>
>Michael
>
>>-Original Message-
>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:25
>>To: Tomcat Users List
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>The META tags should not have an effect on cookies. Firefox would not 
>>be the one that expires your session, Tomcat would.
>>Do you have a session timeout specified in your application?
>>
>>Earnie!
>>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: Wednesday, February 15, 2006 10:19 AM
>>To: 'Tomcat Users List'
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>
>>Hi Earnie,
>>
>>Cookies are allowed at the browser.  It seems for some reason that at 
>>then end of loading each JSP firefox expires my session.  I use some 
>>meta tags (CONTENT="No-Cache">, >HTTP-EQUIV="Pragma" CONTENT="No-Cache">, >CONTENT="-1">) and also set the corresponding header values using 
>>response.setHeader but even if I remove them nothing changes.
>>
>>Michael
>>
>>>-Original Message-
>>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 17:10
>>>To: Tomcat Users List
>>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>Are you blocking cookies at the browser?
>>>
>>>Earnie!
>>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, February 15, 2006 10:06 AM
>>>To: 'Tomcat Users List'
>>>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>
>>> Anybody has an idea what could be causing what I describe in
>>the below
>>>two emails?
>>>
-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
>>rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>>>text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
>>>FireFox but
not in the case of IE could be the cause of my problems.

Michael



>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: 15 February 2006 11:27
>To: users@tomcat.apache.org
>Subject: Session Problems with Firefox
>
>Hello,
>
>I have some problems with session management when our application 
>runsin Firefox.
>
>Basically, what happens is that after I set in the session some 
>attributes/beans which are needed down the application, I
check in all
>JSPs and servlets that an old session is still there by using
>   if (request.getSession(false)==null){
> 
>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>
>}
>
>With IE all works fine, however with Firefox, it seems that
the session
>is re-initialised whenever the client/br

Re: password protection

[David Delbecq]

Zohar Amir a écrit :

> Thank you again,
> I've set a security-constraint on the context (in the web.xml), and it
> works OK now.
> What I'd like to know is:
> 1. Can I do it anywhere else other than the web.xml, so that the
> deployer can control this and not the developer?

No, but on some webapplication container there is the possibility to map
from application roles to real roles (eg, the 'admin' role of app XYZ is
in fact the role PublicationManager). But am not sure tomcat handles this.

> 2. Can I set it for a group of contexts, so that they will all be able
> to use request.getPricipal() and have the user name that logged in?

When authenticated, request.getPrincipal() returns the authenticated
principal

>
>
> - Original Message - From: "David Delbecq" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" 
> Sent: Wednesday, February 15, 2006 3:05 PM
> Subject: Re: password protection
>
>
>> http://www.onjava.com/pub/a/onjava/2001/07/24/tomcat.html
>> http://www.cafesoft.com/products/cams/tomcat-security.html
>>
>> for other ones, use favorite search engine.
>>
>> Zohar Amir a écrit :
>>
>>> Thanks,
>>> Where can I find info on how exactly to do this? maybe an example...?
>>> - Original Message - From: "David Delbecq" <[EMAIL PROTECTED]>
>>> To: "Tomcat Users List" 
>>> Sent: Wednesday, February 15, 2006 2:52 PM
>>> Subject: Re: password protection
>>>
>>>
 Zohar Amir a écrit :

> Hello,
> I'm using tomcat 5.5.15 on Win XP.
> I have a servlet that is deployed on a certain context. I would like
> anyone trying to use that servlet use a username-password. how do
> I do
> this?



 set a security-constrain in WEB-INF/web.xml

> What if I need to protect a jsp that is part of the servlet?



 You mean to prevent direct loading of a jsp included by your servlet?
 Same thing, add a security-constraint to the url of your jsp.

> Thanks,
> Zohar.
> -
> 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]


>>>
>>> -
>>> 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]
>>
>>
>
> -
> 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]

Tomcat & JNDI -> javax.naming.NamingException: Cannot create resource instance

[Claus Giesenberg (1&1 Privat)]

Hi !

While writing a custom JNDI Resource factory, Tomcat 5 runs into an 
exception i can't explain:


 javax.naming.NamingException: Cannot create resource instance
   at 
org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:132)
   at 
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)


this exception will be thrown by the following code lines:

   private void initDBConnectionPool(){
  try {   
   Context ctx = new InitialContext();   
   Context envCtx = (Context) ctx.lookup("java:comp/env");

   thePool = (DBConnectionPool)
   envCtx.lookup("webarts/DBConnectionPool");   
   }  catch (NamingException e) {
   e.printStackTrace();   
   }

   }



To configure my resource factory i've added the following lines into to 
_server.xml_:


auth="Container" type="de.webarts.DBConnectionPool.DBConnectionPool"/>



factoryde.webarts.DBConnectionPool.DBConnectionPoolSingleton

   
driverClassNameoracle.jdbc.driver.OracleDriver
   
driverNamejdbc:oracle:thin:@ 

   
user##
   
password##
   
poolSize10
   
maxSize30   
   
initSize5
   
expiryTime18000
  
   
poolNameWebArts_DBConnectionPool
   
  



For declaring the custom resource factory i have added the following 
lines into the _web.xml_


   
   DBConnectionPool Factory
   webarts/DBConnectionPool
   de.webarts.DBConnectionPool.DBConnectionPool
   Container
   

My factory class looks like that:


package de.webarts.DBConnectionPool;
import javax.naming.*;
import java.util.Enumeration;
import java.util.Hashtable;
import de.webarts.DBConnectionPool.*;


public final class  DBConnectionPoolSingleton implements ObjectFactory {
  
   private static DBConnectionPool theStaticPool = null;
  
   private DBConnectionPoolSingleton(){   
   }
  
   public static DBConnectionPool createDBConnectionPool(String name, 
int poolSize, int maxSize, int initSize, int expiryTime, String url, 
String passwd, String user){

   if (theStaticPool != null) {
   theStaticPool =  new DBConnectionPool(name, poolSize, 
maxSize, initSize, expiryTime, url, passwd, user);

   }
   return theStaticPool;
   }


   public Object getObjectInstance(Object obj, Name name, Context 
nameCtx, Hashtable environment) throws Exception {


   Reference ref = (Reference) obj;
   Enumeration enumRef = ref.getAll();
  
   String poolName= "WebArts DBConnectionPool";
// "poolName"
   String driverClassName  = null;   // 
"driverClass"
   String driverName  = null;
   // "driverName"
   String user = null;
   // "user"   
   String password = null;   
   // "password"
  
   int poolSize = 0;   // "poolSize"

   int maxSize  = 0;   // "maxSize"
   int initSize = 0;  // "intSize"
   int expiryTime = 18000; // "expiryTime"
  
  
   // extract the values for the parameters specified in server.xml

   // and create a database connection pool as singleton.
   while (enumRef.hasMoreElements()) {
   RefAddr refAddr = (RefAddr) enumRef.nextElement();
   String type  = refAddr.getType();   
   String value = (String)refAddr.getContent();
  
   if (type.equals("poolName")) {

   poolName = value;
   } else
   if (type.equals("driverClassName")) {
   driverClassName = value;
   } else
   if (type.equals("driverName")) {
   driverName = value;
   } else
   if (type.equals("user")) {
   user = value;   
   } else

   if (type.equals("password")) {
   password = value;
   } else
   if (type.equals("poolSize")) {
   poolSize = 
Integer.getInteger(value).intValue();

   } else
   if (type.equals("maxSize")) {
   maxSize = 
Integer.getInteger(value).intValue();

   } else
   if (type.equals("initSize")) {
   initSize = 
Integer.getInteger(value).intValue();

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

Not at the stage that this problem occurs.  SSL is used further on when the
user logs in to make a payment but the SSL pages are never reached with
FireFox because of the early timeout.  With IE all is ok, including SSL
connections. 

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:43
>To: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>Are you using SSL connection ?
>
>-Message d'origine-
>De :
>[EMAIL PROTECTED]
pache.org
>[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
tomcat.ap
>ache.org]De la part de Michael Andreas Omerou Envoye : 
>mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
>Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
>It is 30 minutes.  If I do 
>request.getSession().getMaxInactiveInterval() I get 1800 
>(seconds I guess) which is the correct value for 30 minutes. 
>
>Michael
>
>>-Original Message-
>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:25
>>To: Tomcat Users List
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>The META tags should not have an effect on cookies. Firefox would not 
>>be the one that expires your session, Tomcat would.
>>Do you have a session timeout specified in your application?
>>
>>Earnie!
>>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: Wednesday, February 15, 2006 10:19 AM
>>To: 'Tomcat Users List'
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>
>>Hi Earnie,
>>
>>Cookies are allowed at the browser.  It seems for some reason that at 
>>then end of loading each JSP firefox expires my session.  I use some 
>>meta tags (CONTENT="No-Cache">, >HTTP-EQUIV="Pragma" CONTENT="No-Cache">, >CONTENT="-1">) and also set the corresponding header values using 
>>response.setHeader but even if I remove them nothing changes.
>>
>>Michael
>>
>>>-Original Message-
>>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 17:10
>>>To: Tomcat Users List
>>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>Are you blocking cookies at the browser?
>>>
>>>Earnie!
>>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, February 15, 2006 10:06 AM
>>>To: 'Tomcat Users List'
>>>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>
>>> Anybody has an idea what could be causing what I describe in
>>the below
>>>two emails?
>>>
-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
>>rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
>>>text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
>>>FireFox but
not in the case of IE could be the cause of my problems.

Michael



>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: 15 February 2006 11:27
>To: users@tomcat.apache.org
>Subject: Session Problems with Firefox
>
>Hello,
>
>I have some problems with session management when our application 
>runsin Firefox.
>
>Basically, what happens is that after I set in the session some 
>attributes/beans which are needed down the application, I
check in all
>JSPs and servlets that an old session is still there by using
>   if (request.getSession(false)==null){
> 
>response.sendRedirect(response.encodeRedirectURL("timeout.jsp"));
>
>}
>
>With IE all works fine, however with Firefox, it seems that
the session
>is re-initialised whenever the client/browser requests a new
>>>page.  I
>checked this by printing the session id in the log on each 
>page and 
>with IE it does not change, while with Firefox it changes.
>
>I checked my firefox settings fo

Re: Tomcat 5.5.15 Clustering ?

[David Avenante]

I try it and the multicast seems OK ?

On 2/15/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
>
> It is a multicast problem, your second box is not receiving any
> multicast messages, only from itself.
>
> To run this test properly, you will need to shutdown your tomcats, then
> run MCaster on both machines at the same time,
> if both machines are not receiving messages from each other (like your
> example below) then you have a multicast problem
>
> Filip
>
>
> David Avenante wrote:
> > Thank you very much for the toolkit ;)
> > My feeling was also on my multicast support.
> > But i' ve read more documentation for my Linux
> > and i think that my servers support MULTICAST like
> > explaned on my first message (compile kernel support
> > and add route + test with tcpdump)
> >
> > So this toolkit seems confirme the fact that my servers support
> multicast.
> > When i test on agnes with target ovea-inspiron i've:
> >
> > java -cp tomcat-replication.jar MCaster 224.0.0.1 45564 ovea-inspiron
> > Usage MCaster [address port message]
> > BEGIN TO RECEIVE
> > SENT:ovea-inspiron1
> > RECEIVED:ovea-inspiron1 FROM /192.168.2.102:45564
> > SENT:ovea-inspiron2
> > BEGIN TO RECEIVE
> > RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564
> > SENT:ovea-inspiron3
> > BEGIN TO RECEIVE
> > RECEIVED:(ftcp://192.168.2.102:400catalina FROM /192.168.2.102:45564
> > SENT:ovea-inspiron4
> > BEGIN TO RECEIVE
> > RECEIVED:(gtcp://192.168.2.103:400cluster1 FROM /192.168.2.103:45564
> >
> > And when i test on ovea-inspiron with target agnes i've:
> > java -cp tomcat-replication.jar MCaster 224.0.0.1 
> 45566
> > agnes
> >  Usage MCaster [address port message]
> > BEGIN TO RECEIVE
> > SENT:agnes1
> > RECEIVED:agnes1 FROM /192.168.2.103:45566
> > SENT:agnes2
> > BEGIN TO RECEIVE
> > RECEIVED:agnes2 FROM /192.168.2.103:45566
> > SENT:agnes3
> > BEGIN TO RECEIVE
> > RECEIVED:agnes3 FROM /192.168.2.103:45566
> > SENT:agnes4
> > BEGIN TO RECEIVE
> > RECEIVED:agnes4 FROM /192.168.2.103:45566
> > SENT:agnes5
> > BEGIN TO RECEIVE
> > RECEIVED:agnes5 FROM /192.168.2.103:45566
> > SENT:agnes6
> > BEGIN TO RECEIVE
> > RECEIVED:agnes6 FROM /192.168.2.103:45566
> > SENT:agnes7
> > BEGIN TO RECEIVE
> > RECEIVED:agnes7 FROM /192.168.2.103:45566
> >
> > So it's not a multicast probleme but most a configuration probleme.
> > ovea-inspiron sent is ok but the received is empty ?
> > Some suggestion(s) ?
> >
> > Thank's for the progress
> >
> > On 2/15/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> >
> >>> 1)Clustering need sticky_session=true and is only design for
> >>>
> >> failover (see servlet spec).
> >>
> >> Not true for Tomcat, using replicationMode="pooled" and
> >> waitForAck="true", you can do round robin non sticky load balancing as
> >> long as you don't have more than one thread accessing the session at
> any
> >> point in time.
> >>
> >>
> >>> INFO: Manager [/cluster-1.0-SNAPSHOT]: skipping state transfer. No
> >>>
> >> members active in cluster group.
> >>
> >> yes, your multicast isn't working, or it should have said that you had
> a
> >> member.
> >> Take a look at the bottom of the page and run the MCaster test included
> >> in a super old version of Tomcat 4 clustering.
> >> http://people.apache.org/~fhanik/
> >>
> >> On multihomed hosts, it can get a little tricky to get multicasting
> >> working and you might have to setup some routes to help. Check with
> your
> >> sysadmin.
> >>
> >> Filip
> >>
> >>
> >>
> >> Peter Rossbach wrote:
> >>
> >>> Hey,
> >>>
> >>> 1)Clustering need sticky_session=true and is only design for
> >>> failover (see servlet spec).
> >>> 2)Are your sure that MULTICAST is enabled at eth0?
> >>>
> >>> regards
> >>> Peter
> >>> [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>> Am 15.02.2006 um 02:26 schrieb David Avenante:
> >>>
> >>>
>  Hi,
> 
>  I' ve try to use Tomcat 5.5.15 in cluster mod. And after some work on
>  configuration and test
>  i seems to be on limit of my all possibilities ;)
> 
>  I try to use two tomcat in cluster with apache web server and mod_jk
> as
>  connector.
> 
>  my Apache configuration look like :
> 
> 
>  # workers.properties
> 
>  ps=/
> 
>  # List the workers name
>  worker.list=loadbalancer
> 
>  # 
>  # First worker
>  # 
>  worker.node01.port=8009
>  worker.node01.host=agnes
>  worker.node01.type=ajp13
>  worker.node01.lbfactor=1
>  #worker.node01.domain=cluster1
>  # 
>  # Second worker
>  # 
>  worker.node02.port=9009
>  worker.node02.host=ovea-inspiron
>  worker.node02.type=ajp13
>  worker.node02.lbfactor=1
>  #worker.node02.domain=cluster1
>  # --
>  # Load Balancer worker
>  # --
>  worker.loadbalancer.type=lb
>  worker.loadbalancer.sticky_session=false
> >

Re: Tomcat 5.5.15 Clustering ?

[David Avenante]

Yes all right !

INFO: Register manager /cluster-1.0-SNAPSHOT to cluster element Host with
name localhost
Feb 15, 2006 10:47:32 AM org.apache.catalina.cluster.session.DeltaManagerstart

But Why 
my mcastAddress is good !

now i' ve a new error

Feb 15, 2006 10:50:41 AM
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThreadpushQueuedMessages
WARNING: Unable to asynchronously send session with id=[GET-ALL-/cluster-
1.0-SNAPSHOT] - message will be ignored.
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)

but it's a big progress ;)

I got to verifiy if my ntp synchronisation between my server is OK ;)

Thank you very much.





On 2/15/06, Peter Rossbach <[EMAIL PROTECTED]> wrote:
>
> Can you test your config without the parameter mcastBindAddress="xx"?
>
>
> Peter
>
>
>
> Am 15.02.2006 um 14:35 schrieb David Avenante:
>
> > Yes MULTICAST is enabled i see that by too fact :
> >
> > first,
> > ifconfig eth0 :
> >
> > eth0  Link encap:Ethernet  HWaddr 00:13:D4:45:A6:3F
> >   inet addr:192.168.2.102  Bcast:192.168.2.255  Mask:
> > 255.255.255.0
> >   UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST  MTU:1500
> > Metric:1
> >   RX packets:264493 errors:0 dropped:0 overruns:0 frame:0
> >   TX packets:292063 errors:0 dropped:0 overruns:0 carrier:0
> >   collisions:0 txqueuelen:1000
> >   RX bytes:98079150 (93.5 Mb)  TX bytes:41007393 (39.1 Mb)
> >
> > ALLMULTI and MULTICAST is enabled on two serveur interface.
> >
> > second,
> >
> > as you see in my first post tcpdump track the UDP messages send
> > between
> > server.
> >
> >
> > For sticky_session=true i' m not agree with you.
> > In the connector documentation (see
> > http://tomcat.apache.org/connectors-doc/config/workers.html)
> > => Set sticky_session to *False* when Tomcat is using a Session
> > Manager
> > which can persist session data across multiple instances of Tomcat
> > It' s my situation.
> >
> > So i' m alway in the trouble by thanks a lot for the verification ;)
> >
> >
> > On 2/15/06, Peter Rossbach <[EMAIL PROTECTED]> wrote:
> >>
> >> Hey,
> >>
> >> 1)  Clustering need sticky_session=true and is only design for
> >> failover (see servlet spec).
> >> 2)  Are your sure that MULTICAST is enabled at eth0?
> >>
> >> regards
> >> Peter
> >> [EMAIL PROTECTED]
> >>
> >>
> >>
> >> Am 15.02.2006 um 02:26 schrieb David Avenante:
> >>
> >>> Hi,
> >>>
> >>> I' ve try to use Tomcat 5.5.15 in cluster mod. And after some
> >>> work on
> >>> configuration and test
> >>> i seems to be on limit of my all possibilities ;)
> >>>
> >>> I try to use two tomcat in cluster with apache web server and
> >>> mod_jk as
> >>> connector.
> >>>
> >>> my Apache configuration look like :
> >>>
> >>>
> >>> # workers.properties
> >>>
> >>> ps=/
> >>>
> >>> # List the workers name
> >>> worker.list=loadbalancer
> >>>
> >>> # 
> >>> # First worker
> >>> # 
> >>> worker.node01.port=8009
> >>> worker.node01.host=agnes
> >>> worker.node01.type=ajp13
> >>> worker.node01.lbfactor=1
> >>> #worker.node01.domain=cluster1
> >>> # 
> >>> # Second worker
> >>> # 
> >>> worker.node02.port=9009
> >>> worker.node02.host=ovea-inspiron
> >>> worker.node02.type=ajp13
> >>> worker.node02.lbfactor=1
> >>> #worker.node02.domain=cluster1
> >>> # --
> >>> # Load Balancer worker
> >>> # --
> >>> worker.loadbalancer.type=lb
> >>> worker.loadbalancer.sticky_session=false
> >>> worker.loadbalancer.balanced_workers=node01,node02
> >>>
> >>> As you can see i use two server ('agnes' IP : 192.168.2.102 and
> >>> 'ovea-inspiron' IP : 192.168.2.103)
> >>> I' ve coded a little aplication who read un file and create a
> >>> sessions if
> >>> session not exist.
> >>>
> >>> If i use the system in mod load balancing (with no cluster mod
> >>> activate)
> >>> all is great (my config is of course
> >>> worker.loadbalancer.sticky_session=true
> >>> )
> >>>
> >>> So system run with session affinitu but the two server are
> >>> accessible ;)
> >>>
> >>> Now i try to configure as cluster mode with session replication
> >>> (my config is now worker.loadbalancer.sticky_session=3Dfalse)
> >>>
> >>> I configure my to server.xml like that :
> >>> agnes (IP : 192.168.2.102)
> >>>
> >>> 
> >>>   
> >>>  >>>type="org.apache.catalina.UserDatabase"
> >>>description="User database that can be updated
> >>> and saved"
> >>>factory="
> >>> org.apache.catalina.users.MemoryUserDatabaseFactory"
> >>>pathname="conf/tomcat-users.xml" />
> >>>
> >>>   
> >>>
> >>>   
> >>>  >>>   maxThreads="150" minSpareThreads="25"
> >>>   maxSpareThreads="75"
> >>>   enableLookups="false" redirectPort="8443"
> >>> acceptCount="100"
> >>>   conn

Change Max Post Size

[Diwan, Dronesh \(Genworth, Contractor\)]

Any idea on how to change the maxPostSize in the Connector instead of
using the dafault values.

I have problem in uploading files > 2 MB. I tried setting different
values as prescribed but it didn't work.
 http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html 


Thanks
Dronesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.15 Clustering ?

[Filip Hanik - Dev Lists]

David, you are all over the place. Slow down for a second.
my guess is that one of your interfaces is not doing what you think it 
is doing.


follow these simple steps

1. Make sure that your multicast is working
2. Stop all your tomcat processes
3. Make sure nothing else is broadcasting on the same mcast address
4. Delete or archive all your previous logs
5. Startup tomcat 1 - wait 10 seconds
6. Startup tomcat 2

Then do the following
7. Set tcpListenAddress="auto" in your server.xml file
8. Repeat steps 1 through 6

9. email the logs to the list

our guess is that you have a networking problem, but you just don't dont 
look into it close enough for yourself and then provide us with the info.


Filip




David Avenante wrote:

Yes all right !

INFO: Register manager /cluster-1.0-SNAPSHOT to cluster element Host with
name localhost
Feb 15, 2006 10:47:32 AM org.apache.catalina.cluster.session.DeltaManagerstart

But Why 
my mcastAddress is good !

now i' ve a new error

Feb 15, 2006 10:50:41 AM
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThreadpushQueuedMessages
WARNING: Unable to asynchronously send session with id=[GET-ALL-/cluster-
1.0-SNAPSHOT] - message will be ignored.
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)

but it's a big progress ;)

I got to verifiy if my ntp synchronisation between my server is OK ;)

Thank you very much.



  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Change Max Post Size

[Carl Olivier]

Hi.

Its done in the Connector tag within the /conf/server.xml - see the docs for
the exact attribute but I believe it's the maxPostSize attribute.

Regards,

Carl

-Original Message-
From: Diwan, Dronesh (Genworth, Contractor)
[mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 16:01
To: users@tomcat.apache.org
Subject: Change Max Post Size

Any idea on how to change the maxPostSize in the Connector instead of using
the dafault values.

I have problem in uploading files > 2 MB. I tried setting different values
as prescribed but it didn't work.
 http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html 


Thanks
Dronesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



__ NOD32 1.1409 (20060215) Information __

This message was checked by NOD32 antivirus system.
http://www.eset.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Error using java archives

[Eduardo Clemos]

Im trying to display data from an java object in a web
page, invoking the method toString implicitly. The
java programs run ok, I have tested them. But when I
include the tag

  <%=resp%>

(the object resp is of type Respuesta)

I obtain this result in Tomcat:

  Error in servlet generated:
  The type Respuesta cannot be resolved. It is
indirectly referenced from required .class files

All of the .class are in the same directory, and I
import "conexiones.*" (I supose that load all .class
of the directory "WEB-INF/classes/conexiones")


Anyone can tell me what is the mistake? THANK YOU!




__ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Change Max Post Size

[Diwan, Dronesh \(Genworth, Contractor\)]

Thanks Carl for the update.We have already tried changing maxPostSize in
the Connector tag option but it does not work.
Then we thought of changing the maxPostSize from the admin console but
we do not get any option to change the connector
setting. MaxPostSize does not come as an option unlike oother attribute.

Now our last resort is to change the default value of maxPostSize
variable defined in the Connector class and
recompile it.

Thanks
Dronesh

-Original Message-
From: Carl Olivier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 11:09 AM
To: 'Tomcat Users List'
Subject: RE: Change Max Post Size


Hi.

Its done in the Connector tag within the /conf/server.xml - see the docs
for
the exact attribute but I believe it's the maxPostSize attribute.

Regards,

Carl

-Original Message-
From: Diwan, Dronesh (Genworth, Contractor)
[mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 16:01
To: users@tomcat.apache.org
Subject: Change Max Post Size

Any idea on how to change the maxPostSize in the Connector instead of
using
the dafault values.

I have problem in uploading files > 2 MB. I tried setting different
values
as prescribed but it didn't work.
 http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html 


Thanks
Dronesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



__ NOD32 1.1409 (20060215) Information __

This message was checked by NOD32 antivirus system.
http://www.eset.com



-
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]

Problem with hosting web application on tomcat / error 404 for an exists file

[Legolas Woodland]

Hi
Thank you for reading my post.
I have a web application which i developed and works well on my tomcat 5.5.9
Now i purchase a hosting plane with tomcat 5.5.9 it is on linux and have 
cpanel.
they said that i should upload all contents of my war file into http_doc 
folder , so i did
I used ftp to upload them all , now that i try to access my web site it 
return



 HTTP Status 404 - /index.jsp


meanwhile index.jsp in under that www folder.
I test the server by uploading an html file to make sure that i put 
content of war file in correct place. nad it works ok with HTML file.

can some one help me about this problem ?


Thanks

LoginModule JAAS and Tomcat (initialize method is not called)

[Vincent Delhommois]

Hello,
I developped my own LoginModule which is very simple for the moment. I wanted 
to know if I have to create the JAAS configuration file ? If yes where you I 
locate it ?
When I start Tomcat, the constructor of the LoginModule is well called but 
Tomcat failed before the initialize method. Tomcat launch an exception : 
"Arguments type error".
Do you have any idea ?
Thanks for all !!

Question about caseSensitive - how does it work?

[David Kerber]

With the trouble I've been having with getting caseSensitive="false" to 
work in my app, I got to wondering if it really does what I think it 
does on Windows XP.


My interpretation of the doc description is that when 
caseSensitive=:"false", I should be able to have a document root and 
context path at (for example) "/SiteData", and be able to reach it with 
urls including "sitedata", "SITEDATA", "SiteData", or any other 
combination of upper- and lower-case letters which spell the correct 
word.  Is this interpretation correct?


If so, then I can go back to figuring out how to actually make it work.

TIA!
Dave



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Configuring a web application at the container level

[Matt Munz]

Hi all,

  Here's a newbie question -- I'm looking forward to RTFM :)  I would
like to find a consistent way to do application-specific configuration
of a web application.  Is there a best-practice for this that you might
recommend?

  Consider the following example.  I have a hello world application that
contains one servlet, which outputs the string "Hello World".  The
application is bundled in hello-world.war, which I will then deploy in
various tomcat instances.  

  Now, if I want to make the output string configurable, I might make an
entry in web.xml for this.  If I do it this way, then, at each
deployment, I have to unpack the web.xml and edit it to include the
correct configuration setting (e.g. "Hello World, from your friends at
sample.com").  Yuck.  I'd much rather put these configuration settings
in a central file or registry for each tomcat instance, and then
hello-world.war could just inherit those settings from the container.
That way I edit the configuration file once, and each re-deploy doesn't
require a re-edit of the configuration file.

  So, how do I do that?  JNDI, JMX, something else?

  Thanks for considering this question.

  - Matt Munz
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

question about JNDIRealm and OpenLDAP with access control

[Gary]

Hi,

I have JDNIRealm set in the context.xml like this

 
   
connectionURL="ldap://localhost:389";
  userPattern="uid={0},ou=people,dc=example,dc=com"
 userRoleName="affiliation" />


Authentication works fine until I added this to slapd.conf

access to *
  by anonymous auth
  by users read


Because I don't want to let anonymous users query ldap.

Now when I login, I get http status 403 (access denied).

Without ldap access control set, request.getUserPrincipal() prints
this: GenericPrincipal[gary(member,)]
but with access control, it print this: GenericPrincipal[gary()]

Not sure why the role information would be missing.
I am using tomcat 5.5.15, openldap 2.2.29

Thanks,
Gary

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

I tried with NetScape and Opera to see what happens.  

For NetScape the first time I tried it was ok up to the stage that I
switched to SSL.  At that step, I lost my session.  After trying several
times again I noticed NetScape was ok.

With Opera all works fine, like with IE, from the beginning.

So major problem is still FireFox and it must be something that it sends (or
not sends) back to Tomcat that causes session expiration.

Thanks for your assistance.

Michael

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 17:48
>To: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>Not at the stage that this problem occurs.  SSL is used 
>further on when the user logs in to make a payment but the SSL 
>pages are never reached with FireFox because of the early 
>timeout.  With IE all is ok, including SSL connections. 
>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:43
>>To: 'Tomcat Users List'
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>Are you using SSL connection ?
>>
>>-Message d'origine-
>>De :
>>[EMAIL PROTECTED]
>pache.org
>>[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
>tomcat.ap
>>ache.org]De la part de Michael Andreas Omerou Envoye : 
>>mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
>>Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>
>>It is 30 minutes.  If I do
>>request.getSession().getMaxInactiveInterval() I get 1800 (seconds I 
>>guess) which is the correct value for 30 minutes.
>>
>>Michael
>>
>>>-Original Message-
>>>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 17:25
>>>To: Tomcat Users List
>>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>The META tags should not have an effect on cookies. Firefox 
>would not 
>>>be the one that expires your session, Tomcat would.
>>>Do you have a session timeout specified in your application?
>>>
>>>Earnie!
>>>
>>>-Original Message-
>>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, February 15, 2006 10:19 AM
>>>To: 'Tomcat Users List'
>>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>
>>>Hi Earnie,
>>>
>>>Cookies are allowed at the browser.  It seems for some 
>reason that at 
>>>then end of loading each JSP firefox expires my session.  I use some 
>>>meta tags (>CONTENT="No-Cache">, >>HTTP-EQUIV="Pragma" CONTENT="No-Cache">, >>CONTENT="-1">) and also set the corresponding header values using 
>>>response.setHeader but even if I remove them nothing changes.
>>>
>>>Michael
>>>
-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in
>>>the below
two emails?

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: 15 February 2006 13:10
>To: 'Tomcat Users List'
>Subject: RE: Session Problems with Firefox
>
>Further to my below email I have put in some code to check 
>the HTTP 
>headers in each case (IE and FireFox).
>
>These are:
>
>IE
>accept: */*
>accept-language: en-gb
>accept-encoding: gzip, deflate
>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 
>5.1; SV1; 
>.NET CLR 1.1.4322; InfoPath.1)
>host: localhost
>connection: Keep-Alive
>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>
>FireFox
>host: localhost
>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
>>>rv:1.7.12)
>Gecko/20050919 Firefox/1.0.7
>accept:
>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
>0.8,image/png,*/*;q=0.5
>accept-language: en-gb,en;q=0.5
>accept-encoding: gzip,deflate
>accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>keep-alive: 300
>connection: keep-alive
>cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
>cache-control: max-age=0
>
>
>I wonder whether the keep-alive which exists in the case of
FireFox but
>not in the case of IE could be the cause of my problems.
>
>Michael
>
>
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 11:27
>>To: users@tomcat.apache.org
>>Subject: Session Problems with Firefox
>>
>>Hell

RE: Tomcat 5.5.15 Context Reloading issue

[Joey Geiger]

Well, I discovered the cause of the bug, and I can now stop it from
happening, but I'm unable to *fix* the problem. The top logging statement
works properly, while the commented one does not. 

The NullPointer on the date occurs because a date is not being sent to the
logger when the context is reloaded. The date is sent on a startup. Tomcat
can survive this error during reload. The other error
(NoClassDefFoundError:VectorWriter) is an issue with the line number being
sent to the logger, which causes the reload to completely fail. 

log4j.appender.ap.layout.ConversionPattern=%p %t %c - %m%n
#log4j.appender.ap.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n


Log output:
Initial Load:
11:42:20,781 INFO
org.apache.catalina.core.ContainerBase.[Catalina].[hostname.com].[/] -
Loading Spring root WebApplicationContext

Reload:
INFO org.apache.catalina.core.ContainerBase.[Catalina].[hostname.com].[/] -
Loading Spring root WebApplicationContext

-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 9:15 AM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.15 Context Reloading issue

> From: Joey Geiger [mailto:[EMAIL PROTECTED] 
> Subject: Tomcat 5.5.15 Context Reloading issue
> 
> The host is configured as:
> 
>  unpackWARs="true" autoDeploy="true" xmlValidation="false"
> xmlNamespaceAware="false" reloadable="true">
> 
> 
> 
> 

An empty docBase path is rather odd.  The appBase parameter is supposed
to point to the directory under which one or more application
directories or war files are stored; docBase should specify the
directory or war for the given application.  Perhaps you should try
setting appBase to "C:\web" and docBase to "application".

> I've tried to add log4j 1.2.9 to both the common/lib and 
> server/lib with no success.

Not at the same time, I hope.

 - 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 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: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Michael Andreas Omerou]

As the problem occurs with a live site, you can see it yourself at
www.tophotelchoices.com.  Do a search for any hotel.   You will see the
results.  By the time the results page is loaded your session has expired
but you do not know.  Click on the "Book" or "Request" button of any hotel
and you will see the Timeout page.

Remember that the above only happens with FireFox.

I will greatly appreciate your help.

>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
>Sent: 15 February 2006 19:45
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Cc: 'Tomcat Users List'
>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>I tried with NetScape and Opera to see what happens.  
>
>For NetScape the first time I tried it was ok up to the stage 
>that I switched to SSL.  At that step, I lost my session.  
>After trying several times again I noticed NetScape was ok.
>
>With Opera all works fine, like with IE, from the beginning.
>
>So major problem is still FireFox and it must be something 
>that it sends (or not sends) back to Tomcat that causes 
>session expiration.
>
>Thanks for your assistance.
>
>Michael
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 17:48
>>To: 'Tomcat Users List'
>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>
>>Not at the stage that this problem occurs.  SSL is used 
>further on when 
>>the user logs in to make a payment but the SSL pages are 
>never reached 
>>with FireFox because of the early timeout.  With IE all is ok, 
>>including SSL connections.
>>
>>>-Original Message-
>>>From: [EMAIL PROTECTED]
>>>[mailto:[EMAIL PROTECTED]
>>>Sent: 15 February 2006 17:43
>>>To: 'Tomcat Users List'
>>>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>Are you using SSL connection ?
>>>
>>>-Message d'origine-
>>>De :
>>>[EMAIL PROTECTED]
>>pache.org
>>>[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
>>tomcat.ap
>>>ache.org]De la part de Michael Andreas Omerou Envoye : 
>>>mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
>>>Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>>>
>>>
>>>It is 30 minutes.  If I do
>>>request.getSession().getMaxInactiveInterval() I get 1800 (seconds I
>>>guess) which is the correct value for 30 minutes.
>>>
>>>Michael
>>>
-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox
>>would not
be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some
>>reason that at
then end of loading each JSP firefox expires my session.  I 
>use some 
meta tags (>>CONTENT="No-Cache">, >>>HTTP-EQUIV="Pragma" CONTENT="No-Cache">, >>>CONTENT="-1">) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing changes.

Michael

>-Original Message-
>From: Earnie Dyke [mailto:[EMAIL PROTECTED]
>Sent: 15 February 2006 17:10
>To: Tomcat Users List
>Subject: RE: Session Expires At Every Request 
>(Tomcat5.0.28/Firefox)
>
>Are you blocking cookies at the browser?
>
>Earnie!
>
>-Original Message-
>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 15, 2006 10:06 AM
>To: 'Tomcat Users List'
>Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)
>
>
> Anybody has an idea what could be causing what I describe in
the below
>two emails?
>
>>-Original Message-
>>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>>Sent: 15 February 2006 13:10
>>To: 'Tomcat Users List'
>>Subject: RE: Session Problems with Firefox
>>
>>Further to my below email I have put in some code to check
>>the HTTP
>>headers in each case (IE and FireFox).
>>
>>These are:
>>
>>IE
>>accept: */*
>>accept-language: en-gb
>>accept-encoding: gzip, deflate
>>user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
>>5.1; SV1;
>>.NET CLR 1.1.4322; InfoPath.1)
>>host: localhost
>>connection: Keep-Alive
>>cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320
>>
>>FireFox
>>host: localhost
>>user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.12)
>>Gecko/20050919 Firefox/1.0.7
>>

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

You do realize that sessions don't carry over between SSL and non-SSL
request don't you?

You can't have a session ID that carries over from a non-ssl session to an
SSL session because that session ID is compromised (it has been exposed) as
plain text.

As an aside, I looked at your form. You should really use
HttpServletRequest.getLocale() to pick up your user's locale and then
provide date formatting for the user locale.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 11:03 AM
> To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED]
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> As the problem occurs with a live site, you can see it yourself at
> www.tophotelchoices.com.  Do a search for any hotel.   You 
> will see the
> results.  By the time the results page is loaded your session 
> has expired
> but you do not know.  Click on the "Book" or "Request" button 
> of any hotel
> and you will see the Timeout page.
> 
> Remember that the above only happens with FireFox.
> 
> I will greatly appreciate your help.
> 
> >-Original Message-
> >From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> >Sent: 15 February 2006 19:45
> >To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> >Cc: 'Tomcat Users List'
> >Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >
> >I tried with NetScape and Opera to see what happens.  
> >
> >For NetScape the first time I tried it was ok up to the stage 
> >that I switched to SSL.  At that step, I lost my session.  
> >After trying several times again I noticed NetScape was ok.
> >
> >With Opera all works fine, like with IE, from the beginning.
> >
> >So major problem is still FireFox and it must be something 
> >that it sends (or not sends) back to Tomcat that causes 
> >session expiration.
> >
> >Thanks for your assistance.
> >
> >Michael
> >
> >>-Original Message-
> >>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
> >>Sent: 15 February 2006 17:48
> >>To: 'Tomcat Users List'
> >>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >>
> >>Not at the stage that this problem occurs.  SSL is used 
> >further on when 
> >>the user logs in to make a payment but the SSL pages are 
> >never reached 
> >>with FireFox because of the early timeout.  With IE all is ok, 
> >>including SSL connections.
> >>
> >>>-Original Message-
> >>>From: [EMAIL PROTECTED]
> >>>[mailto:[EMAIL PROTECTED]
> >>>Sent: 15 February 2006 17:43
> >>>To: 'Tomcat Users List'
> >>>Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> >>>
> >>>Are you using SSL connection ?
> >>>
> >>>-Message d'origine-
> >>>De :
> >>>[EMAIL PROTECTED]
> >>pache.org
> >>>[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
> >>tomcat.ap
> >>>ache.org]De la part de Michael Andreas Omerou Envoye : 
> >>>mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
> >>>Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >>>
> >>>
> >>>It is 30 minutes.  If I do
> >>>request.getSession().getMaxInactiveInterval() I get 1800 (seconds I
> >>>guess) which is the correct value for 30 minutes.
> >>>
> >>>Michael
> >>>
> -Original Message-
> From: Earnie Dyke [mailto:[EMAIL PROTECTED]
> Sent: 15 February 2006 17:25
> To: Tomcat Users List
> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> 
> The META tags should not have an effect on cookies. Firefox
> >>would not
> be the one that expires your session, Tomcat would.
> Do you have a session timeout specified in your application?
> 
> Earnie!
> 
> -Original Message-
> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 15, 2006 10:19 AM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> 
> 
> Hi Earnie,
> 
> Cookies are allowed at the browser.  It seems for some
> >>reason that at
> then end of loading each JSP firefox expires my session.  I 
> >use some 
> meta tags ( >>>CONTENT="No-Cache">,  HTTP-EQUIV="Pragma" CONTENT="No-Cache">,  HTTP-EQUIV="Expires"
> CONTENT="-1">) and also set the corresponding header values using 
> response.setHeader but even if I remove them nothing changes.
> 
> Michael
> 
> >-Original Message-
> >From: Earnie Dyke [mailto:[EMAIL PROTECTED]
> >Sent: 15 February 2006 17:10
> >To: Tomcat Users List
> >Subject: RE: Session Expires At Every Request 
> >(Tomcat5.0.28/Firefox)
> >
> >Are you blocking cookies at the browser?
> >
> >Earnie!
> >
> >-Original Message-
> >From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
> >Sent: Wednesday, February 15, 2006 1

Re: LoginModule JAAS and Tomcat (initialize method is not called)

[Vincent Delhommois]

I start Tomcat with the following option :
set 
JVM_OPTS=-Djava.security.auth.login.config=D:/Appl/eclipse/workspace2/testAppli/jaas.conf
 (in the catalina.bat)

My jaas.conf is :
/** Login Configuration for the JAAS **/
MyLoginModule {
com.gcatrans.testappli.MyLoginModule required debug=true app=testAppli;
};

The error message is :
15 fÚvr. 2006 19:14:25 org.apache.commons.digester.Digester endElement
GRAVE: End event threw exception
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.jav
a:252)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(
Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.catalina.startup.Catalina.start(Catalina.java:420)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
Catalina.start using D:\Appl\Tomcat 4.1\conf\server.xml: java.lang.IllegalArgume
ntException: argument type mismatch
java.lang.IllegalArgumentException: argument type mismatch
at org.apache.commons.digester.Digester.createSAXException(Digester.java
:2540)
at org.apache.commons.digester.Digester.createSAXException(Digester.java
:2566)
at org.apache.commons.digester.Digester.endElement(Digester.java:1061)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(
Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)





> Message du 15/02/06 à 17h51
> De : "Vincent Delhommois" 
> A : users@tomcat.apache.org
> Copie à : 
> Objet : LoginModule JAAS and Tomcat (initialize method is not called)
> 
> Hello,
> I developped my own LoginModule which is very simple for the moment. I wanted 
> to know if I have to create the JAAS configuration file ? If yes where you I 
> locate it ?
> When I start Tomcat, the constructor of the LoginModule is well called but 
> Tomcat failed before the initialize method. Tomcat launch an exception : 
> "Arguments type error".
> Do you have any idea ?
> Thanks for all !!

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Caldarale, Charles R]

> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> As the problem occurs with a live site, you can see 
> it yourself at www.tophotelchoices.com.

(OT: A bit depressing to see a Holiday Inn at Aylesbury - I used to live
just down the road from there in the 1950s.)

I noticed that a secondary window opened during the search; is it
possible that with Firefox the session is being associated only with
this secondary window?  Can you use Ethereal or something similar to see
which requests/responses contain the desired session id?

 - 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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: LoginModule JAAS and Tomcat (initialize method is not called)

[Caldarale, Charles R]

> From: Vincent Delhommois [mailto:[EMAIL PROTECTED] 
> Subject: Re: LoginModule JAAS and Tomcat (initialize method 
> is not called)
> 
> I start Tomcat with the following option :
> set 
> JVM_OPTS=-Djava.security.auth.login.config=D:/Appl/eclipse/wor
> kspace2/testAppli/jaas.conf (in the catalina.bat)

Do you mean JAVA_OPTS?  JVM_OPTS is not used in the distributed scripts,
unless you've modified them.

 - 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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Filip Hanik - Dev Lists]

for FireFox - use LiveHttpHeaders and the webDeveloper plugins to 
examine requests/responses cookies and more

I think chuck might be onto something

Filip

Caldarale, Charles R wrote:
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


As the problem occurs with a live site, you can see 
it yourself at www.tophotelchoices.com.



(OT: A bit depressing to see a Holiday Inn at Aylesbury - I used to live
just down the road from there in the 1950s.)

I noticed that a secondary window opened during the search; is it
possible that with Firefox the session is being associated only with
this secondary window?  Can you use Ethereal or something similar to see
which requests/responses contain the desired session id?

 - 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 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: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Joey Geiger]

>>You do realize that sessions don't carry over between SSL and non-SSL
>>request don't you?

What is the proper/best way to go about this then, since I will be facing a
similar situation in the near future? (Shopping cart bean, customer bean
saved in the session.)

Thanks.


-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 12:17 PM
To: 'Tomcat Users List'; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

You do realize that sessions don't carry over between SSL and non-SSL
request don't you?

You can't have a session ID that carries over from a non-ssl session to an
SSL session because that session ID is compromised (it has been exposed) as
plain text.

As an aside, I looked at your form. You should really use
HttpServletRequest.getLocale() to pick up your user's locale and then
provide date formatting for the user locale.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 11:03 AM
> To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED]
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> As the problem occurs with a live site, you can see it yourself at
> www.tophotelchoices.com.  Do a search for any hotel.   You 
> will see the
> results.  By the time the results page is loaded your session 
> has expired
> but you do not know.  Click on the "Book" or "Request" button 
> of any hotel
> and you will see the Timeout page.
> 
> Remember that the above only happens with FireFox.
> 
> I will greatly appreciate your help.
> 
> >-Original Message-
> >From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> >Sent: 15 February 2006 19:45
> >To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> >Cc: 'Tomcat Users List'
> >Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >
> >I tried with NetScape and Opera to see what happens.  
> >
> >For NetScape the first time I tried it was ok up to the stage 
> >that I switched to SSL.  At that step, I lost my session.  
> >After trying several times again I noticed NetScape was ok.
> >
> >With Opera all works fine, like with IE, from the beginning.
> >
> >So major problem is still FireFox and it must be something 
> >that it sends (or not sends) back to Tomcat that causes 
> >session expiration.
> >
> >Thanks for your assistance.
> >
> >Michael
> >
> >>-Original Message-
> >>From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
> >>Sent: 15 February 2006 17:48
> >>To: 'Tomcat Users List'
> >>Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >>
> >>Not at the stage that this problem occurs.  SSL is used 
> >further on when 
> >>the user logs in to make a payment but the SSL pages are 
> >never reached 
> >>with FireFox because of the early timeout.  With IE all is ok, 
> >>including SSL connections.
> >>
> >>>-Original Message-
> >>>From: [EMAIL PROTECTED]
> >>>[mailto:[EMAIL PROTECTED]
> >>>Sent: 15 February 2006 17:43
> >>>To: 'Tomcat Users List'
> >>>Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> >>>
> >>>Are you using SSL connection ?
> >>>
> >>>-Message d'origine-
> >>>De :
> >>>[EMAIL PROTECTED]
> >>pache.org
> >>>[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
> >>tomcat.ap
> >>>ache.org]De la part de Michael Andreas Omerou Envoye : 
> >>>mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
> >>>Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >>>
> >>>
> >>>It is 30 minutes.  If I do
> >>>request.getSession().getMaxInactiveInterval() I get 1800 (seconds I
> >>>guess) which is the correct value for 30 minutes.
> >>>
> >>>Michael
> >>>
> -Original Message-
> From: Earnie Dyke [mailto:[EMAIL PROTECTED]
> Sent: 15 February 2006 17:25
> To: Tomcat Users List
> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> 
> The META tags should not have an effect on cookies. Firefox
> >>would not
> be the one that expires your session, Tomcat would.
> Do you have a session timeout specified in your application?
> 
> Earnie!
> 
> -Original Message-
> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 15, 2006 10:19 AM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> 
> 
> Hi Earnie,
> 
> Cookies are allowed at the browser.  It seems for some
> >>reason that at
> then end of loading each JSP firefox expires my session.  I 
> >use some 
> meta tags ( >>>CONTENT="No-Cache">,  HTTP-EQUIV="Pragma" CONTENT="No-Cache">,  HTTP-EQUIV="Expires"
> CONTENT="-1">) and also set the corresponding header values using 
> 

RE: App will work on localhost but blank on client PC.

[Alexander Alekseev]

I checked server.xml and found



So I changed the value to 43, and was able to access
http://192.168.2.100:8447/ from the server (before could only access
localhost:8447

Still can't access 192.168.2.100:8447 from client PC's

-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 7:32 AM
To: Tomcat Users List
Subject: Re: App will work on localhost but blank on client PC.

Take a look at server.xml and specifically the  element 
corresponding to port 8447. Does it have an attribute named address set 
to "127.0.0.1" ?  If so, remove that attribute and restart tomcat.  
Setting the address attribute to 127.0.0.1 specifically binds tomcat to 
the localhost adapter and you'll never be able to connect to it from any 
other client.

-- David

Alexander Alekseev wrote:
> Server is 192.168.2.100, client is 192.168.2.X
>
> We tried using http://192.168.2.100:8447/ from the client, and the blank
> problem first cropped up.
>
> Now, instead of http://localhost:8447/ we tried http://192.168.2.100:8447/
> from the server itself, and it also comes up blank.
>
>
>
> -Original Message-
> From: Mike Sabroff [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, February 14, 2006 9:55 AM
> To: Tomcat Users List
> Subject: Re: App will work on localhost but blank on client PC.
>
>   
>> How does localhost resolve in that scenario...why not use the hostname 
>> or ip address
>> 
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   


-- 
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change Max Post Size

[Mark Thomas]

Diwan, Dronesh (Genworth, Contractor) wrote:
> Thanks Carl for the update.We have already tried changing maxPostSize in
> the Connector tag option but it does not work.

Works for me. Did you restart Tomcat after the change?

Mark



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Performance issues with tomcat 5

[David Bishop]

Hi,

I was running Apache Cocoon with Tomcat 5.0.28 and a Sun 1.4.2 JVM.

Unexpectedly the system was falling over at a certain load and not  
gracefully slowing down. At a certain number of concurrent users it  
was returning very strange errors including Java Out of Memory  
errors, but only after returning some weird ones!


After doing some intensive testing and not getting anywhere I looked  
for help from the Cocoon community and was pointed at the JVM because  
the stock for garbage collection is no good for web servers and can  
be improved with fine tuning via command line parameters. The  
following document has some good points regarding it..


http://java.sun.com/docs/hotspot/gc1.4.2/index.html

I actually solved all my problems by upgrading to the 1.5 JVM which  
has far better garbage collection handling and I have found under  
regression testing the web system gracefully slows down when things  
get tough as opposed to falling over, it also performs much better  
than it did under the 1.4.2 JVM.


Hope this helps,

David.

On 15 Feb 2006, at 13:29, Leon Rosenberg wrote:


Hi,

has someone ever estimated the max possible load for tomcat? We are
suffering from very odd behaviour, as long as tomcat/machine is under
certain load it works very well, but then it just "breaks a magical
limit" and the performance breaks down.
Tomcat or the JVM are starting to leak memory (we are running with
mx800M, and are normally at 600+ free memory, but then it goes to
zero). Tomcat begins to throw absolutely ununderstandable exceptions,
like beans not present in scope which are normally there, socket/pipe
errors, unable to deliver 5xx or 4xx error pages and so on. Busy
threads are going high, from 10-20 to some hundreds.

We are running with jdk1.4.2_04, tomcat 5.0.25, linux kernel 2.6.8
(debian) 32 bit on different hardware, intel or opteron 1-2
processors, 32 and 64 bit processors (up to 4 virtual processors). No
tomcat clustering, no app. server. Our loadbalancing is based on CPU
Idle time, so the amount of traffic on each machine is different,
faster machines serving 4 times more then slower. The faster machines
are serving 100-150 requests per second in normal, and approx. 300-400
requests per second in peak times. Avg. request duration is <15 ms in
normal times (the servlet execution, not counting the jsp transmission
afterwards) and 100-200 under high load.

We need some serious performance benchmarks, but those are hard to
find (most people talk about absolutely irrelevant things like
database tuning)...
Any good links?

TIA
Leon

-
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: Question about caseSensitive - how does it work?

[Mark Thomas]

David Kerber wrote:
> With the trouble I've been having with getting caseSensitive="false" to
> work in my app, I got to wondering if it really does what I think it
> does on Windows XP.

I strongly suggest you read the documentation for this attribute
before you go any further.
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

In my shopping cart application, I create a cart with a unique (random) id
and track the request type (secure/non-secure). 

If they invoke the program from an SSL request, and the previous request was
non-SSL then I create a new cart with a new unique ID, copy the information
from the insecure cart, and then delete the old cart.

If someone tries to come back with the old cart id, then that cart just
doesn't exist and they get a new cart.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Joey Geiger [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 11:50 AM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> >>You do realize that sessions don't carry over between SSL 
> and non-SSL
> >>request don't you?
> 
> What is the proper/best way to go about this then, since I 
> will be facing a
> similar situation in the near future? (Shopping cart bean, 
> customer bean
> saved in the session.)
> 
> Thanks.
> 
> 
> -Original Message-
> From: George Sexton [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 12:17 PM
> To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> You do realize that sessions don't carry over between SSL and non-SSL
> request don't you?
> 
> You can't have a session ID that carries over from a non-ssl 
> session to an
> SSL session because that session ID is compromised (it has 
> been exposed) as
> plain text.
> 
> As an aside, I looked at your form. You should really use
> HttpServletRequest.getLocale() to pick up your user's locale and then
> provide date formatting for the user locale.
> 
> George Sexton
> MH Software, Inc.
> http://www.mhsoftware.com/
> Voice: 303 438 9585
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Question about caseSensitive - how does it work?

[David Kerber]

I have read it several times, each time more carefully than the last, 
and googled several dozen references, and the way I read that doc and 
everything else, it should work the way I describe. 

But I cannot get it to work and it's driving me nuts!  I'm aware of the 
security implications, but at the moment I don't give a rat's a** about 
them; I just want my context path to be non-case sensitive.



Mark Thomas wrote:


David Kerber wrote:
 


With the trouble I've been having with getting caseSensitive="false" to
work in my app, I got to wondering if it really does what I think it
does on Windows XP.
   



I strongly suggest you read the documentation for this attribute
before you go any further.
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html

Mark


-
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: LoginModule JAAS and Tomcat (initialize method is not called)

[Vincent Delhommois]

Thanks for your answer.
You are right.I tried several positions. I'm sure that the conf file is used.
In my conf file :
MyLoginModule {
com.gcatrans.testappli.MyLoginModule required debug=true app=testAppli;
};
I don't know where is made the mapping between the realm name and the conf 
file...





> Message du 15/02/06 à 19h29
> De : "Caldarale, Charles R" 
> A : "Tomcat Users List" , [EMAIL PROTECTED]
> Copie à : 
> Objet : RE: LoginModule JAAS and Tomcat (initialize method is not called)
> 
> > From: Vincent Delhommois [mailto:[EMAIL PROTECTED] 
> > Subject: Re: LoginModule JAAS and Tomcat (initialize method 
> > is not called)
> > 
> > I start Tomcat with the following option :
> > set 
> > JVM_OPTS=-Djava.security.auth.login.config=D:/Appl/eclipse/wor
> > kspace2/testAppli/jaas.conf (in the catalina.bat)
> 
> Do you mean JAVA_OPTS? JVM_OPTS is not used in the distributed scripts,
> unless you've modified them.
> 
> - 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.
> 
>

Re: New isapi_redirect.dll has problems

[Mark Thomas]

David Thielen wrote:
> Hi;
> 
> I checked the registry - it's using the workers.properties.minimal I believe
> (but I would be happier if it logged the files it uses).
> 
> The problem with the urls it should not touch only showed up with the new
> version from Mark - that never happened before.
> 
> As to the thread count, if someone tells me how to raise this, I will do so.
> But we get very low volume on this so I would be surprised if that is it.
> 
> Any other ideas anyone?

Can you post the following:
worker.properties
the AJP connector element from server.xml

Also, are you able to provide a test case that reproduces the errors
you are seeing?

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: New isapi_redirect.dll has problems

[Mark Thomas]

One more thing, turn up the logging level to debug and post the
sequence of log messages associated with one of these odd URLs.

Cheers,

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Filip Hanik - Dev Lists]

sessions started in non-ssl mode should carry over to SSL, but not the 
other way around.

Filip


Joey Geiger wrote:

You do realize that sessions don't carry over between SSL and non-SSL
request don't you?
  


What is the proper/best way to go about this then, since I will be facing a
similar situation in the near future? (Shopping cart bean, customer bean
saved in the session.)

Thanks.


-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 12:17 PM

To: 'Tomcat Users List'; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

You do realize that sessions don't carry over between SSL and non-SSL
request don't you?

You can't have a session ID that carries over from a non-ssl session to an
SSL session because that session ID is compromised (it has been exposed) as
plain text.

As an aside, I looked at your form. You should really use
HttpServletRequest.getLocale() to pick up your user's locale and then
provide date formatting for the user locale.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

  

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 11:03 AM
To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
[EMAIL PROTECTED]

Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

As the problem occurs with a live site, you can see it yourself at
www.tophotelchoices.com.  Do a search for any hotel.   You 
will see the
results.  By the time the results page is loaded your session 
has expired
but you do not know.  Click on the "Book" or "Request" button 
of any hotel

and you will see the Timeout page.

Remember that the above only happens with FireFox.

I will greatly appreciate your help.



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 19:45

To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

I tried with NetScape and Opera to see what happens.  

For NetScape the first time I tried it was ok up to the stage 
that I switched to SSL.  At that step, I lost my session.  
After trying several times again I noticed NetScape was ok.


With Opera all works fine, like with IE, from the beginning.

So major problem is still FireFox and it must be something 
that it sends (or not sends) back to Tomcat that causes 
session expiration.


Thanks for your assistance.

Michael

  

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:48
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Not at the stage that this problem occurs.  SSL is used 

further on when 
  
the user logs in to make a payment but the SSL pages are 

never reached 
  
with FireFox because of the early timeout.  With IE all is ok, 
including SSL connections.




-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:43
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request 
  

(Tomcat5.0.28/Firefox)


Are you using SSL connection ?

-Message d'origine-
De :
[EMAIL PROTECTED]
  

pache.org


[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
  

tomcat.ap

ache.org]De la part de Michael Andreas Omerou Envoye : 
mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'

Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


It is 30 minutes.  If I do
request.getSession().getMaxInactiveInterval() I get 1800 (seconds I
guess) which is the correct value for 30 minutes.

Michael

  

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request 


(Tomcat5.0.28/Firefox)


The META tags should not have an effect on cookies. Firefox


would not


be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request 


(Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some


reason that at

then end of loading each JSP firefox expires my session.  I 

use some 
  

meta tags (

CONTENT="No-Cache">,   
HTTP-EQUIV="Pragma" CONTENT="No-Cache">, 

HTTP-EQUIV="Expires"

CONTENT="-1">) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing chang

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

Does the code transparently create a new JSessionID value then?

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 12:48 PM
> To: Tomcat Users List
> Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> sessions started in non-ssl mode should carry over to SSL, 
> but not the 
> other way around.
> Filip
> 
> 
> Joey Geiger wrote:
> >>> You do realize that sessions don't carry over between SSL 
> and non-SSL
> >>> request don't you?
> >>>   
> >
> > What is the proper/best way to go about this then, since I 
> will be facing a
> > similar situation in the near future? (Shopping cart bean, 
> customer bean
> > saved in the session.)
> >
> > Thanks.
> >
> >
> > -Original Message-
> > From: George Sexton [mailto:[EMAIL PROTECTED] 
> > Sent: Wednesday, February 15, 2006 12:17 PM
> > To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED];
> > [EMAIL PROTECTED]
> > Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> >
> > You do realize that sessions don't carry over between SSL 
> and non-SSL
> > request don't you?
> >
> > You can't have a session ID that carries over from a 
> non-ssl session to an
> > SSL session because that session ID is compromised (it has 
> been exposed) as
> > plain text.
> >
> > As an aside, I looked at your form. You should really use
> > HttpServletRequest.getLocale() to pick up your user's 
> locale and then
> > provide date formatting for the user locale.
> >
> > George Sexton
> > MH Software, Inc.
> > http://www.mhsoftware.com/
> > Voice: 303 438 9585
> >   
> >
> >   
> >> -Original Message-
> >> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> >> Sent: Wednesday, February 15, 2006 11:03 AM
> >> To: 'Tomcat Users List'; [EMAIL PROTECTED]; 
> >> [EMAIL PROTECTED]
> >> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> >>
> >> As the problem occurs with a live site, you can see it yourself at
> >> www.tophotelchoices.com.  Do a search for any hotel.   You 
> >> will see the
> >> results.  By the time the results page is loaded your session 
> >> has expired
> >> but you do not know.  Click on the "Book" or "Request" button 
> >> of any hotel
> >> and you will see the Timeout page.
> >>
> >> Remember that the above only happens with FireFox.
> >>
> >> I will greatly appreciate your help.
> >>
> >> 
> >>> -Original Message-
> >>> From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
> >>> Sent: 15 February 2006 19:45
> >>> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> >>> Cc: 'Tomcat Users List'
> >>> Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> >>>
> >>> I tried with NetScape and Opera to see what happens.  
> >>>
> >>> For NetScape the first time I tried it was ok up to the stage 
> >>> that I switched to SSL.  At that step, I lost my session.  
> >>> After trying several times again I noticed NetScape was ok.
> >>>
> >>> With Opera all works fine, like with IE, from the beginning.
> >>>
> >>> So major problem is still FireFox and it must be something 
> >>> that it sends (or not sends) back to Tomcat that causes 
> >>> session expiration.
> >>>
> >>> Thanks for your assistance.
> >>>
> >>> Michael
> >>>
> >>>   
>  -Original Message-
>  From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
>  Sent: 15 February 2006 17:48
>  To: 'Tomcat Users List'
>  Subject: RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> 
>  Not at the stage that this problem occurs.  SSL is used 
>  
> >>> further on when 
> >>>   
>  the user logs in to make a payment but the SSL pages are 
>  
> >>> never reached 
> >>>   
>  with FireFox because of the early timeout.  With IE all is ok, 
>  including SSL connections.
> 
>  
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Sent: 15 February 2006 17:43
> > To: 'Tomcat Users List'
> > Subject: RE: Session Expires At Every Request 
> >   
> >> (Tomcat5.0.28/Firefox)
> >> 
> > Are you using SSL connection ?
> >
> > -Message d'origine-
> > De :
> > [EMAIL PROTECTED]
> >   
>  pache.org
>  
> > [mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
> >   
>  tomcat.ap
>  
> > ache.org]De la part de Michael Andreas Omerou Envoye : 
> > mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
> > Objet : RE: Session Expires At Every Request 
> (Tomcat5.0.28/Firefox)
> >
> >
> > It is 30 minutes.  If I do
> > request.getSession().getMaxInactiveInterval() I get 
> 1800 (seconds I
> > guess) which is the correct value for 30 minutes.
> >
> > Mic

Re: Tomcat 5.5.15 Clustering ?

[Paul Smith]

Is the multicast going over the 127.0.0.1 instead?  We've had this  
problem before (redhat el3), and to fix it, you have to make sure  
that in /etc/hosts that localhost is bound to a real IP address and  
not 127.0.0.1.  for some reason, in Java it always seems to want to  
stick to the local interface when localhost is mapped to this.


Paul Smith
On 16/02/2006, at 3:08 AM, Filip Hanik - Dev Lists wrote:


David, you are all over the place. Slow down for a second.
my guess is that one of your interfaces is not doing what you think  
it is doing.


follow these simple steps

1. Make sure that your multicast is working
2. Stop all your tomcat processes
3. Make sure nothing else is broadcasting on the same mcast address
4. Delete or archive all your previous logs
5. Startup tomcat 1 - wait 10 seconds
6. Startup tomcat 2

Then do the following
7. Set tcpListenAddress="auto" in your server.xml file
8. Repeat steps 1 through 6

9. email the logs to the list

our guess is that you have a networking problem, but you just don't  
dont look into it close enough for yourself and then provide us  
with the info.


Filip




David Avenante wrote:

Yes all right !

INFO: Register manager /cluster-1.0-SNAPSHOT to cluster element  
Host with

name localhost
Feb 15, 2006 10:47:32 AM  
org.apache.catalina.cluster.session.DeltaManagerstart


But Why 
my mcastAddress is good !

now i' ve a new error

Feb 15, 2006 10:50:41 AM
org.apache.catalina.cluster.tcp.FastAsyncSocketSender 
$FastQueueThreadpushQueuedMessages
WARNING: Unable to asynchronously send session with id=[GET-ALL-/ 
cluster-

1.0-SNAPSHOT] - message will be ignored.
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)

but it's a big progress ;)

I got to verifiy if my ntp synchronisation between my server is OK ;)

Thank you very much.







-
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: question about JNDIRealm and OpenLDAP with access control

[Gary]

Gary wrote:


Hi,

I have JDNIRealm set in the context.xml like this



connectionURL="ldap://localhost:389";
  userPattern="uid={0},ou=people,dc=example,dc=com"
 userRoleName="affiliation" />


Authentication works fine until I added this to slapd.conf

access to *
  by anonymous auth
  by users read


Because I don't want to let anonymous users query ldap.

Now when I login, I get http status 403 (access denied).

Without ldap access control set, request.getUserPrincipal() prints
this: GenericPrincipal[gary(member,)]
but with access control, it print this: GenericPrincipal[gary()]

Not sure why the role information would be missing.




Ok, I think I have this figured out... but correct me if I am wrong.

Authentication and authorization are done separately. The realm setting 
I have above
was only able to succeed for the authentication part.  And failed on the 
authorization part,
it wasn't able to get the user role because my ldap access control 
prohibited

read from anonymous users.

After I added  connectionName, and  connectionPassword  to the realm tag.
It was able to use that to get the role information out of ldap.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Filip Hanik - Dev Lists]

George Sexton wrote:

Does the code transparently create a new JSessionID value then?


George,
you might wanna rethink your comments, they don't shine any light on the 
issue and they for sure don't state any facts, let me prove you I am 
right. Below is the headers I tracked with LiveHttpHeaders, as you can 
see, JSESSIONID remains exactly the same in the browser request when the 
switch from HTTP to HTTPS happens.

This is Firefox on Fedora 4. The site works fine.

This must be a browser issue, can you tell us a little bit more about 
what version and platform your browser is on.


1. Request to the home - non secure

http://www.tophotelchoices.com/
GET / HTTP/1.1
Host: www.tophotelchoices.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) 
Gecko/20060124 Firefox/1.5.0.1
Accept: 
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5

Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.tophotelchoices.com/

HTTP/1.x 200 OK
Date: Wed, 15 Feb 2006 20:08:55 GMT
Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
Set-Cookie: JSESSIONID=735009FD40D725EDAA14389409CD60FF; Path=/
Cache-Control: no-cache
Pragma: no-cache
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Keep-Alive: timeout=5, max=20
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=UTF-8

2. Click on the request button - switch from HTTP to HTTPS
https://www.tophotelchoices.com/bookingServlet1?hotel=ASI
GET /bookingServlet1?hotel=ASI HTTP/1.1
Host: www.tophotelchoices.com:443
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) 
Gecko/20060124 Firefox/1.5.0.1
Accept: 
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5

Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.tophotelchoices.com/searchResults.jsp
Cookie: JSESSIONID=735009FD40D725EDAA14389409CD60FF

HTTP/1.x 200 OK
Date: Wed, 15 Feb 2006 20:11:54 GMT
Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
Cache-Control: no-cache
Pragma: no-cache
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Keep-Alive: timeout=5, max=20
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=UTF-8


George Sexton wrote:

Does the code transparently create a new JSessionID value then?

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585



-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 12:48 PM
To: Tomcat Users List
Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

sessions started in non-ssl mode should carry over to SSL,
but not the
other way around.
Filip




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Question about caseSensitive - how does it work?

[Bob Faist]

My guess is that the web app name will need to be treated as case
sensitive regardless of the  configuration.

http://localhost:8080/tomcat-docs/INDEX.html
http://localhost:8080/tomcat-docs/index.html

Both of these work for serving static content.

http://localhost:8080/TOMCAT-DOCS/index.html

This does not work.



-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 11:52 AM
To: Tomcat Users List
Subject: Question about caseSensitive - how does it work?

With the trouble I've been having with getting caseSensitive="false" to
work in my app, I got to wondering if it really does what I think it
does on Windows XP.

My interpretation of the doc description is that when
caseSensitive=:"false", I should be able to have a document root and
context path at (for example) "/SiteData", and be able to reach it with
urls including "sitedata", "SITEDATA", "SiteData", or any other
combination of upper- and lower-case letters which spell the correct
word.  Is this interpretation correct?

If so, then I can go back to figuring out how to actually make it work.

TIA!
Dave



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


**
Confidentiality Notice
The information contained in this e-mail is confidential and intended for
use only by the person(s) or organization listed in the address. If you have
received this communication in error, please contact the sender at O'Neil &
Associates, Inc., immediately. Any copying, dissemination, or distribution
of this communication, other than by the intended recipient, is strictly
prohibited.
**


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 1:16 PM
> To: Tomcat Users List
> Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> George Sexton wrote:
> > Does the code transparently create a new JSessionID value then?
> 
> George,
> you might wanna rethink your comments, they don't shine any 
> light on the 
> issue and they for sure don't state any facts, let me prove you I am 
> right. Below is the headers I tracked with LiveHttpHeaders, 
> as you can 
> see, JSESSIONID remains exactly the same in the browser 
> request when the 
> switch from HTTP to HTTPS happens.

And this is an incredibly major trap that lies waiting for every application
developer that uses sessions. You see, I have given a great deal of thought
about sessions and what should happen when a connection transitions to
secure, or from secure to non-secure.

Let's take a simple shopping cart app. User Adam visit a site on a
non-secure connection and receives a session. He shops and puts something in
his cart.

Mallory (crypto speak for the person in the middle) monitors Adam's network
stream and picks up the jsessionid from the data stream.

Adam then goes to the check out screen and starts entering checkout data
(name, address, and credit card information). To give ourselves a window,
assume that Adam then continues shopping or is just slow, or the credit card
processing procedure takes time...

Mallory can forge a request using the JSessionID, and go to the checkout
pages. Since Mallory has the same session, all of the information entered by
Adam is now visible.

This is the flaw. This is why sessions should not transition from non-secure
to secure, or if they do transition a new ID should be generated and the old
session ID invalidated. The session ID is a key into the data store and if
the session key has been exposed to the public, then no confidential data
should be accessed using that session key.

I think this should be submitted as a bug. 


George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

An even simpler case:

Adam visits a banking site. On entering the site he gets a cookie. 


Mallory snoops the session ID on the data stream.

Adam then authenticates to read his account information. The application
sets a session attribute (say a bean with the account name and number) on
the session.


Mallory now enters the secure area of the banking site using the forged
session ID. 

Poof. Mallory is logged in as Adam.

Poof. Adam is had and his data is there to be stolen, or wire transferred to
another account.



George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: George Sexton [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 2:09 PM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> 
> 
> > -Original Message-
> > From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
> > Sent: Wednesday, February 15, 2006 1:16 PM
> > To: Tomcat Users List
> > Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> > 
> > George Sexton wrote:
> > > Does the code transparently create a new JSessionID value then?
> > 
> > George,
> > you might wanna rethink your comments, they don't shine any 
> > light on the 
> > issue and they for sure don't state any facts, let me prove 
> you I am 
> > right. Below is the headers I tracked with LiveHttpHeaders, 
> > as you can 
> > see, JSESSIONID remains exactly the same in the browser 
> > request when the 
> > switch from HTTP to HTTPS happens.
> 
> And this is an incredibly major trap that lies waiting for 
> every application
> developer that uses sessions. You see, I have given a great 
> deal of thought
> about sessions and what should happen when a connection transitions to
> secure, or from secure to non-secure.
> 
> Let's take a simple shopping cart app. User Adam visit a site on a
> non-secure connection and receives a session. He shops and 
> puts something in
> his cart.
> 
> Mallory (crypto speak for the person in the middle) monitors 
> Adam's network
> stream and picks up the jsessionid from the data stream.
> 
> Adam then goes to the check out screen and starts entering 
> checkout data
> (name, address, and credit card information). To give 
> ourselves a window,
> assume that Adam then continues shopping or is just slow, or 
> the credit card
> processing procedure takes time...
> 
> Mallory can forge a request using the JSessionID, and go to 
> the checkout
> pages. Since Mallory has the same session, all of the 
> information entered by
> Adam is now visible.
> 
> This is the flaw. This is why sessions should not transition 
> from non-secure
> to secure, or if they do transition a new ID should be 
> generated and the old
> session ID invalidated. The session ID is a key into the data 
> store and if
> the session key has been exposed to the public, then no 
> confidential data
> should be accessed using that session key.
> 
> I think this should be submitted as a bug. 
> 
> 
> George Sexton
> MH Software, Inc.
> http://www.mhsoftware.com/
> Voice: 303 438 9585
> 
> 
> -
> 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: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Filip Hanik - Dev Lists]

Adam and Mallory have to stop shopping! =)

this debate has been going on for years, you just caught onto to it now, 
and I was in it last time, don't plan on participating again. Have fun 
with it though!!


Filip


George Sexton wrote:

An even simpler case:

Adam visits a banking site. On entering the site he gets a cookie. 



Mallory snoops the session ID on the data stream.

Adam then authenticates to read his account information. The application
sets a session attribute (say a bean with the account name and number) on
the session.


Mallory now enters the secure area of the banking site using the forged
session ID. 


Poof. Mallory is logged in as Adam.

Poof. Adam is had and his data is there to be stolen, or wire transferred to
another account.



George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

  

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 2:09 PM

To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)





-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 1:16 PM

To: Tomcat Users List
Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

George Sexton wrote:
  

Does the code transparently create a new JSessionID value then?


George,
you might wanna rethink your comments, they don't shine any 
light on the 
issue and they for sure don't state any facts, let me prove 
  
you I am 

right. Below is the headers I tracked with LiveHttpHeaders, 
as you can 
see, JSESSIONID remains exactly the same in the browser 
request when the 
switch from HTTP to HTTPS happens.
  
And this is an incredibly major trap that lies waiting for 
every application
developer that uses sessions. You see, I have given a great 
deal of thought

about sessions and what should happen when a connection transitions to
secure, or from secure to non-secure.

Let's take a simple shopping cart app. User Adam visit a site on a
non-secure connection and receives a session. He shops and 
puts something in

his cart.

Mallory (crypto speak for the person in the middle) monitors 
Adam's network

stream and picks up the jsessionid from the data stream.

Adam then goes to the check out screen and starts entering 
checkout data
(name, address, and credit card information). To give 
ourselves a window,
assume that Adam then continues shopping or is just slow, or 
the credit card

processing procedure takes time...

Mallory can forge a request using the JSessionID, and go to 
the checkout
pages. Since Mallory has the same session, all of the 
information entered by

Adam is now visible.

This is the flaw. This is why sessions should not transition 
from non-secure
to secure, or if they do transition a new ID should be 
generated and the old
session ID invalidated. The session ID is a key into the data 
store and if
the session key has been exposed to the public, then no 
confidential data

should be accessed using that session key.

I think this should be submitted as a bug. 



George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585


-
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]

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[Joey Geiger]

Oddly enough, the banks don't even care about this.

US Bank, for example, claims their login on the front page is "secure" and
has you enter your account data into a non https form. After the browser
sends the information, it then redirects to a secure(https) link.

I wrote them about this, and their response was, we know it's not secure,
but we'll compensate you for any losses you may have... Crazy.

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 3:16 PM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

An even simpler case:

Adam visits a banking site. On entering the site he gets a cookie. 


Mallory snoops the session ID on the data stream.

Adam then authenticates to read his account information. The application
sets a session attribute (say a bean with the account name and number) on
the session.


Mallory now enters the secure area of the banking site using the forged
session ID. 

Poof. Mallory is logged in as Adam.

Poof. Adam is had and his data is there to be stolen, or wire transferred to
another account.



George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: George Sexton [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 2:09 PM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> 
> 
> > -Original Message-
> > From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
> > Sent: Wednesday, February 15, 2006 1:16 PM
> > To: Tomcat Users List
> > Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> > 
> > George Sexton wrote:
> > > Does the code transparently create a new JSessionID value then?
> > 
> > George,
> > you might wanna rethink your comments, they don't shine any 
> > light on the 
> > issue and they for sure don't state any facts, let me prove 
> you I am 
> > right. Below is the headers I tracked with LiveHttpHeaders, 
> > as you can 
> > see, JSESSIONID remains exactly the same in the browser 
> > request when the 
> > switch from HTTP to HTTPS happens.
> 
> And this is an incredibly major trap that lies waiting for 
> every application
> developer that uses sessions. You see, I have given a great 
> deal of thought
> about sessions and what should happen when a connection transitions to
> secure, or from secure to non-secure.
> 
> Let's take a simple shopping cart app. User Adam visit a site on a
> non-secure connection and receives a session. He shops and 
> puts something in
> his cart.
> 
> Mallory (crypto speak for the person in the middle) monitors 
> Adam's network
> stream and picks up the jsessionid from the data stream.
> 
> Adam then goes to the check out screen and starts entering 
> checkout data
> (name, address, and credit card information). To give 
> ourselves a window,
> assume that Adam then continues shopping or is just slow, or 
> the credit card
> processing procedure takes time...
> 
> Mallory can forge a request using the JSessionID, and go to 
> the checkout
> pages. Since Mallory has the same session, all of the 
> information entered by
> Adam is now visible.
> 
> This is the flaw. This is why sessions should not transition 
> from non-secure
> to secure, or if they do transition a new ID should be 
> generated and the old
> session ID invalidated. The session ID is a key into the data 
> store and if
> the session key has been exposed to the public, then no 
> confidential data
> should be accessed using that session key.
> 
> I think this should be submitted as a bug. 
> 
> 
> George Sexton
> MH Software, Inc.
> http://www.mhsoftware.com/
> Voice: 303 438 9585
> 
> 
> -
> 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]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: classloader issue?

[Boris Unckel]

Rik Claesen wrote:

Thnx Boris, I forgot to mention it.
The assist.jar is currently located in the WEB-INF/lib.
and ...this is working fine as long as the security manager is not 
active.


Maybe to put this into the system path would solve your problem. But I 
think it is better to solve the security issue.

I have no experience with the Tomcat security manager, maybe
http://tomcat.apache.org/tomcat-5.5-doc/security-manager-howto.html
helps.

Boris


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

  

> -Original Message-
> From: Joey Geiger [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 2:27 PM
> To: 'Tomcat Users List'
> Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> Oddly enough, the banks don't even care about this.
> 
> US Bank, for example, claims their login on the front page is 
> "secure" and
> has you enter your account data into a non https form. After 
> the browser
> sends the information, it then redirects to a secure(https) link.
> 
> I wrote them about this, and their response was, we know it's 
> not secure,
> but we'll compensate you for any losses you may have... Crazy.
> 

Scary. That's my bank. But then, I don't trust people enough to do online
banking.

I bet their shareholders would be really excited to know about their
technical proficiency and offer to re-imburse you for losses


George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.15 Clustering ?

[David Avenante]

 You're right so :

 1 - I reboot my too servers agnes : 192.168.2.102 and ovea-inspiron :
192.168.2.103
 2 - I test the multicat on each server

 for that, I start on agnes the command
 java -cp tomcat-replication.jar MCaster 224.0.0.1 45564 ovea-inspiron
 output :
 Usage MCaster [address port message]
 BEGIN TO RECEIVE
 SENT:ovea-inspiron1
 RECEIVED:ovea-inspiron1 FROM /192.168.2.102:45564
 BEGIN TO RECEIVE
 SENT:ovea-inspiron2
 RECEIVED:ovea-inspiron2 FROM /192.168.2.102:45564
 BEGIN TO RECEIVE
 ...
 a tcpdump on agnes output :
 12:03:56.160976 IP 192.168.2.102.45564 >
all-systems.mcast.net.45564: UDP, length 14
 12:03:59.165908 IP 192.168.2.102.45564 >
all-systems.mcast.net.45564: UDP, length 14
 12:04:02.170789 IP 192.168.2.102.45564 >
all-systems.mcast.net.45564: UDP, length 14
 12:04:05.175930 IP 192.168.2.102.45564 >
all-systems.mcast.net.45564: UDP, length 14
 12:04:08.180810 IP 192.168.2.102.45564 >
all-systems.mcast.net.45564: UDP, length 14
 ...

 a tcpdump on ovea-inspiron output :
 12:00:24.229852 IP AGNES.45564 > ALL-SYSTEMS.MCAST.NET.45564:
UDP, length 15
 12:00:27.234391 IP AGNES.45564 > ALL-SYSTEMS.MCAST.NET.45564:
UDP, length 15
 ...

 I stop the process on agnes and on ovea-inspiron start comand :
java -cp tomcat-replication.jar MCaster 224.0.0.1 45564 agnes
 Usage MCaster [address port message]
 BEGIN TO RECEIVE
 RECEIVED:agnes1 FROM /192.168.2.103:45566
 SENT:agnes1
 BEGIN TO RECEIVE
 SENT:agnes2
 RECEIVED:agnes2 FROM /192.168.2.103:45566
 SENT:agnes3
 BEGIN TO RECEIVE
 RECEIVED:agnes3 FROM /192.168.2.103:45566

 a tcpdump on agnes output :
 12:12:48.210143 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 6
 12:12:51.264541 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 6
 12:12:54.396574 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 7

 a tcpdump on ovea-inspiron output :
 12:27:10.603013 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 8
 12:27:13.855782 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 8
 12:27:16.863749 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 8

 Ok here first problem in the first server name of agnes is not
resolved 
 so i take a look on my hosts and a see the problem 
 fuck ... bad configuration
 it's
 127.0.0.1   localhost  agnes
 192.168.2.103   ovea-inspiron
 but must be
 127.0.0.1   localhost
 192.168.2.102   agnes
 192.168.2.103   ovea-inspiron

 same error on second server so i correct this mistake
 and retry the test ... ok name is resolved as well.

 Now i run the command simultany on two servers
 on agnes the command java -cp tomcat-replication.jar MCaster
224.0.0.1 45564 ovea-inspiron
 and on ovea-inspiron start comand : java -cp
tomcat-replication.jar MCaster 224.0.0.1 45564 agnes

 the ouput as the same a the other tests but tcpdump info are now :
 on agnes
 12:43:02.336748 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 7
 12:43:02.395214 IP agnes.45564 > all-systems.mcast.net.45564:
UDP, length 15
 12:43:05.400696 IP agnes.45564 > all-systems.mcast.net.45564:
UDP, length 15
 12:43:05.506764 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 7
 12:43:08.405287 IP agnes.45564 > all-systems.mcast.net.45564:
UDP, length 15
 12:43:08.604056 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 7
 12:43:11.410371 IP agnes.45564 > all-systems.mcast.net.45564:
UDP, length 15
 12:43:11.608944 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566: UDP, length 7

 on ovea-inspiron
 12:45:55.861466 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 7
 12:45:57.983294 IP AGNES.45564 > all-systems.mcast.net.45564:
UDP, length 14
 12:45:58.914085 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 7
 12:46:00.988429 IP AGNES.45564 > all-systems.mcast.net.45564:
UDP, length 15
 12:46:01.918123 IP ovea-inspiron.45566 >
all-systems.mcast.net.45566:UDP, length 7

 Ok so now I think my multicast is OK no ?

 So now I use the two server configuration of my first post and i
start the first server.
 the log is :
Feb 15, 2006 4:00:26 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/opt/sun-jdk-1.5.0.06/jre/lib/i386/client:/opt/sun-jdk-1.5.0.06/jre/lib/i386:/opt/sun-jdk-1.5.0.06/jre/../lib/i386
Feb 15, 2006 4:00:26 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Feb 15, 2006 4:00:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 980 ms
Feb 15, 2

Re: Tomcat 5.5.15 Clustering ?

[David Avenante]

Yes you're right i' ve a problem in my /etc/hosts as you can see in my
response
to Hanik.

I hope this type of thread can help people to save time.
Because some skills are necessary for reolve the problem.

Thank you Paul ;)


On 2/15/06, Paul Smith <[EMAIL PROTECTED]> wrote:
>
> Is the multicast going over the 127.0.0.1 instead?  We've had this
> problem before (redhat el3), and to fix it, you have to make sure
> that in /etc/hosts that localhost is bound to a real IP address and
> not 127.0.0.1.  for some reason, in Java it always seems to want to
> stick to the local interface when localhost is mapped to this.
>
> Paul Smith
> On 16/02/2006, at 3:08 AM, Filip Hanik - Dev Lists wrote:
>
> > David, you are all over the place. Slow down for a second.
> > my guess is that one of your interfaces is not doing what you think
> > it is doing.
> >
> > follow these simple steps
> >
> > 1. Make sure that your multicast is working
> > 2. Stop all your tomcat processes
> > 3. Make sure nothing else is broadcasting on the same mcast address
> > 4. Delete or archive all your previous logs
> > 5. Startup tomcat 1 - wait 10 seconds
> > 6. Startup tomcat 2
> >
> > Then do the following
> > 7. Set tcpListenAddress="auto" in your server.xml file
> > 8. Repeat steps 1 through 6
> >
> > 9. email the logs to the list
> >
> > our guess is that you have a networking problem, but you just don't
> > dont look into it close enough for yourself and then provide us
> > with the info.
> >
> > Filip
> >
> >
> >
> >
> > David Avenante wrote:
> >> Yes all right !
> >>
> >> INFO: Register manager /cluster-1.0-SNAPSHOT to cluster element
> >> Host with
> >> name localhost
> >> Feb 15, 2006 10:47:32 AM
> >> org.apache.catalina.cluster.session.DeltaManagerstart
> >>
> >> But Why 
> >> my mcastAddress is good !
> >>
> >> now i' ve a new error
> >>
> >> Feb 15, 2006 10:50:41 AM
> >> org.apache.catalina.cluster.tcp.FastAsyncSocketSender
> >> $FastQueueThreadpushQueuedMessages
> >> WARNING: Unable to asynchronously send session with id=[GET-ALL-/
> >> cluster-
> >> 1.0-SNAPSHOT] - message will be ignored.
> >> java.net.ConnectException: Connection timed out
> >> at java.net.PlainSocketImpl.socketConnect(Native Method)
> >>
> >> but it's a big progress ;)
> >>
> >> I got to verifiy if my ntp synchronisation between my server is OK ;)
> >>
> >> Thank you very much.
> >>
> >>
> >>
> >>
> >
> >
> > -
> > 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: Tomcat 5.5.15 Clustering ?

[Filip Hanik - Dev Lists]

ok, we will work through it one item at the time.

show me the output from both servers MCaster program (not the tcpdump) 
when they run simultanously.


Filip


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat problems.

[Angel Prieto]

Hello, I'm having some problems with apache+tomcat with this configuration:
Apache 2.0.51 (on Fedora Core 2)
Tomcat 5.0.28
JDK 1.4.0_04
Mod_jk connector for FC2.


Sometimes system goes down and we don't have any idea what the reason 
is. We get this error sometimes:


10-feb-2006 10:05:02 org.apache.commons.modeler.Registry registerComponent
GRAVE: Error registering 
server:type=RequestProcessor,worker=jk-9109,name=JkRequest413
javax.management.InstanceAlreadyExistsException: 
server:type=RequestProcessor,worker=jk-9109,name=JkRequest413

at mx4j.server.MBeanServerImpl.register(MBeanServerImpl.java:1123)
at mx4j.server.MBeanServerImpl.registerImpl(MBeanServerImpl.java:1054)
at 
mx4j.server.MBeanServerImpl.registerMBeanImpl(MBeanServerImpl.java:1002)

at mx4j.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:978)
at 
org.apache.commons.modeler.Registry.registerComponent(Registry.java:871)
at 
org.apache.jk.common.ChannelSocket.registerRequest(ChannelSocket.java:436)
at 
org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:443)

at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:352)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at 
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) 


at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) 


at java.lang.Thread.run(Thread.java:536)

Could anyone tell me something about it?

thank you in advance.

--
Angel Prieto
[EMAIL PROTECTED] SINERGIA TECNOLÓGICA
C/ Almirante Churruca

30007 Murcia
TEL.  968 270 624Fax. 968 231 501
www.sinergiatec.com
__

La información incluida en el presente correo electrónico es 
CONFIDENCIAL, siendo para el uso exclusivo del destinatario arriba 
mencionado. Si usted lee este mensaje y no es el destinatario señalado, 
el empleado o el agente responsable de entregar el mensaje al 
destinatario, o ha recibido esta comunicación por error, le informamos 
que está totalmente prohibida cualquier divulgación, distribución o 
reproducción de esta comunicación, y le rogamos que nos lo notifique, 
nos devuelva el mensaje original a la dirección arriba mencionada y 
borre el mensaje. Gracias.

__




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

New isapi_redirect.dll issues

[David Thielen]

Hi;

 

I put all of the requested files in a zip at
http://www.windward.net/tomcat_error.zip along with my registry settings.
The errors have not occurred yet but I will leave it running (this is our
production system) and I am sure I will get the errors by morning. I will
post those then.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544

 

isapi_redirect suggestion

[David Thielen]

Hi;

 

I think the following log items should be level info instead of debug:

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_shm.c (134): Initialized
shared memory size=67584 free=65536 addr=0x187

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1166):
Using registry.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1169):
Using log file C:\Tomcat 5.5\logs\isapi_redirect.log.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1170):
Using log level 1.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1171):
Using extension uri /jakarta/isapi_redirect.dll.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1172):
Using worker file C:\Tomcat 5.5\conf\workers.properties.minimal.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1173):
Using worker mount file C:\Tomcat 5.5\conf\uriworkermap.properties.

[Wed Feb 15 16:02:01 2006] [1680:4084] [debug] jk_isapi_plugin.c (1175):
Using uri select 0.

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /store/*=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (268):
exact rule /store=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /track/*=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /forums/*=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (268):
exact rule /forums=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /WindwardReportsServlet/*=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /WindwardReportsJsp/*=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /*.jsp=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_uri_worker_map.c (260):
wildchar rule /*.faces=ajp13w was added

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_worker.c (236): creating
worker ajp13w

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_worker.c (141): about to
create instance ajp13w of ajp13

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_worker.c (154): about to
validate and init ajp13w

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1806):
worker ajp13w contact is 'localhost:8009'

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1895):
setting socket keepalive to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1934):
setting socket timeout to -1

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1938):
setting socket buffer size to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1942):
setting connection recycle timeout to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1946):
setting cache timeout to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1950):
setting connect timeout to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1954):
setting reply timeout to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1958):
setting prepost timeout to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1962):
setting recovery opts to 0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1966):
setting number of retries to 3

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_ajp_common.c (1843):
setting connection cache size to 100

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_worker.c (248): removing
old ajp13w worker

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_isapi_plugin.c (711):
Detected IIS >= 5.0

[Wed Feb 15 16:02:02 2006] [1680:4084] [debug] jk_isapi_plugin.c (762):
Filter started

 

Thanks - dave

 

 

 

David Thielen

www.windwardreports.com

303-499-2544

 

Re: New isapi_redirect.dll issues

[Mark Thomas]

David Thielen wrote:
> I put all of the requested files in a zip at
> http://www.windward.net/tomcat_error.zip along with my registry settings.
> The errors have not occurred yet but I will leave it running (this is our
> production system) and I am sure I will get the errors by morning. I will
> post those then.

All received. I'll look at these tomorrow along with (hopefully) the
debug logs showing what is going on with these odd urls.

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

New to apache / Tomcat

[Andrew English]

I work for a company that had to recently let go its IT/Dev staff
because of issues.

This company runs Tomcat 4.03 on Windows 2003 Server with Catalina, and
has Apache running on a Linux machine. Being use to IIS and not really
having a lot of experience with Tomcat I had hit a few road blocks and
require help.

The companies network is structured so that HTTP requests for their web
site come into the Linux box and then are redirected to the Windows 2003
Server running Tomcat on port 8082.

My problem is I have not been able to figure out how or where the
configuration is for this Tomcat server because on the Linux box for
instance the redirection points to
http://192.168.1.10:8082/ssapp/asn.html

As for the Windows Tomcat server it looks something like
c:\asnweb\jboss_tomcat\jboss\catalina\ssar.e\ssapp (as example), and
when you look for the asn.html file on the windows machine you find it
in totally separate folder than the ssapp folder. 

If I http://localhost/ on the tomcat box its takes me the web site of
the company (notice I didn't add the 8082). However not everything works
partly because the Linux box also flips the HTTP connection into a HTTPS
connection, the apache or linux box contains the certs too.

So what I am looking for the actual config for tomcat so I can create a
document of were things are, were they are going etc.. Also we are
thinking of replacing the crappy WatchGuard firewall they have with ISA
server; so we need to find out lots of info...

Thanks
Andrew


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Performance issues with tomcat 5

[Leon Rosenberg]

Thank you very much David, seems like we have to upgrade.

On 2/15/06, David Bishop <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was running Apache Cocoon with Tomcat 5.0.28 and a Sun 1.4.2 JVM.
>
> Unexpectedly the system was falling over at a certain load and not
> gracefully slowing down. At a certain number of concurrent users it
> was returning very strange errors including Java Out of Memory
> errors, but only after returning some weird ones!
>
> After doing some intensive testing and not getting anywhere I looked
> for help from the Cocoon community and was pointed at the JVM because
> the stock for garbage collection is no good for web servers and can
> be improved with fine tuning via command line parameters. The
> following document has some good points regarding it..
>
> http://java.sun.com/docs/hotspot/gc1.4.2/index.html
>
> I actually solved all my problems by upgrading to the 1.5 JVM which
> has far better garbage collection handling and I have found under
> regression testing the web system gracefully slows down when things
> get tough as opposed to falling over, it also performs much better
> than it did under the 1.4.2 JVM.
>
> Hope this helps,
>
> David.
>
> On 15 Feb 2006, at 13:29, Leon Rosenberg wrote:
>
> > Hi,
> >
> > has someone ever estimated the max possible load for tomcat? We are
> > suffering from very odd behaviour, as long as tomcat/machine is under
> > certain load it works very well, but then it just "breaks a magical
> > limit" and the performance breaks down.
> > Tomcat or the JVM are starting to leak memory (we are running with
> > mx800M, and are normally at 600+ free memory, but then it goes to
> > zero). Tomcat begins to throw absolutely ununderstandable exceptions,
> > like beans not present in scope which are normally there, socket/pipe
> > errors, unable to deliver 5xx or 4xx error pages and so on. Busy
> > threads are going high, from 10-20 to some hundreds.
> >
> > We are running with jdk1.4.2_04, tomcat 5.0.25, linux kernel 2.6.8
> > (debian) 32 bit on different hardware, intel or opteron 1-2
> > processors, 32 and 64 bit processors (up to 4 virtual processors). No
> > tomcat clustering, no app. server. Our loadbalancing is based on CPU
> > Idle time, so the amount of traffic on each machine is different,
> > faster machines serving 4 times more then slower. The faster machines
> > are serving 100-150 requests per second in normal, and approx. 300-400
> > requests per second in peak times. Avg. request duration is <15 ms in
> > normal times (the servlet execution, not counting the jsp transmission
> > afterwards) and 100-200 under high load.
> >
> > We need some serious performance benchmarks, but those are hard to
> > find (most people talk about absolutely irrelevant things like
> > database tuning)...
> > Any good links?
> >
> > TIA
> > Leon
> >
> > -
> > 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]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: New to apache / Tomcat

[Caldarale, Charles R]

> From: Andrew English [mailto:[EMAIL PROTECTED] 
> Subject: New to apache / Tomcat
> 
> As for the Windows Tomcat server it looks something like
> c:\asnweb\jboss_tomcat\jboss\catalina\ssar.e\ssapp (as example), and
> when you look for the asn.html file on the windows machine you find it
> in totally separate folder than the ssapp folder. 

Judging from the directory names, I suspect you're really running JBoss,
not Tomcat.  Tomcat is embedded in JBoss, but in such a scenario, all
configuration is through JBoss, not Tomcat.

 - 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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

[George Sexton]

I've been developing with Tomcat for years, and I never really know about
this issue. 

I'd have to say that it must not be a widely known issue.

Perhaps since the security picture has changed over the past couple of years
its time to revisit this issue.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 15, 2006 2:24 PM
> To: Tomcat Users List
> Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)
> 
> Adam and Mallory have to stop shopping! =)
> 
> this debate has been going on for years, you just caught onto 
> to it now, 
> and I was in it last time, don't plan on participating again. 
> Have fun 
> with it though!!
> 
> Filip
> 
> 
> George Sexton wrote:
> > An even simpler case:
> >
> > Adam visits a banking site. On entering the site he gets a cookie. 
> >
> >
> > Mallory snoops the session ID on the data stream.
> >
> > Adam then authenticates to read his account information. 
> The application
> > sets a session attribute (say a bean with the account name 
> and number) on
> > the session.
> >
> >
> > Mallory now enters the secure area of the banking site 
> using the forged
> > session ID. 
> >
> > Poof. Mallory is logged in as Adam.
> >
> > Poof. Adam is had and his data is there to be stolen, or 
> wire transferred to
> > another account.
> >
> >
> >
> > George Sexton
> > MH Software, Inc.
> > http://www.mhsoftware.com/
> > Voice: 303 438 9585
> >   
> >


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: New to apache / Tomcat

[Andrew English]

Hi Chuck, 

Could it be they are running both?

Their folder structure is:

ASNWeb\JbossTomcat\catalina
ASNWeb\JbossTomcat\jboss

I know that catalina runs under Windows Services along with 3 other
services related to it, and I know from looking in the catalina folder
and reading the readme.txt file that it's a Tomcat Server product. 

I looked through all the jboss folders and found nothing related to
catalina just the files which make up the web site itself. 

Andrew
 

-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 6:48 PM
To: Tomcat Users List
Subject: RE: New to apache / Tomcat

> From: Andrew English [mailto:[EMAIL PROTECTED] 
> Subject: New to apache / Tomcat
> 
> As for the Windows Tomcat server it looks something like
> c:\asnweb\jboss_tomcat\jboss\catalina\ssar.e\ssapp (as example), and
> when you look for the asn.html file on the windows machine you find it
> in totally separate folder than the ssapp folder. 

Judging from the directory names, I suspect you're really running JBoss,
not Tomcat.  Tomcat is embedded in JBoss, but in such a scenario, all
configuration is through JBoss, not Tomcat.

 - 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 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]