We Keep Coding

Remove cache logging with JBoss

I'm working on JBoss EAP 6.3 and in my server.log file, there is all the time the following logs :
10:22:33,525 DEBUG [org.hibernate.cache.spi.UpdateTimestampsCache]
(http-/0.0.0.0:8080-70) Pre-invalidating space [users], timestamp:
15507410135
10:22:33,526 DEBUG
[org.hibernate.cache.spi.UpdateTimestampsCache]
(http-/0.0.0.0:8080-70) Invalidating space [users], timestamp:
15507409535
10:22:33,842 DEBUG
[org.hibernate.cache.spi.UpdateTimestampsCache]
(http-/0.0.0.0:8080-50) Pre-invalidating space [users], timestamp:
15507410138
10:22:33,844 DEBUG
[org.hibernate.cache.spi.UpdateTimestampsCache]
(http-/0.0.0.0:8080-50) Invalidating space [users], timestamp:
15507409538
How can i remove these logs ?

In your case, the logging level for hibernate cache is set to debug. Setting logging level to info means that only log event at info or higher levels are logged.
You can change the logging level with the web console or by using CLI. An example CLI command would look like:
/subsystem=logging/logger=org.hibernate.cache:add(level=INFO)
If you're including Hibernate in your deployment and you have a log4j.properties consider the following.
log4j.properties
log4j.logger.org.hibernate.cache=info
or
log4j.xml file
<logger name="org.hibernate.cache">
<level value="info"/>
</logger>

remove hibernate logging from Dropwizard app logs

I see a lot of logs logging al the queries that make the logs not very useful. I am trying to remove this logging from my dropwizard app logs I tried to do it through the yml file
logging:
level: "DEBUG"
loggers:
org.hibernate: ERROR
And also in the logback.xml
<logger name="org.hibernate">
<level value="ERROR" />
</logger>
I also tried appenders to the yml file as console and syslog. What is the way to remove these SELECT statements from the logs?
I dont want to move the logs to another file as I do want to see the errors
The logger isnt org.hibernate but I only see "Hibernate: select * FROM ....."

You should try changing your default application logging level to INFO instead
logging:
level: INFO
and further, modify log level of a package using
# Sets the level for 'org.hibernate' to ERROR
loggers:
org.hibernate: ERROR
Here is an effective example of the usage from dropwizard itself.
Or in your case probably the package contributing to the logs as
loggers:
org.hibernate.SQL: ERROR # note - not moving to another file either

You have to set hibernate.show_sql to false
database:
properties:
hibernate.show_sql: false
However, this alone may not work. I upvoted the other answer as it led me to this - you do indeed have to pay attention to your configured logging levels for the hibernate package because surprisingly, if your org.hibernate.SQL logging level is set to DEBUG then this will override the hibernate.show_sql: false config and log the SQL anyway!
You need to make sure it's set to INFO or greater
logging:
loggers:
"org.hibernate.SQL":
level: INFO

In my case, setting the "hibernate engine" level (in the application.yaml file) decreased the number of log messages:
loggers:
org.hibernate.engine: error

Disable jboss server log files

I have using simple web application which is hosted in Linux VM on jboss-eap-6.2. Application works fine.
Since My VM is containing very small amount of space I was trying reduce unnecessary log files. For me info log is very much sufficient and
You see there will be always server logs will be inherited automatically when server starts up. Here as follow in server path :
opt/gnrtestbed/jboss-eap-6.4/standalone/log>
-rw-r--r-- 1 gnrtb gnrtestbed 1864 Mar 7 07:40 gc.log.0.current
-rw-r--r-- 1 gnrtb gnrtestbed 14770464 Mar 7 07:40 server.log
so on so
And I don’t want any log details like console, boot,...etc.
I want to control the jboss log server in manner that I can only produce the log which I want.. For me just info which logged/coded in application is more than enough since its very small application
I have searched long in online and many suggested to disable the logs like below through add these lines to standalone.xml or domain.xml:
<system-properties>
<property name="org.jboss.as.logging.per-deployment" value="false"/>
</system-properties>
This above is also not helping. After adding this lines unable to start the server and end up in errors
so on so
And also, I have tried all the commenting stuffs inside of logging.properties file under path :
/opt/gnrtestbed/jboss-eap-6.4/standalone/configuration>
But I couldn’t stop the console,.. server logs… its just keep pouring...
Please let me know what I am missing or what I have to do further to avoid default server logs. Your help will be appreciated. Thanks
For your detailed understanding let me share my logging properties file as follow :
# Note this file has been generated and will be overwritten if a
# logging subsystem has been defined in the XML configuration.
# Additional loggers to configure (the root logger is always configured)
loggers=sun.rmi,jacorb,org.jboss.as.config,jacorb.config,org.apache.tomcat.util.modeler,com.arjuna,System.out
logger.level=TRACE
logger.handlers=FILE,CONSOLE
logger.sun.rmi.level=WARN
logger.sun.rmi.useParentHandlers=true
logger.jacorb.level=WARN
logger.jacorb.useParentHandlers=true
logger.org.jboss.as.config.level=DEBUG
logger.org.jboss.as.config.useParentHandlers=true
logger.jacorb.config.level=ERROR
logger.jacorb.config.useParentHandlers=true
logger.org.apache.tomcat.util.modeler.level=WARN
logger.org.apache.tomcat.util.modeler.useParentHandlers=true
logger.com.arjuna.level=WARN
logger.com.arjuna.useParentHandlers=true
logger.System.out.level=WARN
logger.System.out.useParentHandlers=true
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.level=WARN
handler.CONSOLE.formatter=CONSOLE
handler.CONSOLE.properties=enabled,autoFlush,target
handler.CONSOLE.enabled=true
handler.CONSOLE.autoFlush=true
handler.CONSOLE.target=SYSTEM_OUT
handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
handler.FILE.level=ALL
handler.FILE.formatter=FILE
handler.FILE.properties=append,autoFlush,enabled,suffix,fileName
handler.FILE.append=true
handler.FILE.autoFlush=true
handler.FILE.enabled=true
handler.FILE.suffix=.yyyy-MM-dd
handler.FILE.fileName=/opt/gnrtestbed/jboss-eap-6.4/standalone/log/server.log
formatter.CONSOLE=org.jboss.logmanager.formatters.PatternFormatter
formatter.CONSOLE.properties=pattern
formatter.CONSOLE.constructorProperties=pattern
formatter.CONSOLE.pattern=%K{level}%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n
formatter.FILE=org.jboss.logmanager.formatters.PatternFormatter
formatter.FILE.properties=pattern
formatter.FILE.constructorProperties=pattern
formatter.FILE.pattern=%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n

