Hiram, the configuration is following (I took it from an example):
<broker xmlns="http://activemq.org/config/1.0"; useJmx="false"
persistent="false" start="true">
<persistenceAdapter>
<memoryPersistenceAdapter/>
</persistenceAdapter>
<transportConnectors>
<transportConnector uri="tcp://localhost:0"
discoveryUri="multicast://default"/>
</transportConnectors>
<networkConnectors>
<networkConnector uri="multicast://default"/>
</networkConnectors>
</broker>
Regards,
Maxim
Hiram Chirino wrote:
>
> For the stack trace it looks normal. ActiveMQ is waiting for a
> response from the broker which may take a while. If it takes forever,
> it would be interesting to find out if the broker is remote or if the
> vm:// transport is being used.
>
> Another way to resolve this is to have the Spring
> DefaultMessageListenerContainer use a deamon thread. Not sure if
> there is a way to configure that.
>
> Regards,
> Hiram
>
--
View this message in context:
http://www.nabble.com/Probable-bug.-tf3871562s2354.html#a11039806
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
