Description of problem: WE should remove these log messages continuously being displayed... 11:43:12,394 INFO [TransientRepository] Session closed 11:43:12,396 INFO [TransientRepository] Session opened 11:43:12,397 INFO [TransientRepository] Session closed 11:43:22,400 INFO [TransientRepository] Session opened 11:43:22,402 INFO [TransientRepository] Session closed 11:43:22,404 INFO [TransientRepository] Session opened 11:43:22,405 INFO [TransientRepository] Session closed 11:43:32,409 INFO [TransientRepository] Session opened Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Didn't do any changes for this. This message is not coming from our code. It comes from JackRabbit. It might be possible to edit the logger configurations to silence it, but I'm not sure if we are the ones that should be doing it.
Closing, since there's nothing to do. If the customers want to get rid of the message, they are free to modify their logging configs.
Toni, I can understand that this is coming from Jackrabbit. It is an embedded component inside our product. We can configure it to behave the way we like it. The scrolling logs with no real value out of the box is very annonying. Lets get this fixed in Guvnor by default to not spit this out. Users can go to logs to change it if they need.
We can configure the logging in the BRMS-P standalone to avoid this logging. Example jboss-log4j.xml snippet: <!-- Limit the verbose JackRabbit TransientRepository --> <category name="org.apache.jackrabbit.core.TransientRepository"> <priority value="WARN"/> </category> but we could only document this step for the BRMS-P deployable.
Hi Julian, To make sure I understand what needs to happen with this one: 1. Standalone will be configured by default. 2. We need to document how customers configure themselves for the deployable package. For containers that have jboss-log4j.xml (EAP 5 and SAO)they add the above snippet to the file. How would customers deploying to EWS and Tomcat do this? The installation procedure already tells them to copy log4j*jar to the app server's lib directory, but where do they add the xml that goes into jboss-log4j.xml? Thanks Lee
Ugh it's early here. Configure this for themselves* and SOA*
Resolved with revision of: common/resources/log4j-conf/default/jboss-log4j.xml common/resources/log4j-conf/production/jboss-log4j.xml Commit message: BZ-840579 Limit logging for the verbose JackRabbit TransientRepository.
It seems that we should provide a log4j configuration file if we are asking users to add log4j to their deployments.
Hi Julian, when the configuration file has been added can you update with details and instructions? Thanks Lee
Moving back to modified. Julian I still need configuration instructions, please update the bug with a comment with the instructions. Thanks Lee
After email discussion with Julian, I'm moving this back to ON-QA so that QE can test the implementation, with a note that we still need to update the documentation for the deployable package. Thanks Lee
These log messages still occur when clicking inside Guvnor. The frequency is roughly the same as before (= the log is quickly full of these.) Tested with the default Standalone config on 5.3.1 ER1.
Resolved with revision 11532 of: brms-p/src/main/assembly/brms-standalone.zip.xml BZ 840579 Use our log4j configuration instead of EAP's.
Hi Lee, Yes. For EAP 5 and for SOA-P 5, the above XML snippet needs to be added to the appropriate configuration file "jboss-as/server/<profile>/conf/jboss-log4j.xml". EWS uses java property-style configuration, so after following "Procedure 5.7. Configuring log4j" in the EWS Installation Guide to add log4j to Tomcat, adding the following snippet to log4j.properties should work: log4j.logger.org.apache.jackrabbit.core.TransientRepository=WARN However, I see that jboss-brms.war tries to uses log4j XML configuration, when tomcat is not configured that way: INFO: Deploying web application directory jboss-brms.war log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable to a "org.apache.log4j.spi.Configurator" variable. log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by log4j:ERROR [org.apache.catalina.loader.StandardClassLoader@1c86be5] whereas object of type log4j:ERROR "org.apache.log4j.xml.DOMConfigurator" was loaded by [WebappClassLoader context: /jboss-brms.war delegate: false repositories: /WEB-INF/classes/ ----------> Parent Classloader: org.apache.catalina.loader.StandardClassLoader@1c86be5 ]. log4j:ERROR Could not instantiate configurator [org.apache.log4j.xml.DOMConfigurator]. log4j:WARN No appenders could be found for logger (org.drools.repository.RulesRepositoryConfigurator). log4j:WARN Please initialize the log4j system properly.
VERIFIED in ER3 that the log message no longer appears.