log4j

I use Jboss 6 and my static Logger logger = Logger.getLogger(Foo.class); displays nothing Tried adding log4 to my project, removing it, placing a log4j file on my main/resources folder, placing no log4j file and no results. Only System.Out seems to work, but it doesn't provide all the information I would like to see I even see Hibernate log working but not mine What am I missing? Turns out my logging does work. Hibernate logging is controlled by the jboss logging settings. My logging began to work as soon as I placed the log4j on right next to the classes folder, and placing log4j jar with the

Is there a way to figure out where is Log4J picking the configuration file from? I tried to change my log4j.xml and the changes were not reflected in Log4j behaviour. I deleted log4j.xml and funnily enough, Log4J is still working with the old behaviour. So it must be picking some configuration file which is available in my namespace. But the question is how can I figure out which one. Is there a way to do that? there are so many different dependencies on jars etc, so one of them must contains a log4j.xml or log4j.properties that is overriding my changes. Any ideas? When running your

How do I convert this log4j2.xml config fragment to log4j2.properties format? I cannot use XML format in my maven + netbeans project as I simply cannot get log4j2 to parse and respond to a log4j2.xml file - no matter where I place it in my project, it is ignored by log4j2. However log4j2.properties in main/resource IS parsed and responded to so I -HAVE- to use .properties...: <JDBC name="databaseAppender" tableName="LOGGING.APPLICATION_LOG"> <ConnectionFactory class="log4j_tutorial.ConnectionFactory" method="getDatabaseConnection" /> <Column name="EVENT_DATE" isEventTimestamp="true" /> <Column

I have my application for which the below entry is done in Log4j properties file.Size based rolling is not working for this application. File does not rollover at 5 MB and the application keeps on logging and making it in GB. In one run approximately 6 MB of log is generated.The application runs multiple times a day. Can someone help in pointing out where I am doing a mistake? # SampleApp configuration log4j.category.com.ibm.hmel.hwmmphdya=INFO, SampleApp log4j.additivity.com.ibm.hmel.hwmmphdya=false log4j.appender.SampleApp =org.apache.log4j.rolling.RollingFileAppender log4j.appender

1. 问题描述 druid是国内及公司内部最常用的数据库连接池配置管理工具；其内置监控页面，用于拦截sql及实时监控连接池/sql信息，该页面在原生的druid包中默认为禁用，但其用于适配springboot的druid-spring-boot-starter包，默认打开该监控页面( http://ip:port/druid/index.html ) ，打开后存在如下风险： 1.1 暴露DB信息 由于druid监控页面地址是固定的，容易被猜，监控页面默认没有任何安全措施，容易暴露项目信息，如：数据库域名地址、库名、表名、查询的sql及url等，如果druid有漏洞，甚至可能被攻击。 泄漏DB域名、使用用户及库名： 泄漏SQL信息： 泄漏URL信息： 1.2 成为非法广告的肉机 监控页面中的多个tab页含阿里云广告，且power by连接到作者个人域名，估计没续费，已被澳门赌场站点抢占，国内该类广告是违法的，如下图： 2. 影响范围 springboot项目：该问题我们已向官方提交request官方尚未修复，所以我们使用的任意版本druid-spring-boot-starter都有问题。 非sprinboot项目：如果手工启用监控页面，且未指定登录用户名、密码及允许访问的IP，也存在相同问题。 3. 解决办法 判断项目是否添加druid监控页面的方法：是否能打开druid监控页面(

I have to configure the JDBC appender to use a datasource..is it possible? if so , how? My present file looks like so: # Define the root logger with file appender log4j.rootLogger = DEBUG, sql # Define the file appender log4j.appender.sql=org.apache.log4j.jdbc.JDBCAppender log4j.appender.sql.URL=jdbc:mysql://localhost/test # Set Database Driver log4j.appender.sql.driver=com.mysql.jdbc.Driver # Set database user name and password log4j.appender.sql.user=root log4j.appender.sql.password=password # Set the SQL statement to be executed. log4j.appender.sql.sql=INSERT INTO LOGS VALUES ('%x', now() ,

I am working on a multithreaded application. I am already using Log4j to log statements to files. I have been recently looking into the possibility of logging to a Mysql database. The logging component has to be reliable under a heavy load and has to be thread safe. I heard of SFL4J. My understanding of SLF4J is that is just a facade or abstraction layer. I was wondering if SLF4J was a good database logging solution to use in a multithreaded application? And in the case of a heavy load, would it be a good idea to add a layer (like a buffer or a queue) and let the threads log to it instead of