date:20091117


On 16/11/2009 22:07, André Warnier wrote:

Anthony Jay wrote:


My main issue now is about how the authentication works between Tomcat
and Apache.

That's the only one I can readily answer.
It is extremely simple with mod_jk.
If the user is authenticated at the Apache level, mod_jk will pass this
on to the Tomcat server via AJP.
The only thing to do, is set the 'tomcatAuthentication=false'
attribute in Tomcat's AJP Connector, and Tomcat will just believe the
user-id sent by Apache and mod_jk.
I don't know if, or how, mod_proxy_ajp handles the same thing.



In terms of authentication, which should I use, mod_auth_mysql and
mod_auth_dbm (or mod_auth_form in future or something else?) and why?


There are many many possibilities for this under Apache httpd. Just pick
the one that you like best, on its own merits.
They all basically in the end result in the HTTP request being
authenticated at the Apache httpd level (iow to have a user-id), and
that's what you want.

What you then do with it under Tomcat is another story, but that is also
your choice.


In terms of single sign on how can I make the user experience seamless
between static content-managed pages and jsp/servlets? Will mod_jk
handle sso? This does not seem clear to me in all the pages I read. If I
configure form based auth in a login.jsp page will this be relayed to
apache after a redirect?


No, but why would it be ?
Ah, if you want to do the authentication in Tomcat rather than in
Apache, but still use it in Apache ?
There are ways, but you'll need to write your own Apache (httpd)
authentication module. You could then define a dummy servlet in Tomcat,
which just echoes the authenticated user-id (as gotten via
getRemoteUser() e.g.). Then in Apache httpd, you would make a
side-request (oherwise known as a sub-request) to this Tomcat webapp
to get the user-id, and use it to authenticate the current request in
Apache.
But that is a complicated scheme, probably only worth it if you find
some Tomcat authentication method that does not exist in Apache httpd,
which is unlikely.



What is best practise and what should I be doing? If there is some hard
to find documentation out there with pointers and tips I would
appreciate a few links.


To read in the Apache httpd docs :
http://httpd.apache.org/docs/2.2/howto/auth.html

Also, personally I would recommend having a look around here :
http://cpan.uwinnipeg.ca/search?query=apache%3A%3Aauthmode=dist
This is the Perl library. Even if you do not intend to do anything with
Perl, the documentation of many of these modules is a goldmine of
information about how things work.

Expert advice is appreciated.
You just got it.
;-)


There used to be a mod_auth_cookie module that had form auth 
capabilities, but it wasn't ever in the main distro, it was listed in 
the related modules site.


I used a variant of it in a HTTPD 1.3 install many years ago, so I can't 
vouch for its current status.  GIYF.



p



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: A question about mod_jk 1.2.28 configuration

2009-11-17 Thread thomas2004


I think the reproduction with html is not working because of some other
reasons likely not related with mod_jk. In the original message he has a
jk error message referring to errno 11=EAGAIN. There is a change between
1.2.26 and 1.2.28 related to how EAGAIN gets handled while waiting for
data. So I can imagine he really hit a bug there, although I'm not sure,
because we have to check, whether that observation also happens without
socket_timeout and reply_timeout.


Hi Rainer and Christopher,

I think one can reconstruct my problem in a simple way:

Write a small web-application which contains two steps/pages. The first one
has a button submit. One click the button and it will send a request to
backend. The backend does nothing but just sleep for a while such as 5 min.,
10 min. etc. And then send back the time stamp back to browser (the second
page).

In this way one can check if this problem has to do with mod_jk (or apache
httpd) version or not.

Regards

Thomas
-- 
View this message in context: 
http://old.nabble.com/A-question-about-mod_jk-1.2.28-configuration-tp26264069p26387241.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


On 17/11/2009 04:14, Imad Hachem wrote:


Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.


Are you still using 5.5.12?  Hasn't anyone advised you to upgrade to a 
newer version yet?


I think it's perfectly reasonably to call sessionDestroyed() before 
contextDestroyed().



How can I know if sessionDestroyed is called from session.invalidate()
from the real expiration of the session or shutdown of one cluster node?


You can't know this directly from the Servlet API methods.


Note that on sessionDestroyed event, I am using a Logout behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope) to check

 on it during the sessionDestroyed event, but it seems the context is

destroyed after the session destroy event.


This comes up not infrequently on the list, the archives have more 
information:


http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html


Is there any event listener that I can use before the sessionDestroyed to 
differentiate if one cluster node has been shutdown or my session has been 
expired?

Or is how to configure the contextDestroy to be called before the sessions 
destroy?


No, contextDestroyed() means that the web application itself has been 
stopped, this is mandated by the Servlet Spec.



p



Thanks in advance for your help.

Best Regards,
Imad Hachem

System Engineer



_
Windows Live: Make it easier for your friends to see what you’re up to on 
Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Java Out of Heap Issue


On 16/11/2009 23:54, Elli Albek wrote:

You can try getting an object dump from a profiler and see which
objects are the source of memory starvation. Simple JSPs are very
unlikely to cause memory starvation, but you mentioned “application
code”, which implies that you have more than simple JSPs.

A few things you want to cross off your performance check list, which
will not solve your problem, but are generally necessary:
1. JVM -server option, just in case
2. Disable session persistence
3. If you application does not use sessions, disable them for all JSPs
(typical place to do it is header JSP include)
4. Force session termination, no long running sessions.
5. Remove all apps that you do not need. Tomcat comes with a few built
in apps and those are not trivial to find. Make sure conf/Catalina and
all its sub directories contain only apps that you need. Host manager
and such should be deleted. Same with war files.

What you describe in your memory graph is a simple memory leak.
Generally, I would look in that order:


  1a. Old code? Look for improperly closed DB connections.


1.  Sessions
2.  Application code
3.  Other webapps


p



1 and 3 are easy to deal with. If you don’t need sessions make sure
they are not created at all. If you do, force session termination
after a few minutes in master web.xml or other XML files. Notice that
one file can define a value and another can overwrite it, so you have
to make sure all are checked.

If that does not work, application code is the next candidate. You can
start with an object dump with a profiler or a simple code review/step
through in a debugger.

E

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: centralized log server


On 17/11/2009 07:51, Kaushal Shriyan wrote:

Hi,

is there a centralized application to access all the tomcat server
catalina.logs


All of them on the internet?


p



Thanks,

Kaushal

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat shudown does not kill java process


On 17/11/2009 10:01, raj kumar wrote:

Hi friends,

I am currently using Tomcat( jakarta-tomcat-5.0.28). When i shutdown the
tomcat server from my unix platform using ./shutdown.sh the java process is
not getting closed.I need to close the process explicitly. Please help me in
this regard.


It doesn't stop it, or it's taking a long time to stop it?

Try taking a thread dump after you've called the shutdown script to see 
what's still running in the app.   Should give you a clue as to which 
code is waiting on something.



p





Thanks,
Phani.




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat shudown does not kill java process

2009-11-17 Thread raj kumar

After shutting down the tomcat server, java process remains running till i
explicitly kill it. By the way how to take thread dump. Please help me with
the command

Thanks,
Raj

On Tue, Nov 17, 2009 at 3:57 PM, Pid p...@pidster.com wrote:

 On 17/11/2009 10:01, raj kumar wrote:

 Hi friends,

 I am currently using Tomcat( jakarta-tomcat-5.0.28). When i shutdown the
 tomcat server from my unix platform using ./shutdown.sh the java process
 is
 not getting closed.I need to close the process explicitly. Please help me
 in
 this regard.


 It doesn't stop it, or it's taking a long time to stop it?

 Try taking a thread dump after you've called the shutdown script to see
 what's still running in the app.   Should give you a clue as to which code
 is waiting on something.


 p




  Thanks,
 Phani.



 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Some advice on apache tomcat

2009-11-17 Thread Anthony Jay

Yep, I had come accross mod_auth_cookie, but its current status is
questionable and people seem to have moved on to other things. I am just
trying to find out what those other things are! Best practises etc. It
would be  nice to conduct a poll to find out what people are actually
using. I am accepting that almost everyone else knows more than
me
Tony

On Tue, 17 Nov 2009 10:02 +, Pid p...@pidster.com wrote:
 On 16/11/2009 22:07, André Warnier wrote:
  Anthony Jay wrote:
 
  My main issue now is about how the authentication works between Tomcat
  and Apache.
  That's the only one I can readily answer.
  It is extremely simple with mod_jk.
  If the user is authenticated at the Apache level, mod_jk will pass this
  on to the Tomcat server via AJP.
  The only thing to do, is set the 'tomcatAuthentication=false'
  attribute in Tomcat's AJP Connector, and Tomcat will just believe the
  user-id sent by Apache and mod_jk.
  I don't know if, or how, mod_proxy_ajp handles the same thing.
 
 
  In terms of authentication, which should I use, mod_auth_mysql and
  mod_auth_dbm (or mod_auth_form in future or something else?) and why?
 
  There are many many possibilities for this under Apache httpd. Just pick
  the one that you like best, on its own merits.
  They all basically in the end result in the HTTP request being
  authenticated at the Apache httpd level (iow to have a user-id), and
  that's what you want.
 
  What you then do with it under Tomcat is another story, but that is also
  your choice.
 
  In terms of single sign on how can I make the user experience seamless
  between static content-managed pages and jsp/servlets? Will mod_jk
  handle sso? This does not seem clear to me in all the pages I read. If I
  configure form based auth in a login.jsp page will this be relayed to
  apache after a redirect?
 
  No, but why would it be ?
  Ah, if you want to do the authentication in Tomcat rather than in
  Apache, but still use it in Apache ?
  There are ways, but you'll need to write your own Apache (httpd)
  authentication module. You could then define a dummy servlet in Tomcat,
  which just echoes the authenticated user-id (as gotten via
  getRemoteUser() e.g.). Then in Apache httpd, you would make a
  side-request (oherwise known as a sub-request) to this Tomcat webapp
  to get the user-id, and use it to authenticate the current request in
  Apache.
  But that is a complicated scheme, probably only worth it if you find
  some Tomcat authentication method that does not exist in Apache httpd,
  which is unlikely.
 
 
  What is best practise and what should I be doing? If there is some hard
  to find documentation out there with pointers and tips I would
  appreciate a few links.
 
  To read in the Apache httpd docs :
  http://httpd.apache.org/docs/2.2/howto/auth.html
 
  Also, personally I would recommend having a look around here :
  http://cpan.uwinnipeg.ca/search?query=apache%3A%3Aauthmode=dist
  This is the Perl library. Even if you do not intend to do anything with
  Perl, the documentation of many of these modules is a goldmine of
  information about how things work.
 
  Expert advice is appreciated.
  You just got it.
  ;-)
 
 There used to be a mod_auth_cookie module that had form auth 
 capabilities, but it wasn't ever in the main distro, it was listed in 
 the related modules site.
 
 I used a variant of it in a HTTPD 1.3 install many years ago, so I can't 
 vouch for its current status.  GIYF.
 
 
 p
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: centralized log server

2009-11-17 Thread Kaushal Shriyan

On Tue, Nov 17, 2009 at 3:52 PM, Pid p...@pidster.com wrote:
 On 17/11/2009 07:51, Kaushal Shriyan wrote:

 Hi,

 is there a centralized application to access all the tomcat server
 catalina.logs

 All of them on the internet?

I googled for it. but could not locate any one.

Thanks,

Kaushal

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Servlet MessageBrokerServlet is not available on Ubuntu AMD64

2009-11-17 Thread R. S. Patil

Hello,

Production Config.
OS   - Kubuntu 9.10 AMD64 (Dell Vostro 1710 Laptop, 4 GB, 250GB - XP
Dual Booting)
Java -
   Java version 1.6.0_15
   Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
   Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02, mixed mode)
Tomcat - Tomcat 6.0.20-2ubuntu2 (Repository Install)

Development Config.
OS - XP SP3.
Java -
Java version 1.6.0_14
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
Tomcat 6.0.20 Installed by windows exe installer downloaded from
Tomcat downloads.


I have downloaded blazeds-bin-3.3.0.11688.zip and deployed
blazeds.war on winXP tomcat 6.20.There
http://localhost:8080/blazeds/messagebroker/amf
url in browser gives me blank screen as expected.

I deployed same .war in catalina/localhost and tried same URL but I
get following error

Servlet MessageBrokerServlet is not available

instead of blankscreen as expected.

What might be wrong ?

The Tomcat Log is As Follows. Hope Somebody will be able to decode this

16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: Marking servlet MessageBrokerServlet as unavailable
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /blazeds threw load() exception
javax.servlet.UnavailableException
    at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:170)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
    at 
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
    at 
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:115)
    at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1167)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
    at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:123)
    at 
org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:769)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
    at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
    at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
    at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
    at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
    at org.apache.catalina.core.StandardService.start(StandardService.java:516)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at

Re: jdbc-pool ignoring minIdle ?

2009-11-17 Thread Xavier Poinsard


Hi Filip,

Thanks for this precision.
Based on the description on the minIdle parameter, I was thinking the 
validation query failure was the only case where the pool can have less 
connections than minIdle.

Maybe you could add a note about this or change the behaviour.

Best regards,
Xavier.

Filip Hanik - Dev Lists a écrit :
hi Xavier, the pool is not ignoring the minIdle flag, but you have 
configured

p.setMaxAge(43200);

This means,that if a connection has been connected longer than this, 
next time you call con.close() it will be closed and not returned to the 
pool.


The connection pool itself at this point in time will not create a new 
connection. Only when you actually call getConnection() may another 
connection be created.


Filip


On 11/16/2009 09:04 AM, Xavier Poinsard wrote:

Hi all,

I have seen a strange behaviour with the new Tomcat jdbc-pool (1.0.7.1).
It seems to ignore the minIdle parameter.
I have been able to reproduce it with a simple program.
minIdle is set to 5 and after a few seconds, I don't have any idle 
connection left.

Could anybody confirm the bug or point the mistake in my configuration ?
Thanks in advance.
Best regards,
Xavier.

Here is the test program :

public class TestPool {
public static void main(String[] args) throws Exception {
PoolProperties p = new PoolProperties();
p.setUrl(jdbc:postgresql:XXX);
p.setDriverClassName(org.postgresql.Driver);
p.setUsername(login);
p.setPassword(password);
p.setDefaultAutoCommit(false);
p.setJmxEnabled(false);
p.setTestWhileIdle(true);
p.setTestOnBorrow(true);
p.setValidationQuery(SELECT 1);
p.setTestOnReturn(false);
p.setMaxActive(30);
p.setInitialSize(5);
p.setMaxWait(20);
p.setMaxAge(43200);
p.setMinIdle(5);
p.setMaxIdle(15);
p.setLogAbandoned(true);
p.setRemoveAbandoned(true);
p.setRemoveAbandonedTimeout(300);
p.setJdbcInterceptors(StatementFinalizer;ResetAbandonedTimer);

DataSource datasource = new DataSource();
datasource.setPoolProperties(p);
Connection con = null;
try {
while(true){
con = datasource.getConnection();
Statement st = con.createStatement();
ResultSet rs = st.executeQuery(select count(*) from 
users);

rs.close();
st.close();
System.out.println(Pool size :  +datasource.getSize());
System.out.println(Idle :  +datasource.getIdle());
System.out.println(Active :  +datasource.getActive());
con.close();
Thread.sleep(1000);
}
} finally {
if (con!=null) try {con.close();}catch (Exception ignore) {}
}
}
}


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Testing Tomcat with Virtual Hosts

2009-11-17 Thread Marty Pitt NZ


'm trying to test Tomcat virtual hosts on my dev machine (windows 7/Tomcat
6).

I'd like to have requests for localhost, test1.localhost and test2.localhost
all route through to the same tomcat instance.

I've edited my hosts file to look as follows:

127.0.0.1   localhost
::1 localhost
127.0.0.1   test1.localhost
localhost   test2.localhost

And added modified the Engine in server.xml as follows:

Engine defaultHost=localhost name=Catalina
Realm className=org.apache.catalina.realm.UserDatabaseRealm
resourceName=UserDatabase /
Host appBase=webapps autoDeploy=true name=localhost
unpackWARs=true xmlNamespaceAware=false xmlValidation=false
Aliastest1.localhost/Alias
Aliastest2.localhost/Alias
/Host
/Engine
However, I'm getting a 404 when hitting test1.localhost:8080/myWebApp,
although localhost:8080/myWebApp works fine.

I can ping test1.localhost fine.

What have I missed?
-- 
View this message in context: 
http://old.nabble.com/Testing-Tomcat-with-Virtual-Hosts-tp26387899p26387899.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat shudown does not kill java process

2009-11-17 Thread raj kumar

Hi , Please find my thread dump...and suggest me what;'s causing the issue.


Thread-41 prio=5 tid=0x00319a68 nid=0x33 in Object.wait()
[0xd4181000..0xd41819c8]
at java.lang.Object.wait(Native Method)
- waiting on 0xd941bdd8 (a BlockingQueue)
at java.lang.Object.wait(Object.java:429)
at BlockingQueue.deQueue(BlockingQueue.java:76)
- locked 0xd941bdd8 (a BlockingQueue)
at BlockingQueue.deQueue(BlockingQueue.java:59)
- locked 0xd941bdd8 (a BlockingQueue)
at JProxyUpdate.run(JProxyUpdate.java:40)
- locked 0xd955f0f8 (a java.lang.Object)
at java.lang.Thread.run(Thread.java:534)

Thread-40 prio=5 tid=0x0065c8c0 nid=0x32 in Object.wait()
[0xd4281000..0xd42819c8]
at java.lang.Object.wait(Native Method)
- waiting on 0xd92a9920 (a BlockingQueue)
at java.lang.Object.wait(Object.java:429)
at BlockingQueue.deQueue(BlockingQueue.java:76)
- locked 0xd92a9920 (a BlockingQueue)
at BlockingQueue.deQueue(BlockingQueue.java:59)
- locked 0xd92a9920 (a BlockingQueue)
at JProxyUpdate.run(JProxyUpdate.java:40)
- locked 0xd92cd2c0 (a java.lang.Object)
at java.lang.Thread.run(Thread.java:534)

DestroyJavaVM prio=5 tid=0x000381a8 nid=0x1 waiting on condition
[0x..0xffbeeab0]

Thread-39 prio=5 tid=0x002d0098 nid=0x31 in Object.wait()
[0xd2281000..0xd22819c8]
at java.lang.Object.wait(Native Method)
- waiting on 0xd92abf38 (a BlockingQueue)
at java.lang.Object.wait(Object.java:429)
at BlockingQueue.deQueue(BlockingQueue.java:76)
- locked 0xd92abf38 (a BlockingQueue)
at BlockingQueue.deQueue(BlockingQueue.java:59)
- locked 0xd92abf38 (a BlockingQueue)
at JProxyUpdate.run(JProxyUpdate.java:40)
- locked 0xd9419078 (a java.lang.Object)
at java.lang.Thread.run(Thread.java:534)

http-8078-Processor24 daemon prio=5 tid=0x00324738 nid=0x29 waiting on
condition [0xd2a81000..0xd2a819c8]
at java.lang.Thread.sleep(Native Method)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:540)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)

Thread-6 prio=5 tid=0x002ffec8 nid=0x10 waiting on condition
[0xd4381000..0xd43819c8]
at java.lang.Thread.sleep(Native Method)
at JProcessor.run(JProcessor.java:124)
at java.lang.Thread.run(Thread.java:534)

Thread-5 prio=5 tid=0x002ffca8 nid=0xf waiting on condition
[0xd4481000..0xd44819c8]
at java.lang.Thread.sleep(Native Method)
at SocketHandler.GetMessage(SocketHandler.java:202)
at SocketHandler.run(SocketHandler.java:1060)
at java.lang.Thread.run(Thread.java:534)

Thread-4 prio=5 tid=0x002f8038 nid=0xe waiting on condition
[0xd4581000..0xd45819c8]
at java.lang.Thread.sleep(Native Method)
at JProcessor.run(JProcessor.java:124)
at java.lang.Thread.run(Thread.java:534)

Thread-3 prio=5 tid=0x002f7e90 nid=0xd waiting on condition
[0xd4681000..0xd46819c8]
at java.lang.Thread.sleep(Native Method)
at SocketHandler.GetMessage(SocketHandler.java:202)
at SocketHandler.run(SocketHandler.java:1060)
at java.lang.Thread.run(Thread.java:534)

Thread-2 prio=5 tid=0x003786a8 nid=0xc waiting on condition
[0xd4781000..0xd47819c8]
at java.lang.Thread.sleep(Native Method)
at JProcessor.run(JProcessor.java:124)
at java.lang.Thread.run(Thread.java:534)

Thread-1 prio=5 tid=0x00378500 nid=0xb waiting on condition
[0xd4881000..0xd48819c8]
at java.lang.Thread.sleep(Native Method)
at SocketHandler.GetMessage(SocketHandler.java:202)
at SocketHandler.run(SocketHandler.java:1060)
at java.lang.Thread.run(Thread.java:534)

Signal Dispatcher daemon prio=10 tid=0x000f0de8 nid=0x8 waiting on
condition [0x..0x]

Finalizer daemon prio=8 tid=0x000ed780 nid=0x6 in Object.wait()
[0xfb981000..0xfb9819c8]
at java.lang.Object.wait(Native Method)
- waiting on 0xd8d45590 (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked 0xd8d45590 (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

Reference Handler daemon prio=10 tid=0x000ebe18 nid=0x5 in Object.wait()
[0xfba81000..0xfba819c8]
at java.lang.Object.wait(Native Method)
- waiting on 0xd8d455f8 (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:429)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
- locked 0xd8d455f8 (a java.lang.ref.Reference$Lock)

VM Thread prio=5 tid=0x000ea998 nid=0x4 runnable

VM Periodic Task Thread prio=10 tid=0x000f32e0 nid=0xa

RE: Tomcat shudown does not kill java process

2009-11-17 Thread Gerhardus.Geldenhuis

Hi
Probably not your problem but worth mentioning. 

If you options like:
JAVA_OPTS=$JAVA_OPTS -Dcom.sun.management.jmxremote.port=5001
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false 

that is CATALINA specific you should change it to 

CATALINA_OPTS=-Dcom.sun.management.jmxremote.port=5001
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false 

Otherwise the shutdown script that needs to shutdown your server never
gets started because there is a port conflict.

Regards


-Original Message-
From: raj kumar [mailto:bprajkumar...@gmail.com] 
Sent: 17 November 2009 10:01
To: users@tomcat.apache.org
Subject: Tomcat shudown does not kill java process

Hi friends,

I am currently using Tomcat( jakarta-tomcat-5.0.28). When i shutdown the
tomcat server from my unix platform using ./shutdown.sh the java process
is
not getting closed.I need to close the process explicitly. Please help
me in
this regard.

Thanks,
Phani.

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: centralized log server


On 17/11/2009 10:36, Kaushal Shriyan wrote:

On Tue, Nov 17, 2009 at 3:52 PM, Pidp...@pidster.com  wrote:

On 17/11/2009 07:51, Kaushal Shriyan wrote:


Hi,

is there a centralized application to access all the tomcat server
catalina.logs


All of them on the internet?


I googled for it. but could not locate any one.


That's good.  I'm relieved.  I don't want my catalina.out(s) to be 
accessible from the internet.


Or perhaps you mean something else?


p




Thanks,

Kaushal

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Servlet MessageBrokerServlet is not available on Ubuntu AMD64


On 17/11/2009 10:40, R. S. Patil wrote:

Hello,

Production Config.
OS   - Kubuntu 9.10 AMD64 (Dell Vostro 1710 Laptop, 4 GB, 250GB -  XP
Dual Booting)
Java -
Java version 1.6.0_15
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02, mixed mode)
Tomcat - Tomcat 6.0.20-2ubuntu2 (Repository Install)

Development Config.
OS - XP SP3.
Java -
 Java version 1.6.0_14
 Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
 Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
Tomcat 6.0.20 Installed by windows exe installer downloaded from
Tomcat downloads.


I have downloaded blazeds-bin-3.3.0.11688.zip and deployed
blazeds.war on winXP tomcat 6.20.There
http://localhost:8080/blazeds/messagebroker/amf
url in browser gives me blank screen as expected.

I deployed same .war in catalina/localhost and tried same URL but I
get following error

Servlet MessageBrokerServlet is not available

instead of blankscreen as expected.

What might be wrong ?



Something wrong in your blazeds config I'd guess.  I'd ask those folks 
for help, if I were you.



p



The Tomcat Log is As Follows. Hope Somebody will be able to decode this

16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: Marking servlet MessageBrokerServlet as unavailable
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /blazeds threw load() exception
javax.servlet.UnavailableException
 at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:170)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
 at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
 at 
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
 at 
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:115)
 at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1167)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
 at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
 at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
 at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
 at 
org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:123)
 at 
org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:769)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
 at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
 at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
 at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
 at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.core.StandardService.start(StandardService.java:516)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

Thanks for your reply.

 

But can you specify exactly which Servlets API method to use?

 

Note that Tomat-5.5.12 is deployed on Production environment and we are not 
facing major issues.

 

I will appreciate if you can adivse to which Tomcat Stable version we should 
Migrate taking in consideration that Tomcat Cluster is used in our environment 
as well.

 

 



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 10:15:58 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 On 17/11/2009 04:14, Imad Hachem wrote:
 
  Dear all,
 
  I am using Tomcat-5.5.12 as Clustering nodes, and after one node
  shutdown sessionDestroyed is called before contextDestroyed.
 
 Are you still using 5.5.12? Hasn't anyone advised you to upgrade to a 
 newer version yet?
 
 I think it's perfectly reasonably to call sessionDestroyed() before 
 contextDestroyed().
 
  How can I know if sessionDestroyed is called from session.invalidate()
  from the real expiration of the session or shutdown of one cluster node?
 
 You can't know this directly from the Servlet API methods.
 
  Note that on sessionDestroyed event, I am using a Logout behavior to
  logout my users from the DATABASE.
 
  I have tried to set a KEY on the context (or application scope) to check
  on it during the sessionDestroyed event, but it seems the context is
  destroyed after the session destroy event.
 
 This comes up not infrequently on the list, the archives have more 
 information:
 
 http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html
 
  Is there any event listener that I can use before the sessionDestroyed to 
  differentiate if one cluster node has been shutdown or my session has been 
  expired?
 
  Or is how to configure the contextDestroy to be called before the sessions 
  destroy?
 
 No, contextDestroyed() means that the web application itself has been 
 stopped, this is mandated by the Servlet Spec.
 
 
 p
 
 
  Thanks in advance for your help.
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
  
  _
  Windows Live: Make it easier for your friends to see what you’re up to on 
  Facebook.
  http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
  
_
Keep your friends updated―even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


On 17/11/2009 11:31, Imad Hachem wrote:


Dear Pid,

Thanks for your reply.



But can you specify exactly which Servlets API method to use?


The link I sent had some code in it, did you read it?


Note that Tomat-5.5.12 is deployed on Production environment and we are not 
facing major issues.


But you might be facing some security ones.


I will appreciate if you can adivse to which Tomcat Stable version we should 
Migrate taking in consideration that Tomcat Cluster is used in our environment 
as well.


The latest: Tomcat 5.5.28.  Same app, many bugfixes.  Your version was 
released September 2005, over 4 years ago (that's 28 internet years).


It's not good practice to avoid upgrading for that long.


p









Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed

On 17/11/2009 04:14, Imad Hachem wrote:


Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.


Are you still using 5.5.12? Hasn't anyone advised you to upgrade to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed() before
contextDestroyed().


How can I know if sessionDestroyed is called from session.invalidate()
from the real expiration of the session or shutdown of one cluster node?


You can't know this directly from the Servlet API methods.


Note that on sessionDestroyed event, I am using a Logout behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope) to check
on it during the sessionDestroyed event, but it seems the context is
destroyed after the session destroy event.


This comes up not infrequently on the list, the archives have more
information:

http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html


Is there any event listener that I can use before the sessionDestroyed to 
differentiate if one cluster node has been shutdown or my session has been 
expired?

Or is how to configure the contextDestroy to be called before the sessions 
destroy?


No, contextDestroyed() means that the web application itself has been
stopped, this is mandated by the Servlet Spec.


p



Thanks in advance for your help.

Best Regards,
Imad Hachem

System Engineer



_
Windows Live: Make it easier for your friends to see what you’re up to on 
Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



_
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

