Hi,
I have a graph with a DBJoin node.
It seems that the DB Join is not closing the JDBC connection correctly, because at the end of my graph I get the following message.
Is this a problem or config?
Exception in thread "main" java.lang.RuntimeException: [SQLServer JDBC Driver]Socket closed
at org.jetel.lookup.DBLookupTable.free(DBLookupTable.java:595)
at org.jetel.component.DBJoin.free(DBJoin.java:252)
at org.jetel.graph.Phase.free(Phase.java:337)
at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:577)
at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:822)
at org.jetel.main.runGraph.runGraph(runGraph.java:381)
at org.jetel.main.runGraph.main(runGraph.java:310)
Thanks
Mike
I have a graph with a DBJoin node.
It seems that the DB Join is not closing the JDBC connection correctly, because at the end of my graph I get the following message.
Is this a problem or config?
Exception in thread "main" java.lang.RuntimeException: [SQLServer JDBC Driver]Socket closed
at org.jetel.lookup.DBLookupTable.free(DBLookupTable.java:595)
at org.jetel.component.DBJoin.free(DBJoin.java:252)
at org.jetel.graph.Phase.free(Phase.java:337)
at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:577)
at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:822)
at org.jetel.main.runGraph.runGraph(runGraph.java:381)
at org.jetel.main.runGraph.main(runGraph.java:310)
Thanks
Mike
-
Hello,
this bug was caused by not proper order of freeing graph resources and should have been fixed in last release. -
hi,
Please can you confirm the clover release number this was fixed in.
Thanks -
In 2.5.3 version freeing graph shouldn't throw the exception.
Please sign in to leave a comment.
Comments 3