[jira] [Closed] (OFBIZ-9375) Missing Java Option solr.log.dir. Logging may be missing or incomplete

2017-06-30 Thread Jacques Le Roux (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-9375.
--
Resolution: Fixed

At revision 1800457 I reverted r1795781 and offered a better solid solution.

Byproduct: fixed imports and tabs in OFBizSolrContextFilter.java

> Missing Java Option solr.log.dir. Logging may be missing or incomplete
> --
>
> Key: OFBIZ-9375
> URL: https://issues.apache.org/jira/browse/OFBIZ-9375
> Project: OFBiz
>  Issue Type: Improvement
>  Components: lucene, solr
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Release
>
>
> I  noticed this error in trunk demo error.log
> bq. 2017-05-16 03:05:38,898 |0.0.0.0-startStop-1 |StartupLoggingUtils 
>   |E| Missing Java Option solr.log.dir. Logging may be missing or incomplete.
> It's thrown by 
> https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/servlet/StartupLoggingUtils.java
> I can't see nothing at https://localhost:8443/solr/#/~logging
> On dev ML Jinghai suggested to add
> {code}
> def jvmArguments = ['-Xms128M', '-Xmx1024M',
>   '-Dsolr.log.dir=runtime/logs',
>   '-Dsolr.log.level=INFO']
> {code}
> to main gradle. Taher mentionned that "The master build.gradle file should 
> not point to any plugins"
> I put the same in both lucene and solr components build. gradle (Solrs relies 
> on Lucene but our usage is specific) and saw no drawbacks.
> I must say I was not able to reproduce the "error" locally. But I anyway I 
> propose to commit in the 2 plugins to reassur people who could else wonder.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (OFBIZ-9375) Missing Java Option solr.log.dir. Logging may be missing or incomplete

2017-05-22 Thread Jacques Le Roux (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-9375.
--
Resolution: Implemented

> Missing Java Option solr.log.dir. Logging may be missing or incomplete
> --
>
> Key: OFBIZ-9375
> URL: https://issues.apache.org/jira/browse/OFBIZ-9375
> Project: OFBiz
>  Issue Type: Improvement
>  Components: lucene, solr
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Release
>
>
> I  noticed this error in trunk demo error.log
> bq. 2017-05-16 03:05:38,898 |0.0.0.0-startStop-1 |StartupLoggingUtils 
>   |E| Missing Java Option solr.log.dir. Logging may be missing or incomplete.
> It's thrown by 
> https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/servlet/StartupLoggingUtils.java
> I can't see nothing at https://localhost:8443/solr/#/~logging
> On dev ML Jinghai suggested to add
> {code}
> def jvmArguments = ['-Xms128M', '-Xmx1024M',
>   '-Dsolr.log.dir=runtime/logs',
>   '-Dsolr.log.level=INFO']
> {code}
> to main gradle. Taher mentionned that "The master build.gradle file should 
> not point to any plugins"
> I put the same in both lucene and solr components build. gradle (Solrs relies 
> on Lucene but our usage is specific) and saw no drawbacks.
> I must say I was not able to reproduce the "error" locally. But I anyway I 
> propose to commit in the 2 plugins to reassur people who could else wonder.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)