Re: Application crash after Migrate to different ESX

2011-06-07 Thread הילה
Excellent. thanks a lot for all of your help :) 2011/6/7 Christopher Schultz > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > הילה, > > On 6/6/2011 4:35 PM, הילה wrote: > > I use Tomcat's JDBC pool (tomcat-jdbc.jar) > > Okay. > > > sorry, I haven't quite understood why shouldn't I use the

Re: Application crash after Migrate to different ESX

2011-06-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 הילה, On 6/6/2011 4:35 PM, הילה wrote: > I use Tomcat's JDBC pool (tomcat-jdbc.jar) Okay. > sorry, I haven't quite understood why shouldn't I use the > ValidationInterval="3" (30 seconds) string on my configuration.. > On tomcat's documentation,

Re: Application crash after Migrate to different ESX

2011-06-06 Thread הילה
Hey, I use Tomcat's JDBC pool (tomcat-jdbc.jar) sorry, I haven't quite understood why shouldn't I use the ValidationInterval="3" (30 seconds) string on my configuration.. On tomcat's documentation, it says that testonborrow=true and validationQuery=SELECT 1 were part of the DBCP , and the Valid

Re: Application crash after Migrate to different ESX

2011-06-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 הילה, On 6/6/2011 9:56 AM, הילה wrote: > I've set testonborrow, validationquery and validationinterval - and it did > the trick. After ESX migration or just disconnect and reconnect of the > network card, the application recovers by itself. Note that

Re: Application crash after Migrate to different ESX

2011-06-06 Thread הילה
Thanks :] I've set testonborrow, validationquery and validationinterval - and it did the trick. After ESX migration or just disconnect and reconnect of the network card, the application recovers by itself. Thanks Hila 2011/6/6 Christopher Schultz > -BEGIN PGP SIGNED MESSAGE- > Hash: SH

Re: Application crash after Migrate to different ESX

2011-06-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 הילה, On 6/1/2011 5:14 PM, הילה wrote: > when using the string > testonborrow="true" > do I need to use it alone? It is not effective alone. In fact, testOnBorrow="true" is the default, oddly enough. http://commons.apache.org/dbcp/configuration.html

Re: Application crash after Migrate to different ESX

2011-06-01 Thread הילה
Hey, Explaining the whole infrastructure may be even more confusing. so I'll ask something else, simpler- when using the string testonborrow="true" do I need to use it alone? can it be used alone? or do I have to put also the validationInterval string (or any other string)? Thanks Hila 2011/5/20

Re: Application crash after Migrate to different ESX

2011-05-20 Thread André Warnier
הילה wrote: ... So, if you are using that pool, I basically do not understand why you would need any additional mechanism to overcome the loss of a db connection when your VM is migrated. Particularly that "smart keep alive" you keep talking about, but never telling us where it comes from and w

Re: Application crash after Migrate to different ESX

2011-05-19 Thread chris derham
> > #2 here blows my mind: an LB runs an XSLT that connects to a DB? WTF? > > Another thought that occurs to me is why are you using xslt. Why not code a jsp page - java servlet whatever. At least in this, you could add some proper logging, and possibly take some corrective action when an exception

Re: Application crash after Migrate to different ESX

2011-05-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 הילה, On 5/19/2011 4:06 PM, הילה wrote: >> 1) You have tomcat 6.0.29 running on virtual machines running on win 2008 >> 2) You have a load balancer which calls a home made xslt transform, that >> queries the database. If this fails 3 times in a row, t

Re: Application crash after Migrate to different ESX

2011-05-19 Thread הילה
> > All, > > 16 emails into this chain - might be worth a summary > > 1) You have tomcat 6.0.29 running on virtual machines running on win 2008 > 2) You have a load balancer which calls a home made xslt transform, that > queries the database. If this fails 3 times in a row, the load balancer > trea

Re: Application crash after Migrate to different ESX

2011-05-19 Thread chris derham
All, 16 emails into this chain - might be worth a summary 1) You have tomcat 6.0.29 running on virtual machines running on win 2008 2) You have a load balancer which calls a home made xslt transform, that queries the database. If this fails 3 times in a row, the load balancer treats the machine a

Re: Application crash after Migrate to different ESX

2011-05-19 Thread הילה
Yes, but did you actually ever bother to read its documentation, e.g. at http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html ? > (particularly starting with the attribute "testOnBorrow") > > I do not know much about these things, but just entering > ""org.apache.tomcat.jdbc.pool" in Google,

Re: Application crash after Migrate to different ESX

2011-05-19 Thread André Warnier
הילה wrote: Hey, All of you basically asked about the connection pool I'm using. I stated at the beginning that I'm using JDBC connection pool. I implement it in the xml file under conf\catalina\localhost, under resource tag- *factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"* with placing

