Strange Messages causing log file to bloat - version 1.362

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Strange Messages causing log file to bloat - version 1.362

tim.arant

Hi All,

It appears that there are some tracing messages being logged to the Hudson log.  This is causing our log to grow exponentially as compared to version 1.357.

For example:
                1.357                Average log size for 2 weeks 20 MB.
                1.362                Average log size for 2 weeks 60 MB

Here is an example of the messages...

INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processOutgoing
INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Sending REQUEST
INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processIncoming
INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Recieved RESPONSE
INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM org.jinterop.dcom.core.PingObject read
INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO: Simple Ping Succeeded
INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run
INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Running ClientPingTimerTask !
INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run
INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Within ClientPingTimerTask: holder.currentSetOIDs, current size of which is 0
INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.PingObject write
INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Simple Ping going for setId: 00000: 00 00 00 06 00 02 24 3B                          |......$;        |
INFO   | jvm 1    | 2010/07/20 20:49:21 |
INFO   | jvm 1    | 2010/07/20 20:49:21 |

These message started to show with 1.363 ( although the timing is unsure ).

We have had to down-grade to 1.362, due to issue 6819.
        HUDSON-6819 Jobs are triggered twice occasionally

However, these trace-like messages are still appearing in our 1.362 log.


Any help here will be greatly appreciated.



Phone 419-222-8207 Cell  567-204-6915

This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.
Reply | Threaded
Open this post in threaded view
|

Re: Strange Messages causing log file to bloat - version 1.362

tim.arant

Hi All,

This issue has been solved.

I don't know at what point that this was added, but, until we upgraded to 1.363 ( now using 1.362 ) we did not get these messages.

Here is what we found....

Manage Hudson--->System Log-->Log Levels

        Modified "org.jinterop" from level "INFO" to level "SEVERE".
       
We are no longer getting these trace messages in oour



This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.



From: [hidden email]
To: [hidden email]
Date: 07/20/2010 10:03 PM
Subject: Strange Messages causing log file to bloat - version 1.362






Hi All,


It appears that there are some tracing messages being logged to the Hudson log.  This is causing our log to grow exponentially as compared to version 1.357.


For example:

               1.357                Average log size for 2 weeks 20 MB.

               1.362                Average log size for 2 weeks 60 MB


Here is an example of the messages...


INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processOutgoing

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Sending REQUEST

INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processIncoming

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Recieved RESPONSE

INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM org.jinterop.dcom.core.PingObject read

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO: Simple Ping Succeeded

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Running ClientPingTimerTask !

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Within ClientPingTimerTask: holder.currentSetOIDs, current size of which is 0

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.PingObject write

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Simple Ping going for setId: 00000: 00 00 00 06 00 02 24 3B                          |......$;        |

INFO   | jvm 1    | 2010/07/20 20:49:21 |
INFO   | jvm 1    | 2010/07/20 20:49:21 |


These message started to show with 1.363 ( although the timing is unsure ).


We have had to down-grade to 1.362, due to issue 6819.

       
HUDSON-6819 Jobs are triggered twice occasionally

However, these trace-like messages are still appearing in our 1.362 log.



Any help here will be greatly appreciated.






This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.


Reply | Threaded
Open this post in threaded view
|

Re: Strange Messages causing log file to bloat - version 1.362

tim.arant

Hello all....too tired....or fat fingers....  :)

This issue has been solved.

I don't know at what point that this was added, but, until we upgraded to 1.363 ( now using 1.362 ) we did not get these messages.


Here is what we found....


Manage Hudson--->System Log-->Log Levels


       Modified "org.jinterop" from level "INFO" to level "SEVERE".

       
We are no longer getting these trace messages in our logs.



Phone 419-222-8207 Cell  567-204-6915

This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.



From: [hidden email]
To: [hidden email]
Date: 07/21/2010 11:16 PM
Subject: Re: Strange Messages causing log file to bloat - version 1.362






Hi All,


This issue has been solved.


I don't know at what point that this was added, but, until we upgraded to 1.363 ( now using 1.362 ) we did not get these messages.


Here is what we found....


Manage Hudson--->System Log-->Log Levels


       Modified "org.jinterop" from level "INFO" to level "SEVERE".

       
We are no longer getting these trace messages in oour



This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.



From: [hidden email]
To: [hidden email]
Date: 07/20/2010 10:03 PM
Subject: Strange Messages causing log file to bloat - version 1.362







Hi All,


It appears that there are some tracing messages being logged to the Hudson log.  This is causing our log to grow exponentially as compared to version 1.357.


For example:

              1.357                Average log size for 2 weeks 20 MB.

              1.362                Average log size for 2 weeks 60 MB


Here is an example of the messages...


INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processOutgoing

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Sending REQUEST

INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM rpc.DefaultConnection processIncoming

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO:
INFO   | jvm 1    | 2010/07/20 20:47:21 |  Recieved RESPONSE

INFO   | jvm 1    | 2010/07/20 20:47:21 | Jul 20, 2010 8:47:21 PM org.jinterop.dcom.core.PingObject read

INFO   | jvm 1    | 2010/07/20 20:47:21 | INFO: Simple Ping Succeeded

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Running ClientPingTimerTask !

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.JIComOxidRuntime$ClientPingTimerTask run

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Within ClientPingTimerTask: holder.currentSetOIDs, current size of which is 0

INFO   | jvm 1    | 2010/07/20 20:49:21 | Jul 20, 2010 8:49:21 PM org.jinterop.dcom.core.PingObject write

INFO   | jvm 1    | 2010/07/20 20:49:21 | INFO: Simple Ping going for setId: 00000: 00 00 00 06 00 02 24 3B                          |......$;        |

INFO   | jvm 1    | 2010/07/20 20:49:21 |
INFO   | jvm 1    | 2010/07/20 20:49:21 |


These message started to show with 1.363 ( although the timing is unsure ).


We have had to down-grade to 1.362, due to issue 6819.

     
HUDSON-6819 Jobs are triggered twice occasionally

However, these trace-like messages are still appearing in our 1.362 log.



Any help here will be greatly appreciated.






This e-mail message and any attachments may contain confidential, proprietary or non-public information.  This information is intended solely for the designated recipient(s).  If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail.  Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited.  Any opinions expressed in this e-mail are those of the author personally.