My Oracle Support Banner

OSB Server Consumes High CPU Memory (Doc ID 2386254.1)

Last updated on AUGUST 12, 2024

Applies to:

Oracle Service Bus - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

 OSB server running out of memory 

[2018-04-10T02:54:42.271-05:00] [osbp_server1] [ERROR] [OSB-382004] [oracle.osb.pipeline.kernel.router] [tid: JCA-work-instance:File Adapter-1] [userId: ] [ecid: xx-x-x-x-x-000000d4,0] [APP: Service Bus Routing] [FlowId: xxxx] Failed to process request message for service Pipeline FlConsole/SaveTransmission/Pipeline/SaveTransmission_PL: com.bea.wli.sb.pipeline.PipelineException: Java heap space[[
com.bea.wli.sb.pipeline.PipelineException: Java heap space
at com.bea.wli.sb.pipeline.PipelineContextImpl.handleError(PipelineContextImpl.java:1042)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:918)
at com.bea.wli.sb.pipeline.components.Pipeline.processMessage(Pipeline.java:153)
at com.bea.wli.sb.pipeline.PipelineContextImpl.handleError(PipelineContextImpl.java:1016)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:918)
at com.bea.wli.sb.pipeline.components.PipelineNode.doRequest(PipelineNode.java:64)
at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:80)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:905)
at com.bea.wli.sb.pipeline.components.Router.processMessage(Router.java:205)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:87)
at com.bea.wli.sb.pipeline.dispatcher.PipelineDispatcher$1.run(PipelineDispatcher.java:135)
at com.bea.wli.sb.pipeline.dispatcher.PipelineDispatcher$1.run(PipelineDispatcher.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at com.bea.wli.sb.util.security.SecurityUtils.executeAs(SecurityUtils.java:102)
at com.bea.wli.sb.security.WLSSecurityContextService.executeAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.dispatcher.PipelineDispatcher.dispatch(PipelineDispatcher.java:130)
at com.bea.wli.sb.context.PipelineDispatcherClient.dispatch(PipelineDispatcherClient.java:241)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:518)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:494)
at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:131)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:379)
at com.bea.wli.sb.pipeline.components.RouteNode.doRequest(RouteNode.java:131)
at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:80)

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.