On 05/16/2017 12:19 PM, aragoubi wrote:
I am using activemq 5.9.0.
My client is using mqtt v3.1.
I can't enable more log for my broker because I can't access my broker with
jconsole in order to change th log4j.
There is no problem with my client because connection is established. He
just told that connection is lost (callbacks).
I think that the problem is coming from the broker because connection is
never lost when I try to connect to mosquito broker.
Here the other configuration files for my broker that I deployed in jboss:
In the *ra.xml file* I just changed vm://localhost by tcp://localhost:61616.
There's been a number of fixes to the broker since 5.9.0 both for
WebSockets and for MQTT. Having worked on the WS layer in versions past
even after 5.9.0 I'd say you should probably stay away from it unless
you move to a much newer release. At the very least use the MQTT
transport and not go over WebSockets on that old release
This is my *ironjacamar.xml* file:
<ironjacamar>
<connection-definitions>
<connection-definition
class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory"
jndi-name="java:jboss/jms/ActiveTopicConnectionFactory"
pool-name="TopicConnectionFactory">
<pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<prefill>false</prefill>
</pool>
<security>
<application />
</security>
<timeout>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>60</idle-timeout-minutes>
</timeout>
<validation>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</connection-definition>
<connection-definition
class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory"
jndi-name="java:jboss/jms/ActiveConnectionFactory"
pool-name="QueueConnectionFactory">
<pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<prefill>false</prefill>
</pool>
<security>
<application />
</security>
<timeout>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>60</idle-timeout-minutes>
</timeout>
<validation>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</connection-definition>
</connection-definitions>
<admin-objects>
<admin-object
class-name="org.apache.activemq.command.ActiveMQTopic"
jndi-name="java:jboss/jms/ActiveTestTopic">
<config-property
name="PhysicalName">activemq/topic/TestTopic
</config-property>
</admin-object>
<admin-object
class-name="org.apache.activemq.command.ActiveMQQueue"
jndi-name="java:jboss/jms/ActiveRequestQueue">
<config-property
name="PhysicalName">activemq/queue/RequestQueue
</config-property>
</admin-object>
<admin-object
class-name="org.apache.activemq.command.ActiveMQQueue"
jndi-name="java:jboss/jms/ActiveResponseQueue">
<config-property
name="PhysicalName">activemq/queue/ResponseQueue
</config-property>
</admin-object>
</admin-objects>
</ironjacamar>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-to-activemq-broker-is-lost-within-one-second-tp4726204p4726206.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
