You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Senthil Vaiyapuri <sv...@cisco.com> on 2001/02/02 21:36:16 UTC

Reloading .. Wassup ?

Kindered Folks:

    What is up with Servlet Reloading servlets Tomcat.  Anybody doing
some
    serious servlet app. development needs auto reloading on. (in dev
environments, just
    for the sake of webadmins sanity in the least :-))  Vanilla apps,
without the
    need to share (prestarted, preloaded)  common objects
(ConnectionPool, SessionPool etc.) seems
    to be OK.  Has anybody made it work ?  Any help is appreciated.

    We tried putting the SessionPool, ConnectionPool etc. in  a non
reloadable
    app. as mentioned in one of the mails in the list, but it did'nt
help also.

    Is this going to be fixed any time soon ?

    Thanks for your help.
    -senthil

Re: Reloading .. Wassup ?

Posted by Senthil Vaiyapuri <sv...@cisco.com>.
Pete,
    Thanks for the reply.

    We pre-start (<load-on-startup>), couple of servlets,
    SessionMgr and ConnectionPoolMgr.  They put couple of
    objects in the ServletContext (setAttribute), which will aid the application
servlets to
    get session, connection etc.  This application is marked
    "reloadable" in the server.xml context.  But, when
    any of our application servlets get recompiled, we get a
    "ClassCastException".  This goes away, if tomcat is
    restarted and is not acceptable in a development environment.

    Thanks much.
    -senthil

Pete Ehli wrote:

> Not sure what you are asking.
> In sever.xml you have various contexts or webapps
> If you set reloadable to true the classloader when tomcat
> restarts (the key word is restarts - you must stop then restart tomact)
> checks to see if changes are made to the .class files. If they are then they
> are reloaded into main memory. If this is wrong then someone correct
> me please. P.S. You probably already know this and your question
> is about connection pooling - if so clarify.
>
> <Context path="/myapps"
>                  docBase="webapps/myapps"
>                  crossContext="false"
>                  debug="0"
>                  reloadable="true" >  ******* This works!*******
>  </Context>
>
> ----- Original Message -----
> From: "Senthil Vaiyapuri" <sv...@cisco.com>
> To: <to...@jakarta.apache.org>
> Sent: Friday, February 02, 2001 12:36 PM
> Subject: Reloading .. Wassup ?
>
> > Kindered Folks:
> >
> >     What is up with Servlet Reloading servlets Tomcat.  Anybody doing
> > some
> >     serious servlet app. development needs auto reloading on. (in dev
> > environments, just
> >     for the sake of webadmins sanity in the least :-))  Vanilla apps,
> > without the
> >     need to share (prestarted, preloaded)  common objects
> > (ConnectionPool, SessionPool etc.) seems
> >     to be OK.  Has anybody made it work ?  Any help is appreciated.
> >
> >     We tried putting the SessionPool, ConnectionPool etc. in  a non
> > reloadable
> >     app. as mentioned in one of the mails in the list, but it did'nt
> > help also.
> >
> >     Is this going to be fixed any time soon ?
> >
> >     Thanks for your help.
> >     -senthil
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, email: tomcat-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-user-help@jakarta.apache.org

Re: Reloading .. Wassup ?

Posted by Pete Ehli <pe...@teleport.com>.
Not sure what you are asking.
In sever.xml you have various contexts or webapps
If you set reloadable to true the classloader when tomcat
restarts (the key word is restarts - you must stop then restart tomact)
checks to see if changes are made to the .class files. If they are then they
are reloaded into main memory. If this is wrong then someone correct
me please. P.S. You probably already know this and your question
is about connection pooling - if so clarify.

<Context path="/myapps"
                 docBase="webapps/myapps"
                 crossContext="false"
                 debug="0"
                 reloadable="true" >  ******* This works!*******
 </Context>

----- Original Message -----
From: "Senthil Vaiyapuri" <sv...@cisco.com>
To: <to...@jakarta.apache.org>
Sent: Friday, February 02, 2001 12:36 PM
Subject: Reloading .. Wassup ?


> Kindered Folks:
>
>     What is up with Servlet Reloading servlets Tomcat.  Anybody doing
> some
>     serious servlet app. development needs auto reloading on. (in dev
> environments, just
>     for the sake of webadmins sanity in the least :-))  Vanilla apps,
> without the
>     need to share (prestarted, preloaded)  common objects
> (ConnectionPool, SessionPool etc.) seems
>     to be OK.  Has anybody made it work ?  Any help is appreciated.
>
>     We tried putting the SessionPool, ConnectionPool etc. in  a non
> reloadable
>     app. as mentioned in one of the mails in the list, but it did'nt
> help also.
>
>     Is this going to be fixed any time soon ?
>
>     Thanks for your help.
>     -senthil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-user-help@jakarta.apache.org
>
>