Catalina log file size is large on the TSIM

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Operations Management


    COMPONENT:

    TrueSight Operations Management


    APPLIES TO:

    TrueSight Operations Management all versions less than 11.3.02



    QUESTION:

    The ./pw/tomcat/logs/catalina.log file can grow to the GB size range, which can risk exhausting disk space. Sample excerpt can be seen repeatedly:

    INFO 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Successfully reconnected to tcp://localhost:8093?useInactivityMonitor=false
    WARN 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Transport (tcp://localhost/127.0.0.1:8093@59027) failed, attempting to automatically reconnect
    java.io.EOFException
    at java.io.DataInputStream.readInt(DataInputStream.java:392)
    at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258)
    at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221)
    at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213)
    at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
    at java.lang.Thread.run(Thread.java:748)
    INFO 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Successfully reconnected to tcp://localhost:8093?useInactivityMonitor=false
    WARN 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Transport (tcp://localhost/127.0.0.1:8093@59029) failed, attempting to automatically reconnect
    java.io.EOFException
    at java.io.DataInputStream.readInt(DataInputStream.java:392)
    at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258)
    at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221)
    at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213)
    at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
    at java.lang.Thread.run(Thread.java:748)
    INFO 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Successfully reconnected to tcp://localhost:8093?useInactivityMonitor=false
    WARN 04/15 07:26:59 org.apache.activemq.transport.failover.FailoverTransport Transport (tcp://localhost/127.0.0.1:8093@59031) failed, attempting to automatically reconnect
    java.io.EOFException
    at java.io.DataInputStream.readInt(DataInputStream.java:392)
    at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258)
    at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221)
    at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213)
    at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
    at java.lang.Thread.run(Thread.java:748)


    ANSWER:

    The solution would be to upgrade to 11.3.02 & make use of the log pruning capability located here:
    https://docs.bmc.com/docs/TSInfrastructure/113/configuring-tomcat-log-pruning-parameters-860484777.html

    If upgrading isn't in the cards for the near future, then check for the following entry in pronet.conf
    jms.activemq.maxReconnectAttempts=5
    If it is not present, then stop TSIM server, delete catalina.log, add the above entry & save the file, restart TSIM server.

    Also, check whether there are any recent java*hprof files in ./pronto/logs. If so, see if the MaxHeap/RAM are sufficient for the TSIM.

    Sending the size & checksum of pw/wildfly/standalone/deployments/activemq-rar.rar (ls -l, cksum activemq-rar.rar) to BMC Support might also be useful here. 
    Also send
    the output to 'pw viewhistory'.


    Article Number:

    000167332


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles