[JBoss JIRA] Created: (JBAS-4918) for logging, server.xml references another variable than jboss-log4j.xml does
by Jon Stevens (JIRA)
for logging, server.xml references another variable than jboss-log4j.xml does
-----------------------------------------------------------------------------
Key: JBAS-4918
URL: http://jira.jboss.com/jira/browse/JBAS-4918
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-4.2.0.GA
Environment: all
Reporter: Jon Stevens
Assigned To: Scott M Stark
jboss-log4j.xml has this as default:
<param name="File" value="${jboss.server.log.dir}/server.log"/>
jboss-web.deployer has this:
<!-- Access logger -->
<Valve className="org.apache.catalina.valves.AccessLogValve"
prefix="localhost_access_log." suffix=".log"
pattern="common" directory="${jboss.server.home.dir}/log"
resolveHosts="false" />
Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because
#1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
#2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.
My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.
jon
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Created: (JBAS-4448) Properties MBean attribues don't update properly
by John Mazzitelli (JIRA)
Properties MBean attribues don't update properly
------------------------------------------------
Key: JBAS-4448
URL: http://jira.jboss.com/jira/browse/JBAS-4448
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.0.GA
Reporter: John Mazzitelli
Priority: Minor
I have this in my jboss-service.xml for a custom MBean that has a Properties attribute:
<attribute name="ConfigurationOverrides" serialDataType="jbxb">
<java:properties xmlns:java="urn:jboss:java-properties"
xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
<java:property>
<java:key>my-data-directory</java:key>
<java:value>${jboss.server.data.dir}/subdir</java:value>
</java:property>
... and more java:property definitions ...
I have other non-Properties attributes in my MBean as well.
This works fine when starting up. My MBean's setConfigurationOverrides(Properties p) method is called with proper values and everything works.
However, if I go to the JMX console, and edit one of my other attributes (simple String attribute), it seems my Properties attribute gets hosed - its values are all screwed up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years