On Mar 19, 2008, at 7:07 PM, Matt Johnston wrote:

> I am trying to use quercus to run phorum. I put my phorum installation
> into my war and tried to run it. When I try to run any pages, I get an
> error:
>
> Closing dangling connections.  All connections must have a close()  
> in a
> finally block.
> [21:00:28.114] {http--8080-7} java.lang.IllegalStateException:  
> unclosed
> connection:
> UserPoolItem[jdbc:mysql://localhost:3306/? 
> characterEncoding=ISO8859_1-0,7]
> was allocated at
> [21:00:28.114] {http--8080-7}         at
> com.caucho.jca.UserPoolItem.<init>(UserPoolItem.java:95)
> [21:00:28.114] {http--8080-7}         at
> com.caucho.jca.UserPoolItem.<init>(UserPoolItem.java:101)
> [21:00:28.114] {http--8080-7}         at
> com.caucho.jca.PoolItem.toActive(PoolItem.java:249)
> [21:00:28.114] {http--8080-7}         at
> com.caucho.jca.ConnectionPool.create(ConnectionPool.java:922)
> [21:00:28.114] {http--8080-7}         at
> com.caucho.jca.ConnectionPool.allocatePool(ConnectionPool.java:780)

Can you add more of the stack trace?  That will show where it's  
getting allocated from.

The Quercus code should never throw that exception, because we should  
always close the connection at the end of the request.

-- Scott

>
>
>
> Is there any way to tell what php code is causing this problem? Did I
> not setup something right? I defined the datasource in my web.xml
>
> <servlet-mapping url-pattern="*.php"
>
> servlet-class="com.caucho.quercus.servlet.QuercusServlet">
>                     <init>
>       <database>java:comp/env/jdbc/LattaPhorumDS</database>
>     </init>
>    </servlet-mapping>
>
>
>
> -- 
>
> Matt Johnston
> http://www.lattaoutdoors.com
> http://www.gearapalooza.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

Reply via email to