[malpanisiddhesh]

Hi Mr. Thong, James

I have a same kind of issue with my application.

I have made changes in the standalone.xml and logging.properties file of the JBoss EAP 6.1 server.

I'm using org.jboss.logging instead of apache.log4j. B'coz its our project requirement.

Wen I try to run a demo application, its working fine and writing the logs to desired files. But when I try the same things with my actual application, the logs files are getting generated but its not writing the logs in those files.

At the same time I have configured the server to write ALL the logs in the server.logs (default file) as well. Server.log is getting appended, but the desired log files are empty.

My actual applications has many dependencies, so I'm not getting as to which all dependencies be added the <scope>proviede</scope> element.

I'm badly stuck into this and unable to find any solution. Please help.

[jamezp]

It's hard to say what it could be. If you turn on debugging for the category org.jboss.as.logging it might give you some information like if it's finding a logging configuration file and configuring logging based on that.

--

James R. Perkins

[malpanisiddhesh]

Thanks James!

Assuming that by 'org.jboss.as.logging' you mean 'org.jboss.logging', I would like to add that I have already used the DEBUG level in server logging. In fact I have used all the basic log levels viz: FATAL, ERROR, WARN, INFO, DEBUG, TRACE in the configuration file.

Following is the part of the Console logs generated:

11:17:34,786 DEBUG [org.jboss.as.config]  -  (MSC service thread 1-7) Configured system properties:

  awt.toolkit = sun.awt.windows.WToolkit

  file.encoding = Cp1252

  file.encoding.pkg = sun.io

  file.separator = \

  java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

  java.awt.headless = true

  java.awt.printerjob = sun.awt.windows.WPrinterJob

  java.class.path = C:\Install\jBoss\jboss-eap-6.1\jboss-modules.jar

  java.class.version = 50.0

  java.endorsed.dirs = C:\Install\Java\jdk 1.6\jre\lib\endorsed

  java.ext.dirs = C:\Install\Java\jdk 1.6\jre\lib\ext;C:\windows\Sun\Java\lib\ext

  java.home = C:\Install\Java\jdk 1.6\jre

  java.io.tmpdir = C:\Users\756995\AppData\Local\Temp\

  java.library.path = C:\Install\Java\jdk 1.6\jre\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;native;C:/Program Files/Java/jre7/bin/client;C:/Program Files/Java/jre7/bin;C:/Program Files/Java/jre7/lib/i386;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Subversion\bin;C:\Program Files\TortoiseSVN\bin;C:\Install\Maven\apache-maven-3.1.1\bin; C:\Install\Java\jdk 1.6\bin;C:\Install\eclipse;;.

  java.net.preferIPv4Stack = true

  java.runtime.name = Java(TM) SE Runtime Environment

  java.runtime.version = 1.6.0_41-b02

  java.specification.name = Java Platform API Specification

  java.specification.vendor = Sun Microsystems Inc.

  java.specification.version = 1.6

  java.util.logging.manager = org.jboss.logmanager.LogManager

  java.vendor = Sun Microsystems Inc.

  java.vendor.url = http://java.sun.com/

  java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi

  java.version = 1.6.0_41

  java.vm.info = mixed mode

  java.vm.name = Java HotSpot(TM) Server VM

  java.vm.specification.name = Java Virtual Machine Specification

  java.vm.specification.vendor = Sun Microsystems Inc.

  java.vm.specification.version = 1.0

  java.vm.vendor = Sun Microsystems Inc.

  java.vm.version = 20.14-b01

  javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

  javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

  javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

  javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

  javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

  javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

  javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

  javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

  javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

  javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

  jboss.bind.address = localhost

  jboss.home.dir = C:\Install\jBoss\jboss-eap-6.1

  jboss.host.name = 01hw601432

  jboss.modules.dir = C:\Install\jBoss\jboss-eap-6.1\modules

  jboss.modules.system.pkgs = org.jboss.byteman

  jboss.node.name = 01hw601432

  jboss.qualified.host.name = 01hw601432

  jboss.server.base.dir = C:\Install\jBoss\jboss-eap-6.1\standalone

  jboss.server.config.dir = C:\Install\jBoss\jboss-eap-6.1\standalone\configuration

  jboss.server.data.dir = C:\Install\jBoss\jboss-eap-6.1\standalone\data

  jboss.server.deploy.dir = C:\Install\jBoss\jboss-eap-6.1\standalone\data\content

  jboss.server.log.dir = C:\Install\jBoss\jboss-eap-6.1\standalone\log

  jboss.server.name = 01hw601432

  jboss.server.persist.config = true

  jboss.server.temp.dir = C:\Install\jBoss\jboss-eap-6.1\standalone\tmp

  line.separator =

  logging.configuration = file:/C:/Install/jBoss/jboss-eap-6.1/standalone/configuration/logging.properties

  module.path = C:/Install/jBoss/jboss-eap-6.1/modules

  org.jboss.boot.log.file = C:/Install/jBoss/jboss-eap-6.1/standalone/log/boot.log

  org.jboss.resolver.warning = true

  org.xml.sax.driver = __redirected.__XMLReaderFactory

  os.arch = x86

  os.name = Windows 7

  os.version = 6.1

  path.separator = ;

  sun.arch.data.model = 32

  sun.boot.class.path = C:\Install\Java\jdk 1.6\jre\lib\resources.jar;C:\Install\Java\jdk 1.6\jre\lib\rt.jar;C:\Install\Java\jdk 1.6\jre\lib\sunrsasign.jar;C:\Install\Java\jdk 1.6\jre\lib\jsse.jar;C:\Install\Java\jdk 1.6\jre\lib\jce.jar;C:\Install\Java\jdk 1.6\jre\lib\charsets.jar;C:\Install\Java\jdk 1.6\jre\lib\modules\jdk.boot.jar;C:\Install\Java\jdk 1.6\jre\classes

  sun.boot.library.path = C:\Install\Java\jdk 1.6\jre\bin

  sun.cpu.endian = little

  sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

  sun.desktop = windows

  sun.io.unicode.encoding = UnicodeLittle

  sun.java.command = org.jboss.modules.Main -mp C:/Install/jBoss/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml

  sun.java.launcher = SUN_STANDARD

  sun.jnu.encoding = Cp1252

  sun.management.compiler = HotSpot Tiered Compilers

  sun.os.patch.level = Service Pack 1

  sun.rmi.dgc.client.gcInterval = 3600000

  sun.rmi.dgc.server.gcInterval = 3600000

  user.country = US

  user.dir = C:\Install\jBoss\jboss-eap-6.1\bin

  user.home = C:\Users\756995

  user.language = en

  user.name = 756995

  user.timezone = Asia/Calcutta

  user.variant =

