I'm not sure if this will help, but let me see if I can point out  
some suggestions for your config

> On Nov 16, 2007, at 3:29 AM, Leviz wrote:
>
>>
>> Hi everybodies
>>
>> I'm trying, for one week, to configurate my resin.conf but I don't
>> know why,
>> it doesn't work. My resin service is looping when I launch it.
>>
>> I'm using resin-3.1.3 with IIS.
>>
>> Somebody can help me please?
>>
>> Here is my code  :
>>
>> <!--
>>   - Resin 3.1 configuration file.
>>  -->
>> <resin xmlns="http://caucho.com/ns/resin";
>>       xmlns:resin="http://caucho.com/ns/resin/core";>
>>
>>  <!-- adds all .jar files under the resin/lib directory -->
>>  <class-loader>
>>    <tree-loader path="${resin.home}/lib"/>
>>    <tree-loader path="${resin.home}/lib/ext"/>
>>  </class-loader>
>>

This COULD possibly give you the looping but I doubt it.  You only  
need one tree-loader for the ${resin.home}/lib directory as the tree- 
loader will load all libraries in subdirectories as well.  You can  
remove the second /lib/ext.

>>
>>  <!--
>>     - Logging configuration for the JDK logging API.
>>    -->
>>  <log name="" level="info" path="D:/Exel/www/logs/info.log"
>> timestamp="[%H:%M:%S.%s]" rollover-period="3M"/>
>>  <log name="com.caucho.java" level="config" path="D:/Exel/www/
>> java.log"
>> timestamp="[%H:%M:%S.%s]" rollover-period="3M"/>
>>

Try changing the level for both to "finer" to see if you can get more  
useful information as someone else already suggested.

>>
>>  <!--
>>     - 'info' for production
>>     - 'fine' or 'finer' for development and troubleshooting
>>    -->
>>  <logger name="com.caucho" level="info"/>
>>
>>  <logger name="com.caucho.java" level="config"/>
>>  <logger name="com.caucho.loader" level="config"/>
>>

Temporarily comment these <logger> statements out when you change the  
<log> level to "finer"

