[jboss-jira] [JBoss JIRA] (WFCORE-4436) NPE with the CLI embedded server when in admin-only mode
James Perkins (Jira)
issues at jboss.org
Mon Apr 22 19:01:00 EDT 2019
[ https://issues.jboss.org/browse/WFCORE-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Perkins updated WFCORE-4436:
----------------------------------
Priority: Blocker (was: Major)
> NPE with the CLI embedded server when in admin-only mode
> --------------------------------------------------------
>
> Key: WFCORE-4436
> URL: https://issues.jboss.org/browse/WFCORE-4436
> Project: WildFly Core
> Issue Type: Bug
> Components: Embedded
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 9.0.0.Beta4
>
>
> Executing {{embed-server --admin-only=false}} will cause an NPE due to the fix in WFCORE-4358.
> {code}
> LogManager error of type FLUSH_FAILURE: Error on flush
> java.lang.NullPointerException
> at org.jboss.as.cli.embedded.ThreadLocalContextSelector.getStdioContext(ThreadLocalContextSelector.java:72)
> at org.jboss.stdio.StdioContext$1.getDelegate(StdioContext.java:148)
> at org.jboss.stdio.StdioContext$DelegatingPrintStream.write(StdioContext.java:264)
> at org.jboss.logmanager.handlers.UncloseableOutputStream.write(UncloseableOutputStream.java:44)
> at org.jboss.logmanager.handlers.UncloseableOutputStream.write(UncloseableOutputStream.java:44)
> at org.jboss.logmanager.handlers.UninterruptibleOutputStream.write(UninterruptibleOutputStream.java:84)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at org.jboss.logmanager.handlers.WriterHandler.safeFlush(WriterHandler.java:170)
> at org.jboss.logmanager.handlers.WriterHandler.flush(WriterHandler.java:139)
> at org.jboss.logmanager.ExtHandler.doPublish(ExtHandler.java:105)
> at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:67)
> at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:77)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:333)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.Logger.logRaw(Logger.java:850)
> at org.jboss.logmanager.Logger.log(Logger.java:802)
> at org.jboss.logmanager.Logger.log(Logger.java:814)
> at org.jboss.logging.JBossLogManagerLogger.doLog(JBossLogManagerLogger.java:42)
> at org.jboss.logging.Logger.error(Logger.java:1518)
> at org.jboss.logging.DelegatingBasicLogger.error(DelegatingBasicLogger.java:714)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:328)
> {code}
> This is like due to the TCCL being {{null}}. This can always be a possibility and should be checked for a {{null}} value.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list