11:17:34,791 DEBUG [org.jboss.as.config]  -  (MSC service thread 1-7) VM Arguments: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Install/jBoss/jboss-eap-6.1/standalone/log/boot.log -Dlogging.configuration=file:/C:/Install/jBoss/jboss-eap-6.1/standalone/configuration/logging.properties -Djboss.home.dir=C:/Install/jBoss/jboss-eap-6.1 -Dfile.encoding=Cp1252

We can see that configuration file its using is the logging.properties only.

I'll be very thankful if you could go through these logs and let me know if something is going wrong.

-Siddhesh Malpani

[jamezp]

No I meant turn on trace logging for org.jboss.as.logging. That will print messages trace messages for any logging configuration files found in your deployment.

You can turn on trace logging via this CLI command, then deploy your application or execute a reload to have it redeployed.

/subsystem=logging/logger=org.jboss.as.logging:add(level=TRACE)

The logging.properties file should be the one being used which is fine and normal. That file will be overwritten so it's advised not to make any changes int it.

--

James R. Perkins

[malpanisiddhesh]

Hi James,

Thanks for your quick help..

I'm glad to inform you that I have fixed the issue.

The problem was with the handlers that I used for configuration.

I used async-handler along with periodic-rotating-file-handler, where periodic-rotating-file-handler was the sub-handler of async-handler.

Due to some unknown reasons, my application was unable to log this way. So I just tried with only periodic-rotating-file-handler and it worked fine for me.. I'm very Happy..

Well, Sorry for the late reply.

For future reference of any person in need of such help, below is the link describing the scenario of what I tried earlier..

Duplicate logs in log files generated by JBoss EAP 6.1

Hope this would help someone..

Thanks

-Siddhesh