Push data to ES,got successful=false
squr opened this issue · 1 comments
<weblogic.logging.exporter.LogExportHandler> logging of { "index" : { }}
{"messageID": "BEA-000337","message": "[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "115" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@c6bc2dc[GET /WebRoot/stuck.jsp]
", which is more than the configured time (StuckThreadMaxTime) of "60" seconds in "server-failure-trigger". Stack trace:
java.lang.Thread.sleep(Native Method)
jsp_servlet.__stuck._jspService(__stuck.java:91)
weblogic.servlet.jsp.JspBase.service(JspBase.java:35)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:295)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:353)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:250)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3862)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3829)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
weblogic.servlet.internal.WebAppServletContext.processSecuredExecute(WebAppServletContext.java:2502)
weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2351)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2326)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2304)
weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1779)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1733)
weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:272)
weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:651)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
","timestamp": 1599719366983,"serverName": "AdminServer","threadName": "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'","severity": "Error","userId": "","level": "Error","loggerName": "WebLogicServer","formattedDate": "Sep 10, 2020 2:29:26,983 PM CST","subSystem": "WebLogicServer","machineName": "testServer210","transactionId": "","diagnosticContextId": "8040dd9a-a265-4ede-858b-4c19734e1de9-00000015","sequenceNumber": 258,"domainUID": "testDomain"}
{ "index" : { }}
{"messageID": "BEA-002959","message": "Self-tuning thread pool contains 2 running threads, 10 idle threads, and 0 standby threads","timestamp": 1599719473889,"serverName": "AdminServer","threadName": "Timer-2","severity": "Info","userId": "","level": "Info","loggerName": "WorkManager","formattedDate": "Sep 10, 2020 2:31:13,889 PM CST","subSystem": "WorkManager","machineName": "testServer210","transactionId": "","diagnosticContextId": "8040dd9a-a265-4ede-858b-4c19734e1de9-00000010","sequenceNumber": 259,"domainUID": "testDomain"}
got result Result{response='null', status=400, successful=false}
My WebLogicLoggingExporter.yaml as follows:
weblogicLoggingIndexName: wls
publishHost: 192.168.3.210
publishPort: 9200
domainUID: testDomain
weblogicLoggingExporterEnabled: true
weblogicLoggingExporterSeverity: Debug
weblogicLoggingExporterBulkSize: 2
How to fix this issue?
Thanks.
Logging exporter just exports exactly what it gets from WLS server log, So I'd suggest you check the server log and see why Weblogic server logs throw errors like that