Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
Did this get fixed in the resin-3.1.s080321 snapshot? I tried my phorum
installation again and the first time I called my phorum homepage I got:
[20:07:44.430] {http--8080-0} Closing dangling connections. All
connections must have a close() in a finally block.
[20:07:44.432] {http--8080-0} java.lang.IllegalStateException:
Connection UserConnection[ManagedConnectionImpl[jdbc/LattaPhorumDS.0]]
was not closed. Connections must have a close() in a finally block.
[20:07:44.432] {http--8080-0} at
com.caucho.jca.UserTransactionImpl.abortTransaction(UserTransactionImpl.java:532)
[20:07:44.432] {http--8080-0} at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:208)
[20:07:44.432] {http--8080-0} at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:266)
[20:07:44.432] {http--8080-0} at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:269)
[20:07:44.432] {http--8080-0} at
com.caucho.server.port.TcpConnection.run(TcpConnection.java:675)
[20:07:44.432] {http--8080-0} at
com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:721)
[20:07:44.432] {http--8080-0} at
com.caucho.util.ThreadPool$Item.run(ThreadPool.java:643)
[20:07:44.432] {http--8080-0} at java.lang.Thread.run(Thread.java:619)
If I then reload the page, I get a different stack trace:
[20:08:09.133] {http--8080-0} Closing dangling connections. All
connections must have a close() in a finally block.
[20:08:09.135] {http--8080-0} java.lang.IllegalStateException: unclosed
connection: UserPoolItem[jdbc/LattaPhorumDS,3] was allocated at
[20:08:09.135] {http--8080-0} at
com.caucho.jca.UserPoolItem.(UserPoolItem.java:95)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.UserPoolItem.(UserPoolItem.java:101)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.PoolItem.toActive(PoolItem.java:249)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.ConnectionPool.create(ConnectionPool.java:922)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.ConnectionPool.allocatePool(ConnectionPool.java:780)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.ConnectionPool.allocate(ConnectionPool.java:741)
[20:08:09.135] {http--8080-0} at
com.caucho.jca.ConnectionPool.allocateConnection(ConnectionPool.java:552)
[20:08:09.135] {http--8080-0} at
com.caucho.sql.DataSourceImpl.getConnection(DataSourceImpl.java:65)
[20:08:09.135] {http--8080-0} at
com.caucho.sql.DBPool.getConnection(DBPool.java:701)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.env.Env.getConnection(Env.java:699)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.lib.db.Mysqli.connectImpl(Mysqli.java:331)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.lib.db.JdbcConnectionResource.connectInternal(JdbcConnectionResource.java:195)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.lib.db.Mysqli.(Mysqli.java:141)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.lib.db.MysqlModule.mysql_connect(MysqlModule.java:990)
[20:08:09.135] {http--8080-0} at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[20:08:09.135] {http--8080-0} at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[20:08:09.135] {http--8080-0} at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[20:08:09.135] {http--8080-0} at
java.lang.reflect.Method.invoke(Method.java:597)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.module.StaticFunction.invoke(StaticFunction.java:129)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.env.JavaInvoker.callMethod(JavaInvoker.java:604)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.env.JavaInvoker.call(JavaInvoker.java:539)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.env.AbstractJavaMethod.callCopy(AbstractJavaMethod.java:91)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:180)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.expr.FunctionExpr.evalCopy(FunctionExpr.java:150)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.expr.AssignExpr.eval(AssignExpr.java:86)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java:105)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.IfStatement.execute(IfStatement.java:81)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java:105)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.Function.callImpl(Function.java:354)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.program.Function.callCopy(Function.java:299)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:180)
[20:08:09.135] {http--8080-0} at
com.caucho.quercus.expr.FunctionExpr.evalCopy(FunctionExpr.java:150)
[20:08:09.1
Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
On Mar 20, 2008, at 4:49 PM, Matt Johnston wrote:
> Here you go.
Perfect, thanks. The fix will be in the next snapshot.
-- Scott
>
>
>
> [18:49:26.628] {http--8080-1} Closing dangling connections. All
> connections must have a close() in a finally block.
> [18:49:26.630] {http--8080-1} java.lang.IllegalStateException:
> unclosed
> connection: UserPoolItem[jdbc/LattaPhorumDS,3] was allocated at
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.UserPoolItem.(UserPoolItem.java:95)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.UserPoolItem.(UserPoolItem.java:101)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.PoolItem.toActive(PoolItem.java:249)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.ConnectionPool.create(ConnectionPool.java:922)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.ConnectionPool.allocatePool(ConnectionPool.java:780)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.ConnectionPool.allocate(ConnectionPool.java:741)
> [18:49:26.630] {http--8080-1} at
> com.caucho.jca.ConnectionPool.allocateConnection(ConnectionPool.java:
> 552)
> [18:49:26.630] {http--8080-1} at
> com.caucho.sql.DataSourceImpl.getConnection(DataSourceImpl.java:65)
> [18:49:26.630] {http--8080-1} at
> com.caucho.sql.DBPool.getConnection(DBPool.java:701)
> [18:49:26.630] {http--8080-1} at
> com.caucho.quercus.env.Env.getConnection(Env.java:698)
> [18:49:26.630] {http--8080-1} at
> com.caucho.quercus.lib.db.Mysqli.connectImpl(Mysqli.java:262)
> [18:49:26.630] {http--8080-1} at
> com
> .caucho
> .quercus
> .lib
> .db
> .JdbcConnectionResource.connectInternal(JdbcConnectionResource.java:
> 193)
>
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
Here you go.
[18:49:26.628] {http--8080-1} Closing dangling connections. All
connections must have a close() in a finally block.
[18:49:26.630] {http--8080-1} java.lang.IllegalStateException: unclosed
connection: UserPoolItem[jdbc/LattaPhorumDS,3] was allocated at
[18:49:26.630] {http--8080-1} at
com.caucho.jca.UserPoolItem.(UserPoolItem.java:95)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.UserPoolItem.(UserPoolItem.java:101)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.PoolItem.toActive(PoolItem.java:249)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.ConnectionPool.create(ConnectionPool.java:922)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.ConnectionPool.allocatePool(ConnectionPool.java:780)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.ConnectionPool.allocate(ConnectionPool.java:741)
[18:49:26.630] {http--8080-1} at
com.caucho.jca.ConnectionPool.allocateConnection(ConnectionPool.java:552)
[18:49:26.630] {http--8080-1} at
com.caucho.sql.DataSourceImpl.getConnection(DataSourceImpl.java:65)
[18:49:26.630] {http--8080-1} at
com.caucho.sql.DBPool.getConnection(DBPool.java:701)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.env.Env.getConnection(Env.java:698)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.lib.db.Mysqli.connectImpl(Mysqli.java:262)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.lib.db.JdbcConnectionResource.connectInternal(JdbcConnectionResource.java:193)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.lib.db.Mysqli.(Mysqli.java:99)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.lib.db.MysqliModule.mysqli_connect(MysqliModule.java:214)
[18:49:26.630] {http--8080-1} at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[18:49:26.630] {http--8080-1} at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[18:49:26.630] {http--8080-1} at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[18:49:26.630] {http--8080-1} at
java.lang.reflect.Method.invoke(Method.java:597)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.module.StaticFunction.invoke(StaticFunction.java:129)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.env.JavaInvoker.callMethod(JavaInvoker.java:604)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.env.JavaInvoker.call(JavaInvoker.java:539)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.env.AbstractJavaMethod.callCopy(AbstractJavaMethod.java:91)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:180)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.evalCopy(FunctionExpr.java:150)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.AssignExpr.eval(AssignExpr.java:86)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.IfStatement.execute(IfStatement.java:75)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java:107)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.Function.callImpl(Function.java:354)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.Function.callCopy(Function.java:299)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:180)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.evalCopy(FunctionExpr.java:150)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.SuppressErrorExpr.evalCopy(SuppressErrorExpr.java:145)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.AssignExpr.eval(AssignExpr.java:86)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.ExprStatement.execute(ExprStatement.java:64)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java:107)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.Function.callImpl(Function.java:354)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.Function.call(Function.java:294)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.evalImpl(FunctionExpr.java:182)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.FunctionExpr.eval(FunctionExpr.java:126)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.Expr.evalBoolean(Expr.java:468)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.expr.NotExpr.evalBoolean(NotExpr.java:72)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.IfStatement.execute(IfStatement.java:74)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.BlockStatement.execute(BlockStatement.java:107)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.program.QuercusProgram.execute(QuercusProgram.java:239)
[18:49:26.630] {http--8080-1} at
com.caucho.quercus.page.InterpretedPage.execute(InterpretedPage.java:70)
[
Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
I need the other stack trace, the "UserPoolItem was allocated at ..."
-- Scott
On Mar 20, 2008, at 3:36 PM, Matt Johnston wrote:
> Here is the full stack track.
>
> [17:34:37.747] {http--8080-1} Closing dangling connections. All
> connections must have a close() in a finally block.
> [17:34:37.762] {http--8080-1} java.lang.IllegalStateException:
> Connection UserConnection[ManagedConnectionImpl[jdbc/LattaPhorumDS.0]]
> was not closed. Connections must have a close() in a finally block.
> [17:34:37.762] {http--8080-1} at
> com
> .caucho
> .jca.UserTransactionImpl.abortTransaction(UserTransactionImpl.java:
> 532)
> [17:34:37.762] {http--8080-1} at
> com
> .caucho
> .server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:208)
> [17:34:37.762] {http--8080-1} at
> com
> .caucho
> .server.dispatch.ServletInvocation.service(ServletInvocation.java:266)
> [17:34:37.762] {http--8080-1} at
> com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:269)
> [17:34:37.762] {http--8080-1} at
> com.caucho.server.port.TcpConnection.run(TcpConnection.java:603)
> [17:34:37.762] {http--8080-1} at
> com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:721)
> [17:34:37.762] {http--8080-1} at
> com.caucho.util.ThreadPool$Item.run(ThreadPool.java:643)
> [17:34:37.762] {http--8080-1} at java.lang.Thread.run(Thread.java:
> 619)
>
>
> Matt
>
> Scott Ferguson wrote:
>> 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.(UserPoolItem.java:95)
>>> [21:00:28.114] {http--8080-7} at
>>> com.caucho.jca.UserPoolItem.(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-class="com.caucho.quercus.servlet.QuercusServlet">
>>>
>>> java:comp/env/jdbc/LattaPhorumDS
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> 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
>>
>>
>
>
> --
>
> 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
Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
Here is the full stack track.
[17:34:37.747] {http--8080-1} Closing dangling connections. All
connections must have a close() in a finally block.
[17:34:37.762] {http--8080-1} java.lang.IllegalStateException:
Connection UserConnection[ManagedConnectionImpl[jdbc/LattaPhorumDS.0]]
was not closed. Connections must have a close() in a finally block.
[17:34:37.762] {http--8080-1} at
com.caucho.jca.UserTransactionImpl.abortTransaction(UserTransactionImpl.java:532)
[17:34:37.762] {http--8080-1} at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:208)
[17:34:37.762] {http--8080-1} at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:266)
[17:34:37.762] {http--8080-1} at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:269)
[17:34:37.762] {http--8080-1} at
com.caucho.server.port.TcpConnection.run(TcpConnection.java:603)
[17:34:37.762] {http--8080-1} at
com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:721)
[17:34:37.762] {http--8080-1} at
com.caucho.util.ThreadPool$Item.run(ThreadPool.java:643)
[17:34:37.762] {http--8080-1} at java.lang.Thread.run(Thread.java:619)
Matt
Scott Ferguson wrote:
> 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.(UserPoolItem.java:95)
>> [21:00:28.114] {http--8080-7}at
>> com.caucho.jca.UserPoolItem.(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-class="com.caucho.quercus.servlet.QuercusServlet">
>>
>> java:comp/env/jdbc/LattaPhorumDS
>>
>>
>>
>>
>>
>> --
>>
>> 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
>
>
--
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
Re: [Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
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.(UserPoolItem.java:95)
> [21:00:28.114] {http--8080-7} at
> com.caucho.jca.UserPoolItem.(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-class="com.caucho.quercus.servlet.QuercusServlet">
>
> java:comp/env/jdbc/LattaPhorumDS
>
>
>
>
>
> --
>
> 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
[Resin-interest] Quercus Phorum DB Errors, Closing dangling connections
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.(UserPoolItem.java:95)
[21:00:28.114] {http--8080-7} at
com.caucho.jca.UserPoolItem.(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)
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
java:comp/env/jdbc/LattaPhorumDS
--
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
