You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Claus Ibsen (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 13:25:51 UTC
[jira] [Created] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Less verbose in log when mistyped commands at INFO level
--------------------------------------------------------
Key: KARAF-1013
URL: https://issues.apache.org/jira/browse/KARAF-1013
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Affects Versions: 2.2.2
Reporter: Claus Ibsen
Priority: Minor
If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
{code}
13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
{code}
I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-1013.
---------------------------------
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
> Attachments: karaf1013.patch
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152724#comment-13152724 ]
Jean-Baptiste Onofré commented on KARAF-1013:
---------------------------------------------
Fixed on karaf-2.2.x: revision 1203529.
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
> Attachments: karaf1013.patch
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jean-Baptiste Onofré (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1013:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Glen Mazza (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Mazza updated KARAF-1013:
------------------------------
Attachment: karaf1013.patch
Attached patch is for the 2.2.x branch. It just moves this particular type of error to the DEBUG level; I didn't see a need to suppress the error stack given that it's just a few lines.
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
> Attachments: karaf1013.patch
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1013.
-----------------------------------------
Resolution: Fixed
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
> Attachments: karaf1013.patch
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152721#comment-13152721 ]
Jean-Baptiste Onofré commented on KARAF-1013:
---------------------------------------------
Fixed on trunk: revision 1203523.
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
> Attachments: karaf1013.patch
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1013) Less verbose in log when mistyped
commands at INFO level
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1013:
----------------------------------------
Fix Version/s: 3.0.0
2.2.5
> Less verbose in log when mistyped commands at INFO level
> --------------------------------------------------------
>
> Key: KARAF-1013
> URL: https://issues.apache.org/jira/browse/KARAF-1013
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.2
> Reporter: Claus Ibsen
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
>
> If you mistype a command, then you get a verbose stracktrace in the logs at INFO level
> {code}
> 13:22:22,785 | INFO | l Console Thread | Console | 37 - org.apache.karaf.shell.console - 2.2.2.fuse-02-06 | Exception caught while executing command
> org.apache.felix.gogo.runtime.CommandNotFoundException: Command not found: osgi:header
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:471)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[37:org.apache.karaf.shell.console:2.2.2.fuse-02-06]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_26]
> {code}
> I would prefer if this was less verbose by default. And that strack traces is only included at DEBUG level etc.
> This is the case for CommandNotFoundException, and possible other exceptions where we don't need the stacktrace to make the logs verbose.
> Also if people check the logs, then they spot stacktraces, and may think that its serious problems. Which this of course is not.
> Maybe only log this at DEBUG level all together. As the end users gets reported on the shell about the unknown command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira