Log message: "ERROR ISCObjectPool - return of object already in pool"

[hschack]

During startup of my application, I see the following message in the server log: "[izer] ERROR ISCObjectPool - return of object already in pool"

Please find the complete log in the attached file.

I see the message in hosted mode, as well as in Glassfish.
The application seems to be running ok. However I would like to figure out what is causing the exception, to ensure that it will not cause any problems later on.
Do you have any hint what could be causing that behaviour?

I'm using SmartGWT Framework 4.1 (SNAPSHOT_v9.1d_2014-01-05/PowerEdition). I saw the exception the first time, when I moved from SmartGWT 4.0 to 4.1.

[michaeljseo]

GWT 2.6
Smartgwt 4.1p SNAPSHOT_v4.1p_2014-04-03/EE

I have the same problem. Any resolution?

Actually, my log is a bit different so I have attached it to this post.

[hschack]

I still have the same log message as described in my previous post, and no solution so far.

@Isomorphic, do you have any idea what could be the root cause?

Thank you

[michaeljseo]

Well, I found out that one of my modules was using 4.0 and I was using 4.1 version on the main module. I cleaned up my configuration and rebuilt everything. Now I'm fine.

[Isomorphic]

We are aware of this problem and are currently considering the best way to deal with it. We will post on this thread again when a fix goes in.

[stefan.braicu@xailabs.de]

return of object already in pool

Any news on this matter?

Thanks
Stefan

[wkok]

return of object already in pool

Hello,

SmartClient Version: v10.0p_2015-05-12/PowerEdition Deployment (built 2015-05-12)

I'm having the exact same issue, fills up my log file with this error attached.

Any news on this matter?

Server.properties:

# -------------- SETTINGS FOR MYSQL --------------------

# These are the settings for use with the Mysql database.  If you have
# just done a fresh install of MySQL on the same machine where you are
# running your servlet engine, the values provided below will probably
# just work on most platforms.

# Configuration for Mysql Connector/J
sql.Mysql.database.type: mysql
sql.Mysql.interface.type: jndi
sql.Mysql.driver.name: java:comp/env/MyApp
sql.useAnsiJoins: true
#sql.pool.enabled: false

Tomcat's context.xml:

<Context debug="5" reloadable="true" crossContext="true">

    <Resource name="MyApp"
              auth="Container"
              type="javax.sql.DataSource"
              factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
              maxActive="200"
              maxIdle="200"
              maxWait="10000"
              initialSize="0"
              testOnBorrow="true"
              validationInterval="1000"
              validationQuery="select 1"
              removeAbandoned="true"
              removeAbandonedTimeout="120"
              abandonWhenPercentageFull="50"
              logAbandoned="true"
              username="xxxxx"
              password="xxxxxx"
              driverClassName="com.mysql.jdbc.Driver"
              url="jdbc:mysql://xxxxxxx:3306/mydb"/>

</Context>

[Isomorphic]

We believe we have fixed this issue. Please try tomorrow's nightly build (the one dated July 10) and let us know if you still see the problem. Just to check though: this is a rare / intermittent thing, right? When you say it "fills up my log file", you don't mean that it happens all the time do you? If this is happening to you regularly, it means that your database is regularly cutting connections out from underneath your app, which suggests a database config problem.

[wkok]

This indeed seems fixed in the latest nightly build, thank you.

To answer your question, yes I only started to see this after I moved my database to Amazon RDS (MySQL). It did not happen anywhere else from what I've seen.

It could very well have been a database config issue, although I did not investigate it thoroughly.

This nightly build did make the error go away though.