Is there a way to silence hsqldb logging?

I have an embedded Hsqldb set up in my project. But it dumps a lot of info on the output when working, and I currently do not need that info:
Mar 29, 2012 10:18:11 PM org.hsqldb.persist.Logger logInfoEvent
INFO: Checkpoint start
Mar 29, 2012 10:18:11 PM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose start
Mar 29, 2012 10:18:11 PM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose end
Mar 29, 2012 10:18:11 PM org.hsqldb.persist.Logger logInfoEvent
INFO: Checkpoint end
Is there a way to silence that output?

Unfortunately, i don't believe so. we have the same issue in our project. i believe i checked the source at one point in time and concluded that hsqldb does not provide a way to influence this logging.
I stand corrected (as #fredt mentioned in his comment to the other answer), you can control this logging via the jdk log levels. setting the "hsqldb.db" log level to something like WARNING will suppress this output. you can do this using the logging.properties file or programmatically (after hsqldb loads) using something like Logger.getLogger("hsqldb.db").setLevel(Level.WARNING) (assuming you are using java util logging).
As noted in the comment below, hsqldb also resets the java logging configuration. If embedding it in another application, you may want to disable that functionality by setting the system property "hsqldb.reconfig_logging" to "false" (before hsqldb is loaded).

For anyone looking for a command line solution.
Start your app/server with a property pointing to the location of a dedicated properties file:
-Djava.util.logging.config.file=/location/of/your/hsqldblog.properties"
Which contains the following line to change Java logging for Hsqldb.
# Change hsqldb logging level
org.hsqldb.persist = WARNING
Side note, you can choose from the following levels:
SEVERE WARNING INFO CONFIG FINE FINER FINEST
More info on Java Logging

For Slf4j + Logback users:
Add log4j-over-slf4j as a dependency (don't forget to exclude original log4j dependency if you have any). If you use Gradle, add something like this into your build.gradle:
runtime group: 'org.slf4j', name: 'log4j-over-slf4j', version: '1.7.25'
Then, add this to your logback.xml:
<logger name="hsqldb.db" level="warn"/>

You can use setSilent(true) when starting server from code:
Server server = new Server();
server.setSilent(true);
server.setDatabaseName(0, "mainDb");
server.setDatabasePath(0, "mem:mainDb");
server.setPort(9001);
server.start();

Logging JPA SQL with Weblogic 10.3

By looking into the Open JPA website i've found that i can log the generated SQL by using the following:
<property name="openjpa.Log" value="DefaultLevel=WARN, Runtime=INFO, Tool=INFO"/>
If i try to add the above property to my persistence.xml i get the following warning from weblogic:
<Warning> <J2EE> <BEA-160202> <You have specified a ope
njpa.Log setting in your configuration for persistence unit services.ear#services-ejb.jar#exp#exp. This setting will be ignored, and all log messages
will be sent to the WebLogic logging subsystem. Trace-level logging is controlle
d by the various JPA-specific debug settings in config.xml, or via the WebLogic
console.>
Anyone know what is the option in the console or how i can edit my config.xml to output the SQL?

From the OTN Discussion forum here are the steps :
Log into the weblogic console
Lock and Edit the session
Click Environment | Servers
Select the server you wish to monitor/debug
Click the Debug tab
expand the weblogic tree and select the JPA node
Click the enable button
Activate the changes.
It might depend on the version of WLS you have. I understand that there were some issues if you've downloaded a newer version of OpenJPA and are using it with WLS.
WebLogic issues aside, the configuration string you posted looks a bit off. Did you intend to use something like this (added in SQL=TRACE):
<property name="openjpa.Log"
value="DefaultLevel=WARN, Runtime=INFO, Tool=INFO, SQL=TRACE"/>

For Weblogic 10.3.3, there's some more steps:
Log into the weblogic console
Lock and Edit the session
Click Environment | Servers
Select the server you wish to monitor/debug
Click the Debug tab, expand the weblogic tree and select the JPA node
Click the enable button
Activate the changes at the bottom of the page
Now click the Logging Tab
At the bottom of the page, click Advanced
Under Message destination(s) panel, change Severity Level from Standard Out to Debug
Save your changes and restart server