This content has been marked as final.
Show 2 replies
-
1. Re: Can't change Tomcat log level from DEBUG
raja05 Jan 25, 2005 12:14 AM (in response to mrooney)Can you post your jboss-srevice.xml? There are "debug" attribute elements in the Host/Engine/Service Elements that determine if debug statements need to be printed. the higher the value, the more the messages.
-
2. Re: Can't change Tomcat log level from DEBUG
mrooney Jan 25, 2005 8:42 AM (in response to mrooney)Here it is:
<?xml version="1.0" encoding="UTF-8"?> <!-- The service configuration for the embedded Tomcat4.1.x web container --> <server> <mbean code="org.jboss.web.tomcat.tc4.EmbeddedTomcatService" name="jboss.web:service=WebServer"> <!-- Get the flag indicating if the normal Java2 parent first class loading model should be used over the servlet 2.3 web container first model. --> <attribute name="Java2ClassLoadingCompliance">true</attribute> <attribute name="LenientEjbLink">true</attribute> <!-- A flag indicating if the JBoss Loader should be used. This loader uses a unified class loader as the class loader rather than the tomcat specific class loader. --> <attribute name="UseJBossWebLoader">true</attribute> <!-- The name of the request attribute under with the authenticated JAAS Subject is stored on successful authentication. If null or empty then the Subject will not be stored. --> <attribute name="SubjectAttributeName">j_subject</attribute> <!-- ******************************************************* ****************** CLUSTERING ************************* ******************************************************* In order to activate HTTP Session clustering for Tomcat make sure you run JBoss's "all" configuration i.e. "run -c all" (the default configuration doesn't contain clustering) Furthermore, you may change SnapshotMode and SnapshotInterval attributes below to indicate when to synchronize changes with the other node(s). If you use Apache+mod_jk(2) you will most probably use the AJP1.3 connector below. Thus, if you so wish, you may comment (i.e. deactivate) the HTTP connector as it won't be used anymore. ******************************************************* ******************************************************* ******************************************************* --> <!-- If you are using clustering, the following two attributes define when the sessions are replicated to the other nodes. The default value, "instant", synchronously replicates changes to the other nodes. In this case, the "SnapshotInterval" attribute is not used. The "interval" mode, in association with the "SnapshotInterval" attribute, indicates that Tomcat will only replicates modified sessions every "SnapshotInterval" miliseconds at most. --> <attribute name="SnapshotMode">instant</attribute> <!-- you may switch to "interval" --> <attribute name="SnapshotInterval">2000</attribute> <attribute name="Config"> <Server> <Service name="JBoss-Tomcat"> <Engine name="MainEngine" defaultHost="localhost"> <Logger className="org.jboss.web.tomcat.Log4jLogger" verbosityLevel="warning" category="org.jboss.web.localhost.Engine"/> <Host name="localhost"> <!-- Access logger --> <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="localhost_access" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/> <!-- This valve clears any caller identity set by the realm and provides access to the realm about the existence of an authenticated caller to allow a web app to run with a realm that support unauthenticated identities. It also establishes any run-as principal for the servlet being accessed. --> <Valve className="org.jboss.web.tomcat.security.SecurityAssociationValve"/> <!-- Default context parameters --> <DefaultContext cookies="true" crossContext="true" override="true"/> </Host> </Engine> <!-- A HTTP/1.1 Connector on port 8080 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" address="${jboss.bind.address}" port="8080" minProcessors="5" maxProcessors="100" enableLookups="true" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false"/> <!-- A AJP 1.3 Connector on port 8009 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" address="${jboss.bind.address}" port="8009" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> <!-- SSL/TLS Connector configuration using the SSL domain keystore <Connector className = "org.apache.coyote.tomcat4.CoyoteConnector" address="${jboss.bind.address}" port = "8443" scheme = "https" secure = "true"> <Factory className = "org.apache.coyote.tomcat4.CoyoteServerSocketFactory" keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore" keystorePass="rmi+ssl" protocol = "TLS"/> </Connector> --> </Service> </Server> </attribute> <depends>jboss:service=TransactionManager</depends> </mbean> </server>