Netbeans screwed up my Tomcat install
How do I get rid of it? I can always reinstall tomcat, but I sure don't want to. I installed netbeans 3.5 on Linux. Somehow it screwed up my Tomcat server configuration. I wasn't using it with tomcat, just debugging a stand alone java program. When I went to start Tomcat, it doesn't with this message: 2003-08-04 15:41:18 StandardContext[/resources]: Starting filter 'HTTPMonitorFilter' 2003-08-04 15:41:18 StandardContext[/resources]: Exception starting filter HTTPMonitorFilter java.lang.ClassNotFoundException: org.netbeans.modules.web.monitor.server.MonitorFilter I found the jar file in the Netbeans tree that has the Monitor Filter and copied it into the Tomcat tree, but then it failed to find something else from the Netbeans install. Rather than chase my tail tring to find the right jar files, how can I get rid of the Netbean dependency in Tomcat? Thanks, Jim. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Netbeans screwed up my Tomcat install
Howdy, Look for the web.xml file where there's a Filter element with that netbeans class, and remove the definition (and any filter-mapping elements related to it) from the web.xml file. Just doing a clean install of tomcat is another option: it's quick and easy. Yoav Shapira Millennium ChemInformatics -Original Message- From: Jim Lynch [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2003 4:08 PM To: tomcat Subject: Netbeans screwed up my Tomcat install How do I get rid of it? I can always reinstall tomcat, but I sure don't want to. I installed netbeans 3.5 on Linux. Somehow it screwed up my Tomcat server configuration. I wasn't using it with tomcat, just debugging a stand alone java program. When I went to start Tomcat, it doesn't with this message: 2003-08-04 15:41:18 StandardContext[/resources]: Starting filter 'HTTPMonitorFilter' 2003-08-04 15:41:18 StandardContext[/resources]: Exception starting filter HTTPMonitorFilter java.lang.ClassNotFoundException: org.netbeans.modules.web.monitor.server.MonitorFilter I found the jar file in the Netbeans tree that has the Monitor Filter and copied it into the Tomcat tree, but then it failed to find something else from the Netbeans install. Rather than chase my tail tring to find the right jar files, how can I get rid of the Netbean dependency in Tomcat? Thanks, Jim. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Netbeans screwed up my Tomcat install
1. Delete Tomcat from the IDE. 2. Delete the $TOMCAT_HOME/conf/.nbattrs file and try replacing server.xml with original Tomcat installation file (attached)... I asked about Netbeans/Tomcat integration last week but apparently it is still a mistery ;-) Good luck!!! Hope this helps... - Original Message - From: Jim Lynch [EMAIL PROTECTED] To: tomcat [EMAIL PROTECTED] Sent: Monday, August 04, 2003 2:08 PM Subject: Netbeans screwed up my Tomcat install How do I get rid of it? I can always reinstall tomcat, but I sure don't want to. I installed netbeans 3.5 on Linux. Somehow it screwed up my Tomcat server configuration. I wasn't using it with tomcat, just debugging a stand alone java program. When I went to start Tomcat, it doesn't with this message: 2003-08-04 15:41:18 StandardContext[/resources]: Starting filter 'HTTPMonitorFilter' 2003-08-04 15:41:18 StandardContext[/resources]: Exception starting filter HTTPMonitorFilter java.lang.ClassNotFoundException: org.netbeans.modules.web.monitor.server.MonitorFilter I found the jar file in the Netbeans tree that has the Monitor Filter and copied it into the Tomcat tree, but then it failed to find something else from the Netbeans install. Rather than chase my tail tring to find the right jar files, how can I get rid of the Netbean dependency in Tomcat? Thanks, Jim. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !-- Example Server Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Uncomment these entries to enable JMX MBeans support -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ !-- Global JNDI resources -- GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Tomcat-Standalone !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 4.0 documentation bundle for more detailed instructions): * Download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client
