Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
Ok. I admit that I have not check the list before I was posting. And I can take your comment on MBean part, but not the deploying part. :-) Thanks for your comments, Pae This is really a tomcat-user question (and, has been covered, ad nausium, on that list :) The short form is that you can either use the Ajp13Connector without MBeans, or you can use the Jk2 CoyoteConnector with MBeans. If you have a serious need for the Ajp13Connector with MBeans, patches are always welcome. - Original Message - From: Pae Choi [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 02, 2002 9:42 PM Subject: [4.1.16a] A feeedback from an Initial Installation on WinNT This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And the some parts seem not working as it used be in v4.1.12. The change made in the server.xml as follows: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- !-- commeted Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ -- !-- Define an AJP 1.3 Connector on port 8009 -- !-- uncommented -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ !-- -- And the exception dusring the startup is as follows: ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224) ... But it did not crashed so that I tested the index.jsp as follows: http://localhost/index.jsp http://localhost:8080/index.jsp https://real-domain/index.jsp https://real-domain:8443/index.jsp All above work as it suppose to be. However, a web app, demowa.war, did not deployed. And the exception is as follows: 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at context path /demowa 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at context path /demowa 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild: stop: LifecycleException: Container StandardContext[/demowa] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036) at org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.ja va:420) at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852) at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233) at org.apache.catalina.core.StandardService.stop(StandardService.java:554) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) 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:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Thanks, Pae -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
I have not looked the source code yet. And I won't have time for it for a while. Wasn't the exception in the previous message enough to trace the cause? I will provide you a full log if you think that will help. Pae Pae Choi wrote: This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And the some parts seem not working as it used be in v4.1.12. But it did not crashed so that I tested the index.jsp as follows: http://localhost/index.jsp http://localhost:8080/index.jsp https://real-domain/index.jsp https://real-domain:8443/index.jsp All above work as it suppose to be. However, a web app, demowa.war, did not deployed. And the exception is as follows: 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at context path /demowa 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at context path /demowa 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild: stop: LifecycleException: Container StandardContext[/demowa] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036) Ok, fine. And why wasn't the webapp deployed ? Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Externalizing the Configurable Inforamtion in TOMCAT -- Especially Security related Package
Folks, As J2SDK v1.4.x made changes including the SSL/TLS related APIs, we are no longer in need to embed the SUN's provider package, e.g., import com.sun.net.ssl.KeyManagerFactory; import com.sun.net.ssl.SSLContext; import com.sun.net.ssl.TrustManagerFactory; as defined in the org.apache.catalina.net.SSLServerSocketFactory. We now more use the javax.net.ssl.* package with J2SDK v4.x and a good sample is the RMI Using SSL The sample came with J2SDK v1.3.x and J2SDK v1.4.x are good example for the differences. I am thinking that it would be better for international users and more usability as well as acceptability, if TOMCAT can externalize the definitions of configurable info. e.g., provider name, type of key store, etc. Would it be possble to ask you, especially Harish Prabandham, Costin Manolache, and Craig McClanahan, to add this in the future release. + Support for PKCS12 key store type in addition to JKS + Ability to define the security provier package in the external configuration file. This can be one of three ways we can define the 1. Use the java.security 2. Use the command-line to deifne the sytem properties 3. Embed it in the code as the TOMCAT does. In this way we can continuously use the SUN's provider package as well as other packages based on the USER's prference. BouncyCastle can be one of packages other than SUN's package. Please note that I am not againsnt any specifc vendor not package, but just think that it would create ore flexibility. I for one am very happy with you folks' work. And thank you always. Any comments on this are welcome and will be appreciated. Regards, Pae
Two TCs???
Do we have two seperate TCs in the development process? I see the v4.0.4-b3 release arouind 10th and 11th of May as well as v4.1.3-b release around 28th and 29th of May. What's going on? Pae [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/ [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Two TCs???
Craig, Thank you for your reply as well as clarifying my previous inquiry. Best, Pae - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Cc: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, June 12, 2002 10:33 AM Subject: Re: Two TCs??? On Wed, 12 Jun 2002, Pae Choi wrote: Date: Wed, 12 Jun 2002 12:56:20 -0700 From: Pae Choi [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Cc: Tomcat Developers List [EMAIL PROTECTED] Subject: Two TCs??? Do we have two seperate TCs in the development process? I see the v4.0.4-b3 release arouind 10th and 11th of May as well as v4.1.3-b release around 28th and 29th of May. Active development of new features (such as substantially improved performance on JSP pages, and the new admin webapp) are taking place in the 4.1.x development tree. Because there is lots of new code here, the risk of new bugs is somewhat higher than on a stable release. Bugfix maintenance releases continue in the 4.0.x development tree so that people running production apps have a lower risk way to incorporate fixes for existing bugs -- but new features only go into the new version. What's going on? Same thing that happens in most major software development projects -- overlapping development cycles. Consider Apache (1.3.x versus 2.0.x), Linux (2.4 versus 2.5), and pretty much any other large scale product, and you'll see the same thing. Pae Craig [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/ [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Manager Command List in TC 4.0.3
Folks,
I am awaring of some commands in the Manager app, e.g., [1]Manager App
HOW-TO. Is there a way to get all available commands? If not, wouldn't
it
be nice to have it? Something like,
http(s)://{host}:{port}/manager/command?list
Or in a simliar fashion. How is that? :-). Thank you.
Best,
Pae
[1] Manager App HOW-TO
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/manager-howto.html
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[T4b3] mod_webapps
Folks, I am having a problem to make mod_webapp module for NT by follwing the instruction in server.xml with gcc. It's a kind of my wish that it will be nice to have either have an already-built module or VC++ makefile for WIN32. Is this too much to ask? Pae
Re: [ANNOUNCE] Tomcat 4.0 Beta 2
My THANKS to Craig and all other participants, including the contributers for this milestone to happen. I am not quite ready to move on, but I will be very *glad* to play with this once I am avaialbe to do so. Craig, do you have any documentation plan for the installation and configuration as well? If so, would you share with us? Best regards, Pae -Original Message- From: Craig R. McClanahan [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Friday, March 30, 2001 11:25 PM Subject: [ANNOUNCE] Tomcat 4.0 Beta 2 I'm pleased to announce the availability of the Beta 2 release of the next generation of the Tomcat servlet container, at: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b2/ Tomcat 4.0 beta 2 has many new features, including: * Tomcat 4.0 can now run web applications out of an unpacked directory or directly from a WAR file. * Web applications are now run under the control of a Java SecurityManager that can support fine-grained control over each web-app's access to system resources. * You can now specify a DefaultContext element in the server configuration file (server.xml) that defines default configuration information for contexts that are automatically configured. * An example Filter implementation that supports on-the-fly GZIP compression for clients that support it. * A servlet that implements all of the NCSA documented functionality for server side includes (*.shtml) except for the "exec" capability. * Standard resource factories for JavaMail related resources accessible via a JNDI InitialContext, compatible with J2EE Specification requirements. * Reflects the most up-to-date changes in the Servlet 2.3 and JSP 1.2 APIs that have been approved by the JSR-053 expert group, and will appear in the next published version of the corresponding specifications. In addition, the following major bug fixes are included: * Fixes for two reported security vulnerabilities (a "cross site scripting vulnerability" plus a "URL decoding vulnerability") * The JSP servlet (Jasper) that compiles and executes JSP pages now uses its own classloader its associated XML parser, which avoids potential conflicts with parsers included with a web application. * Bug fix updates for directory listings, the WebDAV support, binding to a single IP address (if requested), incorrectly named access log files, URL decoding improvements, form-based authentication, HTTP/1.1 chunking, isUserInRole(), JSP page parsing problems, and many other patches. See the Tomcat 4.0 Beta 2 Release Notes (RELEASE-NOTES-4.0-B2.txt) that are included in the top-level directory of the release for more detailed information. Craig McClanahan
