Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/8/2011 5:51 PM, Anjib Mulepati wrote: > > when i click on java:/comp it gave error > > Error: Cannot create resource instance > > javax.naming.NamingException: Cannot create resource Then don't click on that. Click on something else

RE: JNDI configuration with 6.0.29

// Allocate and use a connection from the pool Connection connection = ds.getConnection(); -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, September 08, 2011 4:11 PM To: Tomcat Users List Subject: Re: JNDI configuration with 6.0.29 -

Re: JNDI configuration with 6.0.29

when i click on java:/comp it gave error Error: Cannot create resource instance javax.naming.NamingException: Cannot create resource instance at org.apache.naming.factory.TransactionFactory.getObjectIn

Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/8/2011 4:51 PM, Anjib Mulepati wrote: > DataSource ds = null; try { 40. Context initCtx = new > InitialContext(); 41.Context envCtx = (Context) > initCtx.lookup("java:comp/env"); 42. ds = (DataSource) > envC

Re: JNDI configuration with 6.0.29

1. Changed to "ojdbc6" same problem. 2. I didn't change any config 3. public class DynICFactory implements JNDIInterface { private DataSource dataSource; @Override public DataSource getDataSource() { return dataSource; } @Override public AgencyInterface createAg

Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 njib, On 9/8/2011 3:54 PM, Anjib Mulepati wrote: > 1. I have only one instance of jar file "classes12.jar" under lib > folder of tomcat. Wow... classes12? I remember that from back in the year 2000. Are you sure it isn't the old ZIP file they used to

Re: JNDI configuration with 6.0.29

1. I have only one instance of jar file "classes12.jar" under lib folder of tomcat. 2. There is no other error I can see in the log. But error message do change to following Sep 8, 2011 3:50:45 PM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet actio

Re: JNDI configuration with 6.0.29

>>       >> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425) >>       >> org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228) >>       org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913) >>       org.apache.strut

RE: JNDI configuration with 6.0.29

And do you have an instance of the jdbc driver in more than one place? -Original Message- From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] Sent: Thursday, September 08, 2011 2:01 PM To: Tomcat Users List Subject: Re: JNDI configuration with 6.0.29 Am Donnerstag, den

Re: JNDI configuration with 6.0.29

see a message like "NameNotFoundException: Name no_such_name is > > not bound..."? > > > > Felix > >> > >> Anjib Man Mulepati > >> > >> 409-225-6216 > >> > >> > >> > >> > >>> Subject: Re: JN

Re: JNDI configuration with 6.0.29

jib Man Mulepati 409-225-6216 Subject: Re: JNDI configuration with 6.0.29 From: felix.schumac...@internetallee.de Date: Wed, 7 Sep 2011 17:17:21 +0200 To: users@tomcat.apache.org Anjib Mulepati schrieb: Hi All, I am trying to setup JNDI mapping for oracle JDBC Connection Pooling with To

RE: JNDI configuration with 6.0.29

eNotFoundException: Name no_such_name is not bound..."? Felix > > > Anjib Man Mulepati > > 409-225-6216 > > > > > > Subject: Re: JNDI configuration with 6.0.29 > > From: felix.schumac...@internetallee.de > > Date: Wed, 7 Sep 2011 17:17:21 +02

Re: JNDI configuration with 6.0.29

Tomcat log says SEVERE: Servlet.service() for servlet jsp threw exception javax.naming.NameNotFoundException: Name dynic is not bound in this Context at org.apache.naming.NamingContext.lookup(NamingContext.java:770) at org.apache.naming.NamingContext.lookup(NamingContext.java:140) at

Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/7/2011 12:57 PM, Anjib Mulepati wrote: > >>> I did checked the XML file and it looks correct to me. >>> Following is the content: >>> >>> >> antiJARLocking="true" docBase="C:\Users\amulepati\My >>> Projects\ClientDAOTest\build\web" pa

Re: JNDI configuration with 6.0.29

i change to and still same problem. On 9/7/2011 12:31 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/7/2011 12:21 PM, Anjib Mulepati wrote: I did checked the XML file and it looks correct to me. Following is the content: It probably has no beari

Re: JNDI configuration with 6.0.29

I did checked the XML file and it looks correct to me. Following is the content: It probably has no bearing on this particular problem, but the "path" attribute is illegal here. Isn't that context path of web applciation is specified with the "path" attribute. http://tomcat.apache.org/tom

Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/7/2011 12:21 PM, Anjib Mulepati wrote: > I did checked the XML file and it looks correct to me. Following is > the content: > > antiJARLocking="true" docBase="C:\Users\amulepati\My > Projects\ClientDAOTest\build\web" path="/ClientDAOTe

Re: JNDI configuration with 6.0.29

I did checked the XML file and it looks correct to me. Following is the content: Same config work for Tomcat 7 so I am wondering is there any thing I have to different/extra in Tomcat 6 Thanks, Anjib On 9/7/2011 12:15 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Ha

Re: JNDI configuration with 6.0.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anjib, On 9/7/2011 11:22 AM, Anjib Mulepati wrote: > Yes I am positive If you have changed your META-INF/context.xml without doing an undeploy/redeploy, Tomcat may be using an older version of the deployment descriptor than you think it is. Take a l

RE: JNDI configuration with 6.0.29

Yes I am positive Anjib Man Mulepati 409-225-6216 > Subject: Re: JNDI configuration with 6.0.29 > From: felix.schumac...@internetallee.de > Date: Wed, 7 Sep 2011 17:17:21 +0200 > To: users@tomcat.apache.org > > > > Anjib Mulepati schrieb: > > >Hi

Re: JNDI configuration with 6.0.29

Anjib Mulepati schrieb: >Hi All, > >I am trying to setup JNDI mapping for oracle JDBC Connection Pooling >with Tomcat 6.0.29. This is giving me following error > >javax.naming.NameNotFoundException: Name dynic is not bound in this >From your code and configuration I would have expected jdbc/dyn

JNDI configuration with 6.0.29

Hi All, I am trying to setup JNDI mapping for oracle JDBC Connection Pooling with Tomcat 6.0.29. This is giving me following error javax.naming.NameNotFoundException: Name dynic is not bound in this Context org.apache.naming.NamingContext.lookup(NamingContext.java:770) org.apac

RE: JNDI configuration with 6.0.29

ception("Tomcat JNDI setup failed", e); } this.dataSource = ds; } Anjib Man Mulepati 409-225-6216 > Date: Wed, 7 Sep 2011 10:55:19 +0100 > From: p...@pidster.com > To: users@tomcat.apache.org > Subject: Re: JNDI configuration with 6.0.29 > > On 06/09/2

Re: JNDI configuration with 6.0.29

On 06/09/2011 21:11, Anjib Mulepati wrote: > > Hi All, > I am trying to setup JNDI mapping for oracle JDBC Connection Pooling with > Tomcat 6.0.29. This is giving me following error > javax.naming.NameNotFoundException: Name dynic is not bound in this Context > org.apache.naming.NamingConte

JNDI configuration with 6.0.29

Hi All, I am trying to setup JNDI mapping for oracle JDBC Connection Pooling with Tomcat 6.0.29. This is giving me following error javax.naming.NameNotFoundException: Name dynic is not bound in this Context org.apache.naming.NamingContext.lookup(NamingContext.java:770) org