12 Replies Latest reply on Feb 17, 2011 2:04 PM by user9753

    FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard

    craigmckessar

      Summary

      FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard

      Description of the issue

      It appears that with Snow Leopard on FMS 11 or FMP 11 via IWP there is an issue with New Window / Close Window. I have tested this on Leopard with FMS 10 and there is no bug. Likewise with FMP 11 on Windows 7 it works fine because the bug doesn't occur. Bug occurs in all browsers. Some script steps that if placed after the close window step causes the WPE to crash. Some script steps appear to work fine if placed after the Close Window script step, eg Go to first required and exit script. Steps that do not work after the close window command include Set Field, Set Variable, If Statements. Note: All script steps have not been tested. This will cause the web publishing engine to stop. In the browser you will get a message saying 'Service temporarily unavailable'. Both myself and one of our clients have experienced this issue.

        • 1. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
          DennisSirotkine

          We have the same problem with FMSA 11 Advanced via IWP.

           

          FileMaker Product(s) involved:



          FileMaker Server 11.0.1.99 Advanced


          Operating System(s) involved:

          Mac OS X Leopard Server 10.5.8, Mac OS X 10.6.3, ...?

          Detailed description of the issue:

          For example, there are two files, A.fp7 and B.fp7.

          # "Sctipt A" from file "A":
          ############################
          Perform Script ["Sctipt B" from file "B"]
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          New Record/Request
          Commit Record/Request[]

          # "Sctipt B" from file "B":
          ############################
          New Window []
          Pause/Resume Script [Indefinitely]
          Close Window [Current Window]

          In IWP mode, the Close Window [..] script step after Resume crashes FM Web Publishing Engine.


          Exact steps to reproduce the issue:

          1. Create two files as described above

          2. Run "Sctipt A" from file "A"

          3. Perform Resume/Continue in file B

          4. Optionally: Repeat steps 2 and 3


          Expected Result:

          A window from file "A" will appear.

          Actual Result:

          IWPE crash.

          Exact text of any error message(s) that appeared:

          Service Temporarily Unavailable

          Any additional configuration information/troubleshooting that is relevant to the issue:

          2010-06-03 19:06:36 Publishing Engine Access Error 127.0.0.1:63925 - - "/fmi/conf/config.wpc" 401 0

          2010-06-03 19:07:19 Web Server Error [12299:0000] [error] ajp_get_reply::jk_ajp_common.c (1592): (wpc1) Tomcat is down or refused connection. No response has been sent to the client (yet)
          2010-06-03 19:07:19 Web Server Error [12299:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc1) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port
          2010-06-03 19:07:19 Web Server Error [12299:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc2) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port

          +++++++++++++++++++++++++++++

          Process: FM Web Publishing [17809]
          Path: /Library/FileMaker Server/Web Publishing/publishing-engine/wpc/FM Web Publishing.app/Contents/MacOS/FM Web Publishing
          Identifier: FM Web Publishing
          Version: ??? (???)
          Code Type: X86 (Native)
          Parent Process: fmserver_helperd [12062]

          Date/Time: 2010-06-03 19:07:19.549 +0400
          OS Version: Mac OS X 10.6.3 (10D578)
          Report Version: 6

          Exception Type: EXC_BAD_ACCESS (SIGSEGV)
          Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffffe
          Crashed Thread: 25

          Thread 25 Crashed:
          0 com.filemaker.wc9 0x000828e1 wc::WCScriptRuntime::RunButtonScript(Draco::FMWindowModel*, short) + 501
          1 com.filemaker.wc9 0x0009153c wc::FMImpl::ExecuteButtonScript(short) + 190
          2 com.filemaker.wc9 0x0011bc37 wc::IWPButtonScriptDispatchImpl::ModifyModel(wc::Ref<wc::HTTPServletRequestItf>&, wc::HierHashtable&, wc::FMController&) const + 1621
          3 com.filemaker.wc9 0x001198e6 wc::IWPDataSrcDispatchImpl::Dispatch(wc::Ref<wc::HTTPServletRequestItf>&, wc::HierHashtable&, wc::FMController&) const + 70
          4 com.filemaker.wc9 0x0010aaff wc::CGIDataSrcDispatchItf::TryDispatch(wc::Ref<wc::HTTPServletRequestItf>&, wc::HierHashtable&, wc::FMControllerWrapper&) const + 99
          5 com.filemaker.wc9 0x0010be7e wc::CGIDataSrcDispatchItf::UseExistingSession(wc::Ref<wc::HTTPServletRequestItf>&, wc::HierHashtable&, bool) const + 558
          6 com.filemaker.wc9 0x0011d095 wc::IWPDataSrcDispatchImpl::Dispatch(wc::Ref<wc::HTTPServletRequestItf>&, wc::HierHashtable&, bool) const + 237
          7 com.filemaker.wc9 0x0010a6b7 wc::CGIControllerImpl::service(wc::Ref<wc::HTTPServletRequestItf>&, wc::Ref<wc::HTTPServletResponseItf>&, wc::HierHashtable&) const + 263
          8 com.filemaker.wc9 0x00108458 wc::CGIBaseImpl::service(wc::Ref<wc::HTTPServletRequestItf>&, wc::Ref<wc::HTTPServletResponseItf>&) const + 114
          9 com.filemaker.wc9 0x0007e10a wc::HTTPVersion1_1Impl::ProcessRequest(wc::MessageContext volatile&, wc::Request&, wc::Response&, long long) const + 1660
          10 com.filemaker.wc9 0x00081522 wc::HTTPUserAgentImpl::ProcessRequest(wc::MessageContext volatile&, wc::Request&, wc::Response&, long long) const + 1474
          11 com.filemaker.wc9 0x00066ce3 wc::HTTPProtocolImpl::ProcessMessage(wc::MessageContext volatile&, wc::Request&, wc::Response&, long long, wc::TextInputStream&, wc::TextEncoding const&) const + 2777
          12 com.filemaker.wc9 0x00067186 wc::HTTPProtocolImpl::ProcessRequest(wc::MessageContext volatile&, wc::Request&, wc::Response&, long long) const + 614
          13 com.filemaker.wc9 0x0013e1b9 wc::AJPProtocolImpl::ForwardRequest(wc::MessageContext volatile&, wc::HierHashtable&, wc::SyncInputStream&, wc::SyncInputStream&, wc::SyncOutputStream&, wc::SyncOutputStream&, long long, wc::TextEncoding, wc::String) const + 1243
          14 com.filemaker.wc9 0x0013e898 wc::AJPProtocolImpl::ProcessRequest(wc::MessageContext volatile&, wc::Request&, wc::Response&, long long) const + 1082
          15 com.filemaker.wc9 0x00050e9f wc::InvokeMessageStreamTask::Run() + 1583
          16 com.filemaker.wc9 0x0004e18f wc::PooledTaskImpl::Run() + 103
          17 com.filemaker.wc9 0x00090605 wc::DracoThreadTask::Run() + 27
          18 com.filemaker.wc9 0x0004cadc RunThreadFunc + 112
          19 libSystem.B.dylib 0x970baa19 _pthread_start + 345
          20 libSystem.B.dylib 0x970ba89e thread_start + 34

          Thread 25 crashed with X86 Thread State (32-bit):
          eax: 0xfffffffa ebx: 0xb0d3245c ecx: 0x09028890 edx: 0x0613e898
          edi: 0x06136290 esi: 0xb0d32454 ebp: 0xb0d32478 esp: 0xb0d323b0
          ss: 0x0000001f efl: 0x00010202 eip: 0x000828e1 cs: 0x00000017
          ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
          cr2: 0xfffffffe

          Any workarounds that you have found:

          -


























































          • 2. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
            TSGal

            cmac87:

             

            Thank you for your post.

             

            I have been unable to replicate the problem.  This is what I have done:

             

            1. I opened a database file (Test.fp7) with FileMaker Pro 11 Advanced under Mac OS X 10.6.3.

             

            2. I created a new table with Text fields "First" and "Last".

             

            3. I created a button and attached a script that has:

             

            New Window []

            New Record/Request/Page

            Close Window []

            Set Variable [ $var ; "TSGal" ]

            Set Field [ Last ; $var ]

            Set Field [ First ; "TSGal" ]

             

            4. I turned on Instant Web Publishing, selected Test.fp7  and set access to all users.

             

            5. On a second machine, I launched a browser, accessed the other machine, and opened Test.fp7.

             

            6. I clicked on the button to run the script.  Everything worked properly.  I then clicked Submit.  No problem.

             

            7. I manually changed the first record back to no entry and clicked the button again.  No problem.

             

            8. I clicked Submit and then logged out.

             

            It would probably be best if you sent in a clone of your file, or a file that you are able to replicate the problem.  This will save some time, and I'll try to narrow down the cause.  I have sent you a private message (top of this page - right side - envelope icon just beneath the blue horizontal bar) with instructions where to send the file.

             

            TSGal

            FileMaker, Inc.

            • 3. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
              DennisSirotkine

              Dear TSGal,

               

              I can easily provide you with the example files if needed, please advise.

              Thanks
              --
              Best regards,
              Dennis Sirotkine


              • 4. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                TSGal

                cmac87:

                 

                I received your file.  Thank you.

                 

                I am able to replicate the problem with both Mac OS X 10.5.8 and Mac OS X 10.6.3.  I'm still working with the file to narrow down the problem, and it appears to be a combination of your script steps and a button to Resume Script. That is, if I don't click the Resume Script button, but instead click "Continue" in the Status Bar, I don't have the problem.  Can you confirm?

                 

                I'll keep you posted.

                 

                TSGal

                FileMaker, Inc.

                • 5. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                  craigmckessar

                  I confirm that the error only occurs when you press the button on the layout. The error did not occur when clicking "Continue" in the Status Bar.

                  • 6. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                    TSGal

                    cmac87:

                     

                    Thanks for the confirmation.

                     

                    Our Testing department has confirmed the issue and sent it to Development.

                     

                    TSGal

                    FileMaker, Inc.

                    • 7. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                      philmodjunk

                      May I have a bit more detail about "combination of script steps and a button to Resume Script." for the Known Bug List please?

                       

                      Perhaps this occurs with any paused script?

                      • 8. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                        TSGal

                        PhilModJunk:

                         

                        This doesn't appear to be a "black and white" issue.  There are some gray areas here, and the file has the problem.

                         

                        It definitely doesn't occur with any paused script.

                         

                        In general, here is some information.

                         

                        Script 1: Open a New Window, Set field value, Pause/Resume, Set Field Value, Close Window

                        Script 2: Open a New Window, Set field value, Pause/Resume, Close Window, Set Field Value.

                         

                        In essence, both scripts are identical except the last two steps are switched.

                         

                        When you run the first script and click a button to Resume Script, it works fine 100% of the time.  When you run the second script and click a button to Resume Script, it may work the first couple of times or crash Web Publishing Engine.

                         

                        I could not make this fail with my own file, but it does fail with the customer file, so there is another factor(s) involved, and our Testing department is trying to narrow it down.

                         

                        TSGal

                        FileMaker, Inc.

                        • 9. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                          philmodjunk

                          Hmmm, in script 2, once the window is closed, the set field executes in context of the original layout in the parent window...

                           

                          I assume you are looking at that to see where the differences might lie...

                          • 10. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                            user9753

                            Has this been resolved yet?  I am running 11.0.2.217 on both OS X Server 10.5.8 as well as Windows Server 2008 and in both cases the WPE is crashing. (I am also opening a virtual window and closing it)

                            • 11. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                              TSGal

                              SlyBriFry:

                              Thank you for your post.

                              There is no additional information at this time.  The information was sent to Development.

                              Are you using Pause/resume script before window is closed and/or Set Field after window is closed?  This is what appears to be the problem with forum users "cmac87" and "Dennis Sirotkine".  If not, then you should address this in a different post/thread.

                              TSGal
                              FileMaker, Inc.

                              • 12. Re: FileMaker Pro 11 and FileMaker Server 11 IWP bug on Snow Leopard
                                user9753

                                Pause/Resume: In one instance yes, in others no.

                                Set Field:  Yeah, I'm doing a series a of set fields both before and after.

                                I have been able to stabilize the system by starting EVERY script with a Commit step.  But again, because we have GLOBAL fields out on the layouts that we want open at all times, I need to make sure every script ENDS with an Open step.

                                It seems performing db functions while a record is open, causes it to crash.  I would say about 75% of the time.