com.bea.wli.sb.pipeline.PipelineException

java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 8388624, Num elements: 4194304

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Unknown by 753648,
  • via Unknown by 753648,
  • Stack trace

    • com.bea.wli.sb.pipeline.PipelineException: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 8388624, Num elements: 4194304 at com.bea.wli.sb.pipeline.PipelineContextImpl.handleError(PipelineContextImpl.java:964) at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:862) at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:143) at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:851) at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55) at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:68) at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:851) at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:194) at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75) at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:669) at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:668) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:666) at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:304) at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072) at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.