[GeoNetwork-devel] 61616 issue - Could not connect to broker / Connection refused

Hi,

I suppose I get this error due to a closed port 61616 on a server. There is
also a problem with data directory - but that's not related to the 61616
port, or is it?

- here is an extract from the geonetwork.log :
/WARN [org.apache.camel.component.file.FileEndpoint] - Cannot auto create
starting directory: src/test/resources
WARN [geonetwork.data.directory] - - Data directory properties is not
set. Use geonetwork.dir or geonetwork.dir properties.
WARN [geonetwork.data.directory] - - Data directory provided could not
be used. Using default location:
/var/lib/tomcat7/webapps/geonetwork/WEB-INF/data
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for 540 WARN [geonetwork.schemamanager] -
WARNING: schema-substitutions.xml has wiped out XSD substitution list for
gml:CoordinateSystemAxis
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:VerticalCS
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:CoordinateSystemAxis
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'delete-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - Cannot resolve
http://www.w3.org/2001/03/xml.xsd: will append last component to current
path (not sure it will help though!)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.lucene] - Stopwords file with incorrect ISO 639-2 language
as filename: README
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
ERROR [jeeves.engine] - Raised exception while starting the application. Fix
the error and restart.
ERROR [jeeves.engine] - Handler : org.fao.geonet.Geonetwork
ERROR [jeeves.engine] - Exception : java.lang.NullPointerException
ERROR [jeeves.engine] - Message : null
ERROR [jeeves.engine] - Stack : java.lang.NullPointerException
.../

Is there a way to switch those connections off in the GN config files -
which file would that be ? I understand that this will at least affect
harvesting functionalities, but I'd want to verify first if the deployment
procedure can terminate successfully and deal with the server's ports
configuration later.

Thanks in advance for the contributions !

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version "1.8.0_121"
Tomcat 7)/

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

Hi,

That's defined here:
https://github.com/geonetwork/core-geonetwork/blob/develop/pom.xml#L1224

Which is later used in:
workers/wfsfeature-harvester/src/main/resources/config-spring-geonetwork-jms.xml:
     <amq:transportConnector uri="${jms.url}" />
workers/wfsfeature-harvester/src/main/resources/config-spring-geonetwork-jms.xml:
       <property name="brokerURL" value="${jms.url}"/>
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
<amq:transportConnector uri="${jms.url}" />
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
  <property name="brokerURL" value="${jms.url}"/>
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
<property name="jmsUrl" value="${jms.url}"/

Regards,
María.

On Tue, May 9, 2017 at 11:43 AM, zer0mode <otoncopi@anonymised.com> wrote:

Hi,

I suppose I get this error due to a closed port 61616 on a server. There is
also a problem with data directory - but that's not related to the 61616
port, or is it?

- here is an extract from the geonetwork.log :
/WARN [org.apache.camel.component.file.FileEndpoint] - Cannot auto create
starting directory: src/test/resources
WARN [geonetwork.data.directory] - - Data directory properties is not
set. Use geonetwork.dir or geonetwork.dir properties.
WARN [geonetwork.data.directory] - - Data directory provided could not
be used. Using default location:
/var/lib/tomcat7/webapps/geonetwork/WEB-INF/data
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for 540 WARN [geonetwork.schemamanager] -
WARNING: schema-substitutions.xml has wiped out XSD substitution list for
gml:CoordinateSystemAxis
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:VerticalCS
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:CoordinateSystemAxis
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'delete-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - Cannot resolve
http://www.w3.org/2001/03/xml.xsd: will append last component to current
path (not sure it will help though!)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.lucene] - Stopwords file with incorrect ISO 639-2 language
as filename: README
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
ERROR [jeeves.engine] - Raised exception while starting the application. Fix
the error and restart.
ERROR [jeeves.engine] - Handler : org.fao.geonet.Geonetwork
ERROR [jeeves.engine] - Exception : java.lang.NullPointerException
ERROR [jeeves.engine] - Message : null
ERROR [jeeves.engine] - Stack : java.lang.NullPointerException
.../

Is there a way to switch those connections off in the GN config files -
which file would that be ? I understand that this will at least affect
harvesting functionalities, but I'd want to verify first if the deployment
procedure can terminate successfully and deal with the server's ports
configuration later.

Thanks in advance for the contributions !

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version "1.8.0_121"
Tomcat 7)/

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Hi,

So you want to turn off the WFS feature harvester? You can try to
comment that dependency on the pom.xml file of the web project. But
maybe that will lead to other issues.

