1 Reply Latest reply on Sep 16, 2013 11:52 AM by 869615

    AqAdapter log to /dev/null

    869615

      In "BPEL 10g" we were not able to stop the logging from the AqAdapter and therefore set the logging value to /dev/null.

      (setting /weblogic-connector/outbound-resource-adapter/default-connection-properties/logging/logging-enabled  to 'false' did not help).

       

       

      Now after migrating to SOA Suite 11g (11.1.1.7) we have done the exact same thing. And everything seem to work, besides an exception we get from time to time. The exception is from some internal scheduler that runs from time to time. The exception is:

       

      ####<Aug 23, 2013 7:00:45 AM CEST> <Error> <Diagnostics> <xxx> <DomainName> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <xxxxxxxxxxxxxxx:xxxxxxxxx:-xxxxxxx> <1377234045709> <BEA-320004> <The following unexpected exception was thrown: Internal error in data retirement scheduler

      java.lang.IllegalArgumentException: LogFilename is a not a recognized property on weblogic.j2ee.descriptor.wl.LoggingBeanImpl@1b67a39b(/OutboundResourceAdapter/ConnectionDefinitionGroups[oracle.sdp.messaging.driver.DriverConnectionFactory]/DefaultConnectionProperties/Logging)

              at weblogic.descriptor.internal.AbstractDescriptorBean.isSet(AbstractDescriptorBean.java:259)

              at weblogic.connector.external.impl.OutboundInfoImpl.getLogFilename(OutboundInfoImpl.java:1469)

              at weblogic.connector.external.RAUtil.getAvailableConnectorLogNames(RAUtil.java:96)

              at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl.getAvailableDiagnosticDataAccessorNames(WLSAccessorMBeanFactoryImpl.java:113)

              at weblogic.diagnostics.archive.DataRetirementScheduler.createDataRetirementTask(DataRetirementScheduler.java:177)

              at weblogic.diagnostics.archive.DataRetirementScheduler.processTimer(DataRetirementScheduler.java:157)

              at weblogic.diagnostics.archive.DataRetirementScheduler.timerExpired(DataRetirementScheduler.java:124)

              at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)

              at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

              at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

       

       

      Is it possible that the exception is related to configuring  AqAdapters /weblogic-connector/outbound-resource-adapter/default-connection-properties/logging/log-filename value to /dev/null ?

      Or does the exception have nothing to do with us configuring logging filename as /dev/null?

       

      When the exception occur the whole SOA Suite becomes unusable and must be restarted.

       

      It was working fine on 10g but on 11g we are not sure if the two things are related.