[Beginners Corner] - Re: Help with JBOSS Log Configuration
by johnloo
Sorry! Unfamiliar with this BBS... Let me try again..:
I am having a problem re-configuring the JBOSS log files. I am running 4.0.1SP1. I had the log files configured like this, which pretty much is the config supplied by the third-party app vendor:
| <!-- A time/date based rolling appender -->
| <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.home.dir}/log/server.log"/>
| <param name="Append" value="false"/>
|
| <!-- Rollover at midnight each day -->
| <param name="DatePattern" value="'.'yyyy-MM-dd"/>
|
| <!-- Rollover at the top of each hour
| <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
| -->
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
|
| <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
| <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
| -->
| </layout>
| </appender>
|
|
This produced daily log files, and only a little bit of boot.log output. I decided that I wanted a size-based logging system, so I altered the log4j.xml file to remove the above, and substituted this:
| <!-- A size based file rolling appender -->
| <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.home.dir}/log/server.log"/>
| <param name="Append" value="true"/>
| <param name="MaxFileSize" value="10MB"/>
| <param name="MaxBackupIndex" value="25"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
| </layout>
| </appender>
|
After saving the log4j.xml file, I restarted the JBOSS server. Now, I get no server log files, only a boot.log file that seems to be growing at the rate of 2MB / min.
What am I missing?? Something simple, I'm sure. TIA for the help!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212407#4212407
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212407
17 years, 2 months
[Beginners Corner] - Help with JBOSS Log Configuration
by johnloo
I am having a problem re-configuring the JBOSS log files. I am running 4.0.1SP1. I had the log files configured like this, which pretty much is the config supplied by the third-party app vendor:
<!-- A time/date based rolling appender -->
<!-- Rollover at midnight each day -->
<param name="DatePattern" value="'.'yyyy-MM-dd"/>
<!-- Rollover at the top of each hour
<param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
-->
<!-- The default pattern: Date Priority [Category] Message\n -->
<!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
-->
This produced daily log files, and only a little bit of boot.log output. I decided that I wanted a size-based logging system, so I altered the log4j.xml file to remove the above, and substituted this:
<!-- A size based file rolling appender -->
After saving the log4j.xml file, I restarted the JBOSS server. Now, I get no server log files, only a boot.log file that seems to be growing at the rate of 2MB / min.
What am I missing?? Something simple, I'm sure. TIA for the help!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212405#4212405
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212405
17 years, 2 months
[JBoss Portal] - Re: multiple JBP instance + 1 DB (only one db)
by Antoine_h
Yes, that comes from the Hibernate cache.
JBP1 have loaded the instance definition, so it is in cache.
JBP2 have loaded the instance definition, so it is in cache.
Change is made on the instance, with JBP1.
JBP1 have saved the instance definition, so the cache have updated it's instance too.
JBP2 still uses the cached one... hence the change does not appear.
With a cluster, Hibernate synchronizes it's cache... so it works fine.
I guess you may find a way to clear all the cache (from JMX console may be). But I don't know how.
Note on thing : on startup, all the contents of the CMS are loaded in the hibernate cache. This is for performance, when using the CMS. so make sure not to clear this cache. I guess they are separate, but not sure.
**********
when I asked the question, I had in mind this : only for prod, not changing things in the portal.
neither the portal definition, nor the CMS.
At this time, the portal did not used the JBPM. It is used for user registration now.
so this may also make some problem with only one DB. Should not, but make sure before to go further.
**********
And, by the way : on my opinion, the Admin GUI is nice, but it should be used only for prototyping, and making quick demo.
and nice for newbee to have a sexy software out of the box.
very good to get familiar with the portal.
but for prod, especially if you have to instances, I would recommend only to use the XML descriptor files.
using the Admin GUI drives you to some troubles.
main cons :
- if you have two developpers working on two different parts of the portal : how do you merge their changes ?
with xml files, you can do a merge (with svn or cvs)... or also the merge is imediate if they work on two different wars.
- in XML files if you work on a page, window, instance or portlet, by deleting one or even just changing the name, then the former one remains in the database. it is not suppressed.
So as soon as you start with the GUI, you cannot touch the xml file, without many trouble. You may have some remaining objects in the portal configuration. And deleting them "a la mano" in the GUI is quite boredom.
It is much more easy to drop all the tables, and relaunch the portal : all is rebuilt from the xml.
- if you want to start from a new JBP configuration (from dev to testing, then to prod), it is quite heavy to dump and restore the database to the new configuration.
Portal is producing a new version oftenly.
It is much more work, and much more risk with the GUI + database.
so... for a heavy portal, that goes to prod, I recommend that you use the XML files.
Hope it helps,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212403#4212403
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212403
17 years, 2 months