Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2281

[AMQ6, STOMP+NIO+SSL] missing remote ip from exception message.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.3.x
    • JBoss A-MQ 6.3
    • broker
    • None
    • +
    • Hide

      I don't have a reproducer for this exception at this time.

      Show
      I don't have a reproducer for this exception at this time.

    Description

      The remote IP is missing from the following exception on the broker - it prints "Could not accept connection from null ..."

      2019-03-11 13:24:27,639 [ActiveMQ BrokerService[XXXX] Task-14] ERROR TransportConnector - Could not accept connection from null: java.io.IOException: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
      2019-03-11 13:24:27,639 [ActiveMQ BrokerService[XXXX] Task-14] DEBUG TransportConnector - Reason: java.io.IOException: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
      java.io.IOException: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
      	at org.apache.activemq.transport.nio.NIOSSLTransport.initializeStreams(NIOSSLTransport.java:177)
      	at org.apache.activemq.transport.stomp.StompNIOSSLTransport.initializeStreams(StompNIOSSLTransport.java:49)
      	at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:519)
      	at org.apache.activemq.transport.nio.NIOTransport.doStart(NIOTransport.java:160)
      	at org.apache.activemq.transport.nio.NIOSSLTransport.doStart(NIOSSLTransport.java:448)
      	at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
      	at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
      	at org.apache.activemq.transport.stomp.StompTransportFilter.start(StompTransportFilter.java:65)
      	at org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:169)
      	at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
      	at org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:1061)
      	at org.apache.activemq.broker.TransportConnector$1$1.run(TransportConnector.java:218)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Caused by: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
      	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
      	at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
      	at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
      	at sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:1561)
      	at org.apache.activemq.transport.nio.NIOSSLTransport.secureRead(NIOSSLTransport.java:359)
      	at org.apache.activemq.transport.nio.NIOSSLTransport.doHandshake(NIOSSLTransport.java:406)
      	at org.apache.activemq.transport.nio.NIOSSLTransport.initializeStreams(NIOSSLTransport.java:146)
      	... 14 more
      

      User want to identify which client is connecting to the broker.

      Attachments

        Activity

          People

            gtully@redhat.com Gary Tully
            rhn-support-pfox Patrick Fox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: