c3p0 / boneCP are basically connection pools around JDBC drivers. You can simply point your JDBC client (in this case the jdbc river) to c3p0 or bonecp which in turn, use the microsoft jdbc driver. Each connection pool has its own documentation on how to configure it -
it's pretty similar to your jdbc configuration.

By the way, I forgot to mention the jTDS driver [1], an open-source 
implementation for SQL server and Sybase.
Try first with that and see whether it alleviates your issue if not, I would 
pick BoneCP first followed by C3P0.

You could also try to see whether the MS driver has any options (such as timeout) and enable tracing to figure out why it's hanging [4]
[5]

Hope this helps,

[1] http://jtds.sourceforge.net/index.html
[2] http://jolbox.com/
[3] http://sourceforge.net/projects/c3p0/
[4] http://msdn.microsoft.com/en-us/library/ms378517.aspx
[5] http://msdn.microsoft.com/en-us/library/ms378522.aspx

On 1/7/15 5:43 AM, Garrett Johnson wrote:
I tried increasing the logging but it didn't give me anymore info.

I'm sure it is the jdbc driver as I have had to uninstall / reinstall 
everything several times and without that jdbc
river driver it's fine.

Since the search is working fine is there any issue with me having to kill it 
to restart?

That said it is unwise for that to be the case in a production environment 
regardless so can you give me and pointers to
info about c3P0 and / or Bone PC that directly relate to elasticsearch?

Thanks for your help

On Tuesday, January 6, 2015 5:08:37 AM UTC-6, Costin Leau wrote:

    It might be related then to the underlying JDBC driver. Try to change the 
driver or see if there are any parameters
    that
    you could set.
    Some drivers are buggy in that they prevent the JVM from shutting down 
correctly as they keep hanging on to the
    underlying connections.
    You could try using a connection pool in front, like c3p0 or BoneCP and see 
if it improves things.

    Costin

--
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to
elasticsearch+unsubscr...@googlegroups.com 
<mailto:elasticsearch+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/701e0c3e-d71c-487e-80e3-bc966c8d3f36%40googlegroups.com
<https://groups.google.com/d/msgid/elasticsearch/701e0c3e-d71c-487e-80e3-bc966c8d3f36%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
Costin

--
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/54AD0938.2000606%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to