> Curtis Garman wrote:
>
> Actually that is somewhat helpful because I've noticed others in the
> community are doing the same thing...I could easily enough convert the
> before mentioned portlets to spring...however spring development
> hasn't quite been sanctioned here yet. What you just said will be
> helpful in lobbying for it :)
>
>
> Glad to help ;)
>
> One reason why I am interested in using jndi over an internal pool is
> because we use lamba probe to help monitor things and it provides a
> nice web interface to be able to view jndi connection pools and how
> many open connections there are for each. I really don't want to lose
> that if possible.
>
>
> You can take a look at jmxContext.xml in uPortal to see an example of using
> Spring to easily expose things such as local DataSource pools via JMX. Not
> sure if lamba prob can talk JMX but uPortal exposes a whole bunch of data
> that way.
>
> Another thing that makes the jndi thing problematic is that related to
> another thread I started too...I set up a portlet overlay to apply all
> customizations to our portlets...but it seemes to loose all
> context.xml files from the META-INF directory...which obviously hurts
> when using this file to link to or provide credentials to your
> datasource.
>
>
> Does the default overlay configuration include any <excluded> paths? That
> would be my first guess in diagnosing that. Perhaps add an explicit include
> in the overlay config?
>
> Curtis
>
>
> On Fri, Oct 16, 2009 at 1:51 PM, Eric Dalquist
> <
[hidden email]> wrote:
>
>
> This isn't very helpful for your current problem but we haven't used JNDI
> managed DataSources in uPortal or our portlets since upgrading to 3.0. They
> always seem to have some sort of issue and a locally declared DBCP
> DataSource in the Spring app context seems to work much better.
>
> -Eric
>
> Curtis Garman wrote:
>
> Since the connection pool is only used by a single portlet and there
> is no need for any other webapp to see it, I placed my Resource in the
> the context.xml of my application (portlet)...I had tried placing my
> driver in the shared/lib too but that didn't help.
>
> On Fri, Oct 16, 2009 at 1:06 PM, Susan Bramhall <
[hidden email]>
> wrote:
>
>
> Are you putting the jndi information in the server context.xml or in the
> applicationContext.xml? It has to be in the server context to allow all the
> portlets to share the connections. And the jdbc library has to be shared as
> well.
> Susan
>
> Curtis Garman wrote:
>
> Does anyone have experience using jndi database resources for portlets
> that deploy in uportal 3.1.1 on tomcat 6. I've got some portlets we
> are running via jndi connection pooling in our uportal 2.6.1
> environment on tomcat 5.5.25 and while they work great for 2.6.1, I
> can't get the portlets to run on 3.1.1 unless I hard-code the
> connection information into the portlets. The portlets are not
> spring-based at this point. I keep getting the following exception
>
> javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
>
> My context.xml configuration is as follows
>
> <Resource name="jdbc/cancellation" auth="Container"
> type="javax.sql.DataSource"
> username="user" password="password"
> driverClassName="net.sourceforge.jtds.jdbc.Driver"
> url="jdbc:jtds:sqlserver://server:1433;databaseName=database"
> maxActive="10" maxIdle="5" maxWait="1000"
> poolPreparedStatements="true"
> removeAbandoned="true"
> removeAbandonedTimeout="300"
> logAbandoned="true"
> />
>
> I usually do not use the web.xml resource-ref...it seems to work without
> it...
>
> <resource-ref>
> <description>DB Connection</description>
> <res-ref-name>jdbc/cancellation</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> ...and it actually starts throwing a different error when I include it
>
> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC
> driver of class '' for connect URL 'null'
>
> I tried moving my context.xml to conf/Catalina/localhost and changing
> the name of the file to appname.xml and this gave me yet another error
>
> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC
> driver class 'net.sourceforge.jtds.jdbc.Driver'
>
> Does anyone have any ideas?
>
>
>
> --
>
> Susan Bramhall (
[hidden email])
> Senior Developer, Infrastructure Systems and Architecture (formerly T&P)
> Yale University Information Technology Services (ITS)
> 25 Science Park, 150 Munson St, New Haven, CT 06520
> Phone: 203 432 6697
>
> --
>
> You are currently subscribed to
[hidden email] as:
>
[hidden email]
> To unsubscribe, change settings or access archives, see
>
http://www.ja-sig.org/wiki/display/JSG/uportal-user>
>
>
>
>
>
smime.p7s (4K) 