Alas, no luck. This is what I found in my directory:
-rw-r--r--. root root 30694 Nov 25 22:49 catalina
-rw-r--r--. root root 0 Nov 25 22:49 catalina.out
-rw-r--r--. root root 0 Nov 25 22:49 host-manager
-rw-r--r--. root root 31909 Nov 25 22:49 localhost
-rw-r--r--. root root 0 Nov 25 22:49
localhost_access_log.2015-11-25.txt
-rw-r--r--. root root 0 Nov 25 22:49 manager
[root@centos7sys1 logs]# date
Thu Nov 26 00:07:25 EST 2015
On Wed, Nov 25, 2015 at 7:22 PM, Joleen Barker <oldenuf2no...@gmail.com>
wrote:
> I changed it back to use the log4j setting as I liked it better and the
> boss wants the files to rollover at midnight each night. Now when I startup
> the catalina.out file is empty and the logs appear to be split between the
> catalina file (not catalina.out) and the localhost file. Some of the
> messages are doubled between the two files.
>
>
> We will see what happens now with the swallowOutput=true. I'm so excited
> to see what is there tomorrow morning. lol
>
> -Joleen
>
> On Wed, Nov 25, 2015 at 6:59 PM, Joleen Barker <oldenuf2no...@gmail.com>
> wrote:
>
>> Sorry. I all of a sudden noticed the swallowOutput="false" in the
>> cfcc.xml I had. I changed this to be true and now it appears most of the
>> messages are being written to the locahost file. I don't see any messages
>> missing. I will leave it run over night and see what happens and report
>> tomorrow.
>>
>> -Joleen
>>
>> On Wed, Nov 25, 2015 at 3:50 PM, Joleen Barker <oldenuf2no...@gmail.com>
>> wrote:
>>
>>> I didn't get too far. For the option b and setting the
>>> swallowOutput=true in right place I need to get some clarification.
>>>
>>> I was looking up more information about the swallowOutput parm so I
>>> understood more. In Christopher's comments he spoke about updating the
>>> context xml. This is where I am confused. When I think of the word
>>> "context" it has always referring to the vendors web page to log in with
>>> and the context set is "cfcc". There is a file named cfcc.xml in the
>>> <Install_directory>/server/conf/Catalina/localhost directory. Then there is
>>> the actual context.xml file located in the <Install_directory>/server/conf
>>> directory. I am not sure which one I would put the swallowOutput parm in.
>>> Maybe it would be both.
>>>
>>> The only items in the context.xml file that are not commented out are
>>> the following settings and it's a pretty small file:
>>>
>>> <Context>
>>> <WatchedResource>WEB-INF/web.xml</WatchedResource>
>>> <WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
>>> ...
>>> ...
>>> <Manager pathname="" />
>>> ...
>>> ...
>>> <Valve
>>> classname="org.apache.catalina.valves.CometConnectionManagerValve" />
>>> </Context>
>>>
>>> The cfcc.xml file that I have has the following:
>>>
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <Context cachingAllowed="true"
>>> charsetMapperClass="org.apache.catalina.util.CharsetMapper"
>>> className="org.apache.catalina.core.StandardContext" cookies="true"
>>> crossContext="false" debug="0" displayName="Secure Internet File Transfer
>>> Web Services" docBase="/opt/mftcc730/server/webapps/cfcc"
>>> mapperClass="org.apache.catalina.core.StandardContextMapper" path="/cfcc"
>>> privileged="false" reloadable="false" swallowOutput="false"
>>> useHttpOnly="false" useNaming="true"
>>> wrapperClass="org.apache.catalina.core.StandardWrapper">
>>> <Valve className="com.proginet.sift.tomcat.valve.LoginValve"/>
>>> <Valve className="com.proginet.sift.tomcat.valve.CfccAuthenticator"/>
>>> <Logger className="org.apache.catalina.logger.FileLogger" debug="0"
>>> directory="/opt/mftcc730/server/logs" prefix="localhost_cfcc_"
>>> suffix=".txt" timestamp="true" verbosity="2"/>
>>> <Realm className="com.proginet.sift.tomcat.ssldap.JDBCRealm"
>>> connectionName="cfcc" connectionPassword="TgPGKAy//0gDOq2Co5UnM2AE8pM="
>>> connectionURL="jdbc:mysql://
>>> 192.168.1.7:3306/mft730?characterEncoding=UTF8" debug="0" digest="SHA"
>>> driverName="com.mysql.jdbc.Driver" roleNameCol="RoleID"
>>> userCredCol="Passwd" userNameCol="UserID" userRoleTable="UsersMap"
>>> userTable="Users" validate="true"/>
>>> <Resource auth="Container" name="jdbc/sift" scope="Shareable"
>>> type="javax.sql.DataSource"/>
>>> </Context>
>>>
>>> Thank you.
>>>
>>> -Joleen
>>>
>>>
>>> On Wed, Nov 25, 2015 at 10:16 AM, Joleen Barker <oldenuf2no...@gmail.com
>>> > wrote:
>>>
>>>> Thank you for some direction.
>>>>
>>>> I'll go ahead and put back the logging as it was from the vendor using
>>>> the logging.properties file, etc. etc. so as to minimize their lack of
>>>> support due to me changing a lot in their product.
>>>>
>>>> Then I'll go on to try option b.
>>>>
>>>> I'll report back with how it goes.
>>>>
>>>> -Joleeb
>>>> Joleen,
>>>>
>>>> On 11/24/15 4:31 PM, Joleen Barker wrote:
>>>> > I have setup the logrotate using cron in the past and it was very
>>>> > successful on the Linux boxes but I could not find an equivalent
>>>> setup for
>>>> > AIX. Things seem so much easier on Linux. The company wants a
>>>> universal
>>>> > approach so that left that option out.
>>>>
>>>> Only some things are easier on Linux.
>>>>
>>>> This may help:
>>>> http://www-01.ibm.com/support/docview.wss?uid=isg3T1012796
>>>>
>>>> > I did see the section you copied in from the catalina.sh file but
>>>> couldnt
>>>> > make much out from it so I left it alone.
>>>> >
>>>> > I like the sound of option b. I know where the context xml file is.
>>>> (Under
>>>> > the Catalina/localhost/<context>.xml) Im not sure if this is what you
>>>> mean
>>>> > by descriptor.
>>>>
>>>> Yup, that's the one. Just add the swallowOutput setting and restart the
>>>> web application. (Or restart Tomcat if that's easier for you.)
>>>>
>>>> > If I did this would I leave the log4j config changes that I
>>>> > have in place that already?
>>>>
>>>> No, you wouldn't have to use log4j at all. JULI can do log-rotation as
>>>> well, though the options aren't as nice as log4j. Log4j is a really
>>>> great logging system, actually.
>>>>
>>>> -chris
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>
>>>>
>>>
>>
>
