Weird tomcat issue

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Weird tomcat issue

Vinny
Was playing with a vanilla grails 1.3.6  app using the
spring-security-core  and spring-security-ldap plugins and getting
weird errors from standalone tomcat:


Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesJdbc
SEVERE: The web application [/myapp] registered the JDBC driver
[com.mysql.jdbc.Driver] but failed to unregister it when the web
application was stopped. To prevent a memory leak, the JDBC Driver has
been forcibly unregistered.

This error causes my app not to deploy or at least be unreachable. I
read that this could happen when using Commons DBCP so I tried
swapping it out for the
Tomcat JDBC Connection Pool. But even after installing the jdbc-pool
plugin, I still get the above error and now the one below as well:


Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/myapp] appears to have started a thread
named [[Pool-Cleaner]:Tomcat Connection Pool[1-881341271]] but has
failed to stop it. This is very likely to create a memory leak.


Happens both on OSX and Linux with 64-bin java 6.
grails plugins installed:

famfamfam           1.0.1            --  Silk icons from famfamfam.com
greenmail           1.2.2            --  Greenmail Plugin for Grails
hibernate           1.3.6            --  Hibernate for Grails
jdbc-pool           0.3              --  Tomcat JDBC Pool plugin
jquery              1.4.4.1          --  JQuery for Grails
jquery-ui           1.8.7            --  jQuery UI resources
mail                1.0-SNAPSHOT     --  Provides Mail support to a
running Grails application
mysql-connectorj    5.1.12           --  MySQL Connector/J
spring-security-core1.1.2            --  Spring Security Core Plugin
spring-security-ldap1.0.2            --  LDAP authentication support
for the Spring Security plugin.
spring-security-ui  0.1.2            --  User interface extensions for
the Spring Security plugin.
tomcat              1.3.6            --  Apache Tomcat plugin for Grails

Has anyone run into this one. What's kind of funny is that I don't
even need a database but I can't figure out how to use
Spring-security-core without the hibernate/jdbc dependency.

Thanks in advance

--
biz: http://www.linkedin.com/in/vincentstoessel/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Weird tomcat issue

Vinny
Ok, I just realized that this was a URL  mapping issue.  The tomcat
error messages were not  stopping the app from deploying like I
thought it was.
Sorry :)
--
biz: http://www.linkedin.com/in/vincentstoessel/



On Mon, Feb 28, 2011 at 5:55 PM, Vinny <[hidden email]> wrote:

> Was playing with a vanilla grails 1.3.6  app using the
> spring-security-core  and spring-security-ldap plugins and getting
> weird errors from standalone tomcat:
>
>
> Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesJdbc
> SEVERE: The web application [/myapp] registered the JDBC driver
> [com.mysql.jdbc.Driver] but failed to unregister it when the web
> application was stopped. To prevent a memory leak, the JDBC Driver has
> been forcibly unregistered.
>
> This error causes my app not to deploy or at least be unreachable. I
> read that this could happen when using Commons DBCP so I tried
> swapping it out for the
> Tomcat JDBC Connection Pool. But even after installing the jdbc-pool
> plugin, I still get the above error and now the one below as well:
>
>
> Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/myapp] appears to have started a thread
> named [[Pool-Cleaner]:Tomcat Connection Pool[1-881341271]] but has
> failed to stop it. This is very likely to create a memory leak.
>
>
> Happens both on OSX and Linux with 64-bin java 6.
> grails plugins installed:
>
> famfamfam           1.0.1            --  Silk icons from famfamfam.com
> greenmail           1.2.2            --  Greenmail Plugin for Grails
> hibernate           1.3.6            --  Hibernate for Grails
> jdbc-pool           0.3              --  Tomcat JDBC Pool plugin
> jquery              1.4.4.1          --  JQuery for Grails
> jquery-ui           1.8.7            --  jQuery UI resources
> mail                1.0-SNAPSHOT     --  Provides Mail support to a
> running Grails application
> mysql-connectorj    5.1.12           --  MySQL Connector/J
> spring-security-core1.1.2            --  Spring Security Core Plugin
> spring-security-ldap1.0.2            --  LDAP authentication support
> for the Spring Security plugin.
> spring-security-ui  0.1.2            --  User interface extensions for
> the Spring Security plugin.
> tomcat              1.3.6            --  Apache Tomcat plugin for Grails
>
> Has anyone run into this one. What's kind of funny is that I don't
> even need a database but I can't figure out how to use
> Spring-security-core without the hibernate/jdbc dependency.
>
> Thanks in advance
>
> --
> biz: http://www.linkedin.com/in/vincentstoessel/
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Weird tomcat issue

Dean Del Ponte-2
In reply to this post by Vinny
Thanks for following up with your solution!

Dean Del Ponte

On Monday, February 28, 2011, Vinny <[hidden email]> wrote:

> Was playing with a vanilla grails 1.3.6  app using the
> spring-security-core  and spring-security-ldap plugins and getting
> weird errors from standalone tomcat:
>
>
> Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesJdbc
> SEVERE: The web application [/myapp] registered the JDBC driver
> [com.mysql.jdbc.Driver] but failed to unregister it when the web
> application was stopped. To prevent a memory leak, the JDBC Driver has
> been forcibly unregistered.
>
> This error causes my app not to deploy or at least be unreachable. I
> read that this could happen when using Commons DBCP so I tried
> swapping it out for the
> Tomcat JDBC Connection Pool. But even after installing the jdbc-pool
> plugin, I still get the above error and now the one below as well:
>
>
> Feb 28, 2011 5:38:20 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/myapp] appears to have started a thread
> named [[Pool-Cleaner]:Tomcat Connection Pool[1-881341271]] but has
> failed to stop it. This is very likely to create a memory leak.
>
>
> Happens both on OSX and Linux with 64-bin java 6.
> grails plugins installed:
>
> famfamfam           1.0.1            --  Silk icons from famfamfam.com
> greenmail           1.2.2            --  Greenmail Plugin for Grails
> hibernate           1.3.6            --  Hibernate for Grails
> jdbc-pool           0.3              --  Tomcat JDBC Pool plugin
> jquery              1.4.4.1          --  JQuery for Grails
> jquery-ui           1.8.7            --  jQuery UI resources
> mail                1.0-SNAPSHOT     --  Provides Mail support to a
> running Grails application
> mysql-connectorj    5.1.12           --  MySQL Connector/J
> spring-security-core1.1.2            --  Spring Security Core Plugin
> spring-security-ldap1.0.2            --  LDAP authentication support
> for the Spring Security plugin.
> spring-security-ui  0.1.2            --  User interface extensions for
> the Spring Security plugin.
> tomcat              1.3.6            --  Apache Tomcat plugin for Grails
>
> Has anyone run into this one. What's kind of funny is that I don't
> even need a database but I can't figure out how to use
> Spring-security-core without the hibernate/jdbc dependency.
>
> Thanks in advance
>
> --
> biz: http://www.linkedin.com/in/vincentstoessel/
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email