Cycle Policy Batch Hung 'SystemDatagramSocketProvider Failed To Bind To Configured Port xxxx' Message
(Doc ID 3065681.1)
Last updated on JANUARY 02, 2025
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.3.0.27 and laterInformation in this document applies to any platform.
Symptoms
On : 11.3.0.27 version, Cycle
The Production Environment has encountered a few instances where the Policy level job has a Coherence issue with one of the JVMs unable to connect with the batch DBE server.
Within the log, it is shown that it stops the Cluster service, restarts the Cluster, and hits a stack trace with a failure to bind (Address already in use).
However, this does not fail the job and the level keeps running, even though it's not doing anything.
ERROR
-----------------------
Oracle Coherence GE 12.2.1.3.0 (thread=DistributedCache, member=n/a): Error while starting \
cluster: (Wrapped) java.io.IOException: SystemDatagramSocketProvider failed to bind to configured port 43400. Note, that port auto-\
adjust feature has been explicitly disabled
at com.tangosol.util.Base.ensureRuntimeException(Base.java:296)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:277)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:41)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:12)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:32)
at com.tangosol.coherence.component.util.SafeService.restartService(SafeService.CDB:20)
at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:40)
at com.tangosol.coherence.component.util.SafeService.getRunningService(SafeService.CDB:7)
at com.tangosol.coherence.component.util.SafeService.getInfo(SafeService.CDB:1)
at com.tangosol.net.management.MBeanHelper.unregisterCacheMBean(MBeanHelper.java:331)
at com.tangosol.net.management.MBeanHelper.unregisterCacheMBean(MBeanHelper.java:377)
at com.tangosol.net.cache.NearCache.unregisterMBean(NearCache.java:598)
at com.tangosol.net.cache.CachingMap$DeactivationListener.entryDeleted(CachingMap.java:1944)
at com.tangosol.util.MapEvent.dispatch(MapEvent.java:278)
at com.tangosol.coherence.component.util.CacheEvent.dispatchSafe(CacheEvent.CDB:14)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.invalidate\
(PartitionedCache.CDB:27)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.releaseAllCache(Pa\
rtitionedCache.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onExit(Partitioned\
Cache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:82)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.io.IOException: SystemDatagramSocketProvider failed to bind to configured port 43400. Note, that port auto-adjust f\
eature has been explicitly disabled
at com.tangosol.coherence.component.net.Cluster$SocketManager.bindSockets(Cluster.CDB:162)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:37)
... 19 more
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:461)
at sun.nio.ch.Net .bind(Net.java:453)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
at com.oracle.common.internal.net.WrapperServerSocket.bind(WrapperServerSocket.java:71)
at com.oracle.common.internal.net.MultiplexedSocketProvider.open(MultiplexedSocketProvider.java:2234)
at com.oracle.common.internal.net.MultiplexedSocketProvider.open(MultiplexedSocketProvider.java:2106)
at com.oracle.common.internal.net.MultiplexedSocketProvider$MultiplexedServerSocketChannel$1.bind(MultiplexedSocketProvider.java:7\
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Go to CycleClient\bin directory.
2. Execute shell command - ./run.sh
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 |