[
https://issues.apache.org/jira/browse/QPID-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476013#comment-13476013
]
Keith Wall edited comment on QPID-4332 at 10/15/12 8:02 AM:
------------------------------------------------------------
Fixed by way of QPID-4335. As QPID-4353 removed Felix, this has removed the
class loader visibility issue that caused this problem.
was (Author: k-wall):
Fixed by way of QPID-4353. As QPID-4353 removed Felix, this has removed the
class loader visibility issue that caused this problem.
> Java Broker logs "Warning: The encoding 'UTF-8' is not supported by the Java
> runtime." in response to some LoggingMangement operations
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4332
> URL: https://issues.apache.org/jira/browse/QPID-4332
> Project: Qpid
> Issue Type: Bug
> Affects Versions: 0.18
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.19
>
>
> The Java Broker logs a warning to stderr in response to the use of JMX
> LoggingManagement operations setConfigFileLoggerLevel and
> setConfigFileRootLoggerLevel.
> {noformat}
> Warning: The encoding 'UTF-8' is not supported by the Java runtime.
> {noformat}
> The warning appears not to cause a functional issue, the log4j file is still
> successfully written with the changes.
> It appears the problem is the visibility of classes beneath java.nio.charset
> to the management-jmx bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
