Re: JNDI connection pool in Tomcat 10.1

On 04/09/2024 21:34, charliedidon...@gmail.com wrote: Hello Tomcat 10.1, Java 17, MySQL Connector 9.0 Not sure if this is a Tomcat Config issue or Spring MVC 6 issue I am converting from Spring MVC 4 to 6 and have the following set up in Tomcat 10.1 Context.xml url="jdbc:m

RE: JNDI connection pool in Tomcat 10.1

Hello Tomcat 10.1, Java 17, MySQL Connector 9.0 Not sure if this is a Tomcat Config issue or Spring MVC 6 issue I am converting from Spring MVC 4 to 6 and have the following set up in Tomcat 10.1 Context.xml Server.xml ResourceLink name="j

Re: JNDI resourse name value

Rob, On 11/7/22 16:40, Rob Sargent wrote: On 11/7/22 14:26, Christopher Schultz wrote: Rob, On 11/7/22 14:09, Rob Sargent wrote: Are there any semantics to Resourse name attributes? Or is no more or less valid than As far as Tomcat is concerned, it's basically the Wild West. Some oth

Re: JNDI resourse name value

On 11/7/22 14:26, Christopher Schultz wrote: Rob, On 11/7/22 14:09, Rob Sargent wrote: Are there any semantics to Resourse name attributes? Or is no more or less valid than As far as Tomcat is concerned, it's basically the Wild West. Some other application servers (usually the "enterpr

Re: JNDI resourse name value

Rob, On 11/7/22 14:09, Rob Sargent wrote: Are there any semantics to Resourse name attributes? Or is no more or less valid than As far as Tomcat is concerned, it's basically the Wild West. Some other application servers (usually the "enterprise" ones) are super strict about where things

RE: JNDI ldaps Problem with SSO

