[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337206#comment-15337206
]
ASF subversion and git services commented on SOLR-8676:
---
Commit c20b41fe6b1d023a5bdf30e39afa1b470597bcc5 in lucene-solr's branch
refs/heads/branch_5x from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c20b41f ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Fix For: 5.6, 6.1, 5.5.2, master (7.0), 6.0.2
>
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337207#comment-15337207
]
ASF subversion and git services commented on SOLR-8676:
---
Commit 60c140c244c4f93bbd3af2fe1b6244101a8db971 in lucene-solr's branch
refs/heads/branch_6_0 from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=60c140c ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Fix For: 5.6, 6.1, 5.5.2, master (7.0), 6.0.2
>
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337204#comment-15337204
]
ASF subversion and git services commented on SOLR-8676:
---
Commit 3d8a6b0cb8be7c5e7fc683d13034d74d46238c44 in lucene-solr's branch
refs/heads/branch_5_5 from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3d8a6b0 ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Fix For: 5.6, 6.1, 5.5.2, master (7.0), 6.0.2
>
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317226#comment-15317226
]
ASF subversion and git services commented on SOLR-8676:
---
Commit 87d46225cdc80f515ecd191fe618d2942eab8289 in lucene-solr's branch
refs/heads/branch_6x from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=87d4622 ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317224#comment-15317224
]
ASF subversion and git services commented on SOLR-8676:
---
Commit 00602a3a7a3f6542ff2993bf6f2fb8f6edbd9c22 in lucene-solr's branch
refs/heads/master from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=00602a3 ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314246#comment-15314246
]
Ahmet Arslan commented on SOLR-8676:
[~mkhludnev] do you mind looking into SOLR-8445 too?
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows
[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305248#comment-15305248
]
Mikhail Khludnev commented on SOLR-8676:
[~thelabdude], do you have an any objections? I see that {{LOG4J_CONFIG}} set
to empty for non-example launch during SOLR-6833.
> It's not possible to use a different log4.properties file on windows
>
>
> Key: SOLR-8676
> URL: https://issues.apache.org/jira/browse/SOLR-8676
> Project: Solr
> Issue Type: Bug
>Affects Versions: 5.4.1
>Reporter: Kristine Jetzke
>Assignee: Mikhail Khludnev
> Attachments: SOLR-8676.patch
>
>
> It's currently not possible to change the location of the log4j.properties
> file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the
> default value {{server\resources\log4j.properties}}. Thus, this file inside
> the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why
> {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works
> when running an example so I hope that this line is really just obsolete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
