com.bea.wli.sb.pipeline.PipelineException: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 8388624, Num elements: 4194304

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 753648, 1 year ago
java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 8388624, Num elements: 4194304
via Oracle Community by 753648, 1 year ago
java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 8388624, Num elements: 4194304
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)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.