Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SOL-79061] Very verbose logging when connection to broker is interuppted: #174

Closed
GreenRover opened this issue Sep 22, 2022 · 2 comments
Closed
Labels
enhancement New feature or request tracked Internally tracked by Solace's internal issue tracking system

Comments

@GreenRover
Copy link
Contributor

GreenRover commented Sep 22, 2022

When the connection between application an broker is interrupted,
i get thounds of exception per second:

2022-09-16 15:59:59,999 WARN [pool-26-thread-1] com.solace.spring.cloud.stream.binder.inbound.InboundXMLMessageListener  Received error while trying to read message from endpoint INTERNAL/tms/capaopt/oda/d-geheim/odainterfaceprocessor/v3/operatingstate/executionura
com.solacesystems.jcsmp.StaleSessionException: Tried to call receive on a stopped message consumer.
      at com.solacesystems.jcsmp.impl.flow.FlowHandleImpl.throwClosedException(FlowHandleImpl.java:1900)
      at com.solacesystems.jcsmp.impl.flow.FlowHandleImpl.receive(FlowHandleImpl.java:852)
      at com.solacesystems.jcsmp.impl.flow.FlowHandleImpl.receive(FlowHandleImpl.java:819)
      at com.solace.spring.cloud.stream.binder.util.FlowReceiverContainer.receive(FlowReceiverContainer.java:279)
      at com.solace.spring.cloud.stream.binder.util.FlowReceiverContainer.receive(FlowReceiverContainer.java:211)
      at com.solace.spring.cloud.stream.binder.inbound.InboundXMLMessageListener.receive(InboundXMLMessageListener.java:93)
      at com.solace.spring.cloud.stream.binder.inbound.InboundXMLMessageListener.run(InboundXMLMessageListener.java:73)
      at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
      at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
      at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: com.solacesystems.jcsmp.JCSMPTransportException: (JCSMPTransportException) Error communicating with the router. (KeepAlive)
      at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel$ClientChannelReconnect.call(TcpClientChannel.java:2320)
      ... 4 common frames omitted
Caused by: com.solacesystems.jcsmp.JCSMPTransportException: (Client name: geheim/2711347/#00100002/JOIVd_o7yW   Local addr: 10.1.1.1 Local port: 56744   Remote addr: geheim  Remote port: 15443) - Timeout happened when reading response from the router.
      at com.solacesystems.jcsmp.protocol.impl.TcpChannel.executePostOnce(TcpChannel.java:240)
      at com.solacesystems.jcsmp.protocol.impl.ChannelOpStrategyClient.performOpen(ChannelOpStrategyClient.java:97)
      at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.performOpenSingle(TcpClientChannel.java:399)
      at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.access$800(TcpClientChannel.java:106)
      at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel$ClientChannelReconnect.call(TcpClientChannel.java:2156)
      ... 4 common frames omitted
Caused by: java.net.SocketTimeoutException: null
      at java.base/sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:214)
      at java.base/sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103)
      at java.base/java.io.InputStream.read(InputStream.java:205)
      at com.solacesystems.jcsmp.protocol.smf.SSLSmfClient.readBytes(SSLSmfClient.java:549)
      at com.solacesystems.jcsmp.protocol.smf.SSLSmfClient.doPostNoResponse(SSLSmfClient.java:292)
      at com.solacesystems.jcsmp.protocol.smf.SimpleSmfClient.doPost(SimpleSmfClient.java:230)
      at com.solacesystems.jcsmp.protocol.impl.TcpChannel.executePostOnce(TcpChannel.java:196)
      ... 8 common frames omitted

A broken broker connection should not throw exception.
There for a #145 health indicator should report an issue.

Some else also notices this problem.
https://solace.community/discussion/1438/stalesessionexception-spam-when-disconnected-from-host

@mackenza
Copy link
Contributor

This has been logged in the Solace Jira and we are targeting Q1CY2023 for a fix.

@mackenza mackenza added the enhancement New feature or request label Sep 29, 2022
@Nephery Nephery added the tracked Internally tracked by Solace's internal issue tracking system label Sep 29, 2022
@Nephery Nephery changed the title Very verbose logging when connection to broker is interuppted: [SOL-79061] Very verbose logging when connection to broker is interuppted: Sep 29, 2022
@carolmorneau
Copy link
Collaborator

Closed with #215

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tracked Internally tracked by Solace's internal issue tracking system
Projects
None yet
Development

No branches or pull requests

4 participants