You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (JIRA)" <ji...@apache.org> on 2010/03/14 07:33:27 UTC
[jira] Created: (DAEMON-137) Allow to configure JNI message logging
Allow to configure JNI message logging
--------------------------------------
Key: DAEMON-137
URL: https://issues.apache.org/jira/browse/DAEMON-137
Project: Commons Daemon
Issue Type: New Feature
Components: Procrun
Affects Versions: 1.0.2
Reporter: Mladen Turk
Assignee: Mladen Turk
Fix For: 1.0.2
Currently procrun always uses vprintf callback. Add --LogJniMessages configuration option that would allow to bypass that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAEMON-137) Allow to configure JNI message
logging
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-137.
--------------------------------
Resolution: Fixed
Fixed with the 1.0.3
> Allow to configure JNI message logging
> --------------------------------------
>
> Key: DAEMON-137
> URL: https://issues.apache.org/jira/browse/DAEMON-137
> Project: Commons Daemon
> Issue Type: New Feature
> Components: Procrun
> Affects Versions: 1.0.2
> Reporter: Mladen Turk
> Assignee: Mladen Turk
> Fix For: 1.0.2
>
>
> Currently procrun always uses vprintf callback. Add --LogJniMessages configuration option that would allow to bypass that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-137) Allow to configure JNI message logging
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk updated DAEMON-137:
-------------------------------
Affects Version/s: 1.0.3
(was: 1.0.2)
> Allow to configure JNI message logging
> --------------------------------------
>
> Key: DAEMON-137
> URL: https://issues.apache.org/jira/browse/DAEMON-137
> Project: Commons Daemon
> Issue Type: New Feature
> Components: Procrun
> Affects Versions: 1.0.3
> Reporter: Mladen Turk
> Assignee: Mladen Turk
> Fix For: 1.0.2
>
>
> Currently procrun always uses vprintf callback. Add --LogJniMessages configuration option that would allow to bypass that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-137) Allow to configure JNI message logging
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk updated DAEMON-137:
-------------------------------
Fix Version/s: 1.0.3
(was: 1.0.2)
> Allow to configure JNI message logging
> --------------------------------------
>
> Key: DAEMON-137
> URL: https://issues.apache.org/jira/browse/DAEMON-137
> Project: Commons Daemon
> Issue Type: New Feature
> Components: Procrun
> Affects Versions: 1.0.3
> Reporter: Mladen Turk
> Assignee: Mladen Turk
> Fix For: 1.0.3
>
>
> Currently procrun always uses vprintf callback. Add --LogJniMessages configuration option that would allow to bypass that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.