The issue is related to the fact that there are two different solr deployments on a single tomcat, one of which knows about solr.home, and the other does not.
If there is a row in the logs which says:
org.apache.solr.core.SolrResourceLoader – Using JNDI solr.home: /opt/solr/webapps/solr1
then it actually means that some solr instance found the solr.home parameter.
But if there are multiple deployments(e.g. for sharding testing), and solr.home is set on per-deployment, and not server-wide (e.g. -Dsolr.solr.home=/some/dir
), then some deployments may fail to start.
To avoid such issues(or at least make it more debug-friendly) - one can log each Solr instance to it's own log file.