Problem with JNDIConnectionSource
Hi *, I apologize, if this get's posted twice. My first post (through Nabble) shows up in Nabble, but I got a "You may not post" message. Anyway, I'm trying to get logback (0.9.24) to log to my Oracle Database (11g) from an Enterprise Application running on an Oracle Weblogic (11g). I'm getting the following error: 2010-09-23 11:25:34 INFO LoggerContext Could NOT find resource [logback.groovy] 2010-09-23 11:25:34 INFO LoggerContext Could NOT find resource [logback-test.xml] 2010-09-23 11:25:34 INFO LoggerContext Found resource [logback.xml] at [file:/export/home/zielk_an/workspace_produktion_trunk/trunk/base/project_base/bin/logback.xml] 2010-09-23 11:25:34 INFO ConfigurationAction debug attribute not set 2010-09-23 11:25:34 INFO AppenderAction About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 2010-09-23 11:25:34 INFO AppenderAction Naming appender as [STDOUT] 2010-09-23 11:25:34 INFO NestedComplexPropertyIA Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 2010-09-23 11:25:34 INFO NestedComplexPropertyIA Pushing component [encoder] on top of the object stack. 2010-09-23 11:25:34 INFO AppenderAction About to instantiate appender of type [ch.qos.logback.classic.db.DBAppender] 2010-09-23 11:25:34 INFO AppenderAction Naming appender as [DB] 2010-09-23 11:25:34 INFO NestedComplexPropertyIA Pushing component [connectionSource] on top of the object stack. 2010-09-23 11:25:34 INFO JNDIConnectionSource Driver name=Oracle JDBC driver 2010-09-23 11:25:34 INFO JNDIConnectionSource Driver version=11.1.0.7.0-Production 2010-09-23 11:25:34 INFO JNDIConnectionSource supportsGetGeneratedKeys=true 2010-09-23 11:25:34 INFO RootLoggerAction Setting level of ROOT logger to DEBUG 2010-09-23 11:25:34 INFO AppenderRefAction Attaching appender named [STDOUT] to Logger[ROOT] 2010-09-23 11:25:34 INFO AppenderRefAction Attaching appender named [DB] to Logger[ROOT] 2010-09-23 11:25:41 ERROR DBAppender problem appending event java.sql.SQLException: prepareStatement, Exception = 14 at weblogic.jdbc.wrapper.XAConnection.invocationExceptionHandler(XAConnection.java:190) at weblogic.jdbc.wrapper.XAConnection.prepareStatement(XAConnection.java:1113) at weblogic.jdbc.common.internal.ConnectionEnv.makeStatement(ConnectionEnv.java:1361) at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatement(ConnectionEnv.java:1114) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:793) at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:99) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:91) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:283) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:270) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:471) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:425) at ch.qos.logback.classic.Logger.info(Logger.java:629) Has anyone experienced similar problems? Could it be related to the weblogic JDBC wrapper? Any help is appreciated & thanks for any hints. Kind regards, Andreas
Hi *, I've just realized, that I omitted valuable information by cutting the stack trace, so here is the complete trace: java.sql.SQLException: prepareStatement, Exception = 14 at weblogic.jdbc.wrapper.JDBCWrapperImpl.invocationExceptionHandler(JDBCWrapperImpl.java:141) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:800) at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:99) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:91) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:283) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:270) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:471) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:425) at ch.qos.logback.classic.Logger.info(Logger.java:629) at de.bayern.lvg.alkis.boschshapeabgabe.ejb.ShapeAbgabeLifecycleListener.postStart(ShapeAbgabeLifecycleListener.java:33) at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:297) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199) at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:71) at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.ArrayIndexOutOfBoundsException: 14 at oracle.jdbc.driver.OracleSql.computeBasicInfo(OracleSql.java:950) at oracle.jdbc.driver.OracleSql.getSqlKind(OracleSql.java:623) at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:1215) at oracle.jdbc.driver.T4CPreparedStatement.<init>(T4CPreparedStatement.java:28) at oracle.jdbc.driver.T4CDriverExtension.allocatePreparedStatement(T4CDriverExtension.java:68) at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3140) at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3042) at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:6022) at weblogic.jdbc.common.internal.ConnectionEnv.makeStatement(ConnectionEnv.java:1361) at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatement(ConnectionEnv.java:1114) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:793) ... 35 more Kind regards Andreas -- View this message in context: http://old.nabble.com/Problem-with-JNDIConnectionSource-tp29787867p29788049.... Sent from the Logback User mailing list archive at Nabble.com.
Hi *, I just found out, that when I force the value of cnxSupportsGetGeneratedKeys in ch.qos.logback.core.db.DBAppenderBase to false, everything seems to work. So I'm speculating that the weblogic wrapper of the oracle driver kills this capability. Is there a way to enforce setting the cnxSupportsGetGeneratedKeys value to false using configuration? If not, could you suggest a workaround, as I'm new to logback? Thanks & kind regards Andreas -- View this message in context: http://old.nabble.com/Problem-with-JNDIConnectionSource-tp29787867p29788259.... Sent from the Logback User mailing list archive at Nabble.com.
Problem could be related to http://forums.oracle.com/forums/thread.jspa?messageID=3468587 -- View this message in context: http://old.nabble.com/Problem-with-JNDIConnectionSource-tp29787867p29788972.... Sent from the Logback User mailing list archive at Nabble.com.
participants (1)
-
Andreas Zielke