You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Geoffrey Arnold <ge...@geoffreyarnold.com> on 2009/12/04 19:50:23 UTC

OutOfMemoryError when reconnecting forwarding bridge

Hi all,

We have a forwarding bridge between an embedded broker in one VM and a remote broker in another VM using the examples from the network-of-brokers documentation[1].  While testing failover, we left the embedded broker VM running overnight but did not start the remote broker VM.  NOTE: The embedded broker VM was idle (we were not testing application logic).

In the morning the embedded broker VM threw an OutOfMemoryError:

	Exception in thread "Simple Discovery Agent: java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c" java.lang.OutOfMemoryError: Java heap space
		at org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
		at org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
		at org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
		at org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
		at org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
		at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
		at org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
		at org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
		at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
		at java.lang.Thread.run(Thread.java:637)

Our logs contained repeated (and expected) messages indicating that a connection could not be established with the remote broker.  The one thing that stands out from these logs is that a new thread was created in the embedded broker VM on each attempt to connect to the remote broker VM:

	[1259881226751][Thread-10] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259881227757][Thread-11] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259881229762][Thread-12] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	...
	[1259888976178][Thread-267] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259889006398][Thread-268] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused
	[1259889036611][Thread-269] Could not start network bridge between: vm://embeddedBroker and: tcp://localhost:61616 due to: java.net.ConnectException: Connection refused

The embedded broker VM is configured via Spring as follows:

	<amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true" persistent="false" useShutdownHook="true">
		<amq:managementContext>
			<amq:managementContext createConnector="false"/>
		</amq:managementContext>
		<amq:networkConnectors>
			<amq:networkConnector uri="static:(tcp://localhost:61616)"/>
		</amq:networkConnectors>
	</amq:broker>

Any help would be greatly appreciated.

Thanks,
Geoff.

[1] http://activemq.apache.org/networks-of-brokers.html

Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by Geoffrey Arnold <ge...@geoffreyarnold.com>.
Ok, looking forward to 5.3.1.  Thanks Swen!

On Dec 5, 2009, at 1:01 PM, smoc wrote:

> 
> Seems to be the same bug as: 
> http://issues.apache.org/activemq/browse/AMQ-2448
> http://issues.apache.org/activemq/browse/AMQ-2448 
> 
> -- 
> View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p26657809.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> 


Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by smoc <sw...@gmx.de>.
Seems to be the same bug as: 
http://issues.apache.org/activemq/browse/AMQ-2448
http://issues.apache.org/activemq/browse/AMQ-2448 

-- 
View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p26657809.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by dialsc <di...@bluewin.ch>.
cool, thx for the info!

greez,

dialsc

Geoffrey Arnold wrote:
> 
> Hi all,
> 
> We have a forwarding bridge between an embedded broker in one VM and a
> remote broker in another VM using the examples from the network-of-brokers
> documentation[1].  While testing failover, we left the embedded broker VM
> running overnight but did not start the remote broker VM.  NOTE: The
> embedded broker VM was idle (we were not testing application logic).
> 
> In the morning the embedded broker VM threw an OutOfMemoryError:
> 
> 	Exception in thread "Simple Discovery Agent:
> java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
> java.lang.OutOfMemoryError: Java heap space
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
> 		at
> org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
> 		at
> org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
> 		at
> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
> 		at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
> 		at
> org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
> 		at
> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 		at java.lang.Thread.run(Thread.java:637)
> 
> Our logs contained repeated (and expected) messages indicating that a
> connection could not be established with the remote broker.  The one thing
> that stands out from these logs is that a new thread was created in the
> embedded broker VM on each attempt to connect to the remote broker VM:
> 
> 	[1259881226751][Thread-10] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881227757][Thread-11] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881229762][Thread-12] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	...
> 	[1259888976178][Thread-267] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889006398][Thread-268] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889036611][Thread-269] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 
> The embedded broker VM is configured via Spring as follows:
> 
> 	<amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true"
> persistent="false" useShutdownHook="true">
> 		<amq:managementContext>
> 			<amq:managementContext createConnector="false"/>
> 		</amq:managementContext>
> 		<amq:networkConnectors>
> 			<amq:networkConnector uri="static:(tcp://localhost:61616)"/>
> 		</amq:networkConnectors>
> 	</amq:broker>
> 
> Any help would be greatly appreciated.
> 
> Thanks,
> Geoff.
> 
> [1] http://activemq.apache.org/networks-of-brokers.html
> 

-- 
View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p29086521.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by Dejan Bosanac <de...@nighttale.net>.
This has been fixed in the trunk and will be available in the 5.4.0 release

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Tue, Jul 6, 2010 at 3:28 PM, dialsc <di...@bluewin.ch> wrote:
>
> hello,
>
> we are running version 5.3.1 but facing the same problem.
>
>
>
> Geoffrey Arnold wrote:
>>
>> Hi all,
>>
>> We have a forwarding bridge between an embedded broker in one VM and a
>> remote broker in another VM using the examples from the network-of-brokers
>> documentation[1].  While testing failover, we left the embedded broker VM
>> running overnight but did not start the remote broker VM.  NOTE: The
>> embedded broker VM was idle (we were not testing application logic).
>>
>> In the morning the embedded broker VM threw an OutOfMemoryError:
>>
>>       Exception in thread "Simple Discovery Agent:
>> java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
>> java.lang.OutOfMemoryError: Java heap space
>>               at
>> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
>>               at
>> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
>>               at
>> org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
>>               at
>> org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
>>               at
>> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
>>               at
>> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
>>               at
>> org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
>>               at
>> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
>>               at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>               at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>               at java.lang.Thread.run(Thread.java:637)
>>
>> Our logs contained repeated (and expected) messages indicating that a
>> connection could not be established with the remote broker.  The one thing
>> that stands out from these logs is that a new thread was created in the
>> embedded broker VM on each attempt to connect to the remote broker VM:
>>
>>       [1259881226751][Thread-10] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259881227757][Thread-11] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259881229762][Thread-12] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       ...
>>       [1259888976178][Thread-267] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259889006398][Thread-268] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259889036611][Thread-269] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>
>> The embedded broker VM is configured via Spring as follows:
>>
>>       <amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true"
>> persistent="false" useShutdownHook="true">
>>               <amq:managementContext>
>>                       <amq:managementContext createConnector="false"/>
>>               </amq:managementContext>
>>               <amq:networkConnectors>
>>                       <amq:networkConnector uri="static:(tcp://localhost:61616)"/>
>>               </amq:networkConnectors>
>>       </amq:broker>
>>
>> Any help would be greatly appreciated.
>>
>> Thanks,
>> Geoff.
>>
>> [1] http://activemq.apache.org/networks-of-brokers.html
>>
>
> --
> View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p29085359.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by dialsc <di...@bluewin.ch>.
hello,

we are running version 5.3.1 but facing the same problem.



Geoffrey Arnold wrote:
> 
> Hi all,
> 
> We have a forwarding bridge between an embedded broker in one VM and a
> remote broker in another VM using the examples from the network-of-brokers
> documentation[1].  While testing failover, we left the embedded broker VM
> running overnight but did not start the remote broker VM.  NOTE: The
> embedded broker VM was idle (we were not testing application logic).
> 
> In the morning the embedded broker VM threw an OutOfMemoryError:
> 
> 	Exception in thread "Simple Discovery Agent:
> java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
> java.lang.OutOfMemoryError: Java heap space
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
> 		at
> org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
> 		at
> org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
> 		at
> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
> 		at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
> 		at
> org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
> 		at
> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 		at java.lang.Thread.run(Thread.java:637)
> 
> Our logs contained repeated (and expected) messages indicating that a
> connection could not be established with the remote broker.  The one thing
> that stands out from these logs is that a new thread was created in the
> embedded broker VM on each attempt to connect to the remote broker VM:
> 
> 	[1259881226751][Thread-10] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881227757][Thread-11] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881229762][Thread-12] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	...
> 	[1259888976178][Thread-267] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889006398][Thread-268] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889036611][Thread-269] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 
> The embedded broker VM is configured via Spring as follows:
> 
> 	<amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true"
> persistent="false" useShutdownHook="true">
> 		<amq:managementContext>
> 			<amq:managementContext createConnector="false"/>
> 		</amq:managementContext>
> 		<amq:networkConnectors>
> 			<amq:networkConnector uri="static:(tcp://localhost:61616)"/>
> 		</amq:networkConnectors>
> 	</amq:broker>
> 
> Any help would be greatly appreciated.
> 
> Thanks,
> Geoff.
> 
> [1] http://activemq.apache.org/networks-of-brokers.html
> 

-- 
View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p29085359.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by Gary Tully <ga...@gmail.com>.
We are shooting for completion by the end of this month.

