]
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}
Pax-Logging deployment causes stack overflow
--------------------------------------------
Key: AS7-1445
URL:
https://issues.jboss.org/browse/AS7-1445
Project: Application Server 7
Issue Type: Bug
Reporter: Thomas Diesler
Assignee: David Bosschaert
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: