On 12/12/14 10:50 AM, Kevin Luo wrote:
Hi, I've been thrown to the bottom of valley over last 2 hours trying
to figure out why I was keeping the error message:"
>>Returning connection
org.apache.commons.dbcp.PoolableConnection@fc23cf to data source.
>>Remaining connections: None
F:\NBProject\DBTool\dist\build.xml:33: which is*<ddlToDatabase
schemaFile="project-schema.xml" verbosity="debug">*
org.apache.ddlutils.io.DataSinkException: java.sql.SQLException:
Connection is closed.
at
org.apache.ddlutils.io.DataToDatabaseSink.end(DataToDatabaseSink.java:221)
at
org.apache.ddlutils.task.WriteDataToDatabaseCommand.execute(WriteDataToDatabaseCommand.java:187)
at
org.apache.ddlutils.task.DatabaseTaskBase.executeCommands(DatabaseTaskBase.java:341)
at
org.apache.ddlutils.task.DatabaseTaskBase.execute(DatabaseTaskBase.java:381)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:392)
at org.apache.tools.ant.Target.performTasks(Target.java:413)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at
org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:283)
at
org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:541)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
Caused by: java.sql.SQLException: Connection is closed.
I followed the instructions every steps away written in the derby
official site http://db.apache.org/derby/integrate/db_ddlutils.html.
Can anyone please shed some lights on where could it possibly go wrong?
Thanks
Kev
Hi Kev,
It is hard to say what is going on here. The stack trace is a ddlutils
stack trace, which I don't understand. It is possible that there is also
a diagnostic log for Derby errors (usually called derby.log). If you
could post that derby.log, then we might be able to say more.
Thanks,
-Rick