Hi Christopher Enclosed is the stacktrace of the tomcat (localhost) 03-Mar-2021 15:57:15.221 SEVERE [http-nio-8080-exec-10] org.apache.catalina.realm.JNDIRealm.authenticate Exception performing authentication javax.naming.NamingException: [LDAP: error code 1 - 04DC: LdapErr: DSID-0C0907E

RE: JNDI ldaps Problem with SSO

> -Original Message- > From: Christopher Schultz > Sent: Donnerstag, 20. Mai 2021 18:37 > To: users@tomcat.apache.org > Subject: Re: JNDI ldaps Problem with SSO > > Susan, > > On 5/18/21 16:58, susan.w...@swisscom.com wrote: > > When we are using plain ldap 3268, a

Re: JNDI ldaps Problem with SSO

ce and not just the message? -chris -----Original Message- From: Christopher Schultz Sent: Dienstag, 18. Mai 2021 18:02 To: users@tomcat.apache.org Subject: Re: JNDI ldaps Problem with SSO Susan, On 5/18/21 09:43, susan.w...@swisscom.com wrote: Hi all apache-tomcat-8.0.36 java ve

RE: JNDI ldaps Problem with SSO

: # extended LDIF # # LDAPv3 # base with scope subtree # filter: (objectclass=*) # requesting: ALL # Organization, Schema, Configuration, bcintra.ch We think, ssl-handshake is fine but bind is failing. Why? Thank you Susan > -Original Message- > From: Christopher Schultz > Sent: Die

Re: JNDI ldaps Problem with SSO

Susan, On 5/18/21 09:43, susan.w...@swisscom.com wrote: Hi all apache-tomcat-8.0.36 java version "1.8.0_281" Java(TM) SE Runtime Environment (build 1.8.0_281-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.281-b09, mixed mode) We are having a problem with our Single sign On config. When usin

Re: JNDI ldaps Problem with SSO

there maybe another debug Option for the ldap? > > > > Thank you > > > > Susan > > > > > > > > > -Original Message- > > > From: Brian Wolfe > > > Sent: Donnerstag, 25. Februar 2021 17:00 > > > To: Tomcat Users Lis

Re: JNDI ldaps Problem with SSO

aps with port 3269 fails > > Is there maybe another debug Option for the ldap? > > Thank you > > Susan > > > > > -Original Message- > > From: Brian Wolfe > > Sent: Donnerstag, 25. Februar 2021 17:00 > > To: Tomcat Users List > > Subje

RE: JNDI ldaps Problem with SSO

. So the search itself seems to be fine. Only ldaps with port 3269 fails Is there maybe another debug Option for the ldap? Thank you Susan > -Original Message- > From: Brian Wolfe > Sent: Donnerstag, 25. Februar 2021 17:00 > To: Tomcat Users List > Subject: Re

Re: JNDI ldaps Problem with SSO

m. > Could it be, that a ssl config is necessary too? > > Thank you > > Susan > > > -Original Message- > > From: Bill Stewart > > Sent: Donnerstag, 25. Februar 2021 16:04 > > To: Tomcat Users List > > Subject: Re: JNDI ldaps Problem wit

RE: JNDI ldaps Problem with SSO

ginal Message- > From: Bill Stewart > Sent: Donnerstag, 25. Februar 2021 16:04 > To: Tomcat Users List > Subject: Re: JNDI ldaps Problem with SSO > > On Thu, Feb 25, 2021 at 2:31 AM wrote: > > We are having a problem with our Single sign On config. > > When using ldap -

Re: JNDI ldaps Problem with SSO

On Thu, Feb 25, 2021 at 2:31 AM wrote: We are having a problem with our Single sign On config. > When using ldap - all works well. > > When switiching to ldaps , the User loses to connection all together > (Server not reachable) > > server.xml > > Good: > connection

Re: JNDI match of LDAP hashed passwords fail against cleartext

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 4/21/20 10:31, Mark H. Wood wrote: > On Mon, Apr 20, 2020 at 12:17:54PM -0400, Christopher Schultz > wrote: >> Hmm. The LDAP stuff I think wasn't me, but I understand it a >> little bit. Brian, is there a standard I can read for this? I'm >

Re: JNDI match of LDAP hashed passwords fail against cleartext

On Mon, Apr 20, 2020 at 12:17:54PM -0400, Christopher Schultz wrote: > Hmm. The LDAP stuff I think wasn't me, but I understand it a little > bit. Brian, is there a standard I can read for this? I'm familiar with > LDAP servers storing credentials with "{sha}" prefixes but not others. > Honestly, fo

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 19/04/2020 06:59, Brian Burch wrote: > On 17/4/20 10:28 pm, Mark Thomas wrote: >> On 16/04/2020 09:56, Brian Burch wrote: >>> On 15/4/20 6:24 am, Mark Thomas wrote: >> >> >> I'd expect you to see an error message if your server.xml isn't quite right although that is what this looks li

Re: JNDI match of LDAP hashed passwords fail against cleartext

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Brian, On 4/17/20 08:28, Mark Thomas wrote: > On 16/04/2020 09:56, Brian Burch wrote: >> On 15/4/20 6:24 am, Mark Thomas wrote: > > > >>> I'd expect you to see an error message if your server.xml isn't >>> quite right although that is what this loo

Re: JNDI match of LDAP hashed passwords fail against cleartext

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Brian, On 4/20/20 12:17, Christopher Schultz wrote: > Brian, > > On 4/17/20 08:28, Mark Thomas wrote: >> On 16/04/2020 09:56, Brian Burch wrote: >>> On 15/4/20 6:24 am, Mark Thomas wrote: > >> > I'd expect you to see an error message if your s

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 17/4/20 10:28 pm, Mark Thomas wrote: On 16/04/2020 09:56, Brian Burch wrote: On 15/4/20 6:24 am, Mark Thomas wrote: I'd expect you to see an error message if your server.xml isn't quite right although that is what this looks like. There was no error message. I think my xml was syntax-f

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 16/04/2020 09:56, Brian Burch wrote: > On 15/4/20 6:24 am, Mark Thomas wrote: >> I'd expect you to see an error message if your server.xml isn't quite >> right although that is what this looks like. > > There was no error message. I think my xml was syntax-free, but it did > not reflect my i

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 15/4/20 6:24 am, Mark Thomas wrote: On 14/04/2020 07:34, Brian Burch wrote: I searched for usages of MessageDigestCredentialHandler.setAlgorithm, but only found it used once - within TestJNDIRealm. I did not find any occurrences within tomcat mainline code, but would not be surprised if th

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 14/4/20 8:05 pm, Brian Burch wrote: On 14/4/20 6:53 pm, logo wrote: Brian, see down below Am 2020-04-14 08:34, schrieb Brian Burch: My initial code inspection makes me strongly suspect tomcat does not initialise JNDIRealm and a nested CredentialHandler properly during startup. Howeve

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 14/04/2020 07:34, Brian Burch wrote: > I searched for usages of MessageDigestCredentialHandler.setAlgorithm, > but only found it used once - within TestJNDIRealm. I did not find any > occurrences within tomcat mainline code, but would not be surprised if > the algorithm was intended to be set

Re: JNDI match of LDAP hashed passwords fail against cleartext

On 14/4/20 6:53 pm, logo wrote: Brian, see down below Am 2020-04-14 08:34, schrieb Brian Burch: I thought it would be helpful to start this issue on the users list because it will contain a lot of helpful search terms. I am upgrading a stable production tomcat 7.0.52 system to tomcat 8.5.

Re: JNDI match of LDAP hashed passwords fail against cleartext

Brian, see down below Am 2020-04-14 08:34, schrieb Brian Burch: I thought it would be helpful to start this issue on the users list because it will contain a lot of helpful search terms. I am upgrading a stable production tomcat 7.0.52 system to tomcat 8.5.54. Both were built from source c

Re: JNDI look up with tomcat 8.5.6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ajay, On 11/3/16 12:41 AM, Ajay Bilotia wrote: > *Below code is for JNDI look up which is working fine in tomcat 7 > and 8 .* > > InitialContext initContext = new InitialContext(); DataSource ds = > (DataSource)initContext.lookup(initContext.getNa

Re: JNDI lookup failure with tomcat 8.5.6

Hi, Is there a way to add our application's contextclassloader to the list of tomcat's " Bindings class loader list " so that "ContextBindings.isClassLoaderBound()" returns true? Please correct me if i'm wrong in understanding the problem!! Thanks, Padma On Fri, Nov 4, 2016 at 4:16 PM, Mark Th

Re: JNDI lookup failure with tomcat 8.5.6

Hi Mark, Thanks for your quick reply . Sorry to bug you , I didn't get you. Will you please explain a bit on how to make the custom loader as parent (any configuration changes )? Thanks & Regards, Padma On Fri, Nov 4, 2016 at 4:16 PM, Mark Thomas wrote: > On 04/11/2016 10:45, padma T wrote:

Re: JNDI lookup failure with tomcat 8.5.6

On 04/11/2016 10:45, padma T wrote: > Hi, > > Getting ,JNDI lookup failed exception while starting tomcat 8. > > While debugging it was found that getInitialContext() > of org.apache.naming.java.javaURLContextFactory class returns NamingContext > context instead of the custom ContextClassLoader s

Re: JNDI look up with tomcat 8.5.6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ajay, On 11/2/16 1:29 AM, Ajay Bilotia wrote: > We are upgrading the tomcat from apache-tomcat-7.0.59 to > apache-tomcat-8.5.6. We are setting the custom class loader as we > required for our application and JNDI look up is not working with > tomca

Re: JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis

Hi Mark, On Wed, May 25, 2016 at 4:56 AM, Mark Thomas wrote: > On 24/05/2016 23:23, Woonsan Ko wrote: >> Hi, >> >> Since 8.0, I think we should use maxTotal instead of maxActive and >> maxWaitMillis instead of maxWait. [1,2] >> However, if I use maxTotal for instance, the jmx console doesn't show

Re: JNDI DataSource in Tomcat 8: maxTotal and maxWaitMillis

On 24/05/2016 23:23, Woonsan Ko wrote: > Hi, > > Since 8.0, I think we should use maxTotal instead of maxActive and > maxWaitMillis instead of maxWait. [1,2] > However, if I use maxTotal for instance, the jmx console doesn't show > it but show the old maxActive value (100, probably the default > v

Re: JNDI Datasource override default settings for ALL resources in a central XML ?

Hello Mark, Thanks for the quick reply, we will definitely try this ! Aurelien

Re: JNDI Datasource override default settings for ALL resources in a central XML ?

On 16/09/2015 09:59, Aurelien Pernoud wrote: > Hello, > > In our Tomcat (7 or 8 doesn't matter) servers we always override many > parameters among datasources, in each application context file (we deploy > one context file / application under conf/Catalina/localhost). > > Every time I have to set

Re: JNDI realm Global Catalog question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Neil, On 4/29/15 12:01 PM, Lazarow, Neil wrote: > -Original Message- From: Felix Schumacher > [mailto:felix.schumac...@internetallee.de] Sent: Tuesday, April 28, > 2015 10:18 AM To: Tomcat Users List Subject: Re: JNDI realm Global

RE: JNDI realm Global Catalog question

-Original Message- From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] Sent: Tuesday, April 28, 2015 10:18 AM To: Tomcat Users List Subject: Re: JNDI realm Global Catalog question Am 28. April 2015 17:11:55 MESZ, schrieb Christopher Schultz : >-BEGIN PGP SIG

RE: JNDI realm Global Catalog question

-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, April 28, 2015 10:12 AM To: Tomcat Users List Subject: Re: JNDI realm Global Catalog question -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Neil, On 4/28/15 9:48 AM, Lazarow, Neil wrote

Re: JNDI realm Global Catalog question

Am 28. April 2015 17:11:55 MESZ, schrieb Christopher Schultz : >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >Neil, > >On 4/28/15 9:48 AM, Lazarow, Neil wrote: >> I have multiple domain controllers, all of which are set to >> function as global catalog servers. >> >> Is it possible to put

Re: JNDI realm Global Catalog question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Neil, On 4/28/15 9:48 AM, Lazarow, Neil wrote: > I have multiple domain controllers, all of which are set to > function as global catalog servers. > > Is it possible to put multiple alternateURL entires into your > JNDIRealm confiugration (see exam

Re: JNDI initialization since Tomcat 8.0.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 4/16/14, 10:44 AM, David Landis wrote: > On Sun, Apr 13, 2014 at 4:02 PM, Konstantin Kolinko > wrote: >> >> >> By the way, there exists an Apache project implementing the JPA >> specification, http://openjpa.apache.org/ > > > It does

Re: JNDI initialization since Tomcat 8.0.1

On Sun, Apr 13, 2014 at 4:02 PM, Konstantin Kolinko wrote: > > > By the way, there exists an Apache project implementing the JPA > specification, > http://openjpa.apache.org/ It does not really work with Tomcat though does it? See this issue: https://issues.apache.org/jira/browse/OPENJPA-1590 or

Re: JNDI initialization since Tomcat 8.0.1

There is already a hibernate issue on this bug (https://hibernate.atlassian.net/browse/HHH-8818). Regards, Christian - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomc

Re: JNDI initialization since Tomcat 8.0.1

On 13.04.2014 22:02, Konstantin Kolinko wrote: > I do not know, what version of hibernate you are using, but if I look > at 4.3.x sources [1], the following method mentioned in your > stacktrace changes TCCL and thus breaks JNDI: > > org.hibernate.boot.registry. > classloading.internal.ClassLoader

Re: JNDI initialization since Tomcat 8.0.1

2014-04-13 19:32 GMT+04:00 Christian : >> Is hibernate initialized via a in web.xml, or where? > > I don't know exactly how it is initialized. I use spring annotation > configuration with a > javax.servlet.ServletContainerInitializer but I don't know, if hibernate gets > loaded immediately. > L

Re: JNDI initialization since Tomcat 8.0.1

> Is hibernate initialized via a in web.xml, or where? I don't know exactly how it is initialized. I use spring annotation configuration with a javax.servlet.ServletContainerInitializer but I don't know, if hibernate gets loaded immediately. Looking at the call stack, it seems that it gets ini

Re: JNDI initialization since Tomcat 8.0.1

2014-04-13 15:10 GMT+04:00 Christian : > Hi, > > I'm experimenting with java 8, spring data JPA, hibernate and tomcat 8. > Spring Data JPA initializes hibernate on deployment. > > On tomcat 8.0.0-RC10 everything is fine. Using Tomcat 8.0.1 or newer, an > exception is thrown when hibernate tries to

Re: JNDI Realm and GSSAPI problems with TC 7

On 05/12/2013 14:48, Hendrik Dev wrote: > Hi, > > i have a few questions about the JNDIRealm, GSSAPI (Kerberos 5 mech) > authentication and the SPNEGO Authenticator Valve in TC 7.0.47: > > Preface: In the docs SPNEGO Authenticator Valve/JNDIRealm is called > "30) Windows Authentication" but i gue

Re: JNDI property roleSearchAsUser not working as expected

ect to the directory. Regards Felix ____ De : Felix Schumacher [felix.schumac...@internetallee.de] Envoyé : jeudi 14 mars 2013 12:03 À : Tomcat Users List Objet : Re: JNDI property roleSearchAsUser not working as expected Am 13.03.2013 21:46, schrieb Eugène A

Re: JNDI property roleSearchAsUser not working as expected

Am 13.03.2013 21:46, schrieb Eugène Adell: Hello I am running the following : java version "1.6.0_25" Java(TM) SE Runtime Environment (build 1.6.0_25-b06) Java HotSpot(TM) Client VM (build 20.0-b11, mixed mode, sharing) Tomcat 7.0.37 CentOS release 6.3 with this REALM configuration i

Re: JNDI Feedback

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alan, On 1/29/13 12:24 PM, alan.farr...@renfrewshire.gov.uk wrote: > Thanks for feedback. If a SQLException can be returned then I > could probably use that in the Java application to determine if an > exception occurred. Can you provide any guida

Re: JNDI Feedback

ot;javax.sql.DataSource" > url="jdbc:sqlserver://egovsql2005\p40010:1433;databaseName=AuditDEV" > username="username" /> This doesn't have a factory, so it'll use the default DBCP connection pool. See Chris' email for a link to the docs for DBCP.

Re: JNDI Feedback

Street Paisley PA1 1HY 0141 618 7961 alan.farr...@renfrewshire.gov.uk www.renfrewshire.gov.uk From: Christopher Schultz To: Tomcat Users List Date: 29/01/2013 17:11 Subject:Re: JNDI Feedback -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alan, On 1/29/13 11:54 AM

Re: JNDI Feedback

PA1 1HY 0141 618 7961 alan.farr...@renfrewshire.gov.uk www.renfrewshire.gov.uk From: Daniel Mikusa To: "Tomcat Users List" Date: 29/01/2013 17:06 Subject: Re: JNDI Feedback On Jan 29, 2013, at 11:54 AM, alan.farr...@renfrewshire.gov.uk wrote: > Hello, >

Re: JNDI Feedback

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alan, On 1/29/13 11:54 AM, alan.farr...@renfrewshire.gov.uk wrote: > Running Tomcat 7.0.29 on Windows XP Professional Service Pack 3 Ready for a Microsoft upgrade cycle? The clock is ticking... > I have been handed a project developed by a former

Re: JNDI Feedback

On Jan 29, 2013, at 11:54 AM, alan.farr...@renfrewshire.gov.uk wrote: > Hello, > > Running Tomcat 7.0.29 on Windows XP Professional Service Pack 3 > > I have been handed a project developed by a former colleague and I am > still learning Java and Tomcat. > > The project has 4 JNDI's set up, 2

RE: JNDI setup oracle 11 g

Oh ok, very good! -Original Message- From: tsidhu [mailto:tsidh...@yahoo.com] Sent: Thursday, January 10, 2013 3:20 PM To: users@tomcat.apache.org Subject: Re: JNDI setup oracle 11 g Thank you all for the help. I manged to resolve it. It was actually "human error" :(. I was

Re: JNDI setup oracle 11 g

ain for help.  Tony From: "Propes, Barry L [via Tomcat]" To: tsidhu Sent: Thursday, January 10, 2013 3:36 PM Subject: RE: JNDI setup oracle 11 g And FWIW, Tony, I'm using this oracle jar. ojdbc6.jar -Original Message- From: Marco de Booij [mailto:[hidden

RE: JNDI setup oracle 11 g

And FWIW, Tony, I'm using this oracle jar. ojdbc6.jar -Original Message- From: Marco de Booij [mailto:marco.develo...@debooy.eu] Sent: Thursday, January 10, 2013 2:24 PM To: users@tomcat.apache.org Subject: Re: JNDI setup oracle 11 g If you get an error when you provide a wrong use

RE: JNDI setup oracle 11 g

I was going to ask this, too. Which oracle jar are you using for this? -Original Message- From: Marco de Booij [mailto:marco.develo...@debooy.eu] Sent: Thursday, January 10, 2013 2:24 PM To: users@tomcat.apache.org Subject: Re: JNDI setup oracle 11 g If you get an error when you

Re: JNDI setup oracle 11 g

t]" To: tsidhu Sent: Thursday, January 10, 2013 2:32 PM Subject: RE: JNDI setup oracle 11 g Hmmm. I didn't know that, I guess. Well, I wonder if that long string requires some kind of escape character to be inserted in it? -Original Message- From: tsidhu [mailto:[hidd

Re: JNDI setup oracle 11 g

to the db, that oracle does not like when used via JNDI but works fine when used via JDBC.  Tony From: "Propes, Barry L [via Tomcat]" To: tsidhu Sent: Thursday, January 10, 2013 2:32 PM Subject: RE: JNDI setup oracle 11 g Hmmm. I didn't kno

RE: JNDI setup oracle 11 g

Hmmm. I didn't know that, I guess. Well, I wonder if that long string requires some kind of escape character to be inserted in it? -Original Message- From: tsidhu [mailto:tsidh...@yahoo.com] Sent: Thursday, January 10, 2013 1:22 PM To: users@tomcat.apache.org Subject: Re: JNDI

Re: JNDI setup oracle 11 g

s the JDBC/Oracle driver.  I can work around the issue by not using JNDI in the web app, however I am not then able to use pooling I guess.  Tony From: "Propes, Barry L [via Tomcat]" To: tsidhu Sent: Thursday, January 10, 2013 1:09 PM Subject: RE:

RE: JNDI setup oracle 11 g

I might add, Tony, one other thing I noticed in my JNDI config. I'd removed the validationQuery attribute. It might have been regarding this, but I'd writtten a comment right below it that per Konstantin, there was a memory leak regarding the Eviction Timer. Try removing that attribute (valida

RE: JNDI setup oracle 11 g

Tony, I have a similar standalone Java app that hits Oracle 11g. At your line with the DBURL, I have something much more concise. Where you have public static final String DBURL = "jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = abc-def-scan.corp.xyz.com)(PORT = 1521)) (CONN

RE: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27

tober 27, 2012 5:24 PM To: Tomcat Users List Subject: Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27 Hello, I am mot familiar with Hibernate or Liferay, but I ran into what appear to be similar. Look onto the thread titled " JDBCRealm conection timeout failure on getPasswor

RE: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27

tion. Bob -Original Message- From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Sent: Saturday, October 27, 2012 3:28 PM To: Tomcat Users List Subject: Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27 2012/10/28 Bob Dietrich : > Greetings, > I've researched this pro

Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27

Hello, I am mot familiar with Hibernate or Liferay, but I ran into what appear to be similar. Look onto the thread titled " JDBCRealm conection timeout failure on getPassword" in thus list. It may help. Aladin On Oct 27, 2012, at 6:28 PM, Konstantin Kolinko wrote: > 2012/10/28 Bob Dietrich :

Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27

2012/10/28 Bob Dietrich : > Greetings, > I've researched this problem for several days, but I must be doing something > wrong. I'm trying to upgrade from Tomcat 7.0.23 to 7.0.27 (actually running > Liferay). I'm getting the following exception when trying to access a > datasource via Hibernate: > >

Re: JNDI Access in Lifecycle Listener

Hey, thanks for the reply. I found a solution. The issue was, that i load my spring xml during the INIT lifecycle event. In this state the jndi context isn't available. I moved my code to the START event and it works as expected. Regards Sascha 2012/2/14 chris derham : >> >> i load a spring xml

Re: JNDI Access in Lifecycle Listener

> > i load a spring xml with my own lifecycle listener. Which works pretty > well actually. > In my spring xml i try to get a datasource from the JNDI context. I > put the definition in the server.xml under . > My lifecycle listener is loaded after the GlobalResourcesLifecycleListener > > During th

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

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

Re: JNDI, resource and LDAP Trouble

> > I have tried this before - with little success. The code does not through > any exception now - but the DirContext object (ctx) is null and by that > unusable: > >DirContext ctx = (DirContext) > newCtx.lookup("java:comp/env/blah"); >if (ctx != nul

Re: JNDI, resource and LDAP Trouble

Thanks Chris, I have tried this before - with little success. The code does not through any exception now - but the DirContext object (ctx) is null and by that unusable: DirContext ctx = (DirContext) newCtx.lookup("java:comp/env/blah"); if (ctx !=

Re: JNDI, resource and LDAP Trouble

> But when I try to access my resource with the following code: > >Context newCtx = null; >try { >newCtx = new InitialContext(); >} catch (NamingException e) { >// TODO Auto-generated catch block >

  1   2   3   4   >