Then I guess you are left with disabling the debug logging for NSLog or making a subclass of JDBCContext and, IIRC, the JDBCAdaptor to get it your use your JDBCContext subclass.
Chuck From: <webobjects-dev-bounces+chill=gevityinc....@lists.apple.com<mailto:webobjects-dev-bounces+chill=gevityinc....@lists.apple.com>> on behalf of René Bock <b...@salient.de<mailto:b...@salient.de>> Date: Monday, December 14, 2015 at 2:02 AM To: webobjects-dev <webobjects-dev@lists.apple.com<mailto:webobjects-dev@lists.apple.com>> Subject: Re: Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context Nope. The ConnectionDictionairies of the models in use are all empty... René Am 11.12.2015 um 19:03 schrieb Chuck Hill <ch...@gevityinc.com<mailto:ch...@gevityinc.com>>: Check your models. I think you will find somewhere a connection dictionary with a value for the key DataSourceJndiName. Remove that. Chuck From: <webobjects-dev-bounces+chill=gevityinc....@lists.apple.com<mailto:webobjects-dev-bounces+chill=gevityinc....@lists.apple.com>> on behalf of René Bock <b...@salient.de<mailto:b...@salient.de>> Date: Thursday, December 10, 2015 at 8:22 AM To: webobjects-dev <webobjects-dev@lists.apple.com<mailto:webobjects-dev@lists.apple.com>> Subject: Suppressing javax.naming.NameNotFoundException: Name "comp/env/jdbc" not found in context 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é
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
