BMC Performance Manager Portal web transaction alarm returns an I/O Exception error and a timeout. What can we do to troubleshoot this?

Version 3
    Share This:

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


    BMC Performance Manager Portal


    BMC PM Portal


    BMC Performance Manager Portal


       Getting time outs for web transaction monitoring:   
    I/O error occurred: org.apache.commons.httpclient.HttpRecoverableException: Error in parsing the status line from the response: unable to find line starting with "HTTP":patsdk-http  
    What can be done to troubleshoot?



    Legacy ID:KA340404

      Getting time outs for web transaction monitoring:  
    I/O error occurred: org.apache.commons.httpclient.HttpRecoverableException: Error in parsing the status line from the response: unable to find line starting with "HTTP":patsdk-http 
      Additional debugging can be enabled: 
      Go to <Install_Dir>\Remote Service Monitor\RSM\conf\  
    First take backup of the file named rsmwrapper.conf 
      stop RSM and Portal services  
    Edit rsmwrapper.conf 
      Search for  
    # Java Additional Parameters 
      Below that see how many parameters are present 
      The parameters are in following format<no>=<value> 
      For example 
      See how many uncommented parameters are there  
    (Uncommented means the parameter should not start with # symbol) 
      Generally there are 5 uncommented parameters and 2 commented parameters related to debug,  
    so count the maximum number of parameters and then we need to add 2 new timeout parameters. 
    Add those elements to the next line after the commented elements 
      Suppose you have entries in your rsmwrapper.conf as follows:  
    # Java Additional Parameters  
      # Uncomment to add in debugging 
      So you will add new parameters after the commented parameters as follows: 
      These are the connection timeout and read timeout parameters we are adding.  
    Please keep in mind, we have to add new parameter's count = previous maximum uncommented parameter's count+1. 
      Here we have considered that you have 5 uncommented elements so we added two elements as 
      If you are having different numbers of uncommented parameters, then you have to create the parameters accordingly.  
    We are not considering the commented element's count. 
      Suppose your last uncommented element is<VALUE>  
    you will have<N+1>=-Dcom.bmc.patrol.patsdk.lib.http.connectTimeout=60000<N+2>=-Dcom.bmc.patrol.patsdk.lib.http.readTimeout=60000 
      After that save the file  
    Do not change any other contents of this file. 
      Do the same for other RSM 
      Start the Portal and  both RSM services  
    After you start your RSM,  wait a couple of minutes and then open the boot log under the following path:  
    <Install_Directory>\Remote Service Monitor\RSM\server\rsm\log 
      Search for following entries  
    com.bmc.patrol.patsdk.lib.http.readTimeout: 60000  
    com.bmc.patrol.patsdk.lib.http.connectTimeout: 60000 
      If you could find those entries, that means you have configured timeout successfully. 
      Now check if the problem persists  
    If yes then provide us with the rsm.log, newly created (both) rsmwrapper.conf  and (both) boot.log files. 
    In case of any other problems please do the following: 
    Stop Portal and (both) RSM.  
    After successfully stopping the services 
      Move the changed rsmwrapper.conf files to temporary folder. If the problem persists, please send the rsm and boot log files to  
    Copy original backed up files to  <Install Dir>\Remote Service Monitor\RSM\conf\  
    Restart Portal and (both) RSM services to restore the system to normal. 
      Here are few common questions: 
      Q. What was the original time out value?  
    Ans. It is 30 seconds. 
      Q. How does one come to know, if this has taken effect?  
    Ans. After applying new changes and restarting servers. You can verify the timeout value in the boot.log 
      Q. How will this effect the system?  
    Ans. After increasing the timeout, the RSM will wait for new timeout value 60 seconds, in that time it will get the connection and the timeout wont occur.  So the theory is that if you raise the time out value the HTTP error will not occur. 
    Related Products:  
    1. BMC Performance Manager Portal


    Article Number:


    Article Type:


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