Mantis Bugtracker
  

Viewing Issue Advanced Details Jump to Notes ] View Simple ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0001241 [Quercus] minor always 07-10-06 16:40 07-18-06 09:44
Reporter koreth View Status public  
Assigned To ferg
Priority normal Resolution fixed Platform
Status closed   OS
Projection none   OS Version
ETA none Fixed in Version 3.0.20 Product Version 3.0.19
  Product Build
Summary 0001241: Lots of InstanceAlreadyExists exceptions when using MySQL from Quercus
Description It looks like something in the current (Subversion) Quercus MySQL code isn't playing nice with JMX. I get tons of these exceptions, though the app appears to work fine. Seems to spit out one every time our code connects to MySQL, which of course happens a lot.

[16:36:40.552] javax.management.InstanceAlreadyExistsException: resin:type=ConnectionPool,Host=default,WebApp=/,name=dbpool-0
[16:36:40.552] at com.caucho.jmx.AbstractMBeanServer.registerMBean(AbstractMBeanServer.java:427)
[16:36:40.552] at com.caucho.jmx.Jmx.register(Jmx.java:252)
[16:36:40.552] at com.caucho.management.server.AbstractManagedObject.registerSelf(AbstractManagedObject.java:122)
[16:36:40.552] at com.caucho.jca.ConnectionPool.init(ConnectionPool.java:439)
[16:36:40.552] at com.caucho.sql.DBPool.init(DBPool.java:599)
[16:36:40.552] at com.caucho.sql.DatabaseManager.findDatabaseImpl(DatabaseManager.java:112)
[16:36:40.552] at com.caucho.sql.DatabaseManager.findDatabase(DatabaseManager.java:88)
[16:36:40.552] at com.caucho.quercus.env.Env.getConnection(Env.java:497)
[16:36:40.552] at com.caucho.quercus.lib.db.Mysqli.connectInternal(Mysqli.java:136)
[16:36:40.552] at com.caucho.quercus.lib.db.Mysqli.<init>(Mysqli.java:96)
[16:36:40.552] at com.caucho.quercus.lib.db.MysqlModule.mysql_connect(MysqlModule.java:744)
...
Steps To Reproduce
Additional Information
Attached Files

- Relationships

- Notes
(0001398)
koreth
07-13-06 22:23

A slight clarification: this seems to happen every time our code connects to a particular MySQL instance for the first time (which I assume implies the creation of a connection pool for that instance). Once the site has been up for a while and we've contacted all our databases, I stop seeing the error message.
 

- Issue History
Date Modified Username Field Change
07-10-06 16:40 koreth New Issue
07-13-06 22:23 koreth Note Added: 0001398
07-18-06 09:44 ferg Assigned To  => ferg
07-18-06 09:44 ferg Status new => closed
07-18-06 09:44 ferg Resolution open => fixed
07-18-06 09:44 ferg Fixed in Version  => 3.0.20


Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
26 unique queries executed.
Powered by Mantis Bugtracker