On Tue, May 9, 2017 at 11:51 AM, María Arias de Reyna <delawen@anonymised.com.> wrote:

Hi,

That's defined here:
https://github.com/geonetwork/core-geonetwork/blob/develop/pom.xml#L1224

Which is later used in:
workers/wfsfeature-harvester/src/main/resources/config-spring-geonetwork-jms.xml:
     <amq:transportConnector uri="${jms.url}" />
workers/wfsfeature-harvester/src/main/resources/config-spring-geonetwork-jms.xml:
       <property name="brokerURL" value="${jms.url}"/>
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
<amq:transportConnector uri="${jms.url}" />
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
  <property name="brokerURL" value="${jms.url}"/>
messaging/src/main/resources/config-spring-geonetwork-parent.xml:
<property name="jmsUrl" value="${jms.url}"/

Regards,
María.

On Tue, May 9, 2017 at 11:43 AM, zer0mode <otoncopi@anonymised.com> wrote:

Hi,

I suppose I get this error due to a closed port 61616 on a server. There is
also a problem with data directory - but that's not related to the 61616
port, or is it?

- here is an extract from the geonetwork.log :
/WARN [org.apache.camel.component.file.FileEndpoint] - Cannot auto create
starting directory: src/test/resources
WARN [geonetwork.data.directory] - - Data directory properties is not
set. Use geonetwork.dir or geonetwork.dir properties.
WARN [geonetwork.data.directory] - - Data directory provided could not
be used. Using default location:
/var/lib/tomcat7/webapps/geonetwork/WEB-INF/data
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for 540 WARN [geonetwork.schemamanager] -
WARNING: schema-substitutions.xml has wiped out XSD substitution list for
gml:CoordinateSystemAxis
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:VerticalCS
WARN [geonetwork.schemamanager] - WARNING: schema-substitutions.xml has
wiped out XSD substitution list for gml:CoordinateSystemAxis
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'delete-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
WARN [geonetwork.schemamanager] - Cannot resolve
http://www.w3.org/2001/03/xml.xsd: will append last component to current
path (not sure it will help though!)
WARN [geonetwork.schemamanager] - WARNING: gco:Record is a global element
without a type - assuming a string
WARN [geonetwork.lucene] - Stopwords file with incorrect ISO 639-2 language
as filename: README
ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] -
Could not refresh JMS Connection for destination 'harvest-wfs-features' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
(Connection refused)
ERROR [jeeves.engine] - Raised exception while starting the application. Fix
the error and restart.
ERROR [jeeves.engine] - Handler : org.fao.geonet.Geonetwork
ERROR [jeeves.engine] - Exception : java.lang.NullPointerException
ERROR [jeeves.engine] - Message : null
ERROR [jeeves.engine] - Stack : java.lang.NullPointerException
.../

Is there a way to switch those connections off in the GN config files -
which file would that be ? I understand that this will at least affect
harvesting functionalities, but I'd want to verify first if the deployment
procedure can terminate successfully and deal with the server's ports
configuration later.

Thanks in advance for the contributions !

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version "1.8.0_121"
Tomcat 7)/

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Hi Maria, thanks for the quick response. Yes, simply said that's what I'd
like - to turn off WFS feature harvester.

I don't find that section in the pom.xml file (it resides in
/var/lib/tomcat7/webapps/geonetwork/META-INF/maven/org.geonetwork-opensource/web-app).

In fact a search for a file including the pattern 'localhost:61616' gives no
results.

So for the moment I couldn't disable that via the GN configuration. As you
say, that might provoke other issues, but I don't have other options since
the server is opened only for specific ports and 61616 is not one of them.

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5319880.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

Hi

In fact a search for a file including the pattern ‘localhost:61616’ gives no
results.

Look for 61616 instead. The localhost might be replaced with your hostname.
Did you build the sources or are you talking about the war ?

···

On Tue, May 9, 2017 at 2:19 PM, zer0mode <otoncopi@anonymised.com…> wrote:

Hi Maria, thanks for the quick response. Yes, simply said that’s what I’d
like - to turn off WFS feature harvester.

I don’t find that section in the pom.xml file (it resides in
/var/lib/tomcat7/webapps/geonetwork/META-INF/maven/org.geonetwork-opensource/web-app).

In fact a search for a file including the pattern ‘localhost:61616’ gives no
results.

So for the moment I couldn’t disable that via the GN configuration. As you
say, that might provoke other issues, but I don’t have other options since
the server is opened only for specific ports and 61616 is not one of them.


View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5319880.html

Sent from the GeoNetwork developer mailing list archive at Nabble.com.


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


