cancel
Showing results for 
Search instead for 
Did you mean: 

Exception while applying time filter in Logging API for file ./log/applicat

Former Member
0 Kudos

Folks,

We are getting this error every second on our Portal Box . We are on 2004s SP 13 . Does anybody have any idea bout it ?

Thanks,

Manish

<i>Category: n/a

Exception while applying time filter in Logging API for file ./log/applications/com.sap.caf.rt/CAF.%g.log

Location: com.sap.tc.logging.APILogger.ReadableLog[setFilter()]

Application: n/a

Thread: SAPEngine_System_Thread[impl:5]_25

Data Source: I:\usr\sap\D41\JC41\j2ee\cluster\server0\log\defaultTrace.trc

Message ID: 001A64642244003D0000000F000018680004407B55859E0D

Argument Objects: java.lang.Exception: Exception while applying time filter in Logging API for file ./log/applications/com.sap.caf.rt/CAF.%g.log

at com.sap.tc.logging.reader.ReadableLog.setTimeFilter(ReadableLog.java:311)

at com.sapmarkets.bam.logcontroller.AbstractBAMLogReader.setTimeFilter(AbstractBAMLogReader.java:791)

at com.sapmarkets.bam.logcontroller.BAMLogReaderRecordSource.initFastTimeSearch(BAMLogReaderRecordSource.java:315)

at com.sapmarkets.bam.logcontroller.BAMLogReaderRecordSource.<init>(BAMLogReaderRecordSource.java:57)

at com.sapmarkets.bam.logcontroller.LogQueryBrowser.<init>(LogQueryBrowser.java:57)

at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.createLogQuerySession(LogControllerFacade.java:333)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)

at javax.management.StandardMBean.invoke(StandardMBean.java:286)

at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)

at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)

at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)

at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)

at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)

at sun.reflect.GeneratedMethodAccessor373.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.tc.logviewer.mbean.LocalLVMBeanServer.invoke(LocalLVMBeanServer.java:73)

</i>

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Did you ever resolve this issue? We are now experiencing the same issue in our portal environment.