I have tried that code and didn't helped, note that my context  session 
variables are not coming as null in order to rely on to be able to 
differenciate between Tomcat Node shutdown  session.invalidate().

 

 



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 11:41:20 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 On 17/11/2009 11:31, Imad Hachem wrote:
 
  Dear Pid,
 
  Thanks for your reply.
 
  But can you specify exactly which Servlets API method to use?
 
 The link I sent had some code in it, did you read it?
 
  Note that Tomat-5.5.12 is deployed on Production environment and we are not 
  facing major issues.
 
 But you might be facing some security ones.
 
  I will appreciate if you can adivse to which Tomcat Stable version we 
  should Migrate taking in consideration that Tomcat Cluster is used in our 
  environment as well.
 
 The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was 
 released September 2005, over 4 years ago (that's 28 internet years).
 
 It's not good practice to avoid upgrading for that long.
 
 
 p
 
 
 
 
 
 
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 10:15:58 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
  sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 04:14, Imad Hachem wrote:
 
  Dear all,
 
  I am using Tomcat-5.5.12 as Clustering nodes, and after one node
  shutdown sessionDestroyed is called before contextDestroyed.
 
  Are you still using 5.5.12? Hasn't anyone advised you to upgrade to a
  newer version yet?
 
  I think it's perfectly reasonably to call sessionDestroyed() before
  contextDestroyed().
 
  How can I know if sessionDestroyed is called from session.invalidate()
  from the real expiration of the session or shutdown of one cluster node?
 
  You can't know this directly from the Servlet API methods.
 
  Note that on sessionDestroyed event, I am using a Logout behavior to
  logout my users from the DATABASE.
 
  I have tried to set a KEY on the context (or application scope) to check
  on it during the sessionDestroyed event, but it seems the context is
  destroyed after the session destroy event.
 
  This comes up not infrequently on the list, the archives have more
  information:
 
  http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html
 
  Is there any event listener that I can use before the sessionDestroyed to 
  differentiate if one cluster node has been shutdown or my session has 
  been expired?
 
  Or is how to configure the contextDestroy to be called before the 
  sessions destroy?
 
  No, contextDestroyed() means that the web application itself has been
  stopped, this is mandated by the Servlet Spec.
 
 
  p
 
 
  Thanks in advance for your help.
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
  _
  Windows Live: Make it easier for your friends to see what you’re up to on 
  Facebook.
  http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
  
  _
  Keep your friends updated―even when you’re not signed in.
  http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
  
_
Windows Live: Make it easier for your friends to see what you’re up to on 
Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009

Re: Cannot Start Apache Tomcat 6 service

2009-11-17 Thread Konstantin Kolinko

2009/11/17 Ron Halford rhalf...@crnm.mb.ca:
 Running Windows 7  - 64 bit o/s


 [174 javajni.c] [error] %1 is not a valid win32 application

 [994 prunsrv.c] [error] failed creating java c:\program
 files\\java\jre6\bin\server\jmv.dll


I think it should be jvm, not jmv

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: https and port numbers

2009-11-17 Thread David Smith

Your tomcat has to listen on 443 to remove the port number from the  
URL.  This is not a tomcat issue, but rather the browser's expectation.


-- David


On Nov 17, 2009, at 4:40 AM, Robert Denison r...@blim.org wrote:


Hi,

I've set up my tomcat server to serve http requests on port 8080 and  
https on port 8443. My firewall forwards requests for 80 to 8080 and  
8443 to 8443.


It works fine but as it stands https requests have the form https://mydomain.com:8443 
. I would like to set it up so like most secure internet sites there  
is no port number in the URL even when using https. Can anyone point  
me in the right direction or at some documentation that will help?


Cheers for any help,

R.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 6.0 requires JRE 5.0 issue

2009-11-17 Thread Elizabeth Gorkic

Thank you!

 Date: Mon, 16 Nov 2009 19:28:52 -0500
 From: ma...@apache.org
 To: users@tomcat.apache.org
 Subject: Re: Tomcat 6.0 requires JRE 5.0 issue

 Caldarale, Charles R wrote:
  From: Elizabeth Gorkic [mailto:egor...@hotmail.com]
  Subject: Tomcat 6.0 requires JRE 5.0 issue

  When you open http://apache.crihan.fr/dist/tomcat/tomcat-6/
  v6.0.20/README.html , you get this message:

  Tomcat 6.0 requires JRE 5.0. Read the RELEASE-NOTES and the RUNNING.txt
  file in the distribution for more details.

  It's not at all clear where this README.html file comes from.

 It originates from the ASF server that feeds the mirror system.

  Rely on what's in the Tomcat downloads, which say Java SE 5 or later.

 +1. I have updated README.html for Tomcat 6.0.20 onwards which should get used
 for future versions. The updated file should make it out to the mirror system 
 in
 the next 24 hours or so.

 Mark

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

_
Bing brings you maps, menus, and reviews organized in one place.
http://www.bing.com/search?q=restaurantsform=MFESRPpubl=WLHMTAGcrea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1

Re: https and port numbers

2009-11-17 Thread Tobias Crefeld

Am Tue, 17 Nov 2009 09:40:46 +
schrieb Robert Denison r...@blim.org:

 I've set up my tomcat server to serve http requests on port 8080 and
 https on port 8443. My firewall forwards requests for 80 to 8080 and
 8443 to 8443. 

Tomcat cannot help you in this case. 

You will have to make your firewall forward port 443 to 8443 because
443 is the port number that an average webbrowser assumes if the URL
starts with https://

RU,
 Tobias.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

2009-11-17 Thread Pid Ster

On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com wrote:


 Dear Pid,



 I have tried that code and didn't helped, note that my context 
 session variables are not coming as null in order to rely on to be
 able to differenciate between Tomcat Node shutdown 
 session.invalidate().

I'm sorry but I don't understand what you're saying here.

Tomcat  the servlet api can't tell you the difference between an app
shutdown and a session expiry without you writing code.

What did you try?

What was or wasn't null exactly?

p


 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 11:41:20 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
 shutdown, sessionDestroyed been called before contextDestroyed

 On 17/11/2009 11:31, Imad Hachem wrote:

 Dear Pid,

 Thanks for your reply.

 But can you specify exactly which Servlets API method to use?

 The link I sent had some code in it, did you read it?

 Note that Tomat-5.5.12 is deployed on Production environment and
 we are not facing major issues.

 But you might be facing some security ones.

 I will appreciate if you can adivse to which Tomcat Stable version
 we should Migrate taking in consideration that Tomcat Cluster is
 used in our environment as well.

 The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
 released September 2005, over 4 years ago (that's 28 internet years).

 It's not good practice to avoid upgrading for that long.


 p








 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 10:15:58 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
 shutdown, sessionDestroyed been called before contextDestroyed

 On 17/11/2009 04:14, Imad Hachem wrote:

 Dear all,

 I am using Tomcat-5.5.12 as Clustering nodes, and after one node
 shutdown sessionDestroyed is called before contextDestroyed.

 Are you still using 5.5.12? Hasn't anyone advised you to upgrade
 to a
 newer version yet?

 I think it's perfectly reasonably to call sessionDestroyed() before
 contextDestroyed().

 How can I know if sessionDestroyed is called from
 session.invalidate()
 from the real expiration of the session or shutdown of one
 cluster node?

 You can't know this directly from the Servlet API methods.

 Note that on sessionDestroyed event, I am using a Logout
 behavior to
 logout my users from the DATABASE.

 I have tried to set a KEY on the context (or application scope)
 to check
 on it during the sessionDestroyed event, but it seems the
 context is
 destroyed after the session destroy event.

 This comes up not infrequently on the list, the archives have more
 information:

 http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html

 Is there any event listener that I can use before the
 sessionDestroyed to differentiate if one cluster node has been
 shutdown or my session has been expired?

 Or is how to configure the contextDestroy to be called before
 the sessions destroy?

 No, contextDestroyed() means that the web application itself has
 been
 stopped, this is mandated by the Servlet Spec.


 p


 Thanks in advance for your help.

 Best Regards,
 Imad Hachem

 System Engineer



 _
 Windows Live: Make it easier for your friends to see what yo
 u锟斤拷re up to on Facebook.
 http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009


 ---
 --
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


 _
 Keep your friends updated锟斤拷even when you锟斤拷re not
 signed in.
 http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


 _
 Windows Live: Make it easier for your friends to see what you锟斤拷
 re up to on Facebook.
 http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

I am running a Logout Process at each sessionDestroy.

 

After applying the Cluster configuration,  I don't want to Logout my Users (or 
run this Logout Process) after any Tomcat Cluster node shutdown, since the 
Session has been replicated to the other Node Cluster.

 



Best Regards,
Imad Hachem 

System Engineer 



 
 From: p...@pidster.com
 Date: Tue, 17 Nov 2009 13:09:47 +
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 To: users@tomcat.apache.org
 
 On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com wrote:
 
 
  Dear Pid,
 
 
 
  I have tried that code and didn't helped, note that my context 
  session variables are not coming as null in order to rely on to be
  able to differenciate between Tomcat Node shutdown 
  session.invalidate().
 
 I'm sorry but I don't understand what you're saying here.
 
 Tomcat  the servlet api can't tell you the difference between an app
 shutdown and a session expiry without you writing code.
 
 What did you try?
 
 What was or wasn't null exactly?
 
 p
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 11:41:20 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 11:31, Imad Hachem wrote:
 
  Dear Pid,
 
  Thanks for your reply.
 
  But can you specify exactly which Servlets API method to use?
 
  The link I sent had some code in it, did you read it?
 
  Note that Tomat-5.5.12 is deployed on Production environment and
  we are not facing major issues.
 
  But you might be facing some security ones.
 
  I will appreciate if you can adivse to which Tomcat Stable version
  we should Migrate taking in consideration that Tomcat Cluster is
  used in our environment as well.
 
  The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
  released September 2005, over 4 years ago (that's 28 internet years).
 
  It's not good practice to avoid upgrading for that long.
 
 
  p
 
 
 
 
 
 
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 10:15:58 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 04:14, Imad Hachem wrote:
 
  Dear all,
 
  I am using Tomcat-5.5.12 as Clustering nodes, and after one node
  shutdown sessionDestroyed is called before contextDestroyed.
 
  Are you still using 5.5.12? Hasn't anyone advised you to upgrade
  to a
  newer version yet?
 
  I think it's perfectly reasonably to call sessionDestroyed() before
  contextDestroyed().
 
  How can I know if sessionDestroyed is called from
  session.invalidate()
  from the real expiration of the session or shutdown of one
  cluster node?
 
  You can't know this directly from the Servlet API methods.
 
  Note that on sessionDestroyed event, I am using a Logout
  behavior to
  logout my users from the DATABASE.
 
  I have tried to set a KEY on the context (or application scope)
  to check
  on it during the sessionDestroyed event, but it seems the
  context is
  destroyed after the session destroy event.
 
  This comes up not infrequently on the list, the archives have more
  information:
 
  http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html
 
  Is there any event listener that I can use before the
  sessionDestroyed to differentiate if one cluster node has been
  shutdown or my session has been expired?
 
  Or is how to configure the contextDestroy to be called before
  the sessions destroy?
 
  No, contextDestroyed() means that the web application itself has
  been
  stopped, this is mandated by the Servlet Spec.
 
 
  p
 
 
  Thanks in advance for your help.
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
  _
  Windows Live: Make it easier for your friends to see what yo
  u锟斤拷re up to on Facebook.
  http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009
 
 
  ---
  --
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
  _
  Keep your friends updated锟斤拷even when you锟斤拷re not
  signed in.
  http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
 
 
  -
  To unsubscribe, e-mail:

RE: https and port numbers

2009-11-17 Thread Neil Aggarwal

 It works fine but as it stands https requests have the form 
 https://mydomain.com:8443. I would like to set it up so like 
 most secure internet sites there is no port number in the URL 
 even when using https. Can anyone point me in the right 
 direction or at some documentation that will help?

For that, you need to have your firewall forward port
443 to port 8443 on Tomcat.

Neil

--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
Host your tomcat app on a CentOS VPS for only $25/month!
Unmetered bandwidth, 7 day no risk trial, Google Checkout


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: https and port numbers

2009-11-17 Thread Robert Denison

That's exactly what I was hoping for, thanks David (and others who have 
posted), you're a gent. 

I thought it might be something like that but I couldn't find any conclusive 
evidence about handling secure ports...

R.

On 17 Nov 2009, at 12:39, David Smith wrote:

 Your tomcat has to listen on 443 to remove the port number from the URL.  
 This is not a tomcat issue, but rather the browser's expectation.
 
 -- David
 
 
 On Nov 17, 2009, at 4:40 AM, Robert Denison r...@blim.org wrote:
 
 Hi,
 
 I've set up my tomcat server to serve http requests on port 8080 and https 
 on port 8443. My firewall forwards requests for 80 to 8080 and 8443 to 8443.
 
 It works fine but as it stands https requests have the form 
 https://mydomain.com:8443. I would like to set it up so like most secure 
 internet sites there is no port number in the URL even when using https. Can 
 anyone point me in the right direction or at some documentation that will 
 help?
 
 Cheers for any help,
 
 R.
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Apache Tomcat 5.5.27 on a load balanced environment

2009-11-17 Thread Yashesh Bhatia

Hello Group:

   I was trying to configure Apache Solr using the Tomcat Servlet container in a
load balanced environment.

Here's the setup

 Load Balancer
|
---
   ||
  Front End 1 Front End 2

Now the domain we're using is  solr.company1.com which points to the
load balancer and
the traffic on port 8080 on the LB is routed to FE1 or FE2

ApacheSolr using the tomcat servlet container is installed on both FE1
and FE2 (installation
instructions are here - http://drupal.org/node/443976#comment-2256696)

This was done a week ago and i was able to access the Solr Admin interface at
http://solr.company1.com:8080/solr/admin/

We wanted to remove the localhost completely and have it only accessed
with solr.company1.com
and here's what i did (i messed it here for sure)

- Moved $CATALINA_HOME/conf/Catalina/localhost to
$CATALINA_HOME/conf/Catalina/solr.company1.com
- Edited $CATALINA_HOME/conf/server.xml and server-minimal.xml and
replaced localhost with solr.company1.com

restarted solr and tried to view the admin at -
http://solr.company1.com:8080/solr/admin/ ,
but  now i get the error
---
HTTP Status 404 - missing core name in path
type Status report
message missing core name in path
description The requested resource (missing core name in path) is not available.
Apache Tomcat/5.5.27
---

After getting the new found error i revered back solr.company1.com
changes to localhost
and restarted solr. However,  i still get the same error.

Any help on how to fix it ?

Thanks.

Yashesh Bhatia.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

authenticate LDAP across domains

2009-11-17 Thread nabbleQuestioner


I am trying to use tomcat to authenticate using LDAP and configured the
server.xml with no problems... the problem is that the request is not able
to get to the Active directory because I am sending the request from a
client that sits on domain A and the LDAP server sits on domain B. Is there
any way to tell tomcat that I want a different domain that where I currently
am? (tell tomcat what domain the active directory is sitting on)?
-- 
View this message in context: 
http://old.nabble.com/authenticate-LDAP-across-domains-tp26390861p26390861.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Why Tomcat on startup should navigate to some jsp?

2009-11-17 Thread gamby


Hi all,

In my web app I've noticed that on Tomcat startup, someone tries to
navigate to some unidentified jsp and not finding that, tries to navigate to
404 error page.

And so, there is a page forwarding during Tomcat startup that I'm not able
to understand, even if enable all tomcat logs.

The only thing that I can see is that it's being called the 404 page during
startup.

My problem related to this issue is that, I have defined my own 404 page,
and it contains some beans that during Tomcat startup are yet null,
generating a lot of exceptions during startup...

I know that this description is quite confusing but is all I can state, hope
someone can give me some hints.

best regards
Raffaele
-- 
View this message in context: 
http://old.nabble.com/Why-Tomcat-on-startup-should-navigate-to-some-jsp--tp26390996p26390996.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

2009-11-17 Thread Ronald Klop

Hi Imad,

I think also that Tomcat should only invalidate the Session on shutdown if it
is the last node in the cluster.
But the developers of Tomcat think of it as invalidating the Session object (as
in java Object) and you and me see it as invalidating the session of the user.

Ronald. (The Ronald of the link mentioned by Pid.)

Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
hachem_i...@hotmail.com:

Dear Pid,

I am running a Logout Process at each sessionDestroy.

After applying the Cluster configuration, I don't want to Logout my Users (or
run this Logout Process) after any Tomcat Cluster node shutdown, since the
Session has been replicated to the other Node Cluster.

Best Regards,
Imad Hachem

System Engineer

From: p...@pidster.com

Date: Tue, 17 Nov 2009 13:09:47 +
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown,
sessionDestroyed been called before contextDestroyed
To: users@tomcat.apache.org

On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com wrote:

Dear Pid,

I'm sorry but I don't understand what you're saying here.

Tomcat the servlet api can't tell you the difference between an app

shutdown and a session expiry without you writing code.

What did you try?

What was or wasn't null exactly?

Best Regards,

Imad Hachem

System Engineer

Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 11:31, Imad Hachem wrote:

Dear Pid,

Thanks for your reply.

But can you specify exactly which Servlets API method to use?

The link I sent had some code in it, did you read it?

Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.

But you might be facing some security ones.

I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.

The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet years).

