-
1. Re: How to write custom logging to server.log on jboss6.1 in domain mode
jamezp Sep 22, 2016 1:20 PM (in response to satishnallabheem)Does your EAR or any of the WAR's in your EAR have a logging configuration file in it?
--
James R. Perkins
-
2. Re: How to write custom logging to server.log on jboss6.1 in domain mode
satishnallabheem Sep 23, 2016 2:47 AM (in response to jamezp)Hi James,
Thanks for the response, Actually our EAR dont have any logging configuration file in it. But I see logging.properties in the server @ domain/configuration/logging.properties. and also a bit of logging-related-configuration in domain.xml.
Basically , I want to run all the INFO loggers to server.log
Please suggest .
Thanks
Satish
-
3. Re: How to write custom logging to server.log on jboss6.1 in domain mode
jamezp Sep 23, 2016 11:27 AM (in response to satishnallabheem)What logging framework are you using? Also are you including any logging libraries in your deployment? There should be nothing special required. By default the root logger is configured to log at INFO.
--
James R. Perkins
-
4. Re: How to write custom logging to server.log on jboss6.1 in domain mode
satishnallabheem Sep 26, 2016 2:02 AM (in response to jamezp)HI James,
I am using log4j and the libraries are included in the deployment. Yeah , thats correct but some how it is not working .
Thanks
Satish
-
5. Re: How to write custom logging to server.log on jboss6.1 in domain mode
jamezp Sep 26, 2016 11:18 AM (in response to satishnallabheem)I don't recall all the details, but there were some issues with log4j in earlier versions of EAP 6. Try removing the log4j dependency from your deployment as the server should automatically put one on the deployment for you.
--
James R. Perkins
-
6. Re: How to write custom logging to server.log on jboss6.1 in domain mode
doh Sep 27, 2016 9:54 AM (in response to jamezp)Can you backup and remove all logging property files in your war file and re-configure with following to below link?
Administration and Configuration Guide
And then update your server.log and standalone.xml to investigate.