I know it's allowed in TC 4. I was saying not allowed in 5, or after 5.0 or 5.5.
-----Original Message----- From: Aparna1 V [mailto:aparna...@tcs.com] Sent: Thursday, October 21, 2010 10:55 AM To: Tomcat Users List Subject: RE: javax.naming.NamingException: Cannot create resource instance Hi Barry, That is allowed in TC 4. From: "Propes, Barry L " <barry.l.pro...@citi.com> To: Tomcat Users List <users@tomcat.apache.org> Date: 10/21/2010 09:21 PM Subject: RE: javax.naming.NamingException: Cannot create resource instance Not sure, but I don't think you need all those attributes separated like that. In TC4 you had to do that -- but not so after 5.0, or at least 5.5 And on top of that, you've got two ResourceLink name attributes pointing to the same class with different names. Not sure, but is that allowed? -----Original Message----- From: Aparna1 V [mailto:aparna...@tcs.com] Sent: Thursday, October 21, 2010 10:25 AM To: users@tomcat.apache.org Subject: javax.naming.NamingException: Cannot create resource instance <ResourceLink name="jdbc/sql_2005" global="jdbc/sql_2005" type="com.microsoft.jdbcx.sqlserver.SQLServerDataSource"/> <ResourceLink name="jdbc/global05" global="jdbc/global05" type="com.microsoft.pool.PoolDataSource"/> <ResourceLink name="jdbc/sql_05" global="jdbc/sql_05" type="com.microsoft.jdbcx.sqlserver.SQLServerDataSource"/> <ResourceLink name="jdbc/fbrae05" global="jdbc/fbrae05" type="com.microsoft.pool.PoolDataSource"/> </Context> </Host> I am getting the following error: PoolName = 2005pool PoolJndiRef = jdbc/global05 Init Param: jdbc/global05 javax.naming.NamingException: Cannot create resource instance at Please advise as to what could be wrong since im using the server.xml that i was using with the tomcat 4. Thanks, Aparna =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
