cancel
Showing results for 
Search instead for 
Did you mean: 

nuxeo.xml file does not reflect nuxeo.conf parameter change.

yginieys_
Champ in-the-making
Champ in-the-making

Using nuxeo 5.5, I changed the SMTP configuration in the Admin console, but it has no effect (even after restart). The default configuration is still used (mail.smtp.host=localhost).

The nuxeo.conf file includes the correct SMTP parameters (mail.smtp.host=<correct_smtp>).

The issue is with the nuxeo.xml configuration file located in NUXEO_HOME/conf/Catalina/localhost which contains the old default parameter.

This file is left unchanged by the restarts. I guess the nuxeo.xml file should be rewrited at each restart to include nuxeo.conf updated values.

Is it right ?

What is the the correct value to be found in the live nuxeo.xml ?

Something like :

<Resource auth="Container" name="Mail" type="javax.mail.Session"
        mail.store.protocol="pop3"
        mail.pop3.host="pop3.nosuchhost.nosuchdomain.com"
        mail.pop3.user="nobody"
        mail.transport.protocol="smtp"
        mail.smtp.host="localhost" mail.smtp.port="25"
        mail.smtp.starttls.enable="false"
        mail.smtp.auth="false"
        mail.smtp.user="anonymous"
        password="password" mail.from="noreply@nuxeo.com"
        mail.debug="false" />

Or something like :

<Resource auth="Container" name="Mail" type="javax.mail.Session"
        mail.store.protocol="${mail.store.protocol}"
        mail.pop3.host="${mail.pop3.host}"
        mail.pop3.user="${mail.user}"
        mail.transport.protocol="${mail.transport.protocol}"
        mail.smtp.host="${mail.smtp.host}" mail.smtp.port="${mail.smtp.port}"
        mail.smtp.starttls.enable="${mail.smtp.usetls}"
        mail.smtp.auth="${mail.smtp.auth}"
        mail.smtp.user="${mail.smtp.username}"
        password="${mail.smtp.password}" mail.from="${mail.from}"
        mail.debug="${mail.debug}" />

Thanks

1 ACCEPTED ANSWER

Julien_Carsique
Elite Collaborator
Elite Collaborator

You're right.

At startup (or simply by running ./bin/nuxeoctl configure), the file conf/Catalina/localhost/nuxeo.xml must be overwritten by templates/default/conf/Catalina/localhost/nuxeo.xml with the values you customized in nuxeo.conf.

Which configuration templates do you use (what is the value of nuxeo.templates)?

View answer in original post

12 REPLIES 12

Julien_Carsique
Elite Collaborator
Elite Collaborator

You're right.

At startup (or simply by running ./bin/nuxeoctl configure), the file conf/Catalina/localhost/nuxeo.xml must be overwritten by templates/default/conf/Catalina/localhost/nuxeo.xml with the values you customized in nuxeo.conf.

Which configuration templates do you use (what is the value of nuxeo.templates)?

Here are the templates we are using

As suggested by Benjamin, check the value of nuxeo.force.generation.

I've found something interesting.

Ok, that's the issue. It comes from the "target" path used by templates. Look into templates/default/nuxeo.defaults, there must be

With the default target value, the wrong path should be nxserver/conf/Catalina/localhost/nuxeo.xml, whereas server/default/deploy/... looks like a JBoss path, I wonder where it comes from. Didn't you mixed Tomcat and JBoss packages or templates? Or don't you have some JBoss properties in /etc/init.d/nuxeo?

Thanks Julien.

The *.target property in each nuxeo.defaults file must be named accordingly to its container template. Here, it must be named "stepnet.target" so it won't override the one of the "default" template.

I have got the same problem and I have noticed the following thing