11:04 a.m.
Ramanathan Lakshmanan [https://community.jboss.org/people/ars.ram] created the discussion
"EAP jboss log.txt getting too large"
To view the discussion, visit: https://community.jboss.org/message/786960#786960
--------------------------------------------------------------
I'm developing Struts 2 application and deploying that as war on EAP Jboss 6. At the
beginning of development nothing gone wrong. But recently i realized that my disk space is
grtting full because of log.txt file . When searching on web about this got lot of
discussions but nothing helped me. From one post i tried to exclude log4j lib from the
'deployment-structure.xml' but nothing happened. Then i gone through
standalone.xml file i found on subsystem tag which is *subsystem
xmlns="urn:jboss:domain:logging:1.1".* i removed that completely and deleted
log.txt from that location. Now file is not created. Then tried different things on that
tag each time log.txt file was created and lo was getting populated. I tried
log4j.properties in my project but file was created not populated.Now i could understand
that the *subsystem xmlns="urn:jboss:domain:logging:1.1"* line calls the inbuilt
jar file and a class from that jar creates the file. So please let me know where is that
jar file actually located. I attached my log4j.properties with this query.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/786960#786960]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:09 p.m.
New subject: [JBoss AS 7 Development] - Re: EAP jboss log.txt getting too large
James Perkins [https://community.jboss.org/people/jamezp] created the discussion
"Re: EAP jboss log.txt getting too large"
To view the discussion, visit: https://community.jboss.org/message/787424#787424
--------------------------------------------------------------
Can you paste your logging configuration from the standalone.xml (assuming you're
running in standalone mode). There is no file by default called log.txt so it has to be
somewhere in a configuration file.
--
James R. Perkins
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/787424#787424]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:28 p.m.
New subject: [JBoss AS 7 Development] - Re: EAP jboss log.txt getting too large
Ramanathan Lakshmanan [https://community.jboss.org/people/ars.ram] created the discussion
"Re: EAP jboss log.txt getting too large"
To view the discussion, visit: https://community.jboss.org/message/788170#788170
--------------------------------------------------------------
I'm running EAP Jboss binding to 0.0.0.0 by using the command 'standalone.bat -b
0.0.0.0 -bmanagement 0.0.0.0'(for Windows) and ' ./standalone.sh
-Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0&' (For
Ubuntu). I'll paste the server console first , because the first echo is about the
log, but i don't understand it,
WARNING: -logmodule is deprecated. Please use the system property
'java.util.logging.manager' or the 'java.util.logging.LogManager' service
loader.
09:54:14,903 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current
PicketBox version=4.0.9.Final-redhat-1
09:54:15,278 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408:
Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
09:54:16,277 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting
Naming Service
09:54:16,340 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400:
Bound mail session [java:jboss/mail/Default]
09:54:16,418 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
09:54:17,573 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080
09:54:18,151 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
09:54:18,182 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "ESS.war"
09:54:18,198 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876:
Starting deployment of "EMAG.war"
09:54:18,213 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1)
JBAS015012: Started FileSystemDeploymentService for directory E:\Servers\EAP
6\jboss-eap-6.0\standalone\deployments
09:54:18,447 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening
on 0.0.0.0:9999
09:54:18,463 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening
on 0.0.0.0:4447
09:54:42,565 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1)
JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
09:54:42,706 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register
module: Module "deployment.EMAG.war:main" from Service Module Loader
09:54:45,842 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web
context: /EMAG
09:54:51,209 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register
module: Module "deployment.ESS.war:main" from Service Module Loader
09:54:52,911 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web
context: /ESS
09:54:52,943 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS018559:
Deployed "ESS.war"
09:54:52,943 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS018559:
Deployed "EMAG.war"
09:54:53,848 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://0.0.0.0:9990 http://0.0.0.0:9990
09:54:53,848 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA
(AS 7.1.2.Final-redhat-1) started in 53562ms - Started 495 of 578 services (82 services
are passive or on-demand)
......
Now i'll paste the standalone.xml where the log manager is called,...
<subsystem xmlns="urn:jboss:domain:logging:1.1">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t)
%s%E%n"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="FILE">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t)
%s%E%n"/>
</formatter>
<file path="server.log"
relative-to="jboss.server.log.dir"/>
<suffix value=".yyyy-MM-dd"/>
<append value="true"/>
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
</subsystem>
.....
Thats what i have in standalone.xml.....
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/788170#788170]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4857
days inactive
4862
days old
jboss-dev-forums@lists.jboss.org
2 comments
2 participants
participants (2)
-
James Perkins -
Ramanathan Lakshmanan