]
David Bosschaert commented on AS7-1445:
---------------------------------------
The problem is that Pax registers a JDK logger which logs to log4j which logs to the
console which is picked up by JBoss Logging which then writes to the JDK logger from Pax
logging and so on.
The issue can be avoided by setting the system property
org.ops4j.pax.logging.skipJUL=true
e.g. by setting the environment variable JAVA_OPTS before launching bin/standalone.sh
{code}export JAVA_OPTS=-Dorg.ops4j.pax.logging.skipJUL=true
bin/standalone.sh{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: