Hi guys,
The problems seems to be caused by a known bug in the Oracle JDBC
driver (see here: http://jrfom.com/2015archive/2014/01/08/fu-ojdbc,
might be NSFW). We found a workaround that seems to solve our particular
problem for the time being. We simply uploaded the oracle jdbc driver
jar to flin
Hi!
One thing you could try and do is create a dump of the JVM when it crashes,
and have a look at all the classes it has loaded.
For these long-running sessions (that share JVMs across jobs) it is
important that classes are properly unloaded.
If someone keeps holding references to the classes (e
Not a solution for your problem,but an alternative, I wrote my own sink
function where I handle all sql activities(insert/update/select), used a
3rd lib for connection pooling, the code has been running stable in
production without any issue.
On Fri, Apr 15, 2016 at 1:41 PM, Maximilian Bode <
maxi
Hi everyone,
we are testing a long-running streaming application, which shares a yarn
session with a batch job (containing JDBC(In|Out)putFormat) that is triggered
periodically. Unfortunately, the session is dying after a few runs of the batch
job. In fact, each run of the batch job kills one t
