[ 
https://issues.apache.org/jira/browse/JAMES-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144670#comment-17144670
 ] 

David Leangen commented on JAMES-3251:
--------------------------------------

Even when I turn all output to "OFF", this still gets logged to the console:

{noformat}
james_1  | WARNING: An illegal reflective access operation has occurred
james_1  | WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/opt/apache-james/james-basic-server/lib/guice-4.2.2.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
james_1  | WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
james_1  | WARNING: Use --illegal-access=warn to enable warnings of further 
illegal reflective access operations
james_1  | WARNING: All illegal access operations will be denied in a future 
release
james_1  | 46  Global  WARN   [main] openjpa.Runtime - Could not create the 
optional validation provider. Reason returned: "A default ValidatorFactory 
could not be created."
james_1  | 1014  Global  INFO   [main] openjpa.Runtime - Starting OpenJPA 3.1.0
james_1  | 1121  Global  INFO   [main] openjpa.jdbc.JDBC - Using dictionary 
class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
james_1  | 2371  Global  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache 
Derby version 10.10 using JDBC driver Apache Derby Embedded JDBC Driver version 
10.14.2.0 - (1828579).

{noformat}

Does anybody know why, and how I can regain control of these messages?

> Reduce INFO chatter for Basic Server
> ------------------------------------
>
>                 Key: JAMES-3251
>                 URL: https://issues.apache.org/jira/browse/JAMES-3251
>             Project: James Server
>          Issue Type: Sub-task
>            Reporter: David Leangen
>            Priority: Major
>
> In the context of the *Basic Server*, based on the principle that the 
> Operator does not know (and does not need to know) the internals of the 
> system:
>  # Reduce the Operator's log output to the absolute minimum (in one way or 
> another)
>  # Ensure that any output is useful and actionable in the Basic context
>  # Consider what to do with regard to diagnostic information that, in the 
> case of a problem, would allow experienced James Developers to assist when 
> necessary
> This issue focuses only on point #1 in the above list. Once that is 
> completed, we should consider the other two points.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to