On 6 July 2010 15:31, dialsc <di...@bluewin.ch> wrote:
>
> any idea when 5.4.0 will be available?
>
> greez,
>
> dialsc
>
> Geoffrey Arnold wrote:
>>
>> Hi all,
>>
>> We have a forwarding bridge between an embedded broker in one VM and a
>> remote broker in another VM using the examples from the network-of-brokers
>> documentation[1].  While testing failover, we left the embedded broker VM
>> running overnight but did not start the remote broker VM.  NOTE: The
>> embedded broker VM was idle (we were not testing application logic).
>>
>> In the morning the embedded broker VM threw an OutOfMemoryError:
>>
>>       Exception in thread "Simple Discovery Agent:
>> java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
>> java.lang.OutOfMemoryError: Java heap space
>>               at
>> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
>>               at
>> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
>>               at
>> org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
>>               at
>> org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
>>               at
>> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
>>               at
>> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
>>               at
>> org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
>>               at
>> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
>>               at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>               at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>               at java.lang.Thread.run(Thread.java:637)
>>
>> Our logs contained repeated (and expected) messages indicating that a
>> connection could not be established with the remote broker.  The one thing
>> that stands out from these logs is that a new thread was created in the
>> embedded broker VM on each attempt to connect to the remote broker VM:
>>
>>       [1259881226751][Thread-10] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259881227757][Thread-11] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259881229762][Thread-12] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       ...
>>       [1259888976178][Thread-267] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259889006398][Thread-268] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>       [1259889036611][Thread-269] Could not start network bridge between:
>> vm://embeddedBroker and: tcp://localhost:61616 due to:
>> java.net.ConnectException: Connection refused
>>
>> The embedded broker VM is configured via Spring as follows:
>>
>>       <amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true"
>> persistent="false" useShutdownHook="true">
>>               <amq:managementContext>
>>                       <amq:managementContext createConnector="false"/>
>>               </amq:managementContext>
>>               <amq:networkConnectors>
>>                       <amq:networkConnector uri="static:(tcp://localhost:61616)"/>
>>               </amq:networkConnectors>
>>       </amq:broker>
>>
>> Any help would be greatly appreciated.
>>
>> Thanks,
>> Geoff.
>>
>> [1] http://activemq.apache.org/networks-of-brokers.html
>>
>
> --
> View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p29086032.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Re: OutOfMemoryError when reconnecting forwarding bridge

Posted by dialsc <di...@bluewin.ch>.
any idea when 5.4.0 will be available?

greez,

dialsc

Geoffrey Arnold wrote:
> 
> Hi all,
> 
> We have a forwarding bridge between an embedded broker in one VM and a
> remote broker in another VM using the examples from the network-of-brokers
> documentation[1].  While testing failover, we left the embedded broker VM
> running overnight but did not start the remote broker VM.  NOTE: The
> embedded broker VM was idle (we were not testing application logic).
> 
> In the morning the embedded broker VM threw an OutOfMemoryError:
> 
> 	Exception in thread "Simple Discovery Agent:
> java.util.concurrent.ThreadPoolExecutor$Worker@61472b3c"
> java.lang.OutOfMemoryError: Java heap space
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:60)
> 		at
> org.apache.activemq.openwire.OpenWireFormat.<init>(OpenWireFormat.java:69)
> 		at
> org.apache.activemq.openwire.OpenWireFormatFactory.createWireFormat(OpenWireFormatFactory.java:62)
> 		at
> org.apache.activemq.transport.TransportFactory.createWireFormat(TransportFactory.java:212)
> 		at
> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:140)
> 		at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:67)
> 		at
> org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:111)
> 		at
> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:164)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 		at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 		at java.lang.Thread.run(Thread.java:637)
> 
> Our logs contained repeated (and expected) messages indicating that a
> connection could not be established with the remote broker.  The one thing
> that stands out from these logs is that a new thread was created in the
> embedded broker VM on each attempt to connect to the remote broker VM:
> 
> 	[1259881226751][Thread-10] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881227757][Thread-11] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259881229762][Thread-12] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	...
> 	[1259888976178][Thread-267] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889006398][Thread-268] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 	[1259889036611][Thread-269] Could not start network bridge between:
> vm://embeddedBroker and: tcp://localhost:61616 due to:
> java.net.ConnectException: Connection refused
> 
> The embedded broker VM is configured via Spring as follows:
> 
> 	<amq:broker id="embeddedBroker" brokerName="embeddedBroker" useJmx="true"
> persistent="false" useShutdownHook="true">
> 		<amq:managementContext>
> 			<amq:managementContext createConnector="false"/>
> 		</amq:managementContext>
> 		<amq:networkConnectors>
> 			<amq:networkConnector uri="static:(tcp://localhost:61616)"/>
> 		</amq:networkConnectors>
> 	</amq:broker>
> 
> Any help would be greatly appreciated.
> 
> Thanks,
> Geoff.
> 
> [1] http://activemq.apache.org/networks-of-brokers.html
> 

-- 
View this message in context: http://old.nabble.com/OutOfMemoryError-when-reconnecting-forwarding-bridge-tp26647354p29086032.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.