5 Replies Latest reply on Sep 16, 2009 11:18 AM by hschlossberg

    WPC Access Log Interpretation/WPE Performance Issues

    jsussenbach

      Title

      WPC Access Log Interpretation/WPE Performance Issues

      Your post

      What do the result codes at the end of each line in the wpc_access_log.txt file indicate?  I'm having trouble with my wpe timing out (serving xml data) using a split configuration of Filemaker Server 10 with the core on Windows Server 2003 and the wpe components on Mac OSX Server 10.5.  Here are some sample lines from the wpc log.

       

      10.1.1.2:0 - Administrator 2009-03-11 14:20:02 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 455
      10.1.1.2:0 - Administrator 2009-03-11 14:20:03 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 10223
      10.1.1.2:0 - Administrator 2009-03-11 14:20:04 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 19256
      10.1.1.2:0 - Administrator 2009-03-11 14:20:04 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 1047
      10.1.1.34:0 - Administrator 2009-03-11 14:20:04 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 1058231
      10.1.1.2:0 - Administrator 2009-03-11 14:20:06 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 7743
      10.1.1.34:0 - Administrator 2009-03-11 14:20:06 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 1058231
      10.1.1.2:0 - Administrator 2009-03-11 14:20:07 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 10136
      10.1.1.2:0 - Administrator 2009-03-11 14:20:07 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 3539
      10.1.1.34:0 - Administrator 2009-03-11 14:20:08 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 9072
      10.1.1.34:0 - Administrator 2009-03-11 14:20:11 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 1058231
      10.1.1.34:0 - Administrator 2009-03-11 14:20:11 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 9331
      10.1.1.34:0 - Administrator 2009-03-11 14:20:13 -0500 "/fmi/xml/FMPXMLRESULT.xml" 200 9000
      10.1.1.34:0 - Administrator 2009-03-11 14:20:18 -0500 "/fmi/xml/FMPXMLLAYOUT.xml" 200 1058231






        • 1. Re: WPC Access Log Interpretation/WPE Performance Issues
          TSGal

          jsussenbach:

           

          Thank you for your post.

           

          The result codes at the end of each line are not relevant for the user.  They are for internal use only.

           

          TSGal

          FileMaker, Inc. 

          • 2. Re: WPC Access Log Interpretation/WPE Performance Issues
            jsussenbach
               So you're telling me that there is essentially no way to diagnose connectivity issues between the WPE and FMS components?
            • 3. Re: WPC Access Log Interpretation/WPE Performance Issues
              hschlossberg
                

              Though this thread was from April, it doesn't really seem to have been resolved for the original poster, and now I have a further question about it.  You note that the result codes are not really relevant.  Are you sure?  Can you tell us what they mean, just in case they really are relevant to us?

               

              I have either this:

              "/fmi/xml/fmresultset.xml" 200 42022

               

              or this:

              "/fmi/xml/FMPXMLRESULT.xml?-db=Music+Playlist&-lay=playlistsearch_web&-max=50&-sortfield.1=Sort_Order&-sortorder.1=ascend&xF_PlaylistID=16421&-find" 200 95000

               

              Are neither of the codes at the end an error code of ANY kind or perhaps a response time or anything else that might be meaningful to our debugging efforts?

               

              I've spent the afternoon trying to find out for my web guy why FileMaker Server temporarily stops responding to his scripts' XML calls.  

              • 4. Re: WPC Access Log Interpretation/WPE Performance Issues
                MartinBrändle
                  

                It's similar to a web access log. 200 is the HTTP status code (OK). 500 would mean that the server is not responsive anymore. The next number is the length of the XML message transmitted. This one should be kept small (e.g. by setting -max) in order to have a short response time. A very large number (e.g. several million bytes) indicates a mistake in your XML query which has as effect that probably all records are downloaded.

                 

                For tracking errors, more important than the wpc_access_log.txt is the pe_application_log.txt file. 

                 

                • 5. Re: WPC Access Log Interpretation/WPE Performance Issues
                  hschlossberg
                    

                  Martin Brändle wrote:

                  For tracking errors, more important than the wpc_access_log.txt is the pe_application_log.txt file. 


                  I'm not really sure what that pe_application_log data represents.  The last entry in it has some scripting errors from a couple months ago.