Re: Connection pooling issue on Tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Barry, On 3/28/14, 11:58 AM, Propes, Barry L wrote: Hi folks, I'm using Tomcat 6.0.29 for an app I've had in place for years. I run the Java app I have on a Windows 2003 server for my production region, but have local builds on both my desktop and laptop, both of which are Windows XP Pro. Yes, I do realize that the Tomcat version is old, but we'll be retiring the app in a few months so there's no need (at this time) to upgrade it. I use connection pooling, specifically Tomcat's DBCP class. This app has worked for years, but is suddenly encountering a strange connection error and issue to the PROD region only of Oracle 11. This just started in the last week. I'll include the contents of my context XML file and the errors that it's generating. Even stranger, my development build to the Oracle UAT region works just fine! These content.xml files are virtually the same, except one references the Oracle PROD region, and the other references the Oracle UAT region. The Resource name attributes vary really only slightly, one called myoracle, the other called myoracledev. Context Resource auth=Container description=changectrlapp name=jdbc/myoracle type=javax.sql.DataSource driverClassName=oracle.jdbc.driver.OracleDriver username=username password=password url=jdbc:oracle:thin:@servername.dom.net:1648:SVCNAME maxIdle=30 maxWait=1 maxActive=20 testOnBorrow=true timeBetweenEvictionRunsMillis=-1 minEvictableIdleTimeMillis=28800 poolPreparedStatements=true removeAbandoned=true removeAbandonedTimeout=300 logAbandoned=false/ The errors I am getting are: javax.servlet.ServletException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress This may not be much to go on. But like I said, with attributes only slightly different, the connection to UAT works. By the way, I am connecting successfully to the Oracle PROD DB through other avenues: TOAD,SQL Plus, MS Access, etc. So the DB itself is working. Both my DEV/UAT and PROD regions use the same DBCP classes. Could something have gotten corrupted for one and not the other? Any feedback is welcomed. Let me know, please, if I neglected to add anything pertinent to this. Have you been able to connect with any type of Java-based client? Perhaps the driver is convinced something is wrong when everything is fine? I suspect that this is not Tomcat or DBCP-related. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTNZ9vAAoJEBzwKT+lPKRYRkwP/0FAVLj0gNJf/BvJ2jv3lwwd rdTssFpqIQWGTrvcZnHele+ALk+7UeUo4NwI79EWZOgJVbT7TlsfJMgOaQUQ4tzQ WwMRvMP2H/zYx0U5PrcAD/eJF//gAw0oNtOYCQJ502spw0tC6rbLem8l91AaMwsF gEtTyUfgdQvpITyhWfb3fh+Dt5M2FR8AijBkY5pwTao3IGBpjT/4cTjk6ZMj6kD3 TEOVa2TTOxt4EZ18lVGTSmJVBwBs6403swGSTPtZCpj5jUcweNxNQYQF6YwUj+Vf BM7pXD11lgDh9wqMylt9/uwjq24CDSasPnnZOkxGhA1rDaUgSQXZF2aW5fX1czK2 DlzBQAdkz5PM2+Ft2yMSKGbZIXe+CCbI3x+lTOqy+7QtsPye+zMc+4CV67v+49PG wMyCCng5fAtixhvb4kQvnGOfAZ+9IPWLiRH+V5HUc4FotfKT1kaR0m/y0VdfvpIK TZJgzaAeuDvo6eM4I7AYctbXwfDL1Sdppq76WiJvof49awomEGcLPurCxGftbLPy VwYTQcfLud659Tdf2sbvwrmYorVO/VarokzFutoW3UMPRY60b1dr0Tkc6+p4ysu/ cgWjduyZ5Ml63A+UCn8N4U7XUTzRUuaFeQF/E3wA+2E8FLFALe8Xk8jeAO845WWq FZSmueBHQ/XPN8cU7J0G =G31J -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Connection pooling issue on Tomcat
On 03/28/2014 11:58 AM, Propes, Barry L wrote: Hi folks, I'm using Tomcat 6.0.29 for an app I've had in place for years. I run the Java app I have on a Windows 2003 server for my production region, but have local builds on both my desktop and laptop, both of which are Windows XP Pro. Yes, I do realize that the Tomcat version is old, but we'll be retiring the app in a few months so there's no need (at this time) to upgrade it. I use connection pooling, specifically Tomcat's DBCP class. This app has worked for years, but is suddenly encountering a strange connection error and issue to the PROD region only of Oracle 11. This just started in the last week. I'll include the contents of my context XML file and the errors that it's generating. Even stranger, my development build to the Oracle UAT region works just fine! These content.xml files are virtually the same, except one references the Oracle PROD region, and the other references the Oracle UAT region. The Resource name attributes vary really only slightly, one called myoracle, the other called myoracledev. Context Resource auth=Container description=changectrlapp name=jdbc/myoracle type=javax.sql.DataSource driverClassName=oracle.jdbc.driver.OracleDriver username=username password=password url=jdbc:oracle:thin:@servername.dom.net:1648:SVCNAME maxIdle=30 maxWait=1 maxActive=20 testOnBorrow=true timeBetweenEvictionRunsMillis=-1 minEvictableIdleTimeMillis=28800 poolPreparedStatements=true removeAbandoned=true removeAbandonedTimeout=300 logAbandoned=false/ The errors I am getting are: javax.servlet.ServletException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress For what its worth, I recently got this error which looks like it is an ORACLE issue rather than connection pool issue. When I talked to our db administrator, they were doing some sort of maintenance on oracle at exactly the same time I got the error. mas This may not be much to go on. But like I said, with attributes only slightly different, the connection to UAT works. By the way, I am connecting successfully to the Oracle PROD DB through other avenues: TOAD,SQL Plus, MS Access, etc. So the DB itself is working. Both my DEV/UAT and PROD regions use the same DBCP classes. Could something have gotten corrupted for one and not the other? Any feedback is welcomed. Let me know, please, if I neglected to add anything pertinent to this. -- Mark Shifman MD. Ph.D. Yale Center for Medical Informatics Phone (203)737-5219 mark.shif...@yale.edu - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Connection pooling issue on Tomcat
-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Friday, March 28, 2014 11:13 AM To: Tomcat Users List Subject: Re: Connection pooling issue on Tomcat -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Barry, On 3/28/14, 11:58 AM, Propes, Barry L wrote: Hi folks, I'm using Tomcat 6.0.29 for an app I've had in place for years. I run the Java app I have on a Windows 2003 server for my production region, but have local builds on both my desktop and laptop, both of which are Windows XP Pro. Yes, I do realize that the Tomcat version is old, but we'll be retiring the app in a few months so there's no need (at this time) to upgrade it. The errors I am getting are: javax.servlet.ServletException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress This may not be much to go on. But like I said, with attributes only slightly different, the connection to UAT works. By the way, I am connecting successfully to the Oracle PROD DB through other avenues: TOAD,SQL Plus, MS Access, etc. So the DB itself is working. Both my DEV/UAT and PROD regions use the same DBCP classes. Could something have gotten corrupted for one and not the other? Any feedback is welcomed. Let me know, please, if I neglected to add anything pertinent to this. Have you been able to connect with any type of Java-based client? Perhaps the driver is convinced something is wrong when everything is fine? I suspect that this is not Tomcat or DBCP-related. - -chris --- Chris, I got it solved. It was Tomcat related, but my fault. When stopping and starting the app through the manager console, the conf app xml file in question was not getting overwritten. I had to delete it and get the changes I made recreated. It then worked. Oddly, I had made changes to both my dev environments - laptop and desktop -- but I discovered it right AFTER I posted this! Ugh! Thanks! Consider this closed. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Connection pooling issue on Tomcat
-Original Message- From: Mark Shifman [mailto:mark.shif...@yale.edu] Sent: Friday, March 28, 2014 12:34 PM To: Tomcat Users List Subject: Re: Connection pooling issue on Tomcat On 03/28/2014 11:58 AM, Propes, Barry L wrote: Hi folks, I'm using Tomcat 6.0.29 for an app I've had in place for years. I run the Java app I have on a Windows 2003 server for my production region, but have local builds on both my desktop and laptop, both of which are Windows XP Pro. Yes, I do realize that the Tomcat version is old, but we'll be retiring the app in a few months so there's no need (at this time) to upgrade it. I use connection pooling, specifically Tomcat's DBCP class. This app has worked for years, but is suddenly encountering a strange connection error and issue to the PROD region only of Oracle 11. This just started in the last week. I'll include the contents of my context XML file and the errors that it's generating. Even stranger, my development build to the Oracle UAT region works just fine! These content.xml files are virtually the same, except one references the Oracle PROD region, and the other references the Oracle UAT region. The Resource name attributes vary really only slightly, one called myoracle, the other called myoracledev. Context Resource auth=Container description=changectrlapp name=jdbc/myoracle type=javax.sql.DataSource driverClassName=oracle.jdbc.driver.OracleDriver username=username password=password url=jdbc:oracle:thin:@servername.dom.net:1648:SVCNAME maxIdle=30 maxWait=1 maxActive=20 testOnBorrow=true timeBetweenEvictionRunsMillis=-1 minEvictableIdleTimeMillis=28800 poolPreparedStatements=true removeAbandoned=true removeAbandonedTimeout=300 logAbandoned=false/ The errors I am getting are: javax.servlet.ServletException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01033: ORACLE initialization or shutdown in progress java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress For what its worth, I recently got this error which looks like it is an ORACLE issue rather than connection pool issue. When I talked to our db administrator, they were doing some sort of maintenance on oracle at exactly the same time I got the error. mas This may not be much to go on. But like I said, with attributes only slightly different, the connection to UAT works. By the way, I am connecting successfully to the Oracle PROD DB through other avenues: TOAD,SQL Plus, MS Access, etc. So the DB itself is working. Both my DEV/UAT and PROD regions use the same DBCP classes. Could something have gotten corrupted for one and not the other? Any feedback is welcomed. Let me know, please, if I neglected to add anything pertinent to this. -- Mark Shifman MD. Ph.D. Yale Center for Medical Informatics Phone (203)737-5219 mark.shif...@yale.edu = Thanks, Mark, I got it figured out. I had changed it a couple of weeks back to point to our COB region, which is up only during a specified time, and didn't realize I hadn't changed it back. But I also thought that stopping and starting the app in the manager console would overwrite the app xml file in the conf folder, and that didn't happen. I checked it there and discovered the problem. Thanks, though. Barry - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Connection pooling issue on Tomcat
On Fri, Mar 28, 2014 at 12:31 PM, Propes, Barry L barry.l.pro...@citi.comwrote: -Original Message- From: Mark Shifman [mailto:mark.shif...@yale.edu] Sent: Friday, March 28, 2014 12:34 PM To: Tomcat Users List Subject: Re: Connection pooling issue on Tomcat = Thanks, Mark, I got it figured out. I had changed it a couple of weeks back to point to our COB region, which is up only during a specified time, and didn't realize I hadn't changed it back. But I also thought that stopping and starting the app in the manager console would overwrite the app xml file in the conf folder, and that didn't happen. I checked it there and discovered the problem. I know this thread is closed, but I just wanted to ask you a follow up question Barry. You said that the app xml in the conf folder wasn't being overwritten. Are you placing that xml file there manually? Or did you set copyXML in your Host element to true to make it copy that file there? Because by default, copyXML is set to false, that attribute is not even named in the default Tomcat server.xml if you are using the zip version. And per the docs, that app xml file will be used in place of the one in your web app, even if the web app one is newer. [quote] Set to true if you want a context XML descriptor embedded inside the application (located at /META-INF/context.xml) to be copied to xmlBase when the application is deployed. On subsequent starts, the copied context XML descriptor will be used in preference to any context XML descriptor embedded inside the application *** even if the descriptor embedded inside the application is more recent ***. The flag's value defaults to false. Note if *deployXML* is false, this attribute will have no effect. [/quote] If you place the contents of your app xml file in a file called context.xml in /META-INF/, you won't have to worry about updating the one in the conf folder. I only place xml files in conf when I want something static, like mapping an output directory for GIS applications to write images.