It's not good practice to avoid upgrading for that long.

Best Regards,
Imad Hachem

System Engineer

Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 04:14, Imad Hachem wrote:

Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.

Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed() before
contextDestroyed().

How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?

You can't know this directly from the Servlet API methods.

Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.

This comes up not infrequently on the list, the archives have more
information:

http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html

Is there any event listener that I can use before the
sessionDestroyed to differentiate if one cluster node has been
shutdown or my session has been expired?

Or is how to configure the contextDestroy to be called before
the sessions destroy?

No, contextDestroyed() means that the web application itself has
been
stopped, this is mandated by the Servlet Spec.

Thanks in advance for your help.

Best Regards,
Imad Hachem

System Engineer

_
Windows Live: Make it easier for your friends to see what yo
u锟斤拷re up to on Facebook.

http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009

---
--
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:

RE: Cannot Start Apache Tomcat 6 service

 From: Ron Halford [mailto:rhalf...@crnm.mb.ca]
 Subject: Cannot Start Apache Tomcat 6 service

 Checked Tomcat log: Jakarta_service_20091116 and noted the following -
 [174 javajni.c] [error] %1 is not a valid win32 application
 [994 prunsrv.c] [error] failed creating java c:\program
 files\\java\jre6\bin\server\jmv.dll

Make sure you have the 64-bit version of tomcat6.exe installed; this is 
required since you're running a 64-bit JVM.  Download it from here:
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/res/procrun/amd64/

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Deployment specific configuration - best practice

Rainer Frey (Inxmail GmbH) wrote:
 On Tuesday 17 November 2009 01:15:52 Mark Thomas wrote:
 Rainer Frey wrote:
  * settings in /META-INF/context.xml
 This one please.

 Tomcat will extract it on first deployment. OK that will fail but we can
 then edit the extracted version and Tomcat will use that from then on.
 
 Thanks for the info, will do that. The actual problem is described in 
 Message-Id: 200911161424.38011.rainer.f...@inxmail.de (Webapp reload and 
 DriverManager in Tomcat 6.0 trunk).

Should have said this before - create a Bugzilla entry for this and
attach your demo app there. I suspect my recent JDBC memory leak
protection changes, but I'll need to do some testing to be sure.

Mark




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat shudown does not kill java process

raj kumar wrote:
 Hi , Please find my thread dump...and suggest me what;'s causing the issue.
 
 
 Thread-41 prio=5 tid=0x00319a68 nid=0x33 in Object.wait()
 [0xd4181000..0xd41819c8]



 Thread-40 prio=5 tid=0x0065c8c0 nid=0x32 in Object.wait()
 [0xd4281000..0xd42819c8]


and any threads like them. If you start a thread, you have to either:
a) make it a daemon thread
or
b) stop it before shutting down Tomcat

Mark



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Why Tomcat on startup should navigate to some jsp?

gamby wrote:
 Hi all,
 
 In my web app I've noticed that on Tomcat startup, someone tries to
 navigate to some unidentified jsp and not finding that, tries to navigate to
 404 error page.
 
 And so, there is a page forwarding during Tomcat startup that I'm not able
 to understand, even if enable all tomcat logs.
 
 The only thing that I can see is that it's being called the 404 page during
 startup.
 
 My problem related to this issue is that, I have defined my own 404 page,
 and it contains some beans that during Tomcat startup are yet null,
 generating a lot of exceptions during startup...

And the full stack trace of the first of those exceptions is...?

Mark



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: authenticate LDAP across domains


On 17/11/2009 14:25, nabbleQuestioner wrote:


I am trying to use tomcat to authenticate using LDAP and configured the
server.xml with no problems... the problem is that the request is not able
to get to the Active directory because I am sending the request from a
client that sits on domain A and the LDAP server sits on domain B. Is there
any way to tell tomcat that I want a different domain that where I currently
am? (tell tomcat what domain the active directory is sitting on)?


Which Tomcat version are you using?

What have you found when you searched the archives?

Can't you just specify the connectionURL=ldap://ldap.domain.com;?


p

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat DBCP Connection Pooling to MySQL limited number of connection issue in Spring2.5 + Hibernate3 + commons-DBCP1.2

2009-11-17 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yagnesh,

On 11/17/2009 12:32 AM, Yagnesh Chawda wrote:
  Thanks Chris, That was just a typo. Thanks for pointing it out. But in real
 configuration was was not commented. It was some other config which I was
 trying and forgot to uncomment it in posting.

Ok.

 bean id=dataSource destroy-method=close
   class=org.apache.commons.dbcp.BasicDataSource
   property name=driverClassName
value=com.mysql.jdbc.jdbc2.optional.MysqlDataSource/
   property name=url value=${db.url}/
   property name=username value=${db.user}/
   property name=password value=${db.pass}/
   property name=initialSize value=40/
   property name=minIdle value=35/
   property name=maxActive value=95/
   property name=maxWait value=2/
   /bean

I find it unusual that you'd be using a DataSource as the driver class
name. Typically, for MySQL, you'd use com.mysql.jdbc.Driver as the class
name, not the MySQL-supplied DataSource as the driver class name.

Other than that, I would expect your connection pool to always have a
minimum of 35 connections sitting idle in it, even when your site was
seeing no traffic.

I wonder if the problem is that you appear to be using two data sources
instead of one data source and one JDBC driver.

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

iEYEARECAAYFAksCvlgACgkQ9CaO5/Lv0PCNRQCgwqSmsc1EUj7aCxh1hGhGjImC
7IIAnjC4PQCrSepnOuMUvAcAIAQy8Kia
=8Fl9
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: centralized log server

 From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com]
 Subject: centralized log server

 is there a centralized application to access all the tomcat server
 catalina.logs

Your question is badly phrased, as Pid keeps trying to point out.

If all you want is to be able to look at the log files, any editor will do.

LambdaProbe can display the Tomcat log files in a browser - if it can be 
installed on your version of Tomcat, which you didn't bother to tell us.  You 
also didn't tell us what platform you're running on, or whether you're using a 
standard Tomcat download or a 3rd-party repackaged version.  (The location of 
the log files varies with each.)

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Hi Ronald,

 

Thanks for your reply.

 

So, what 's the solution in my Case?

 

I need to differentiate between Tomat Cluster node shutdown and 
session.invalidate and session Timout?

 

Is that Possible as configuration or Programming ?

 

 



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 15:40:30 +0100
 From: ronald-mailingl...@base.nl
 To: users@tomcat.apache.org
 Subject: RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 Hi Imad,
 
 I think also that Tomcat should only invalidate the Session on shutdown if it 
 is the last node in the cluster.
 But the developers of Tomcat think of it as invalidating the Session object 
 (as in java Object) and you and me see it as invalidating the session of the 
 user.
 
 Ronald. (The Ronald of the link mentioned by Pid.)
 
 
 Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem 
 hachem_i...@hotmail.com:
  
  
  
  
  Dear Pid,
  
  
  
  I am running a Logout Process at each sessionDestroy.
  
  
  
  After applying the Cluster configuration, I don't want to Logout my Users 
  (or run this Logout Process) after any Tomcat Cluster node shutdown, since 
  the Session has been replicated to the other Node Cluster.
  
  
  
  
  
  Best Regards,
  Imad Hachem 
  
  System Engineer 
  
  
  
  
   From: p...@pidster.com
   Date: Tue, 17 Nov 2009 13:09:47 +
   Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
   sessionDestroyed been called before contextDestroyed
   To: users@tomcat.apache.org
   
   On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com wrote:
   
   
Dear Pid,
   
   
   
I have tried that code and didn't helped, note that my context 
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown 
session.invalidate().
   
   I'm sorry but I don't understand what you're saying here.
   
   Tomcat  the servlet api can't tell you the difference between an app
   shutdown and a session expiry without you writing code.
   
   What did you try?
   
   What was or wasn't null exactly?
   
   p
   
   
Best Regards,
Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 11:31, Imad Hachem wrote:
   
Dear Pid,
   
Thanks for your reply.
   
But can you specify exactly which Servlets API method to use?
   
The link I sent had some code in it, did you read it?
   
Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.
   
But you might be facing some security ones.
   
I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.
   
The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet years).
   
It's not good practice to avoid upgrading for that long.
   
   
p
   
   
   
   
   
   
   
   
Best Regards,
Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 04:14, Imad Hachem wrote:
   
Dear all,
   
I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.
   
Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?
   
I think it's perfectly reasonably to call sessionDestroyed() before
contextDestroyed().
   
How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?
   
You can't know this directly from the Servlet API methods.
   
Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.
   
I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.
   
This comes up not infrequently on the list, the archives have more
information:
   
http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html
   
Is there any event listener that I can use before the
sessionDestroyed to differentiate if one cluster node has been
shutdown or my

Re: Why Tomcat on startup should navigate to some jsp?

2009-11-17 Thread gamby


Unfortunately the stacktrace is not useful for you because exceptions are
thrown because of some bean missing, but it is absolutely normal in my
opinion, no one filter has yet started during this phase of startup.

Tomcat tries to load the 404, but I have redefined it, including in it a
header and footer jsp using Struts tiles, and in header there is a bean not
yet loaded on startup, and this is the cause of exception.

What I would you like to know is why Tomcat should navigate toward some page
on startup, launching the 404 even if there wasn't yet a real user
navigation.

I'm using also dwr, I don't know if it could be one of the causes.
Thanks


Mark Thomas wrote:
 
 gamby wrote:
 Hi all,
 
 In my web app I've noticed that on Tomcat startup, someone tries to
 navigate to some unidentified jsp and not finding that, tries to navigate
 to
 404 error page.
 
 And so, there is a page forwarding during Tomcat startup that I'm not
 able
 to understand, even if enable all tomcat logs.
 
 The only thing that I can see is that it's being called the 404 page
 during
 startup.
 
 My problem related to this issue is that, I have defined my own 404 page,
 and it contains some beans that during Tomcat startup are yet null,
 generating a lot of exceptions during startup...
 
 And the full stack trace of the first of those exceptions is...?
 
 Mark
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Why-Tomcat-on-startup-should-navigate-to-some-jsp--tp26390996p26391779.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: https and port numbers

2009-11-17 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

On 11/17/2009 7:39 AM, David Smith wrote:
 Your tomcat has to listen on 443 to remove the port number from the
 URL.  This is not a tomcat issue, but rather the browser's expectation.

That's not entirely true. If Robert configures his firewall to redirect
port 443 - 8443 similar to how he does 80 - 8080, then he can remove
the port number from the URL by changing the redirectPort attribute in
his Connector to 443.

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

iEYEARECAAYFAksCwRQACgkQ9CaO5/Lv0PAEMwCfUG5PRI63Mu1Hqtz/SM1yc44M
g5UAniTtU0Bmr0TkC7CdPdYtZfntKrme
=utz4
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Webapp reload and DriverManager in Tomcat 6.0 trunk

2009-11-17 Thread Rainer Frey

On Monday 16 November 2009 14:24:37 Rainer Frey wrote:
 Hi,

 I found a problem when using DriverManager.getConnection() with a build
 from current 6.0 SVN 

[...]

As requested, added a bugzilla entry:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48214

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Deployment specific configuration - best practice

2009-11-17 Thread Rainer Frey

On Tuesday 17 November 2009 16:04:48 Mark Thomas wrote:
 Rainer Frey (Inxmail GmbH) wrote:
  On Tuesday 17 November 2009 01:15:52 Mark Thomas wrote:
  Rainer Frey wrote:
  Thanks for the info, will do that. The actual problem is described in
  Message-Id: 200911161424.38011.rainer.f...@inxmail.de (Webapp reload
  and DriverManager in Tomcat 6.0 trunk).

 Should have said this before - create a Bugzilla entry for this and
 attach your demo app there. 

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

Thanks
Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Loading customized StandardContext subclass

2009-11-17 Thread Joel SCHAAL


Hello all,

First, thank you for releasing Tomcat as free software, it is some really nice 
and valuable software.

At our company we developped an application server under java, and we used to 
have tomcat included as third-party library.
Now we would like to only have a dependency on Tomcat. Thus, we are converting 
our application server to a Tomcat webapp.

In order to have our server started when the Tomcat server starts the webapp, I 
implemented a sub class of org.apache.catalina.core.StandardContext and 
exported it in our JARs.
I set our test application to use that class in the file META-INF/context.xml (through the attribute 
className of the tag context)
Since we want to have more than one of our application in the same server, I 
put our jars in ${catalina.home}/lib/ instead of WEB-INF/lib and I added the 
reference of every sub-folder in ${catalina.home}/lib/ to the server.loader 
parameter in ${catalina.home}/conf/catalina.properties (using *.jar)
(tried shared.loader and common.loader as well, with no use)

The problem, I get this exception at server startup :
GRAVE: Erreur lors du déploiement du répertoire upsm de l'application web
java.lang.ClassNotFoundException: eserve.framework.EserveContext
  at 
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2808)
  at 
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2834)
  at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1361)
  at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDriver.scanRootElementHook(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown 
Source)
  at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
  at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
Source)
  at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
Source)
  at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
  at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown 
Source)
  at 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
 Source)
  at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1628)
  at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:941)
  at 
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909)
  at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495)
  at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
  at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
  at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
  at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
  at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
  at org.apache.catalina.core.StandardService.start(StandardService.java:516)
  at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)

(sorry for the french message, it does approximately mean : Error during the 
upsm directory deployment of the web application)
The eserve.framework.EserveContext class name is the one that was given to 
context/@className

I looked in the source code, and found out that the class loader of the Digest 
at that time is the one used at startup time.
I thought it would be the one from Bootstrap.catalinaLoader.
What have I done wrong ? Should I specify another classloader in a file ? I did 
not find this information in any of the following locations :
- http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
- http://tomcat.apache.org/tomcat-6.0-doc/config/context.html
- http://www.jcp.org/aboutJava/communityprocess/final/jsr053/

Thank

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

2009-11-17 Thread Ronald Klop


Hi Imad,

You can do everything you like, but it will all be dirty.
1. Set a global variable in your webapp before shutdown of a node. To see If it 
is a planned shutdown or not.
2. Keep references about the nr. of clusternodes yourself. Can be done quite 
cleanly with JMX.
3. Do not really logout the user. Only mark a logout time. If another node 
shuts down or the user really logs out it will overwrite the logout time. And 
in the end the data is quite correct. (This is what I do.)

Everything as pros and cons. Be creative. (I would like to here what works for 
you.)


But the developers of Tomcat think of it as invalidating the Session object (as 
in java Object) and you and me see it as invalidating the session of the user.


This phrase was not very accurate. I meant destroy in stead of invalidating. 
Because those are different things.

Ronald.


Op dinsdag, 17 november 2009 16:23 schreef Imad Hachem 
hachem_i...@hotmail.com:


 



Hi Ronald,

 


Thanks for your reply.

 


So, what 's the solution in my Case?

 


I need to differentiate between Tomat Cluster node shutdown and 
session.invalidate and session Timout?

 


Is that Possible as configuration or Programming ?

 

 




Best Regards,
Imad Hachem 

System Engineer 




 
 Date: Tue, 17 Nov 2009 15:40:30 +0100

 From: ronald-mailingl...@base.nl
 To: users@tomcat.apache.org
 Subject: RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed
 
 Hi Imad,
 
 I think also that Tomcat should only invalidate the Session on shutdown if it is the last node in the cluster.

 But the developers of Tomcat think of it as invalidating the Session object 
(as in java Object) and you and me see it as invalidating the session of the user.
 
 Ronald. (The Ronald of the link mentioned by Pid.)
 
 
 Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem hachem_i...@hotmail.com:
  
  
  
  
  Dear Pid,
  
  
  
  I am running a Logout Process at each sessionDestroy.
  
  
  
  After applying the Cluster configuration, I don't want to Logout my Users (or run this Logout Process) after any Tomcat Cluster node shutdown, since the Session has been replicated to the other Node Cluster.
  
  
  
  
  
  Best Regards,
  Imad Hachem 
  
  System Engineer 
  
  
  
  
   From: p...@pidster.com

   Date: Tue, 17 Nov 2009 13:09:47 +
   Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed
   To: users@tomcat.apache.org
   
   On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com wrote:
   
   

Dear Pid,
   
   
   
I have tried that code and didn't helped, note that my context 
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown 
session.invalidate().
   
   I'm sorry but I don't understand what you're saying here.
   
   Tomcat  the servlet api can't tell you the difference between an app

   shutdown and a session expiry without you writing code.
   
   What did you try?
   
   What was or wasn't null exactly?
   
   p
   
   
Best Regards,

Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 11:31, Imad Hachem wrote:
   
Dear Pid,
   
Thanks for your reply.
   
But can you specify exactly which Servlets API method to use?
   
The link I sent had some code in it, did you read it?
   
Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.
   
But you might be facing some security ones.
   
I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.
   
The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet years).
   
It's not good practice to avoid upgrading for that long.
   
   
p
   
   
   
   
   
   
   
   
Best Regards,
Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 04:14, Imad Hachem wrote:
   
Dear all,
   
I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.
   
Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?
   
I think it's perfectly reasonably to call sessionDestroyed() before

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 14:40, Ronald Klop wrote:

Hi Imad,

Ronald. (The Ronald of the link mentioned by Pid.)

Did the code supplied therein, work for you Ronald?

@Imad

The Servlet Spec (and therefore Tomcat) doesn't differentiate between
causes of session expiry.

The code requires you to set a value in the application scope, then the
HttpSessionListener sessionDestroyed method checks for that value.

If the value is present, you initiated shutdown. If it is not, then
it's probably a session expiry and you run your logout code.

Did you actually set such an attribute?

Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
hachem_i...@hotmail.com:

Dear Pid,

I am running a Logout Process at each sessionDestroy.

After applying the Cluster configuration, I don't want to Logout my
Users (or run this Logout Process) after any Tomcat Cluster node
shutdown, since the Session has been replicated to the other Node
Cluster.

Best Regards,
Imad Hachem
System Engineer

From: p...@pidster.com
Date: Tue, 17 Nov 2009 13:09:47 +
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
To: users@tomcat.apache.org
On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com
wrote:

Dear Pid,

I have tried that code and didn't helped, note that my context
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown
session.invalidate().
I'm sorry but I don't understand what you're saying here.
Tomcat the servlet api can't tell you the difference between an app
shutdown and a session expiry without you writing code.
What did you try?
What was or wasn't null exactly?
p
Best Regards,
Imad Hachem

System Engineer

On 17/11/2009 11:31, Imad Hachem wrote:

Dear Pid,

Thanks for your reply.

But can you specify exactly which Servlets API method to use?

The link I sent had some code in it, did you read it?

Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.

But you might be facing some security ones.

I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.

The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet
years).

It's not good practice to avoid upgrading for that long.

Best Regards,
Imad Hachem

System Engineer

On 17/11/2009 04:14, Imad Hachem wrote:

Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.

Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed()
before
contextDestroyed().

How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?

You can't know this directly from the Servlet API methods.

Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.

This comes up not infrequently on the list, the archives have more
information:

http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html

Is there any event listener that I can use before the
sessionDestroyed to differentiate if one cluster node has been
shutdown or my session has been expired?

Or is how to configure the contextDestroy to be called before
the sessions destroy?

No, contextDestroyed() means that the web application itself has
been
stopped, this is mandated by the Servlet Spec.

Thanks in advance for your help.

Best Regards,
Imad Hachem

System Engineer

_
Windows Live: Make it easier for your friends to see what yo
u锟斤拷re up to on Facebook.

RE: Apache Tomcat 5.5.27 on a load balanced environment

 From: Yashesh Bhatia [mailto:yashe...@venuslabs.co.in]
 Subject: Apache Tomcat 5.5.27 on a load balanced environment

 We wanted to remove the localhost completely and have it only accessed
 with solr.company1.com

Why?  What do you think that achieves?

If you have only one Host entry in your Tomcat configuration, its name is 
irrelevant, so just leave it at localhost.

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

synchronizing in tomcat

2009-11-17 Thread David Balažic

Hi!

Does tomcat offer any mechanism for locking servlet executions?

So if one servlet does:
 - get 10 EUR from account 1 (read account 1 balance; substract 10;
store new balance)
 - add 10 EUR to account 2 (...)

How can I make sure no other servlet does (read account 1 balance;
sustract 10; store new balance) at the same
time and cause lost account money?

The account data is in a database, accessed over hibernate (or
directly, if needed).

Regards,
David

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Multiple war files for the same application context.

 From: Ziggy [mailto:zigg...@gmail.com]
 Subject: Re: Multiple war files for the same application context.

 That is interesting. Is the # supposed to be part of the filename?

Read the doc:
http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic%20Application%20Deployment

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat DBCP Connection Pooling to MySQL limited number of connection issue in Spring2.5 + Hibernate3 + commons-DBCP1.2

2009-11-17 Thread Yagnesh Chawda


Hi Chris,
  Thanks for reply. I had tried using com.mysql.jdbc.Driver as well
earlier. But no luck :(



Christopher Schultz-2 wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Yagnesh,
 
 On 11/17/2009 12:32 AM, Yagnesh Chawda wrote:
  Thanks Chris, That was just a typo. Thanks for pointing it out. But in
 real
 configuration was was not commented. It was some other config which I was
 trying and forgot to uncomment it in posting.
 
 Ok.
 
 bean id=dataSource destroy-method=close
   class=org.apache.commons.dbcp.BasicDataSource
  property name=driverClassName
value=com.mysql.jdbc.jdbc2.optional.MysqlDataSource/
  property name=url value=${db.url}/
  property name=username value=${db.user}/
  property name=password value=${db.pass}/
  property name=initialSize value=40/
  property name=minIdle value=35/
  property name=maxActive value=95/
  property name=maxWait value=2/
  /bean
 
 I find it unusual that you'd be using a DataSource as the driver class
 name. Typically, for MySQL, you'd use com.mysql.jdbc.Driver as the class
 name, not the MySQL-supplied DataSource as the driver class name.
 
 Other than that, I would expect your connection pool to always have a
 minimum of 35 connections sitting idle in it, even when your site was
 seeing no traffic.
 
 I wonder if the problem is that you appear to be using two data sources
 instead of one data source and one JDBC driver.
 
 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
 iEYEARECAAYFAksCvlgACgkQ9CaO5/Lv0PCNRQCgwqSmsc1EUj7aCxh1hGhGjImC
 7IIAnjC4PQCrSepnOuMUvAcAIAQy8Kia
 =8Fl9
 -END PGP SIGNATURE-
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Tomcat-DBCP-Connection-Pooling-to-MySQL-limited-number-of-connection-issue-in-Spring2.5-%2B-Hibernate3-%2B-commons-DBCP1.2-tp26372475p26392261.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Classloading problem in jasper when using JSF with OSGi

2009-11-17 Thread Thierry Templier

Hello,

I'm trying to use JSF RI within an OSGi environment (Equinox) which embeds 
Tomcat 5.5. The latter is started using facilities of Spring DM.

I provision the container with necessary OSGi bundles for JSF RI 1.2.08 
(bundles from SpringSource repository) and create a Web bundle containing a JSF 
Web application.

My JSF pages uses standard JSF taglibs and expressions like that:

%@ taglib uri=http://java.sun.com/jsf/html; prefix=h%
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f%

f:view
html
body lang=fr
h:outputText value=Id / Test
/body
/html
/f:view

Initializing works correctly but I have an exception when trying to load page:

org.apache.jasper.JasperException: Unable to convert string Id to class 
javax.el.ValueExpression for attribute value: Property Editor not 
registered with the PropertyEditorManager
at 
org.apache.jasper.runtime.JspRuntimeLibrary.getValueFromPropertyEditorManager(JspRuntimeLibrary.java:884)
at 
org.apache.jsp.jsp.contacts_jsp._jspx_meth_h_005foutputText_005f0(contacts_jsp.java:136)
at 
org.apache.jsp.jsp.contacts_jsp._jspx_meth_f_005fview_005f0(contacts_jsp.java:107)
at org.apache.jsp.jsp.contacts_jsp._jspService(contacts_jsp.java:68)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)

I think that it's a classloading problem but I need some help to find out where 
it comes from.

I can provide a complete workspace to test if necessary...

Thanks very much for your help!!
Thierry




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: centralized log server

2009-11-17 Thread Matthew Chambers

This application might help.  Doesn't matter what versions you have.  Takes a 
bit to get setup though.

http://www.splunk.com/

From: Caldarale, Charles R [chuck.caldar...@unisys.com]
Sent: Tuesday, November 17, 2009 7:23 AM
To: Tomcat Users List
Subject: RE: centralized log server

 From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com]
 Subject: centralized log server

 is there a centralized application to access all the tomcat server
 catalina.logs

Your question is badly phrased, as Pid keeps trying to point out.

If all you want is to be able to look at the log files, any editor will do.

LambdaProbe can display the Tomcat log files in a browser - if it can be 
installed on your version of Tomcat, which you didn't bother to tell us.  You 
also didn't tell us what platform you're running on, or whether you're using a 
standard Tomcat download or a 3rd-party repackaged version.  (The location of 
the log files varies with each.)

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

I have tried to set application context variables, but it didn't worked, since 
I m expecting to get these variables as null values after node shutdown, but in 
fact they are coming as not null.

 



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 15:38:22 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 On 17/11/2009 14:40, Ronald Klop wrote:
  Hi Imad,
 
  Ronald. (The Ronald of the link mentioned by Pid.)
 
 Did the code supplied therein, work for you Ronald?
 
 
 @Imad
 
 The Servlet Spec (and therefore Tomcat) doesn't differentiate between 
 causes of session expiry.
 
 The code requires you to set a value in the application scope, then the 
 HttpSessionListener sessionDestroyed method checks for that value.
 
 If the value is present, you initiated shutdown. If it is not, then 
 it's probably a session expiry and you run your logout code.
 
 Did you actually set such an attribute?
 
 
 p
 
 
  Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
  hachem_i...@hotmail.com:
 
 
 
 
  Dear Pid,
 
 
 
  I am running a Logout Process at each sessionDestroy.
 
 
 
  After applying the Cluster configuration, I don't want to Logout my
  Users (or run this Logout Process) after any Tomcat Cluster node
  shutdown, since the Session has been replicated to the other Node
  Cluster.
 
 
 
 
 
  Best Regards,
  Imad Hachem
  System Engineer
 
 
 
   From: p...@pidster.com
   Date: Tue, 17 Nov 2009 13:09:47 +
   Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
   To: users@tomcat.apache.org
On 17 Nov 2009, at 12:11, Imad Hachem hachem_i...@hotmail.com
  wrote:

Dear Pid,
   
   
   
I have tried that code and didn't helped, note that my context 
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown 
session.invalidate().
I'm sorry but I don't understand what you're saying here.
Tomcat  the servlet api can't tell you the difference between an app
   shutdown and a session expiry without you writing code.
What did you try?
What was or wasn't null exactly?
p
  Best Regards,
Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 11:31, Imad Hachem wrote:
   
Dear Pid,
   
Thanks for your reply.
   
But can you specify exactly which Servlets API method to use?
   
The link I sent had some code in it, did you read it?
   
Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.
   
But you might be facing some security ones.
   
I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.
   
The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet
  years).
   
It's not good practice to avoid upgrading for that long.
   
   
p
   
   
   
   
   
   
   
   
Best Regards,
Imad Hachem
   
System Engineer
   
   
   
   
Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed
   
On 17/11/2009 04:14, Imad Hachem wrote:
   
Dear all,
   
I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.
   
Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?
   
I think it's perfectly reasonably to call sessionDestroyed()
  before
contextDestroyed().
   
How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?
   
You can't know this directly from the Servlet API methods.
   
Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.
   
I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.
   
This comes up not infrequently on the list, the archives have more
information:

Re: synchronizing in tomcat

2009-11-17 Thread Leon Rosenberg

How would you do it in a non-servlet environment?

Exactly the same works here too.

regards
Leon

On Tue, Nov 17, 2009 at 4:43 PM, David Balažic xerc...@gmail.com wrote:
 Hi!

 Does tomcat offer any mechanism for locking servlet executions?

 So if one servlet does:
  - get 10 EUR from account 1 (read account 1 balance; substract 10;
 store new balance)
  - add 10 EUR to account 2 (...)

 How can I make sure no other servlet does (read account 1 balance;
 sustract 10; store new balance) at the same
 time and cause lost account money?

 The account data is in a database, accessed over hibernate (or
 directly, if needed).

 Regards,
 David

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: synchronizing in tomcat

2009-11-17 Thread Neil Aggarwal


 Does tomcat offer any mechanism for locking servlet executions?

I think you are going to have to take care of this in your
application code.

At first thought, I would create a class
with synchronized static methods to do each of your
processing tasks.  That way, you are guaranteed
only one method is executing at a time.

You have to be careful to avoid deadlock
so you better call the methods in a pre-set
order.

Neil

--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
Host your tomcat app on a CentOS VPS for only $25/month!
Unmetered bandwidth, 7 day no risk trial, Google Checkout


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Why Tomcat on startup should navigate to some jsp?

gamby wrote:
 Unfortunately the stacktrace is not useful for you because exceptions are
 thrown because of some bean missing, but it is absolutely normal in my
 opinion, no one filter has yet started during this phase of startup.
 
 Tomcat tries to load the 404, but I have redefined it, including in it a
 header and footer jsp using Struts tiles, and in header there is a bean not
 yet loaded on startup, and this is the cause of exception.
 
 What I would you like to know is why Tomcat should navigate toward some page
 on startup, launching the 404 even if there wasn't yet a real user
 navigation.
 
 I'm using also dwr, I don't know if it could be one of the causes.

That is what the stack trace will hopefully show.

Mark




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Loading customized StandardContext subclass

2009-11-17 Thread Konstantin Kolinko

2009/11/17 Joel SCHAAL schaal.j...@e-serve.ch:

 Since we want to have more than one of our application in the same server, I
 put our jars in ${catalina.home}/lib/ instead of WEB-INF/lib and I added the
 reference of every sub-folder in ${catalina.home}/lib/ to the server.loader

Tomcat version = ?

Try with common.loader first.

Why do you have sub-folders in /lib/ ?

 put our jars in ${catalina.home}/lib/ instead of WEB-INF/lib

Be sure that you removed duplicate jars from WEB-INF/lib.
(class-loader-howto.html explains why)


 parameter in ${catalina.home}/conf/catalina.properties (using *.jar)
 (tried shared.loader and common.loader as well, with no use)

 The problem, I get this exception at server startup :
 GRAVE: Erreur lors du déploiement du répertoire upsm de l'application web
 java.lang.ClassNotFoundException: eserve.framework.EserveContext
  at
 org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2808)
  at

 I looked in the source code, and found out that the class loader of the
 Digest at that time is the one used at startup time.
 I thought it would be the one from Bootstrap.catalinaLoader.
 What have I done wrong ? Should I specify another classloader in a file ? I


I guess that either you misspelled something, or your class depends on
some other libraries that are not available.

 did not find this information in any of the following locations :

Make sure that you have read and understood the following document:
 - http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


On 17/11/2009 15:57, Imad Hachem wrote:


Dear Pid,

I have tried to set application context variables, but it didn't worked, since 
I m expecting to get these variables as null values after node shutdown, but in 
fact they are coming as not null.


If you set them as not null and they are not null why are you surprised?

Why do you expect them to be null?


p



Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 15:38:22 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed

On 17/11/2009 14:40, Ronald Klop wrote:

Hi Imad,

Ronald. (The Ronald of the link mentioned by Pid.)


Did the code supplied therein, work for you Ronald?


@Imad

The Servlet Spec (and therefore Tomcat) doesn't differentiate between
causes of session expiry.

The code requires you to set a value in the application scope, then the
HttpSessionListener sessionDestroyed method checks for that value.

If the value is present, you initiated shutdown. If it is not, then
it's probably a session expiry and you run your logout code.

Did you actually set such an attribute?


p



Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
hachem_i...@hotmail.com:





Dear Pid,



I am running a Logout Process at each sessionDestroy.



After applying the Cluster configuration, I don't want to Logout my
Users (or run this Logout Process) after any Tomcat Cluster node
shutdown, since the Session has been replicated to the other Node
Cluster.





Best Regards,
Imad Hachem
System Engineer




From: p...@pidster.com
Date: Tue, 17 Nov 2009 13:09:47 +
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node

shutdown, sessionDestroyed been called before contextDestroyed

To: users@tomcat.apache.org

On 17 Nov 2009, at 12:11, Imad Hachemhachem_i...@hotmail.com

wrote:



Dear Pid,



I have tried that code and didn't helped, note that my context
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown
session.invalidate().
I'm sorry but I don't understand what you're saying here.
Tomcat  the servlet api can't tell you the difference between an app

shutdown and a session expiry without you writing code.

What did you try?
What was or wasn't null exactly?
p

Best Regards,

Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 11:31, Imad Hachem wrote:


Dear Pid,

Thanks for your reply.

But can you specify exactly which Servlets API method to use?


The link I sent had some code in it, did you read it?


Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.


But you might be facing some security ones.


I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.


The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet

years).


It's not good practice to avoid upgrading for that long.


p









Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 04:14, Imad Hachem wrote:


Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.


Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed()

before

contextDestroyed().


How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?


You can't know this directly from the Servlet API methods.


Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.


This comes up not infrequently on the list, the archives have more
information:



http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html




Is there any event listener that I can use before the
sessionDestroyed to differentiate if one cluster node has been
shutdown or my session has been expired?

Or is how to configure the contextDestroy to be called before
the sessions destroy?


No, contextDestroyed() means that the web application

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

I am expecting them to come as null to know that the Tomcat Node (or context) 
has been shutdown.

 



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 16:08:37 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 CC: ihac...@lb.path-solutions.com
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 On 17/11/2009 15:57, Imad Hachem wrote:
 
  Dear Pid,
 
  I have tried to set application context variables, but it didn't worked, 
  since I m expecting to get these variables as null values after node 
  shutdown, but in fact they are coming as not null.
 
 If you set them as not null and they are not null why are you surprised?
 
 Why do you expect them to be null?
 
 
 p
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 15:38:22 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
  sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 14:40, Ronald Klop wrote:
  Hi Imad,
 
  Ronald. (The Ronald of the link mentioned by Pid.)
 
  Did the code supplied therein, work for you Ronald?
 
 
  @Imad
 
  The Servlet Spec (and therefore Tomcat) doesn't differentiate between
  causes of session expiry.
 
  The code requires you to set a value in the application scope, then the
  HttpSessionListener sessionDestroyed method checks for that value.
 
  If the value is present, you initiated shutdown. If it is not, then
  it's probably a session expiry and you run your logout code.
 
  Did you actually set such an attribute?
 
 
  p
 
 
  Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
  hachem_i...@hotmail.com:
 
 
 
 
  Dear Pid,
 
 
 
  I am running a Logout Process at each sessionDestroy.
 
 
 
  After applying the Cluster configuration, I don't want to Logout my
  Users (or run this Logout Process) after any Tomcat Cluster node
  shutdown, since the Session has been replicated to the other Node
  Cluster.
 
 
 
 
 
  Best Regards,
  Imad Hachem
  System Engineer
 
 
 
  From: p...@pidster.com
  Date: Tue, 17 Nov 2009 13:09:47 +
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
  To: users@tomcat.apache.org
  On 17 Nov 2009, at 12:11, Imad Hachemhachem_i...@hotmail.com
  wrote:
 
  Dear Pid,
 
 
 
  I have tried that code and didn't helped, note that my context
  session variables are not coming as null in order to rely on to be
  able to differenciate between Tomcat Node shutdown
  session.invalidate().
  I'm sorry but I don't understand what you're saying here.
  Tomcat the servlet api can't tell you the difference between an app
  shutdown and a session expiry without you writing code.
  What did you try?
  What was or wasn't null exactly?
  p
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 11:41:20 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 11:31, Imad Hachem wrote:
 
  Dear Pid,
 
  Thanks for your reply.
 
  But can you specify exactly which Servlets API method to use?
 
  The link I sent had some code in it, did you read it?
 
  Note that Tomat-5.5.12 is deployed on Production environment and
  we are not facing major issues.
 
  But you might be facing some security ones.
 
  I will appreciate if you can adivse to which Tomcat Stable version
  we should Migrate taking in consideration that Tomcat Cluster is
  used in our environment as well.
 
  The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
  released September 2005, over 4 years ago (that's 28 internet
  years).
 
  It's not good practice to avoid upgrading for that long.
 
 
  p
 
 
 
 
 
 
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 10:15:58 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 04:14, Imad Hachem wrote:
 
  Dear all,
 
  I am using Tomcat-5.5.12 as Clustering nodes, and after one node
  shutdown sessionDestroyed is called before contextDestroyed.
 
  Are you still using 5.5.12? Hasn't anyone advised you to upgrade
  to a
  newer version yet?
 
  I think it's perfectly reasonably to call sessionDestroyed()
  before
  contextDestroyed().
 
  How can I know if sessionDestroyed is called from
  session.invalidate()
  from the real expiration of the session or shutdown of one
  cluster node?
 
  You can't know this directly from the Servlet API methods.
 
  Note that on sessionDestroyed event, I am using a Logout
  behavior to
  logout my users from the DATABASE.
 
  I have

RE: synchronizing in tomcat

 From: Neil Aggarwal [mailto:n...@jammconsulting.com]
 Subject: RE: synchronizing in tomcat

 At first thought, I would create a class
 with synchronized static methods to do each of your
 processing tasks.  That way, you are guaranteed
 only one method is executing at a time.

That's probably not going to work, since the posted scenario sounds more like a 
shopping cart situation, requiring lockout across multiple requests.  
Regardless, this has nothing to do with 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: A question about mod_jk 1.2.28 configuration

2009-11-17 Thread Rainer Jung

Hello Thomas,

On 17.11.2009 11:05, thomas2004 wrote:
 
 I think the reproduction with html is not working because of some other
 reasons likely not related with mod_jk. In the original message he has a
 jk error message referring to errno 11=EAGAIN. There is a change between
 1.2.26 and 1.2.28 related to how EAGAIN gets handled while waiting for
 data. So I can imagine he really hit a bug there, although I'm not sure,
 because we have to check, whether that observation also happens without
 socket_timeout and reply_timeout.
 
 
 Hi Rainer and Christopher,
 
 I think one can reconstruct my problem in a simple way:
 
 Write a small web-application which contains two steps/pages. The first one
 has a button submit. One click the button and it will send a request to
 backend. The backend does nothing but just sleep for a while such as 5 min.,
 10 min. etc. And then send back the time stamp back to browser (the second
 page).
 
 In this way one can check if this problem has to do with mod_jk (or apache
 httpd) version or not.

I know, that you have seen a problem, the errno=11 thing. I need to
know, whether *this* problem (errno=11, which is your original PDF
generation problem) also happens, when no socket-timeout and no
reply_timeout is set.

Your reproduction attempt using a simple html snippet did *not* show a
mod_jk problem and therefore is of no interest for me at the moment.
Let's concentrate on the test case with errno=11.

Regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: synchronizing in tomcat

2009-11-17 Thread Joseph Morgan

I completely agree with Chuck, and completely disagree with Neil.  

Never rely upon static state in servlet classes unless you have complete
control over class loading, which you shouldn't, otherwise you'd write
your own servlet container.

As Chuck says, it is not a Tomcat issue, but one for the DB.


-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] 
Sent: Tuesday, November 17, 2009 10:13 AM
To: Tomcat Users List
Subject: RE: synchronizing in tomcat

 From: Neil Aggarwal [mailto:n...@jammconsulting.com]
 Subject: RE: synchronizing in tomcat
 
 At first thought, I would create a class
 with synchronized static methods to do each of your
 processing tasks.  That way, you are guaranteed
 only one method is executing at a time.

That's probably not going to work, since the posted scenario sounds more
like a shopping cart situation, requiring lockout across multiple
requests.  Regardless, this has nothing to do with 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


On 17/11/2009 16:11, Imad Hachem wrote:


Dear Pid,

I am expecting them to come as null to know that the Tomcat Node (or context) 
has been shutdown.


That makes no sense.  These are the logical steps.

1. Manually set an attribute (e.g. MANUAL_STOP=1) in application scope
2. Manually shutdown Tomcat instance.
3. Tomcat expires all sessions
4. Tomcat fires HttpSessionListener.sessionDestroyed for each session
5. custom code checks for, and finds, attribute (e.g. MANUAL_STOP=1)
6. custom code does logout per session
8. Tomcat fires ServletContextListener.contextDestroyed for each app


Perhaps you can explain, clearly, what you expect to happen and where it 
happens?



p



Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 16:08:37 +
From: p...@pidster.com
To: users@tomcat.apache.org
CC: ihac...@lb.path-solutions.com
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed

On 17/11/2009 15:57, Imad Hachem wrote:


Dear Pid,

I have tried to set application context variables, but it didn't worked, since 
I m expecting to get these variables as null values after node shutdown, but in 
fact they are coming as not null.


If you set them as not null and they are not null why are you surprised?

Why do you expect them to be null?


p



Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 15:38:22 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed

On 17/11/2009 14:40, Ronald Klop wrote:

Hi Imad,

Ronald. (The Ronald of the link mentioned by Pid.)


Did the code supplied therein, work for you Ronald?


@Imad

The Servlet Spec (and therefore Tomcat) doesn't differentiate between
causes of session expiry.

The code requires you to set a value in the application scope, then the
HttpSessionListener sessionDestroyed method checks for that value.

If the value is present, you initiated shutdown. If it is not, then
it's probably a session expiry and you run your logout code.

Did you actually set such an attribute?


p



Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
hachem_i...@hotmail.com:





Dear Pid,



I am running a Logout Process at each sessionDestroy.



After applying the Cluster configuration, I don't want to Logout my
Users (or run this Logout Process) after any Tomcat Cluster node
shutdown, since the Session has been replicated to the other Node
Cluster.





