[ https://issues.jboss.org/browse/AS7-1445?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1445: -------------------------------- Description: Arnaud says, http://lists.ops4j.org/pipermail/general/2011q3/006668.html Trying to deploy an application using pax-logging (1.6.3), it seems to hang JBoss AS (7) By waiting some time I had the stackoverflow stack trace above, os I suspected something wrong with pax-logging service. If I remove pax-logging service from my application, it works fine. As JBoss 7 allow to deploy bundles direcly, I tried to deploy pax-logging-api and pax-logging-service directly and it seems to hand Jboss as well, the server stop to answer, but anything is log A simple way t reproduce, start a JBoss AS 7 server, go to the JBoss console (http://127.0.0.1:9990/console/App.html), the console page should be displayed Copy pax-logging-api and pax-logging-service in $JBOSS_HOME/standalone/deployments, wait for pax logging bundles to be deployed Then try to go to the jboss console again, it does not respond anymore. Is it a known issue ? is there any special configuration to have pax logging service to work with JBoss 7 ? was: Arnaud says, Trying to deploy an application using pax-logging (1.6.3), it seems to hang JBoss AS (7) By waiting some time I had the stackoverflow stack trace above, os I suspected something wrong with pax-logging service. If I remove pax-logging service from my application, it works fine. As JBoss 7 allow to deploy bundles direcly, I tried to deploy pax-logging-api and pax-logging-service directly and it seems to hand Jboss as well, the server stop to answer, but anything is log A simple way t reproduce, start a JBoss AS 7 server, go to the JBoss console (http://127.0.0.1:9990/console/App.html), the console page should be displayed Copy pax-logging-api and pax-logging-service in $JBOSS_HOME/standalone/deployments, wait for pax logging bundles to be deployed Then try to go to the jboss console again, it does not respond anymore. Is it a known issue ? is there any special configuration to have pax logging service to work with JBoss 7 ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1445?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-1445: ------------------------------------- Arnaud says, http://lists.ops4j.org/pipermail/general/2011q3/006701.html I have done some additional tests on this. The issue occurs also in previous version of JBoss ( 5 and 6). Having pax-logging service bundle hang the whole server as well (same stackoverflow error than with JBoss 7), the issue gone by removing pax-logging service bundle. So I tested back in 7 as bundles can be direcly deployed into the container, it is easier to reproduce the issue. As I understand, when pax-logging api only is deployed, pax direcltly use System.out to output logs. I have tested and in this case it works, but if both are deployed (api and service bundles) pax-logging use log4j to output logs. In this case stack overflow occurs when pax try to log something on stdout through its log4j logger (probably default root logger for pax when there is no configuration) In this case the logs got through some Jboss classes, then get back to pax, then get back to jboss, .... until the stack overflow. According to some posts in JBoss forum it seems that there should not be any root logger configured for application that comes with their own log4j configuration. So if I launch JBoss with -Dorg.ops4j.pax.logging.DefaultServiceLog.level=FATAL the issue gone, because it prevents some logs to go through default root logger, until I can create a log configuration without stdout root logger. {code} Logger.log(Level, String) line: 434 LoggingWriter(AbstractLoggingWriter).write(char[], int, int) line: 71 LoggingOutputStream(WriterOutputStream).finish() line: 137 LoggingOutputStream(WriterOutputStream).write(byte[], int, int) line: 106 PrintStream.write(byte[], int, int) line: 430 StdioContext$1(StdioContext$DelegatingPrintStream).write(byte[], int, int) line: 225 StreamEncoder.writeBytes() line: 202 [local variables unavailable] StreamEncoder.implWrite(char[], int, int) line: 263 StreamEncoder.write(char[], int, int) line: 106 StreamEncoder.write(String, int, int) line: 116 OutputStreamWriter.write(String, int, int) line: 203 OutputStreamWriter(Writer).write(String) line: 140 QuietWriter.write(String) line: 48 ConsoleAppender(WriterAppender).subAppend(LoggingEvent) line: 310 ConsoleAppender(WriterAppender).append(LoggingEvent) line: 162 ConsoleAppender(AppenderSkeleton).doAppend(LoggingEvent) line: 251 AppenderAttachableImpl.appendLoopOnAppenders(LoggingEvent) line: 66 Logger(Category).callAppenders(LoggingEvent) line: 206 Logger(Category).forcedLog(String, Priority, Object, Throwable) line: 391 Logger(Category).log(String, Priority, Object, Throwable) line: 856 PaxLoggerImpl.log(Priority, Object, Throwable) line: 231 JdkHandler.publish(LogRecord) line: 106 LoggerNode.publish(ExtLogRecord) line: 283 LoggerNode.publish(ExtLogRecord) line: 291 Logger.logRaw(ExtLogRecord) line: 649 Logger.log(Level, String) line: 434 LoggingWriter(AbstractLoggingWriter).write(char[], int, int) line: 71 LoggingOutputStream(WriterOutputStream).finish() line: 137 LoggingOutputStream(WriterOutputStream).flush() line: 155 PrintStream.write(byte[], int, int) line: 432 StdioContext$1(StdioContext$DelegatingPrintStream).write(byte[], int, int) line: 225 StreamEncoder.writeBytes() line: 202 [local variables unavailable] StreamEncoder.implFlushBuffer() line: 272 [local variables unavailable] StreamEncoder.implFlush() line: 276 [local variables unavailable] StreamEncoder.flush() line: 122 [local variables unavailable] OutputStreamWriter.flush() line: 212 [local variables unavailable] QuietWriter.flush() line: 59 ConsoleAppender(WriterAppender).subAppend(LoggingEvent) line: 324 ConsoleAppender(WriterAppender).append(LoggingEvent) line: 162 ConsoleAppender(AppenderSkeleton).doAppend(LoggingEvent) line: 251 AppenderAttachableImpl.appendLoopOnAppenders(LoggingEvent) line: 66 Logger(Category).callAppenders(LoggingEvent) line: 206 Logger(Category).forcedLog(String, Priority, Object, Throwable) line: 391 Logger(Category).log(String, Priority, Object, Throwable) line: 856 PaxLoggerImpl.debug(String, Throwable) line: 132 PaxLoggingServiceImpl.log(Bundle, ServiceReference, int, String, Throwable) line: 149 PaxLoggingServiceImpl.log(Bundle, int, String, Throwable) line: 115 FrameworkHandler.bundleChanged(BundleEvent) line: 93 {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1445?page=com.atlassian.jira.plugin.s... ] David Bosschaert commented on AS7-1445: --------------------------------------- I was able to reproduce this. The topmost piece of the stack trace (it repeats further to the bottom): {code}java.lang.StackOverflowError at java.nio.CharBuffer.arrayOffset(CharBuffer.java:967) at sun.nio.cs.SingleByteEncoder.encodeArrayLoop(SingleByteEncoder.java:91) at sun.nio.cs.SingleByteEncoder.encodeLoop(SingleByteEncoder.java:130) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:544) at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:252) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:48) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310) at org.apache.log4j.WriterAppender.append(WriterAppender.java:162) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at org.ops4j.pax.logging.service.internal.PaxLoggerImpl.log(PaxLoggerImpl.java:231) at org.ops4j.pax.logging.service.internal.JdkHandler.publish(JdkHandler.java:106) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:283) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) at org.jboss.logmanager.Logger.logRaw(Logger.java:649) at org.jboss.logmanager.Logger.log(Logger.java:434) at org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71) at org.jboss.stdio.WriterOutputStream.finish(WriterOutputStream.java:137) at org.jboss.stdio.WriterOutputStream.write(WriterOutputStream.java:106) at java.io.PrintStream.write(PrintStream.java:430) at org.jboss.stdio.StdioContext$DelegatingPrintStream.write(StdioContext.java:225) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:263) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:48) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310) at org.apache.log4j.WriterAppender.append(WriterAppender.java:162) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at org.ops4j.pax.logging.service.internal.PaxLoggerImpl.log(PaxLoggerImpl.java:231) at org.ops4j.pax.logging.service.internal.JdkHandler.publish(JdkHandler.java:106) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:283) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) at org.jboss.logmanager.Logger.logRaw(Logger.java:649) at org.jboss.logmanager.Logger.log(Logger.java:434) ... and so on ... {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1445?page=com.atlassian.jira.plugin.s... ] David Bosschaert resolved AS7-1445. ----------------------------------- Fix Version/s: 7.0.0.Final Resolution: Done Arnaud writes: many thanks for the help, I have tested the property and it works also in my environments -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira