tomcat jmx and INFO: Port busy 8009 java.net.BindException: Address already in use

2008-05-27 Thread sudip shrestha
with tomcat 5.5.20 and mx4j-tools.jar at common/lib and the following setting: Connector port=${AJP.PORT} handler.list=mx mx.enabled=true mx.httpHost=localhost mx.httpPort=8181 protocol=AJP/1.3 / I get the following startup log: INFO:

Re: tomcat jmx and INFO: Port busy 8009 java.net.BindException: Address already in use

2008-05-27 Thread sudip shrestha
Thanks... On 5/27/08, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: you're not trying to configure a JMX connector, you're trying to configure an AJP connector as defined by Connector port=${AJP.PORT} protocol=AJP/1.3 / Filip sudip shrestha wrote: with tomcat 5.5.20 and mx4j

tomcat /shared/lib jars

2007-02-15 Thread sudip shrestha
Hi, I have gone thru' docs and the mailing list, still can't seem to find how to make tomcat recognize /shared/lib/ jars. Any suggestions? Thanks.

Fwd: tomcat /shared/lib jars

2007-02-15 Thread sudip shrestha
using tomcat 5.5.20: -- Forwarded message -- From: sudip shrestha [EMAIL PROTECTED] Date: Feb 15, 2007 9:35 AM Subject: tomcat /shared/lib jars To: users@tomcat.apache.org Hi, I have gone thru' docs and the mailing list, still can't seem to find how to make tomcat recognize

Re: tomcat /shared/lib jars

2007-02-15 Thread sudip shrestha
once again the version is: 5.5.20. the only errors I get are missing jar files type of errors. On 2/15/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: sudip shrestha [mailto:[EMAIL PROTECTED] Subject: tomcat /shared/lib jars I have gone thru' docs and the mailing list, still can't

Re: Tomcat / LDAPS

2005-11-17 Thread sudip shrestha
JNDIRealm does not work in ldaps:// Here is a good source that works! http://www.mozilla.org/directory http://www.dahbura.com/ On 11/17/05, Farid Izem [EMAIL PROTECTED] wrote: Hi all, I'd like to configure a LDAPS Authentication to protect some of my webapps. Has anyone already done that ?

Re: Tomcat 5.0 : howto make a webapp the ROOT webapp the proper way

2005-11-08 Thread sudip shrestha
I had the similar problem before.. http://www.mail-archive.com/users@tomcat.apache.org/msg00057.html Just remove the context elment from the server.xml file. Tomcat 5 docs don't recommend putting context in server.xml. If you do so, it will create webAppName.xml file in your

effects of context defining twice

2005-10-13 Thread sudip shrestha
Configuration: Tomcat 5.5.7 + JDK 1.5.0_01 + Struts 1.2.7 + Hibernate 2.1.8+ Debian Sarge + Kernel 2.6.9 + Apache 2.0.53 I found that my administrator had forgotten to remove context element from the server.xml file when I had META-INF/context.xml (which in effect creates the webAppName.xml file

Re: effects of context defining twice

2005-10-13 Thread sudip shrestha
Just wanted to mention, cpu usage and memory usage just look fine and there is no output/exception on any of the log files during the lock up period. -- Forwarded message -- From: sudip shrestha [EMAIL PROTECTED] Date: Oct 13, 2005 9:04 AM Subject: effects of context defining