Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Please Help: "response passed but not finished" in Apache error log
Forum Updated to NodeBB v4.3 + New Features

Please Help: "response passed but not finished" in Apache error log

Scheduled Pinned Locked Moved Mobile and Embedded
2 Posts 1 Posters 712 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    sharkman
    wrote on last edited by
    #1

    Good Morning,

    I've created a PHP extension for LAMPP/PHP from C++ source code that uses the QT framework. I'm using QCoreApplication, QObject and QEventLoop. I have a QT server running that creates a socket in the /tmp folder of Ubuntu. If I run the client from the command line, all works as expected. If I run the PHP script from Apache using an HTML file what a button that runs the client, the QT framework appears to hang and I have to click the button a second time to complete. What I see in the Apache error log is the output "response passed but not finished." My only thought currently is something is not configured correctly to handle the QT calls. My calls appear basically as follows:

    Create QCoreApplication
    Create QEventLoop
    Create QObject

    QObject->LoadInterface(...)
    QObject->Connect(...);

    QMetaObject::invokeMethod(QObject, ...);

    QEventLoop->exec(QEventLoop::WaitForMoreEvents);

    What appears to hang and cause the error output to the apache log is the call to exec. I've tried to use
    QCoreApplication::flush(); before the call to invokeMethod, but that didn't work. If anyone has an experience with this or has any clues what might be causing this issue I would greatly appreciate any help I receive.

    Thank You,
    Respectfully,
    Wes Brown.

    1 Reply Last reply
    0
    • S Offline
      S Offline
      sharkman
      wrote on last edited by
      #2

      I resolved this issue by adding the destructors to all the classes where QT objects were being instantiated by the constructors.

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved