No tunnel channels are available to handle this request in sap cloud connector logs

[former_member601157]

Hello,

I have seen these errors repeatedly in SCC Master when using SFTP between SCC and SCP and followed by a failover to slave SCC and then same error repeat. Any thoughts?

2019-01-16 17:48:39,012 
-0800#ERROR#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#tunnel-client-12-1#0x2ce52cfe#Exception
 caught while closing an outbound channel [id: 0x6c4df51e, L:/<ip 
address>:44256 ! R:<hostname>/<ip address>:22] 
com.sap.core.connectivity.spi.NoChannelsAvailableException: No tunnel 
channels are available to handle this request
  

at 
com.sap.core.connectivity.tunnel.core.impl.context.TunnelBridge.write(TunnelBridge.java:49)
 at 
com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler.channelInactive(OutboundConnectionErrorHandler.java:77)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
 at 
io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:75)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
 at 
io.netty.handler.flow.FlowControlHandler.channelInactive(FlowControlHandler.java:124)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
 at 
io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:75)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
 at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1354)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
 at 
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:917)
 at 
io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:822)
 at 
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
 at 
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
 at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
 at java.lang.Thread.run(Thread.java:836)| 2019-01-16 17:48:44,628 
-0800#ERROR#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-12-1#0xccb882b6#Discarding
 packet as connection to backend has been unexpectedly closed| 
2019-01-16 17:49:11,257 
-0800#ERROR#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-12-1#0x0d88e650#Discarding
 packet as connection to backend has been unexpectedly closed|

[gregorw]

I would suggest you file an incident via the SAP Support.

[former_member601157]

Hello Greg, yeah I did that. Thank you.