You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by jpgggg <jg...@novell.com> on 2008/10/01 04:32:50 UTC
networkconnector always on port 61616 even if deleted from
activemq?xml?
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 the
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.
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☺ActiveMQ ♥☺ Ç ¶TightEncodingEnabled☺☺ CacheSize♣ ♦
◄TcpNoDel
ayEnabled☺☺ ↕SizePrefixDisabled☺ ◄StackTraceEnabled☺☺
MaxInactivityDurationIni
talDelay♠ '► §MaxInactivityDuration♠ u0 ♀CacheEnabled☺☺
[1]+ Stopped netcat -l -p 61616
> netstat -an | grep 61616
tcp 0 0 127.0.0.1:61616 127.0.0.1:20014
ESTABLISHED
tcp 0 0 127.0.0.1:20014 127.0.0.1:61616
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 ---------------------------------
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- START SNIPPET: example -->
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:amq="http://activemq.apache.org/schema/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd
http://activemq.apache.org/camel/schema/spring
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
<!-- Allows us to use system properties as variables in this
configuration file -->
<bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="localhost" dataDirectory="${activemq.base}/data">
<!-- Destination specific policies using destination names or
wildcards -->
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" memoryLimit="5mb"/>
<policyEntry topic=">" memoryLimit="5mb">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
<!-- Use the following to configure how ActiveMQ is exposed in JMX
-->
<managementContext>
<managementContext createConnector="false"/>
</managementContext>
<persistenceAdapter>
<amqPersistenceAdapter syncOnWrite="false"
directory="${activemq.base}/data" maxFileLength="20 mb"/>
</persistenceAdapter>
<!-- Use the following if you wish to configure the journal with
JDBC -->
<!--
<persistenceAdapter>
<journaledJDBC dataDirectory="${activemq.base}/data"
dataSource="#postgres-ds"/>
</persistenceAdapter>
-->
<!-- Or if you want to use pure JDBC without a journal -->
<!--
<persistenceAdapter>
<jdbcPersistenceAdapter dataSource="#postgres-ds"/>
</persistenceAdapter>
-->
<!-- The maximum about of space the broker will use before slowing
down producers -->
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="20 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="1 gb" name="foo"/>
</storeUsage>
<tempUsage>
<tempUsage limit="100 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<!-- The transport connectors ActiveMQ will listen to -->
<transportConnectors>
<!-- Currently, we are only using the ssl transport. -->
<transportConnector name="ssl" uri="ssl://localhost:61616"/>
<!-- The following unused ports are disabled. -->
<!--
<transportConnector name="openwire"
uri="tcp://localhost:61616"/>
<transportConnector name="openwire" uri="tcp://localhost:61616"
discoveryUri="multicast://default"/>
<transportConnector name="stomp" uri="stomp://localhost:61613"/>
<transportConnector name="xmpp" uri="xmpp://localhost:61222"/>
-->
</transportConnectors>
<plugins>
<!-- use JAAS to authenticate using the login.config file on
the classpath to configure JAAS -->
<jaasAuthenticationPlugin configuration="activemq-domain" />
<authorizationPlugin>
<map>
<authorizationMap>
<authorizationEntries>
<authorizationEntry queue=">" read="admins"
write="admins" admin="admins" />
<authorizationEntry topic=">" read="admins"
write="admins" admin="admins" />
</authorizationEntries>
</authorizationMap>
</map>
</authorizationPlugin>
</plugins>
</broker>
<!--
** Lets deploy some Enterprise Integration Patterns inside the ActiveMQ
Message Broker
** For more details see
**
** http://activemq.apache.org/enterprise-integration-patterns.html
-->
<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
<!-- You can use a <package> element for each root package to search
for Java routes -->
<package>org.foo.bar</package>
<!-- You can use Spring XML syntax to define the routes here using
the <route> element -->
<route>
<from uri="activemq:example.A"/>
<to uri="activemq:example.B"/>
</route>
</camelContext>
<!-- Uncomment to create a command agent to respond to message based
admin commands on the ActiveMQ.Agent topic -->
<!--
<commandAgent xmlns="http://activemq.apache.org/schema/core"
brokerUrl="vm://localhost"/>
-->
<!-- An embedded servlet engine for serving up the Admin console -->
<!-- The admin console is disabled for production installations -->
<!--
<jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
<connectors>
<nioConnector port="8161"/>
</connectors>
<handlers>
<webAppContext contextPath="/admin"
resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true"/>
<webAppContext contextPath="/demo"
resourceBase="${activemq.base}/webapps/demo" logUrlOnStart="true"/>
<webAppContext contextPath="/fileserver"
resourceBase="${activemq.base}/webapps/fileserver" logUrlOnStart="true"/>
</handlers>
</jetty>
-->
<!-- This xbean configuration file supports all the standard spring xml
configuration options -->
<!-- Postgres DataSource Sample Setup -->
<!--
<bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource">
<property name="serverName" value="localhost"/>
<property name="databaseName" value="activemq"/>
<property name="portNumber" value="0"/>
<property name="user" value="activemq"/>
<property name="password" value="activemq"/>
<property name="dataSourceName" value="postgres"/>
<property name="initialConnections" value="1"/>
<property name="maxConnections" value="10"/>
</bean>
-->
<!-- MySql DataSource Sample Setup -->
<!--
<bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName" value="com.mysql.jdbc.Driver"/>
<property name="url"
value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
<property name="username" value="activemq"/>
<property name="password" value="activemq"/>
<property name="maxActive" value="200"/>
<property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Oracle DataSource Sample Setup -->
<!--
<bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName"
value="oracle.jdbc.driver.OracleDriver"/>
<property name="url" value="jdbc:oracle:thin:@localhost:1521:AMQDB"/>
<property name="username" value="scott"/>
<property name="password" value="tiger"/>
<property name="maxActive" value="200"/>
<property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Embedded Derby DataSource Sample Setup -->
<!--
<bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource">
<property name="databaseName" value="derbydb"/>
<property name="createDatabase" value="create"/>
</bean>
-->
</beans>
<!-- END SNIPPET: example -->
--
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.
Re: networkconnector always on port 61616 even if deleted from activemq?xml?
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, Sep 30, 2008 at 8:32 PM, jpgggg <jg...@novell.com> wrote:
>
> 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 the
> 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?
...
> <!--
> ** Lets deploy some Enterprise Integration Patterns inside the ActiveMQ
> Message Broker
> ** For more details see
> **
> ** http://activemq.apache.org/enterprise-integration-patterns.html
> -->
> <camelContext id="camel"
> xmlns="http://activemq.apache.org/camel/schema/spring">
>
> <!-- You can use a <package> element for each root package to search
> for Java routes -->
> <package>org.foo.bar</package>
>
> <!-- You can use Spring XML syntax to define the routes here using
> the <route> element -->
> <route>
> <from uri="activemq:example.A"/>
> <to uri="activemq:example.B"/>
> </route>
> </camelContext>
>
>
> <!-- Uncomment to create a command agent to respond to message based
> admin commands on the ActiveMQ.Agent topic -->
> <!--
> <commandAgent xmlns="http://activemq.apache.org/schema/core"
> brokerUrl="vm://localhost"/>
> -->
>
>
> <!-- An embedded servlet engine for serving up the Admin console -->
> <!-- The admin console is disabled for production installations -->
> <!--
> <jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
> <connectors>
> <nioConnector port="8161"/>
> </connectors>
>
> <handlers>
> <webAppContext contextPath="/admin"
> resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true"/>
> <webAppContext contextPath="/demo"
> resourceBase="${activemq.base}/webapps/demo" logUrlOnStart="true"/>
> <webAppContext contextPath="/fileserver"
> resourceBase="${activemq.base}/webapps/fileserver" logUrlOnStart="true"/>
> </handlers>
> </jetty>
> -->
I see you've already commented out the Jetty configuration but you
left the <camelContext> element. Both of those items try to make a
connection to port 61616 by default. I think this is what's causing
the issue you're seeing. Trying commenting out the <camelContext>
element to see if the error disappears.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Blog: http://bruceblog.org/