• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context


  • Subject: Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context
  • From: René Bock <email@hidden>
  • Date: Thu, 10 Dec 2015 17:22:50 +0100

Hi,

we are deploying our Application as a servlet container.

The database connection is configured via Properties and not via JNDI .

The result is, that each  time a db-connection is opened, the following exception is thrown:


[27.10.15 11:34:40:956 CET] 0000004d SystemOut     O <ProzessCenter>[2015-10-27 11:34:40 CET] <server.startup : 2> javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context "java:".
at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1228)
at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1141)
at com.ibm.ws.naming.ipbase.NameSpace.list(NameSpace.java:1083)
at com.ibm.ws.naming.urlbase.UrlContextImpl.list(UrlContextImpl.java:1142)
at com.ibm.ws.naming.urlbase.UrlContextImpl.list(UrlContextImpl.java:1185)
at org.apache.aries.jndi.DelegateContext.list(DelegateContext.java:145)
at javax.naming.InitialContext.list(InitialContext.java:478)
at com.webobjects.jdbcadaptor.JDBCContext.setupJndiConfiguration(JDBCContext.java:310)
at com.webobjects.jdbcadaptor.JDBCContext.connect(JDBCContext.java:197)
at er.extensions.jdbc.ERXJDBCAdaptor$Context.connect(ERXJDBCAdaptor.java:404)
at com.webobjects.jdbcadaptor.JDBCContext._tryConnect(JDBCContext.java:362)
at com.webobjects.jdbcadaptor.JDBCContext._channelWillOpen(JDBCContext.java:505)
at com.webobjects.jdbcadaptor.JDBCChannel.openChannel(JDBCChannel.java:111)
at com.webobjects.eoaccess.EODatabaseContext._openChannelWithLoginPanel(EODatabaseContext.java:1907)
at com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel(EODatabaseContext.java:1966)


Is there any way to suppress this kind of exceptions? 

regards, 

René

--

salient doremus

salient GmbH
Kontorhaus -  Lindleystraße 12
60314 Frankfurt Main

Fon +49 (0)69 - 650096 -0, Durchwahl: - 18, Fax: -70

http://www.salient.de
http://www.doremus.com
http://www.openforms.de

Geschäftsführer: Peter Biler, Alexander Gerling, Lars Ohlerich
Amtsgericht Frankfurt Main, HRB 48693

// Neuer Schwung auf allen Endgeräten für den Automobilclub von Deutschland: http://www.avd.de/

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: Using multiple servers
  • Next by Date: Re: woframework vs jar packaging in maven
  • Previous by thread: Re: woframework vs jar packaging in maven
  • Next by thread: Re: Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context
  • Index(es):
    • Date
    • Thread