My Oracle Support Banner

Capture Managed Server will not Start and Seeing Error "Broken pipe" in the Capture Log (Doc ID 2606640.1)

Last updated on NOVEMBER 05, 2019

Applies to:

Oracle WebCenter Enterprise Capture - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Running Oracle WebCenter Enterprise Catpure 12.2.1.2.0. The server is not starting and the following information is found in the capture_server1.log:

#### <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >  java.io.IOException: Broken pipe
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
at sun.nio.ch.IOUtil.write(IOUtil.java:65)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
at weblogic.socket.NIOOutputStream$BlockingWriter.write(NIOOutputStream.java:326)
at weblogic.socket.NIOOutputStream.write(NIOOutputStream.java:241)
at weblogic.socket.NIOSocketMuxer.internalWrite(NIOSocketMuxer.java:807)
at weblogic.socket.SocketMuxer.write(SocketMuxer.java:1018)
at weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection.sendMsg(MuxableSocketT3.java:814)
at weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:384)
at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:218)
at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:168)
at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg(ConnectionManager.java:748)
at weblogic.rjvm.RJVMImpl$HeartbeatChecker.timerExpired(RJVMImpl.java:1944)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:290)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
>
#### <Logger@9229983 12.2.1.2.0> <> <> <[severity-value: 256] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[com.tangosol.coherence.component.util.logOutput.Jdk:log] 2019-10-28 16:55:30.859/2171.678 Oracle Coherence GE 12.2.1.2.0 (thread=Cluster, member=1): Service guardian is 35272ms late, indicating that this JVM may be running slowly or experienced a long GC>
#### <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
#### <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >  java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
>
#### <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
#### <Logger@9229983 12.2.1.2.0> <> <> <[severity-value: 256] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <[com.tangosol.coherence.component.util.logOutput.Jdk:log] 2019-10-28 16:59:17.061/2397.880 Oracle Coherence GE 12.2.1.2.0 (thread=Cluster, member=1): Service guardian is 287519ms late, indicating that this JVM may be running slowly or experienced a long GC>

The java memory arguments are

-Xms1024m -Xmx4096m

It was noticed that the machine processor is pegged when attempting to start.

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


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