Re: Application crash after Migrate to different ESX

2011-05-18 Thread הילה
Hey, All of you basically asked about the connection pool I'm using. I stated at the beginning that I'm using JDBC connection pool. I implement it in the xml file under conf\catalina\localhost, under resource tag- *factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"* with placing tomcat-jdbc.ja

Re: Application crash after Migrate to different ESX

2011-05-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 הילה, On 5/18/2011 4:20 AM, הילה wrote: > this behavior occur even when I'm disconnecting the Network card from the VM > settings and connecting it again. At least it's reproducible in a way that you're willing to try in production. What about reprod

Re: Application crash after Migrate to different ESX

2011-05-18 Thread chris derham
> > this behavior occur even when I'm disconnecting the Network card from the > VM > settings and connecting it again. > afterwards, the keep alive is alternately unavailable. looks like it's not > always trying to approach the DB opened wireshark and saw that ip.addr==DB > IP ADDRESS is not always

Re: Application crash after Migrate to different ESX

2011-05-18 Thread André Warnier
הילה wrote: UPDATE- this behavior occur even when I'm disconnecting the Network card from the VM settings and connecting it again. afterwards, the keep alive is alternately unavailable. looks like it's not always trying to approach the DB opened wireshark and saw that ip.addr==DB IP ADDRESS is n

Re: Application crash after Migrate to different ESX

2011-05-18 Thread הילה
UPDATE- this behavior occur even when I'm disconnecting the Network card from the VM settings and connecting it again. afterwards, the keep alive is alternately unavailable. looks like it's not always trying to approach the DB opened wireshark and saw that ip.addr==DB IP ADDRESS is not always show

Re: Application crash after Migrate to different ESX

2011-05-17 Thread הילה
> >>> I'll try explaining it differently. >>> >>> we use smart keep alive with this application. the smart keep alive does >> a >> connection to the DB, query something that relates to the application, and >> if everything turned out good, it returns state OK. if not ok, as in this >> case, it ret

Re: Application crash after Migrate to different ESX

2011-05-17 Thread André Warnier
הילה wrote: ... I'll try explaining it differently. we use smart keep alive with this application. the smart keep alive does a connection to the DB, query something that relates to the application, and if everything turned out good, it returns state OK. if not ok, as in this case, it returns

Re: Application crash after Migrate to different ESX

2011-05-17 Thread הילה
> > how can I abruptly break all connections between application and DB? >> the only way I know is take the server out of the Load balancer so no new >> users can get to the server + the LB kicks the users that are already >> connected. >> > > Pulling the network cable at the db server would do it.

Re: Application crash after Migrate to different ESX

2011-05-17 Thread David kerber
On 5/17/2011 2:39 PM, הילה wrote: I know that after migrate, a disconnection is expected, but in my case - it crashes completely, or alternately until it works (but don't know if it's stable now). It is not a problem, it is a feature. What is your question? what is the feature here exa

Re: Application crash after Migrate to different ESX

2011-05-17 Thread הילה
> > >> I know that after migrate, a disconnection is expected, but in my case - > >> it > >> crashes completely, or alternately until it works (but don't know if > it's > >> stable now). > > > > It is not a problem, it is a feature. What is your question? > what is the feature here exactly? > > A

Re: Application crash after Migrate to different ESX

2011-05-17 Thread הילה
2011/5/17 André Warnier > הילה wrote: > >> Hey Guys, >> >> My application runs on tomcat 6.0.29, win 2008 R2, which is a VM machine. >> i use the JDBC application pool., with java 1.6.24 64bit. >> > > OK. > > > >> I have a problem, in which after migrate of the VM machine to another ESX, >> the a

Re: Application crash after Migrate to different ESX

2011-05-17 Thread Konstantin Kolinko
2011/5/17 André Warnier : > הילה wrote: >> >> Hey Guys, >> >> My application runs on tomcat 6.0.29, win 2008 R2, which is a VM machine. >> i use the JDBC application pool., with java 1.6.24 64bit. > > OK. > >> >> I have a problem, in which after migrate of the VM machine to another ESX, >> the appl

Re: Application crash after Migrate to different ESX

2011-05-17 Thread André Warnier
הילה wrote: Hey Guys, My application runs on tomcat 6.0.29, win 2008 R2, which is a VM machine. i use the JDBC application pool., with java 1.6.24 64bit. OK. I have a problem, in which after migrate of the VM machine to another ESX, the application crashes, and doesn't recover by itself.

Application crash after Migrate to different ESX

2011-05-17 Thread הילה
Hey Guys, My application runs on tomcat 6.0.29, win 2008 R2, which is a VM machine. i use the JDBC application pool., with java 1.6.24 64bit. I have a problem, in which after migrate of the VM machine to another ESX, the application crashes, and doesn't recover by itself. I know that after migrat