>>  <!--
>>     - For production sites, change dependency-check-interval to
>> something
>>     - like 600s, so it only checks for updates every 10 minutes.
>>    -->
>>  <dependency-check-interval>600s</dependency-check-interval>
>>
>>   <!--
>>     - You can change the compiler to "javac", "eclipse" or  
>> "internal".
>>    -->
>>  <javac compiler="internal" args="-source 1.5"/>
>>
>>  <cluster id="app-tier">
>>    <!-- sets the content root for the cluster, relative to
>> server.root -->
>>    <root-directory>D:\Exel</root-directory>
>>
>>    <server-default>
>>      <!-- The http port -->
>>      <http address="*" port="80"/>
>>
>>      <!--
>>         - The JVM arguments
>>        -->
>>      <jvm-arg>-Xmx256m</jvm-arg>
>>      <jvm-arg>-Xss1m</jvm-arg>
>>      <jvm-arg>-Xdebug</jvm-arg>
>>      <jvm-arg>-Dcom.sun.management.jmxremote</jvm-arg>
>>
>>      <!--
>>         - Uncomment to enable admin heap dumps
>>         - <jvm-arg>-agentlib:resin</jvm-arg>
>>        -->
>>
>>      <watchdog-arg>-Dcom.sun.management.jmxremote</watchdog-arg>
>>
>>      <!--
>>         - Configures the minimum free memory allowed before Resin
>>         - will force a restart.
>>        -->
>>      <memory-free-min>1M</memory-free-min>
>>
>>      <!-- Maximum number of threads. -->
>>      <thread-max>256</thread-max>
>>
>>      <!-- Configures the socket timeout -->
>>      <socket-timeout>65s</socket-timeout>
>>
>>      <!-- Configures the keepalive -->
>>      <keepalive-max>128</keepalive-max>
>>      <keepalive-timeout>15s</keepalive-timeout>
>>
>>      <!--
>>         - If starting bin/resin as root on Unix, specify the user  
>> name
>>         - and group name for the web server user.
>>         -
>>         - <user-name>resin</user-name>
>>         - <group-name>resin</group-name>
>>        -->
>>    </server-default>
>>
>>    <!-- define the servers in the cluster -->
>>    <server id="" address="127.0.0.1" port="6800"/>
>>
>>
>>
>>    <!-- includes the app-default for default web-app behavior -->
>>    <resin:import path="${resin.home}/conf/app-default.xml"/>
>>
>>    <!--
>>       - Defaults applied to each web-app.
>>      -->
>>    <web-app-default>
>>
>>      <!--
>>         - Enable EL expressions in Servlet and Filter init-param
>>        -->
>>      <allow-servlet-el/>
>>
>>
>>      <!--
>>         - Some JSP packages have incorrect .tld files.  It's
>> possible to
>>         - set validate-taglib-schema to false to work around these
>> packages.
>>        -->
>>        <jsp>
>>          <validate-taglib-schema>true</validate-taglib-schema>
>>          <fast-jstl>true</fast-jstl>
>>          <fast-jsf>true</fast-jsf>
>>        </jsp>
>>    </web-app-default>
>>
>>
>>    <!-- configures the default host, matching any host name -->
>>    <host id="" root-directory="D:\Exel">
>>      <!--
>>         - configures an explicit root web-app matching the
>>         - webapp's ROOT
>>        -->
>>      <web-app id="/" >
>>      <document-directory>D:\Exel\www</document-directory>
>>      <class-loader>
>>                      <compiling-loader path="WEB-INF/classes"/>
>>                      <library-loader path="WEB-INF/lib"/>
>>              </class-loader>
>>      <session-config>
>>              <!-- 6 hour timeout -->
>>              <session-timeout>60</session-timeout>
>>              <session-max>4096</session-max>
>>      </session-config>
>>      </web-app>
>>      

I would suggest that you take out these <class-loader> configurations  
here.  This is already specified for you in the app-default.xml file  
that you included earlier.  It probably won't fix anything since  
Resin merges all the setting together, but there's not reason to be  
redundant.


>>
>>    <web-app id="/ecom/" >
>>    <document-directory>D:\Exel\ecom</document-directory>
>>      <class-loader>
>>                      <compiling-loader path="WEB-INF/classes"/>
>>                      <library-loader path="WEB-INF/lib"/>
>>              </class-loader>
>>      <session-config>
>>              <!-- 6 hour timeout -->
>>              <session-timeout>60</session-timeout>
>>              <session-max>4096</session-max>
>>      </session-config>
>>      </web-app>
>>

Remove <class-loader> stanza here as well.

Try out these settings and see if anything happens.. I don't think so  
though, but at least it'll eliminate one possibility.

>>      <web-app id="/resin-admin" root-directory="${resin.home}/php/
>> admin">
>>        <!--
>>           - Administration application /resin-admin
>>           -
>>           - password is the md5 hash of the password.
>>           - localhost is true to limit access to the localhost
>>          -->
>>        <prologue>
>>          <resin:set var="resin_admin_user" value=""/>
>>          <resin:set var="resin_admin_password" value=""/>
>>          <resin:set var="resin_admin_external" value="false"/>
>>        </prologue>
>>      </web-app>
>>    </host>
>>  </cluster>
>>
>>
>> </resin>
>>
>>
>>
>>
>> -- 
>> View this message in context: http://www.nabble.com/Problems-with- 
>> the-resin.conf-tf4820117.html#a13789961
>> Sent from the Resin mailing list archive at Nabble.com.
>>
>>
>>
>> _______________________________________________
>> resin-interest mailing list
>> resin-interest@caucho.com
>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>
>
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to