Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi, I am having the same error and I was wondering if you could find a solution? Thank you. -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
As Andrea said "peer to peer in the default configuration requires
*multicast* to be enabled in your network" and sometimes this is not the
case.
If multicast is enabled in your network and with the firewalls
deactivated I cannot think about anything else at the moment :(
If nothing works I would suggest do a try with a standalone ActiveMQ.
On 09/21/2016 09:38 PM, Kevin Berger wrote:
Hello,
As a follow-up, on the network side we have turned off the firewalls
on the 2 geoservers and we are still getting the error. The error
message below indicates it is trying to start a network bridge with
itself - communicate between its own instanceName and localhost
(127.0.0.1)). Is this expected behaviour – or should it try to start a
bridge with another server instance?
We have GeoServer 2.8.2 installed with Java 8 Update 92.
2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] -
Could not start network bridge between:
vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true
and: nio://127.0.0.1:57496 <http://127.0.0.1:57496> due to:
java.net.ConnectException: Connection refused: no further information
Is there any other suggestions we can try? Maybe a configuration tweak
somewhere?
Kevin
*From:*Kevin Berger
*Sent:* September 21, 2016 10:43
*To:* 'Nuno Oliveira'; Andrea Aime
*Cc:* geoserver-users@lists.sourceforge.net
*Subject:* RE: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi Nuno,
We verified that the logs match the contents as outlined below, so we
will consider the brokers are correctly enabled. We will proceed to
look at the network. Thanks for your feedback.
Kevin
*From:*Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it]
*Sent:* September 21, 2016 10:28
*To:* Kevin Berger; Andrea Aime
*Cc:* geoserver-users@lists.sourceforge.net
<mailto:geoserver-users@lists.sourceforge.net>
*Subject:* Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi,
The ERROR line in the log is a "false error" that log should actually
be a INFO.
Debugging the embedded broker is not very easy since he don't have access
to ActiveMQ web console.
In fact you can consider the broker is correctly enable if you have
something like this:
21 Sep 17:17:50 ERROR [cluster.impl] - Started the embedded brokerURI:
BrokerService[f088d295-ab15-470a-a45e-bba8cc3fad8a]
21 Sep 17:17:50 INFO [cluster.client] - Connecting...
21 Sep 17:17:50 INFO [cluster.impl] - Using brokerURI:
vm://f088d295-ab15-470a-a45e-bba8cc3fad8a?create=false&waitForStart=5000
21 Sep 17:17:50 INFO [cluster.client] - Registration...
21 Sep 17:17:50 INFO [cluster.client] - Impossible to register
GeoServer with destination, waiting...
21 Sep 17:17:50 INFO [cluster.client] - Waiting for registration...(1/3)
21 Sep 17:17:50 WARN [TransportConnection.Transport] - Transport
Connection to: tcp://127.0.0.1:58474 failed: java.io.EOFException
21 Sep 17:18:00 INFO [cluster.client] - Registration...
21 Sep 17:18:00 INFO [cluster.client] - Now GeoServer is registered
with the destination
21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event
publisher...
21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event
publisher...
Regards,
Nuno Oliveira
On 09/21/2016 05:06 PM, Kevin Berger wrote:
Hi Andrea,
The GUI page indicates Embedded broker is enabled.
Logs appear to indicate broker is enabled. Getting messages like:
2016-09-21 08:02:56,277 ERROR [cluster.impl] - Started the
embedded brokerURI:
BrokerService[3404d32d-6cd6-4ccb-a9f8-2ee428c12977]
2016-09-21 08:02:56,277 INFO [cluster.client] - Connecting...
2016-09-21 08:02:56,277 INFO [cluster.impl] - Using brokerURI:
vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?create=false&waitForStart=5000
Although we are not sure why the Started the embedded line
indicates ERROR (is this a true error; or false reprting)
As I think we can conclude embedded broker is enabled, looking at
the network is our second troubleshooting step so we will
investigate that angle.
Thanks for your feedback.
Kevin
*From:*andrea.a...@gmail.com <mailto:andrea.a...@gmail.com>
[mailto:andrea.a...@gmail.com] *On Behalf Of *Andrea Aime
*Sent:* September 21, 2016 09:31
*To:* Kevin Berger
*Cc:* geoserver-users@lists.sourceforge.net
<mailto:geoserver-users@lists.sourceforge.net>
*Subject:* Re: [Geoserver-users] GeoServer Clustering - Embedded
Brokers
Hi Kevin,
I'm just going by memory, but believe you can simply look at the
configuration page for the cluster to
check if the embedded broker is enabled? It should also be logging
on the logs on startup.
However, per to peer in the default configuration requires
multicast to be enabled in your network, so that nodes
can find each other. Is that the case for you?
Cheers
Andrea
On Wed
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hello, As a follow-up, on the network side we have turned off the firewalls on the 2 geoservers and we are still getting the error. The error message below indicates it is trying to start a network bridge with itself - communicate between its own instanceName and localhost (127.0.0.1)). Is this expected behaviour - or should it try to start a bridge with another server instance? We have GeoServer 2.8.2 installed with Java 8 Update 92. 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496<http://127.0.0.1:57496> due to: java.net.ConnectException: Connection refused: no further information Is there any other suggestions we can try? Maybe a configuration tweak somewhere? Kevin From: Kevin Berger Sent: September 21, 2016 10:43 To: 'Nuno Oliveira'; Andrea Aime Cc: geoserver-users@lists.sourceforge.net Subject: RE: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi Nuno, We verified that the logs match the contents as outlined below, so we will consider the brokers are correctly enabled. We will proceed to look at the network. Thanks for your feedback. Kevin From: Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it] Sent: September 21, 2016 10:28 To: Kevin Berger; Andrea Aime Cc: geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Subject: Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi, The ERROR line in the log is a "false error" that log should actually be a INFO. Debugging the embedded broker is not very easy since he don't have access to ActiveMQ web console. In fact you can consider the broker is correctly enable if you have something like this: 21 Sep 17:17:50 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[f088d295-ab15-470a-a45e-bba8cc3fad8a] 21 Sep 17:17:50 INFO [cluster.client] - Connecting... 21 Sep 17:17:50 INFO [cluster.impl] - Using brokerURI: vm://f088d295-ab15-470a-a45e-bba8cc3fad8a?create=false&waitForStart=5000 21 Sep 17:17:50 INFO [cluster.client] - Registration... 21 Sep 17:17:50 INFO [cluster.client] - Impossible to register GeoServer with destination, waiting... 21 Sep 17:17:50 INFO [cluster.client] - Waiting for registration...(1/3) 21 Sep 17:17:50 WARN [TransportConnection.Transport] - Transport Connection to: tcp://127.0.0.1:58474 failed: java.io.EOFException 21 Sep 17:18:00 INFO [cluster.client] - Registration... 21 Sep 17:18:00 INFO [cluster.client] - Now GeoServer is registered with the destination 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... Regards, Nuno Oliveira On 09/21/2016 05:06 PM, Kevin Berger wrote: Hi Andrea, The GUI page indicates Embedded broker is enabled. Logs appear to indicate broker is enabled. Getting messages like: 2016-09-21 08:02:56,277 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[3404d32d-6cd6-4ccb-a9f8-2ee428c12977] 2016-09-21 08:02:56,277 INFO [cluster.client] - Connecting... 2016-09-21 08:02:56,277 INFO [cluster.impl] - Using brokerURI: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?create=false&waitForStart=5000 Although we are not sure why the Started the embedded line indicates ERROR (is this a true error; or false reprting) As I think we can conclude embedded broker is enabled, looking at the network is our second troubleshooting step so we will investigate that angle. Thanks for your feedback. Kevin From: andrea.a...@gmail.com<mailto:andrea.a...@gmail.com> [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: September 21, 2016 09:31 To: Kevin Berger Cc: geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Subject: Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi Kevin, I'm just going by memory, but believe you can simply look at the configuration page for the cluster to check if the embedded broker is enabled? It should also be logging on the logs on startup. However, per to peer in the default configuration requires multicast to be enabled in your network, so that nodes can find each other. Is that the case for you? Cheers Andrea On Wed, Sep 21, 2016 at 4:19 PM, Kevin Berger mailto:kevin.ber...@silvacom.com>> wrote: Hello, We have set up clustering between 2 geoservers. We want to implement the "Peer-to-peer newtork with embedded brokers and shared data directory" topology. We are using the default cluster configuration (broker.xml; cluster.properties; embedded-broker.properties). However, the geoserver.log is reporting errors like: 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?a
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi Nuno, We verified that the logs match the contents as outlined below, so we will consider the brokers are correctly enabled. We will proceed to look at the network. Thanks for your feedback. Kevin From: Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it] Sent: September 21, 2016 10:28 To: Kevin Berger; Andrea Aime Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi, The ERROR line in the log is a "false error" that log should actually be a INFO. Debugging the embedded broker is not very easy since he don't have access to ActiveMQ web console. In fact you can consider the broker is correctly enable if you have something like this: 21 Sep 17:17:50 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[f088d295-ab15-470a-a45e-bba8cc3fad8a] 21 Sep 17:17:50 INFO [cluster.client] - Connecting... 21 Sep 17:17:50 INFO [cluster.impl] - Using brokerURI: vm://f088d295-ab15-470a-a45e-bba8cc3fad8a?create=false&waitForStart=5000 21 Sep 17:17:50 INFO [cluster.client] - Registration... 21 Sep 17:17:50 INFO [cluster.client] - Impossible to register GeoServer with destination, waiting... 21 Sep 17:17:50 INFO [cluster.client] - Waiting for registration...(1/3) 21 Sep 17:17:50 WARN [TransportConnection.Transport] - Transport Connection to: tcp://127.0.0.1:58474 failed: java.io.EOFException 21 Sep 17:18:00 INFO [cluster.client] - Registration... 21 Sep 17:18:00 INFO [cluster.client] - Now GeoServer is registered with the destination 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... Regards, Nuno Oliveira On 09/21/2016 05:06 PM, Kevin Berger wrote: Hi Andrea, The GUI page indicates Embedded broker is enabled. Logs appear to indicate broker is enabled. Getting messages like: 2016-09-21 08:02:56,277 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[3404d32d-6cd6-4ccb-a9f8-2ee428c12977] 2016-09-21 08:02:56,277 INFO [cluster.client] - Connecting... 2016-09-21 08:02:56,277 INFO [cluster.impl] - Using brokerURI: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?create=false&waitForStart=5000 Although we are not sure why the Started the embedded line indicates ERROR (is this a true error; or false reprting) As I think we can conclude embedded broker is enabled, looking at the network is our second troubleshooting step so we will investigate that angle. Thanks for your feedback. Kevin From: andrea.a...@gmail.com<mailto:andrea.a...@gmail.com> [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: September 21, 2016 09:31 To: Kevin Berger Cc: geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Subject: Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi Kevin, I'm just going by memory, but believe you can simply look at the configuration page for the cluster to check if the embedded broker is enabled? It should also be logging on the logs on startup. However, per to peer in the default configuration requires multicast to be enabled in your network, so that nodes can find each other. Is that the case for you? Cheers Andrea On Wed, Sep 21, 2016 at 4:19 PM, Kevin Berger mailto:kevin.ber...@silvacom.com>> wrote: Hello, We have set up clustering between 2 geoservers. We want to implement the "Peer-to-peer newtork with embedded brokers and shared data directory" topology. We are using the default cluster configuration (broker.xml; cluster.properties; embedded-broker.properties). However, the geoserver.log is reporting errors like: 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496<http://127.0.0.1:57496> due to: java.net.ConnectException: Connection refused: no further information As a first troubleshooting step, we want to verify embedded broker is running on each server. Is there a way to verify the embedded broker is running? Thanks, Kevin -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s all
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi, The ERROR line in the log is a "false error" that log should actually be a INFO. Debugging the embedded broker is not very easy since he don't have access to ActiveMQ web console. In fact you can consider the broker is correctly enable if you have something like this: 21 Sep 17:17:50 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[f088d295-ab15-470a-a45e-bba8cc3fad8a] 21 Sep 17:17:50 INFO [cluster.client] - Connecting... 21 Sep 17:17:50 INFO [cluster.impl] - Using brokerURI: vm://f088d295-ab15-470a-a45e-bba8cc3fad8a?create=false&waitForStart=5000 21 Sep 17:17:50 INFO [cluster.client] - Registration... 21 Sep 17:17:50 INFO [cluster.client] - Impossible to register GeoServer with destination, waiting... 21 Sep 17:17:50 INFO [cluster.client] - Waiting for registration...(1/3) 21 Sep 17:17:50 WARN [TransportConnection.Transport] - Transport Connection to: tcp://127.0.0.1:58474 failed: java.io.EOFException 21 Sep 17:18:00 INFO [cluster.client] - Registration... 21 Sep 17:18:00 INFO [cluster.client] - Now GeoServer is registered with the destination 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... 21 Sep 17:18:00 INFO [cluster.server] - Activating JMS Catalog event publisher... Regards, Nuno Oliveira On 09/21/2016 05:06 PM, Kevin Berger wrote: Hi Andrea, The GUI page indicates Embedded broker is enabled. Logs appear to indicate broker is enabled. Getting messages like: 2016-09-21 08:02:56,277 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[3404d32d-6cd6-4ccb-a9f8-2ee428c12977] 2016-09-21 08:02:56,277 INFO [cluster.client] - Connecting... 2016-09-21 08:02:56,277 INFO [cluster.impl] - Using brokerURI: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?create=false&waitForStart=5000 Although we are not sure why the Started the embedded line indicates ERROR (is this a true error; or false reprting) As I think we can conclude embedded broker is enabled, looking at the network is our second troubleshooting step so we will investigate that angle. Thanks for your feedback. Kevin *From:*andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] *On Behalf Of *Andrea Aime *Sent:* September 21, 2016 09:31 *To:* Kevin Berger *Cc:* geoserver-users@lists.sourceforge.net *Subject:* Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi Kevin, I'm just going by memory, but believe you can simply look at the configuration page for the cluster to check if the embedded broker is enabled? It should also be logging on the logs on startup. However, per to peer in the default configuration requires multicast to be enabled in your network, so that nodes can find each other. Is that the case for you? Cheers Andrea On Wed, Sep 21, 2016 at 4:19 PM, Kevin Berger mailto:kevin.ber...@silvacom.com>> wrote: Hello, We have set up clustering between 2 geoservers. We want to implement the "Peer-to-peer newtork with embedded brokers and shared data directory" topology. We are using the default cluster configuration (broker.xml; cluster.properties; embedded-broker.properties). However, the geoserver.log is reporting errors like: 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496 <http://127.0.0.1:57496> due to: java.net.ConnectException: Connection refused: no further information As a first troubleshooting step, we want to verify embedded broker is running on each server. Is there a way to verify the embedded broker is running? Thanks, Kevin -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net <mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi Andrea, The GUI page indicates Embedded broker is enabled. Logs appear to indicate broker is enabled. Getting messages like: 2016-09-21 08:02:56,277 ERROR [cluster.impl] - Started the embedded brokerURI: BrokerService[3404d32d-6cd6-4ccb-a9f8-2ee428c12977] 2016-09-21 08:02:56,277 INFO [cluster.client] - Connecting... 2016-09-21 08:02:56,277 INFO [cluster.impl] - Using brokerURI: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?create=false&waitForStart=5000 Although we are not sure why the Started the embedded line indicates ERROR (is this a true error; or false reprting) As I think we can conclude embedded broker is enabled, looking at the network is our second troubleshooting step so we will investigate that angle. Thanks for your feedback. Kevin From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: September 21, 2016 09:31 To: Kevin Berger Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers Hi Kevin, I'm just going by memory, but believe you can simply look at the configuration page for the cluster to check if the embedded broker is enabled? It should also be logging on the logs on startup. However, per to peer in the default configuration requires multicast to be enabled in your network, so that nodes can find each other. Is that the case for you? Cheers Andrea On Wed, Sep 21, 2016 at 4:19 PM, Kevin Berger mailto:kevin.ber...@silvacom.com>> wrote: Hello, We have set up clustering between 2 geoservers. We want to implement the "Peer-to-peer newtork with embedded brokers and shared data directory" topology. We are using the default cluster configuration (broker.xml; cluster.properties; embedded-broker.properties). However, the geoserver.log is reporting errors like: 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496<http://127.0.0.1:57496> due to: java.net.ConnectException: Connection refused: no further information As a first troubleshooting step, we want to verify embedded broker is running on each server. Is there a way to verify the embedded broker is running? Thanks, Kevin -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] GeoServer Clustering - Embedded Brokers
Hi Kevin, I'm just going by memory, but believe you can simply look at the configuration page for the cluster to check if the embedded broker is enabled? It should also be logging on the logs on startup. However, per to peer in the default configuration requires multicast to be enabled in your network, so that nodes can find each other. Is that the case for you? Cheers Andrea On Wed, Sep 21, 2016 at 4:19 PM, Kevin Berger wrote: > Hello, > > > > We have set up clustering between 2 geoservers. We want to implement the > "Peer-to-peer newtork with embedded brokers and shared data directory" > topology. > > > > We are using the default cluster configuration (broker.xml; > cluster.properties; embedded-broker.properties). However, the geoserver.log > is reporting errors like: > > 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could > not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8- > 2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496 due to: > java.net.ConnectException: Connection refused: no further information > > > > As a first troubleshooting step, we want to verify embedded broker is > running on each server. Is there a way to verify the embedded broker is > running? > > > > Thanks, > > > > Kevin > > > -- > > ___ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] GeoServer Clustering - Embedded Brokers
Hello, We have set up clustering between 2 geoservers. We want to implement the "Peer-to-peer newtork with embedded brokers and shared data directory" topology. We are using the default cluster configuration (broker.xml; cluster.properties; embedded-broker.properties). However, the geoserver.log is reporting errors like: 2016-09-21 08:10:43,834 WARN [network.DiscoveryNetworkConnector] - Could not start network bridge between: vm://3404d32d-6cd6-4ccb-a9f8-2ee428c12977?async=false&network=true and: nio://127.0.0.1:57496 due to: java.net.ConnectException: Connection refused: no further information As a first troubleshooting step, we want to verify embedded broker is running on each server. Is there a way to verify the embedded broker is running? Thanks, Kevin -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