Best Regards,
Imad Hachem
System Engineer




From: p...@pidster.com
Date: Tue, 17 Nov 2009 13:09:47 +
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node

shutdown, sessionDestroyed been called before contextDestroyed

To: users@tomcat.apache.org

On 17 Nov 2009, at 12:11, Imad Hachemhachem_i...@hotmail.com

wrote:



Dear Pid,



I have tried that code and didn't helped, note that my context
session variables are not coming as null in order to rely on to be
able to differenciate between Tomcat Node shutdown
session.invalidate().
I'm sorry but I don't understand what you're saying here.
Tomcat  the servlet api can't tell you the difference between an app

shutdown and a session expiry without you writing code.

What did you try?
What was or wasn't null exactly?
p

Best Regards,

Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 11:41:20 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 11:31, Imad Hachem wrote:


Dear Pid,

Thanks for your reply.

But can you specify exactly which Servlets API method to use?


The link I sent had some code in it, did you read it?


Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.


But you might be facing some security ones.


I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.


The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet

years).


It's not good practice to avoid upgrading for that long.


p









Best Regards,
Imad Hachem

System Engineer





Date: Tue, 17 Nov 2009 10:15:58 +
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
shutdown, sessionDestroyed been called before contextDestroyed

On 17/11/2009 04:14, Imad Hachem wrote:


Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.


Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed()

before

contextDestroyed().


How can I know if

Re: synchronizing in tomcat


On 17/11/2009 15:43, David Balažic wrote:

Hi!

Does tomcat offer any mechanism for locking servlet executions?

So if one servlet does:
  - get 10 EUR from account 1 (read account 1 balance; substract 10;
store new balance)
  - add 10 EUR to account 2 (...)

How can I make sure no other servlet does (read account 1 balance;
sustract 10; store new balance) at the same
time and cause lost account money?

The account data is in a database, accessed over hibernate (or
directly, if needed).


The term you are looking for is transaction.  GIYF.


p




Regards,
David

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: centralized log server

2009-11-17 Thread Kaushal Shriyan

On Tue, Nov 17, 2009 at 8:53 PM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
 From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com]
 Subject: centralized log server

 is there a centralized application to access all the tomcat server
 catalina.logs

 Your question is badly phrased, as Pid keeps trying to point out.

 If all you want is to be able to look at the log files, any editor will do.

 LambdaProbe can display the Tomcat log files in a browser - if it can be 
 installed on your version of Tomcat, which you didn't bother to tell us.  You 
 also didn't tell us what platform you're running on, or whether you're using 
 a standard Tomcat download or a 3rd-party repackaged version.  (The location 
 of the log files varies with each.)

Hi Chuck

I got to see tcat server from
http://www.mulesoft.com/tcat-server-enterprise-tomcat-application-server
which says about centralized logging system and also additional
features.

Do you recommend it. I am using the vanila apache tomcat 5.5.27 from
http://tomcat.apache.org/download-55.cgi

Please suggest/Guide

Thanks,

Kaushal

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: centralized log server

 From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com]
 Subject: Re: centralized log server

 I got to see tcat server from
 http://www.mulesoft.com/tcat-server-enterprise-tomcat-application-server
 which says about centralized logging system and also additional
 features.

Sorry, I can't comment on it - I've never tried it, and it would be improper of 
me to discuss commercial products anyway.

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: https and port numbers

2009-11-17 Thread David Smith

Christopher Schultz wrote:
 David,

 On 11/17/2009 7:39 AM, David Smith wrote:
  Your tomcat has to listen on 443 to remove the port number from the
  URL.  This is not a tomcat issue, but rather the browser's expectation.

 That's not entirely true. If Robert configures his firewall to redirect
 port 443 - 8443 similar to how he does 80 - 8080, then he can remove
 the port number from the URL by changing the redirectPort attribute in
 his Connector to 443.

 -chris
You're talking about proxying the connection with a reverse proxy.  That
works, but I believe the connector will have to have proxyPort set so
generated URLs within the app don't include a port number.

--David

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: centralized log server

On 17/11/2009 16:28, Kaushal Shriyan wrote:

On Tue, Nov 17, 2009 at 8:53 PM, Caldarale, Charles R
chuck.caldar...@unisys.com  wrote:

From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com]
Subject: centralized log server

is there a centralized application to access all the tomcat server
catalina.logs

Your question is badly phrased, as Pid keeps trying to point out.

If all you want is to be able to look at the log files, any editor will do.

LambdaProbe can display the Tomcat log files in a browser - if it can be 
installed on your version of Tomcat, which you didn't bother to tell us.  You 
also didn't tell us what platform you're running on, or whether you're using a 
standard Tomcat download or a 3rd-party repackaged version.  (The location of 
the log files varies with each.)

Hi Chuck

I got to see tcat server from
http://www.mulesoft.com/tcat-server-enterprise-tomcat-application-server
which says about centralized logging system and also additional
features.

So you're asking if Tomcat has an additional application, that a 
commercial vendor includes with their commercial application that 
contains a bundled Tomcat?

Fairly obviously not.

p

Do you recommend it. I am using the vanila apache tomcat 5.5.27 from
http://tomcat.apache.org/download-55.cgi

Please suggest/Guide

Thanks,

Kaushal

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Error starting the web server

2009-11-17 Thread John McCleskey

Thanks to everyone who helped with the deployment of this project. I was
able to install a stand-alone Apache web server on my iSeries with java 1.5.
It was not as straight-forward as I would have liked, due mainly to the poor
iSeries how-to documentation and my ignorance, but it is running. - John

On Mon, Nov 16, 2009 at 9:17 AM, Neil Aggarwal n...@jammconsulting.comwrote:

 John:

  It appears that we have several JDK's loaded on our file
  system (up to jdk
  1.5). what apache configuration files need to be modified to
  point to the
  correct jdk? i've modified the workers.properties. any other
  locations I
  should modify?

 I choose a JDK by setting a JAVA_HOME
 environment variable in /etc/init.d/tomcat.

 Here is a sample:
 JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk.x86_64

Neil

 --
 Neil Aggarwal, (281)846-8957, 
 http://UnmeteredVPS.nethttp://unmeteredvps.net/
 Host your tomcat app on a CentOS VPS for only $25/month!
 Unmetered bandwidth, 7 day no risk trial, Google Checkout



 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 
Regards,

John
http://www.linkedin.com/in/johnmccleskey

Re: Servlet MessageBrokerServlet is not available on Ubuntu AMD64

2009-11-17 Thread R. S. Patil

Thanks


 Something wrong in your blazeds config I'd guess.  I'd ask those folks for
 help, if I were you.

I did the same but there was no response. So I thought that there might be
some problem regarding Tomcat Win and Tomcat Lin (Ubuntu Specific).
I too can logically say that when a war file works OK on XP should work on linux
But it fails on Linux so Doubt points to tomcat 6 On Ubuntu Linux.

BTW can u decode log I have mentioned. Will u please tell me why The
servlet is not
available when the class file messagebroker.classs is very well available in
one of the jar files in context/lib dir as part of .jar file, so
logically its available to
tomcat but practically it's not available as log depicts it.

Can somebody spare sometime to go through log and guide me about how should I
precced.

Thanks and best regards.

Raja
. :wq

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Testing Tomcat with Virtual Hosts

 From: Marty Pitt NZ [mailto:martyp...@me.com]
 Subject: Testing Tomcat with Virtual Hosts

 I've edited my hosts file to look as follows:
 127.0.0.1   localhost
 ::1 localhost
 127.0.0.1   test1.localhost
 localhost   test2.localhost

The last line is a little odd; why aren't you using 127.0.0.1 for 
test2.localhost?

 However, I'm getting a 404 when hitting test1.localhost:8080/myWebApp,
 although localhost:8080/myWebApp works fine.

Can't see anything wrong in what you've done in the Tomcat config.  Try 
enabling the AccessLogValve and see what it says.

 - 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: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Error starting the web server

 From: John McCleskey [mailto:jmccleske...@gmail.com]
 Subject: Re: Error starting the web server

 I was able to install a stand-alone Apache web server on 
 my iSeries with java 1.5.

The term Apache web server is rather ambiguous; did you mean httpd or 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.

Re: Error starting the web server

2009-11-17 Thread John McCleskey

Sorry, Tomcat.

On Tue, Nov 17, 2009 at 11:51 AM, Caldarale, Charles R 
chuck.caldar...@unisys.com wrote:

  From: John McCleskey [mailto:jmccleske...@gmail.com]
  Subject: Re: Error starting the web server

  I was able to install a stand-alone Apache web server on
  my iSeries with java 1.5.

 The term Apache web server is rather ambiguous; did you mean httpd or
 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.

-- 
Regards,

John
http://www.linkedin.com/in/johnmccleskey

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

2009-11-17 Thread Ronald Klop

@P
I didn't want to pollute my deployment process with this manual stuff. So I
'solved' it different for our setup. I do not log users out on sessionDestroy.
I only record that they are logged out. Which is overwritten by later logout
events. So in the end the data is pretty ok. Not very nice, but nice enough for
me.

Ronald.

Op dinsdag, 17 november 2009 16:38 schreef Pid p...@pidster.com:

On 17/11/2009 14:40, Ronald Klop wrote:

Hi Imad,

Ronald. (The Ronald of the link mentioned by Pid.)

Did the code supplied therein, work for you Ronald?

@Imad

The Servlet Spec (and therefore Tomcat) doesn't differentiate between causes of
session expiry.

The code requires you to set a value in the application scope, then the
HttpSessionListener sessionDestroyed method checks for that value.

If the value is present, you initiated shutdown. If it is not, then it's
probably a session expiry and you run your logout code.

Did you actually set such an attribute?

Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
hachem_i...@hotmail.com:

Dear Pid,

I am running a Logout Process at each sessionDestroy.

After applying the Cluster configuration, I don't want to Logout my
Users (or run this Logout Process) after any Tomcat Cluster node
shutdown, since the Session has been replicated to the other Node
Cluster.

Best Regards,
Imad Hachem
System Engineer

Dear Pid,

System Engineer

On 17/11/2009 11:31, Imad Hachem wrote:

Dear Pid,

Thanks for your reply.

But can you specify exactly which Servlets API method to use?

The link I sent had some code in it, did you read it?

Note that Tomat-5.5.12 is deployed on Production environment and
we are not facing major issues.

But you might be facing some security ones.

I will appreciate if you can adivse to which Tomcat Stable version
we should Migrate taking in consideration that Tomcat Cluster is
used in our environment as well.

The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was
released September 2005, over 4 years ago (that's 28 internet
years).

It's not good practice to avoid upgrading for that long.

Best Regards,
Imad Hachem

System Engineer

On 17/11/2009 04:14, Imad Hachem wrote:

Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.

Are you still using 5.5.12? Hasn't anyone advised you to upgrade
to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed()
before
contextDestroyed().

How can I know if sessionDestroyed is called from
session.invalidate()
from the real expiration of the session or shutdown of one
cluster node?

You can't know this directly from the Servlet API methods.

Note that on sessionDestroyed event, I am using a Logout
behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope)
to check
on it during the sessionDestroyed event, but it seems the
context is
destroyed after the session destroy event.

This comes up not infrequently on the list, the archives have more
information:

http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html

Is there any event listener that I can use before the
sessionDestroyed to differentiate if one cluster node has been
shutdown or my session has been expired?

Or is how to configure the contextDestroy to be called before

http and/or ajp connectors

2009-11-17 Thread Jeffrey Trimble

Recently, I used the cheap and easy http redirects from my apache
server to my tomcat
server. I ran into two issues, that I hope someone is able to guide
me to a better solution

First, I wanted to have the user not have to know about port 8080, and
to have the root
of the apache redirect to the tomcat servlet running. So for my
apache, I had the

redirect of (in the httpd-vhosts.conf file)

redirect / http//digital.maag.ysu.edu/jspui

Then I had a ProxyPass in the httpd.conf file:

ProxyPass /jspui http://digital.maag.ysu.edu/jspui
ProxyPassReverse /jspui http://digital.maag.ysu.edu/jspui
ProxVia on

In my Tomcat server.xml file I had:

Connector port=8080 protocol=HTTP/1.1
proxyName=digital.maag.ysu.edu proxyPort=80
connectionTimeout=2
redirectPort=8443
URIEncoding=UTF-8 /
!-- A Connector using the shared thread pool--

I ran into two problems:

1. I would see in my apache logs a request that would have the
following

.GET /jspuijspuijspuijspuijspuijspuijspuijspuijspui

GET /
jspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspui

Infinitum

What is causing this and how do I solve it?

2. After setting up the ProxyPass and such, I couldn't figure out how
to use other servlet directories beside the jspui directory. So, if
I had
say two directies in the webapps, was/is it possible to redirect to
them?

Thanks in advance. Any questions, please ask.

Jeffrey Trimble
System LIbrarian
William F. Maag Library
Youngstown State University
330.941.2483 (Office)
jtrim...@cc.ysu.edu
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
I must not fear. Fear is the mind-killer.
I will permit it to pass over me and through me...
--Litany against fear

RE: http and/or ajp connectors

2009-11-17 Thread Neil Aggarwal

Jeffrey:

 Recently, I used the cheap and easy http redirects from my apache  
 server to my tomcat
 server.  I ran into two issues, that I hope someone is able to guide  
 me to a better solution

I think you need to use mod_jk.  That will allow
you to use connections to port 80 and 443 for
both apache and tomcat and you wont have to use
redirects.

Neil

--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
Host your tomcat app on a CentOS VPS for only $25/month!
Unmetered bandwidth, 7 day no risk trial, Google Checkout


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

proxy host System.setProperty question

2009-11-17 Thread J- MAN


Hi,

i'm sure this has been asked a hundred times, but i can't find the answer on 
google.  I'm trying to make my servlet connect to an external webservice, but 
we have an http proxy at work.  

I was initially trying to put this code in my servlet method:

System.setProperty(http.proxyHost, proxy.myHost.com);
System.setProperty(http.proxyPort, 80);

Which works fine when run as a normal Java application, but does not work when 
run inside tomcat servlet.  I have to manually add 

http.proxyPort=80
http.proxyHost= proxy.myHost.com

To my catalina.properties file for it to work.  why does it work from 
catalina.properties but not from System.setProperty??

Thanks,

-J
  
_
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/

Re: http and/or ajp connectors

2009-11-17 Thread Hassan Schroeder

