Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAGrg8DXZy=Up7bVy9WAWYoYcKoW=ug-3EM-+FsHrCWphOCkedg@mail.gmail.com>
References: 
 <CAGrg8DXZy=Up7bVy9WAWYoYcKoW=ug-3EM-+FsHrCWphOCkedg@mail.gmail.com>
Date: Wed, 3 Sep 2014 09:39:10 -0600
Message-ID: 
 <CAAjH2Us9xxYSq_eN=jeJeDhc0H-fXjbY6abfO-cr5PWU_T3kSQ@mail.gmail.com>
Subject: Re: Global JNDI resources lookup behavior difference between version
 6.0.39 and 6.0.41/7.0.55
From: Filip Hanik <filip@hanik.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a11339d2292cf7505022b091d

--001a11339d2292cf7505022b091d
Content-Type: text/plain; charset=UTF-8

can you post your configuration file. that will be the only way we can help
you fix it, as I doubt tomcat will go back to pre 6.0.41 days :)

Filip


On Wed, Sep 3, 2014 at 9:36 AM, Robert Anderson <ranomail@gmail.com> wrote:

> Hi,
>
>
> In a privileged context, a have the following jsp to test a global jndi
> resource:
>
> <%@ page session="false" import="java.util.*,java.sql.*,javax.naming.*,
> javax.sql.*,org.apache.commons.dbcp.*" contentType="text/html" %>
> <%!
>
> protected void doLookup(JspWriter out) throws ServletException, IOException
> {
>  Context ctx;
>  try {
>   ctx = new InitialContext();
>   Object o = ctx.lookup("java:jdbc/cacheapp");
>   out.println(o);
>
>
>  } catch (NamingException e) {
>   out.println(e.getMessage());
>  } catch (Exception e) {
>  }
>  }
>
> %>
>
> <html>
> <head>
>   <title>Test JNDI</title>
> </head>
> <body>
>
> <h1>Teste JNDI</h1>
> <hr/>
> <%
> doLookup(out);
> %>
> <hr/>
>
> </body>
> </html>
>
>
> Versions earlier than 6.0.41:
>
> org.apache.tomcat.jdbc.pool.DataSource@29050dfd
> {ConnectionPool[defaultAutoCommit=null;
> defaultReadOnly=null; defaultTransactionIsolation=-1; defaultCatalog=null;
> driverClassName=com.intersys.jdbc.CacheDriver; maxActive=10; maxIdle=2;
> minIdle=1; initialSize=10; maxWait=10000; testOnBorrow=true;
> testOnReturn=false; timeBetweenEvictionRunsMillis=5000;
> numTestsPerEvictionRun=0; minEvictableIdleTimeMillis=60000;
> testWhileIdle=false; testOnConnect=false; password=********;
> url=jdbc:Cache://localhost:1972/USER; username=tomcat;
> validationQuery=select 1 from dual; validationQueryTimeout=-1;
> validatorClassName=null; validationInterval=0;
> accessToUnderlyingConnectionAllowed=true; removeAbandoned=true;
> removeAbandonedTimeout=300; logAbandoned=false; connectionProperties=null;
> initSQL=null; jdbcInterceptors=null; jmxEnabled=true; fairQueue=true;
> useEquals=true; abandonWhenPercentageFull=0; maxAge=0; useLock=false;
> dataSource=null; dataSourceJNDI=null; suspectTimeout=0;
> alternateUsernameAllowed=true; commitOnReturn=false;
> rollbackOnReturn=false; useDisposableConnectionFacade=true;
> logValidationErrors=false; propagateInterruptState=false;
> ignoreExceptionOnPreLoad=false; }
>
>
> 6.0.41 and 7.0.55:
>
> Name jdbc is not bound in this Context
>
> That is a bug?
>
>
> We are having a issue in psi-probe because this behavior change (
> https://code.google.com/p/psi-probe/issues/detail?id=411).
>
>
> Thanks in advance.
>

--001a11339d2292cf7505022b091d--