Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 20287 invoked from network); 1 Oct 2008 02:33:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Oct 2008 02:33:23 -0000 Received: (qmail 14477 invoked by uid 500); 1 Oct 2008 02:33:21 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 14450 invoked by uid 500); 1 Oct 2008 02:33:21 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 14433 invoked by uid 99); 1 Oct 2008 02:33:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2008 19:33:21 -0700 X-ASF-Spam-Status: No, hits=4.1 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WEIRD_PORT,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Oct 2008 02:32:17 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KkrWE-000436-Pj for users@activemq.apache.org; Tue, 30 Sep 2008 19:32:50 -0700 Message-ID: <19753624.post@talk.nabble.com> Date: Tue, 30 Sep 2008 19:32:50 -0700 (PDT) From: jpgggg To: users@activemq.apache.org Subject: networkconnector always on port 61616 even if deleted from activemq?xml? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: jgassner@novell.com X-Virus-Checked: Checked by ClamAV on apache.org I'm seeing some behavior I cannot explain with ActiveMQ 5.1. I have activemq.xml configured to listen for ssl connections on 61616. This is th= e only port I wish to receive connections on. Also, I've removed the networkConnectors element from the activemq.xml file because I do not want = a network of brokers. My activemq.xml file is pasted below. With this configuration, when I startup my broker I see the following log output: INFO TransportServerThreadSupport - Listening for connections at: ssl://host.net:61616 INFO TransportConnector - Connector ssl Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID: host.net-26274-1224815975049-0:0) started INFO FailoverTransport - Successfully connected to tcp://localhost:61616 WARN FailoverTransport - Transport failed to tcp://localhost:61616 , attempting to automatically reconnect due to: java.io.EOFException ERROR TransportConnector - Could not accept connection : Unrecognized SSL message, plaintext connection? ERROR TransportConnector - Could not accept connection : Unrecognized SSL message, plaintext connection? ERROR TransportConnector - Could not accept connection : Unrecognized SSL message, plaintext connection? The "ERROR TransportConnector - Could not accept connection : Unrecognized SSL message, plaintext connection?" errors continue endlessly.= =20 Eventually (after ~3 days), the broker appears to hang and needs to be restarted in order to continue sending messages. Also, I tried changing the port it listens on to 61617. This causes the "FailoverTransport" and "TransportConnector" errors to go away, but by running netcat -l -p 61616, I can see that connections are still trying to be made to port 61616 from the localhost. > netcat -l -p 61616 U=E2=98=BAActiveMQ =E2=99=A5=E2=98=BA =C3=87 =C2=B6TightEncodingEn= abled=E2=98=BA=E2=98=BA CacheSize=E2=99=A3 =E2=99=A6=20 =E2=97=84TcpNoDel ayEnabled=E2=98=BA=E2=98=BA =E2=86=95SizePrefixDisabled=E2=98=BA =E2=97=84= StackTraceEnabled=E2=98=BA=E2=98=BA=20 MaxInactivityDurationIni talDelay=E2=99=A0 '=E2=96=BA =C2=A7MaxInactivityDuration=E2=99=A0 = u0 =E2=99=80CacheEnabled=E2=98=BA=E2=98=BA [1]+ Stopped netcat -l -p 61616 > netstat -an | grep 61616 tcp 0 0 127.0.0.1:61616 127.0.0.1:20014 =20 ESTABLISHED tcp 0 0 127.0.0.1:20014 127.0.0.1:61616 =20 ESTABLISHED This tells me something in the ActiveMQ broker is trying to connect to itself on port 61616, even though, as far as I can tell, I've disabled all such connections. Any ideas? Thanks, John ----------- activemq.xml contents --------------------------------- " memoryLimit=3D"5mb"/> " memoryLimit=3D"5mb"> =09 =09 =09 =09 " read=3D"admins" write=3D"admins" admin=3D"admins" /> =09 " read=3D"admins" write=3D"admins" admin=3D"admins" /> =09 =09 =20 =09 =09 =09 =20 org.foo.bar --=20 View this message in context: http://www.nabble.com/networkconnector-always= -on-port-61616-even-if-deleted-from-activemq-xml--tp19753624p19753624.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.