GeoNetwork-devel mailing list
GeoNetwork-devel@…537…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Florent Gravin
0479444492

Hi Florent,

Deployment is done by war file. I'm afraid neither '61616' locates no files.

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version "1.8.0_121"
Tomcat 7)/

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5319903.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

Hi,

/var/lib/tomcat7/webapps/geonetwork/WEB-INF/lib$ zipgrep “61616” wfsfeature-harvester-3.2.2-SNAPSHOT.jar

config-spring-geonetwork-jms.xml: <amq:transportConnector uri=“tcp://localhost:61616” />
config-spring-geonetwork-jms.xml:

It is in a JAR file.
You need to rebuild your war after changing the port.

···

On Tue, May 9, 2017 at 3:20 PM, zer0mode <otoncopi@anonymised.com> wrote:

Hi Florent,

Deployment is done by war file. I’m afraid neither ‘61616’ locates no files.

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version “1.8.0_121”
Tomcat 7)/


View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5319903.html

Sent from the GeoNetwork developer mailing list archive at Nabble.com.


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


GeoNetwork-devel mailing list
GeoNetwork-devel@…537…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Florent Gravin
0479444492

Hi

At least in latest 3.2.x branch I see this:

geonetwork/WEB-INF/config.properties

language.default=eng

language.forceDefault=false

jms.url=tcp://localhost:61616

But not sure if in 3.2.1 or previous versions was different.

Regards,
Jose García

···

On Tue, May 9, 2017 at 3:33 PM, Florent Gravin <florent.gravin@anonymised.com> wrote:

Hi,

/var/lib/tomcat7/webapps/geonetwork/WEB-INF/lib$ zipgrep “61616” wfsfeature-harvester-3.2.2-SNAPSHOT.jar

config-spring-geonetwork-jms.xml: <amq:transportConnector uri=“tcp://localhost:61616” />
config-spring-geonetwork-jms.xml:

It is in a JAR file.
You need to rebuild your war after changing the port.


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


GeoNetwork-devel mailing list
GeoNetwork-devel@…537…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

On Tue, May 9, 2017 at 3:20 PM, zer0mode <otoncopi@anonymised.com…1151…> wrote:

Hi Florent,

Deployment is done by war file. I’m afraid neither ‘61616’ locates no files.

/(GN 3.2 deployed with war on
Debian GNU/Linux 8.7
Apache/2.4.10
openjdk version “1.8.0_121”
Tomcat 7)/


View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5319903.html

Sent from the GeoNetwork developer mailing list archive at Nabble.com.


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comorge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Florent Gravin
0479444492

Vriendelijke groeten / Kind regards,

Jose García


Veenderweg 13
6721 WD Bennekom
The Netherlands
T: +31 (0)318 416664

Please consider the environment before printing this email.

The issue was resolved server-side by adding an ip rule in the iptables (as
stated in the first post, the deployment was done on a server with blocked
traffic).

@Jose Garcia : In the latest version, deployed using war (3.2.1), there is
no line with jms.url in the config.properties file.

@Florent gravin-2 : I removed the port and left only localhost, like this :
/config-spring-geonetwork-jms.xml: <amq:transportConnector
uri="tcp://localhost" />
config-spring-geonetwork-jms.xml: <property name="brokerURL"
value="tcp://localhost"/>/

Then repacked and redeployed the war file, but the error persisted.

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5322240.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

Hi,

IMO the WFS indexer should launched as an option, we sould have a setting or a maven profile to tell we don’t want it and nothing would listen on that port (JMS).

···

On Tue, May 30, 2017 at 9:48 AM, zer0mode <otoncopi@anonymised.com> wrote:

The issue was resolved server-side by adding an ip rule in the iptables (as
stated in the first post, the deployment was done on a server with blocked
traffic).

@Jose Garcia : In the latest version, deployed using war (3.2.1), there is
no line with jms.url in the config.properties file.

@Florent gravin-2 : I removed the port and left only localhost, like this :
/config-spring-geonetwork-jms.xml: <amq:transportConnector
uri=“tcp://localhost” />
config-spring-geonetwork-jms.xml: /

Then repacked and redeployed the war file, but the error persisted.


View this message in context: http://osgeo-org.1560.x6.nabble.com/61616-issue-Could-not-connect-to-broker-Connection-refused-tp5319851p5322240.html

Sent from the GeoNetwork developer mailing list archive at Nabble.com.


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


GeoNetwork-devel mailing list
GeoNetwork-devel@…537…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Florent Gravin
0479444492