On Tue, Nov 17, 2009 at 11:05 AM, Jeffrey Trimble jtrim...@cc.ysu.edu wrote:
 Recently, I used the cheap and easy http redirects from my apache server to
 my tomcat
 server.  I ran into two issues, that I hope someone is able to guide me to a
 better solution

 First, I wanted to have the user not have to know about port 8080, and to
 have the root
 of the apache redirect to the tomcat servlet running. So for my apache, I
 had the
 redirect of (in the httpd-vhosts.conf file)

 redirect / http//digital.maag.ysu.edu/jspui

?? What the heck is that? Get rid of it. You're forwarding using
the proxy stuff, not redirecting.

 1.  I would see in my apache logs a request that would have the following
...
/jspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspuijspui
 Infinitum

 What is causing this and how do I solve it?

See above.

 2.  After setting up the ProxyPass and such, I couldn't figure out how to
 use other servlet directories beside the jspui directory.  So, if I had
 say two directies in the webapps, was/is it possible to redirect to them?

Is /jspui the name/path of the webapp or a subdirectory of the app?

-- 
Hassan Schroeder  hassan.schroe...@gmail.com
twitter: @hassan

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Multiple war files for the same application context.

2009-11-17 Thread Ziggy

Lol that was just an example. There are thousands of jsps and servlets.
With regards to the path, i am using struts and tiles so the directories are
not really part of the path to the resource via the browser.  That path will
be configured in the tiles and struts configuration.

I am trying this foo#bar.war approach and see how it will work.

Thanks

On Tue, Nov 17, 2009 at 3:47 PM, Caldarale, Charles R 
chuck.caldar...@unisys.com wrote:

  From: Ziggy [mailto:zigg...@gmail.com]
  Subject: Re: Multiple war files for the same application context.
 
  That is interesting. Is the # supposed to be part of the filename?

 Read the doc:

 http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic%20Application%20Deployment

  - 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: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: http and/or ajp connectors


On 17/11/2009 19:11, Neil Aggarwal wrote:

Jeffrey:


Recently, I used the cheap and easy http redirects from my apache
server to my tomcat
server.  I ran into two issues, that I hope someone is able to guide
me to a better solution


I think you need to use mod_jk.  That will allow
you to use connections to port 80 and 443 for
both apache and tomcat and you wont have to use
redirects.


Umm, no.

mod_proxy is suitable.  You just need to sort out your config.
One simple approach would be to rename your webapp, from jspui to ROOT.

The redirect you've employed is the source of the problem, you're using 
the wrong command.  Read the docs for more info:


 http://httpd.apache.org/docs/2.2/mod/mod_proxy.html

You can use mod_redirect in conjunction with mod_proxy:

 RewriteRule ^/(.+)\.jsp(.+)?  ajp://host/$1.jsp$2  [P,L]

or

 ProxyPass/ajp://host/


p




--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
Host your tomcat app on a CentOS VPS for only $25/month!
Unmetered bandwidth, 7 day no risk trial, Google Checkout


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat DBCP Connection Pooling to MySQL limited number of connection issue in Spring2.5 + Hibernate3 + commons-DBCP1.2

2009-11-17 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yagnesh,

On 11/17/2009 10:51 AM, Yagnesh Chawda wrote:
   Thanks for reply. I had tried using com.mysql.jdbc.Driver as well
 earlier. But no luck :(

What does happen when you use com.mysql.jdbc.Driver?

What are the current values for max_connections and max_user_connections
in MySQL? I know you said you set max_connections=200 but I just wanted
to make sure that MySQL actually has that setting while it's running.

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

iEYEARECAAYFAksDG/IACgkQ9CaO5/Lv0PBc0wCgq7YxJdaIHiCbiKUTwngX99QI
gqoAoL9T9Yw4WR4NXF8gDbC/F6KyDZ1F
=YvGV
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: http and/or ajp connectors

2009-11-17 Thread André Warnier


Jeffrey Trimble wrote:
Recently, I used the cheap and easy http redirects from my apache server 
to my tomcat
server.  I ran into two issues, that I hope someone is able to guide me 
to a better solution


First, I wanted to have the user not have to know about port 8080, and 
to have the root
of the apache redirect to the tomcat servlet running. So for my apache, 
I had the

redirect of (in the httpd-vhosts.conf file)

...

The very first question is : do you use an Apache httpd front-end *only* 
in order to hide port 8080 ?
Because if that is the case, why don't you just have Tomcat listening to 
port 80 directly ? It can also serve static pages, not just JSPs or 
servlets.
The fact that you are using a proxy setup to proxy / to Tomcat, makes 
me wonder.


Second question : are Apache httpd and Tomcat running on the same host ?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

silent / unattended install - tomcat 5.5

2009-11-17 Thread Beatty.Thomas

Hi

Can someone PLEASE tell me how to install tomcat 5.5 silently? I need to 
install the service, set the destination folder, set the Administrator user 
name and password, and set the path to the JVM. Does anyone know the parameters 
that I need to set at the command line in order to accomplish this? So far I 
have the following:

apache-tomcat-5.5.17.exe /S /D=C:\develop\tomcat5.5

Thanks - TJ

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed


Dear Pid,

 

find below my explanation:

 

 1. Manually set an attribute (e.g. MANUAL_STOP=1) in application scope
 2. Manually shutdown Tomcat instance.
 3. Tomcat expires all sessions
 4. Tomcat fires HttpSessionListener.sessionDestroyed for each session
 5. custom code checks for, and finds, attribute (e.g. MANUAL_STOP=1)
  if(MANUAL_STOP == null){  // Tomcat Cluster Node Shutdown

//don't do anything

  }

  else{  //  case of session.invalidate or session timeout

  6. custom code does logout per session
  }

8. Tomcat fires ServletContextListener.contextDestroyed for each app


 

But in fact, the variable MANUAL_STOP saved to the application scope is always 
coming as 1, even after tomcat cluster node shutdown which expected to come as 
null.

 

I need to know if my sessionDestroyed has been called from a session.invalidate 
Event OR session timeout OR Tomcat Cluster node shutdown.



Best Regards,
Imad Hachem 

System Engineer 



 
 Date: Tue, 17 Nov 2009 16:23:16 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 CC: ihac...@lb.path-solutions.com
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
 sessionDestroyed been called before contextDestroyed
 
 On 17/11/2009 16:11, Imad Hachem wrote:
 
  Dear Pid,
 
  I am expecting them to come as null to know that the Tomcat Node (or 
  context) has been shutdown.
 
 That makes no sense. These are the logical steps.
 
 1. Manually set an attribute (e.g. MANUAL_STOP=1) in application scope
 2. Manually shutdown Tomcat instance.
 3. Tomcat expires all sessions
 4. Tomcat fires HttpSessionListener.sessionDestroyed for each session
 5. custom code checks for, and finds, attribute (e.g. MANUAL_STOP=1)
 6. custom code does logout per session
 8. Tomcat fires ServletContextListener.contextDestroyed for each app
 
 
 Perhaps you can explain, clearly, what you expect to happen and where it 
 happens?
 
 
 p
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 16:08:37 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  CC: ihac...@lb.path-solutions.com
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
  sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 15:57, Imad Hachem wrote:
 
  Dear Pid,
 
  I have tried to set application context variables, but it didn't worked, 
  since I m expecting to get these variables as null values after node 
  shutdown, but in fact they are coming as not null.
 
  If you set them as not null and they are not null why are you 
  surprised?
 
  Why do you expect them to be null?
 
 
  p
 
 
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 15:38:22 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node 
  shutdown, sessionDestroyed been called before contextDestroyed
 
  On 17/11/2009 14:40, Ronald Klop wrote:
  Hi Imad,
 
  Ronald. (The Ronald of the link mentioned by Pid.)
 
  Did the code supplied therein, work for you Ronald?
 
 
  @Imad
 
  The Servlet Spec (and therefore Tomcat) doesn't differentiate between
  causes of session expiry.
 
  The code requires you to set a value in the application scope, then the
  HttpSessionListener sessionDestroyed method checks for that value.
 
  If the value is present, you initiated shutdown. If it is not, then
  it's probably a session expiry and you run your logout code.
 
  Did you actually set such an attribute?
 
 
  p
 
 
  Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
  hachem_i...@hotmail.com:
 
 
 
 
  Dear Pid,
 
 
 
  I am running a Logout Process at each sessionDestroy.
 
 
 
  After applying the Cluster configuration, I don't want to Logout my
  Users (or run this Logout Process) after any Tomcat Cluster node
  shutdown, since the Session has been replicated to the other Node
  Cluster.
 
 
 
 
 
  Best Regards,
  Imad Hachem
  System Engineer
 
 
 
  From: p...@pidster.com
  Date: Tue, 17 Nov 2009 13:09:47 +
  Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
  shutdown, sessionDestroyed been called before contextDestroyed
  To: users@tomcat.apache.org
  On 17 Nov 2009, at 12:11, Imad Hachemhachem_i...@hotmail.com
  wrote:
 
  Dear Pid,
 
 
 
  I have tried that code and didn't helped, note that my context
  session variables are not coming as null in order to rely on to be
  able to differenciate between Tomcat Node shutdown
  session.invalidate().
  I'm sorry but I don't understand what you're saying here.
  Tomcat the servlet api can't tell you the difference between an app
  shutdown and a session expiry without you writing code.
  What did you try?
  What was or wasn't null exactly?
  p
  Best Regards,
  Imad Hachem
 
  System Engineer
 
 
 
 
  Date: Tue, 17 Nov 2009 11:41:20 +
  From: p...@pidster.com
  To: users@tomcat.apache.org
  Subject:

Re: silent / unattended install - tomcat 5.5

2009-11-17 Thread Pid Ster

I'd IMAGINE that you could download the zip version and examine the
contents of service.bat.

The rest is generic batch file commands, I think.

p

On 17 Nov 2009, at 23:31, Beatty.Thomas thomas.bea...@igt.com wrote:

 Hi

 Can someone PLEASE tell me how to install tomcat 5.5 silently? I
 need to install the service, set the destination folder, set the
 Administrator user name and password, and set the path to the JVM.
 Does anyone know the parameters that I need to set at the command
 line in order to accomplish this? So far I have the following:

 apache-tomcat-5.5.17.exe /S /D=C:\develop\tomcat5.5

 Thanks - TJ


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed

2009-11-17 Thread Pid Ster

On 18 Nov 2009, at 00:07, Imad Hachem hachem_i...@hotmail.com wrote:
 Dear Pid,
 find below my explanation:

 1. Manually set an attribute (e.g. MANUAL_STOP=1) in application scope
 2. Manually shutdown Tomcat instance.
 3. Tomcat expires all sessions
 4. Tomcat fires HttpSessionListener.sessionDestroyed for each session
 5. custom code checks for, and finds, attribute (e.g. MANUAL_STOP=1)
  if(MANUAL_STOP == null){  // Tomcat Cluster Node Shutdown

//don't do anything

  }

  else{  //  case of session.invalidate or session timeout

  6. custom code does logout per session
  }

 8. Tomcat fires ServletContextListener.contextDestroyed for each app

 But in fact, the variable MANUAL_STOP saved to the application scope
 is always coming as 1, even after tomcat cluster node shutdown which
 expected to come as null.

Yes. The value 1 is expected - you're not explaining why you think it
should be null.

p





 I need to know if my sessionDestroyed has been called from a
 session.invalidate Event OR session timeout OR Tomcat Cluster node
 shutdown.



 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 16:23:16 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 CC: ihac...@lb.path-solutions.com
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
 shutdown, sessionDestroyed been called before contextDestroyed

 On 17/11/2009 16:11, Imad Hachem wrote:

 Dear Pid,

 I am expecting them to come as null to know that the Tomcat Node
 (or context) has been shutdown.

 That makes no sense. These are the logical steps.

 1. Manually set an attribute (e.g. MANUAL_STOP=1) in application
 scope
 2. Manually shutdown Tomcat instance.
 3. Tomcat expires all sessions
 4. Tomcat fires HttpSessionListener.sessionDestroyed for each session
 5. custom code checks for, and finds, attribute (e.g. MANUAL_STOP=1)
 6. custom code does logout per session
 8. Tomcat fires ServletContextListener.contextDestroyed for each app


 Perhaps you can explain, clearly, what you expect to happen and
 where it
 happens?


 p


 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 16:08:37 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 CC: ihac...@lb.path-solutions.com
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
 shutdown, sessionDestroyed been called before contextDestroyed

 On 17/11/2009 15:57, Imad Hachem wrote:

 Dear Pid,

 I have tried to set application context variables, but it didn't
 worked, since I m expecting to get these variables as null
 values after node shutdown, but in fact they are coming as not
 null.

 If you set them as not null and they are not null why are you
 surprised?

 Why do you expect them to be null?


 p


 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 15:38:22 +
 From: p...@pidster.com
 To: users@tomcat.apache.org
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node
 shutdown, sessionDestroyed been called before contextDestroyed

 On 17/11/2009 14:40, Ronald Klop wrote:
 Hi Imad,

 Ronald. (The Ronald of the link mentioned by Pid.)

 Did the code supplied therein, work for you Ronald?


 @Imad

 The Servlet Spec (and therefore Tomcat) doesn't differentiate
 between
 causes of session expiry.

 The code requires you to set a value in the application scope,
 then the
 HttpSessionListener sessionDestroyed method checks for that
 value.

 If the value is present, you initiated shutdown. If it is not,
 then
 it's probably a session expiry and you run your logout code.

 Did you actually set such an attribute?


 p


 Op dinsdag, 17 november 2009 14:36 schreef Imad Hachem
 hachem_i...@hotmail.com:




 Dear Pid,



 I am running a Logout Process at each sessionDestroy.



 After applying the Cluster configuration, I don't want to
 Logout my
 Users (or run this Logout Process) after any Tomcat Cluster
 node
 shutdown, since the Session has been replicated to the other
 Node
 Cluster.





 Best Regards,
 Imad Hachem
 System Engineer



 From: p...@pidster.com
 Date: Tue, 17 Nov 2009 13:09:47 +
 Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster
 node
 shutdown, sessionDestroyed been called before contextDestroyed
 To: users@tomcat.apache.org
 On 17 Nov 2009, at 12:11, Imad
 Hachemhachem_i...@hotmail.com
 wrote:

 Dear Pid,



 I have tried that code and didn't helped, note that my
 context
 session variables are not coming as null in order to rely
 on to be
 able to differenciate between Tomcat Node shutdown
 session.invalidate().
 I'm sorry but I don't understand what you're saying here.
 Tomcat the servlet api can't tell you the difference
 between an app
 shutdown and a session expiry without you writing code.
 What did you try?
 What was or wasn't null exactly?
 p
 Best Regards,
 Imad Hachem

 System Engineer




 Date: Tue, 17 Nov 2009 11:41:20 +
 From: p...@pidster.com
 To: users@tomcat.apache.org

RE: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, sessionDestroyed been called before contextDestroyed