Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #1607
Closed
Open
Issue created Apr 29, 2001 by Peter Bortas@zinoOwner

Poor ODBC hangs Pike/Roxen

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1607

Reported by Toyotomi Hideyoshi, roxen@asylos.org

I use an ODBC driver in Windows that is not very good. When you write certain malformed SQL statements, the driver will not respond.

I am currently running Coldfusion/IIS and Roxen side by side in evaluation.

I am reporting this as a bug, when perhaps it's more of a feature request. With the above-mentioned ODBC driver web code with certain SQL errors will result in the page request endlessly waiting. Coldfusion and Roxen both exhibit this behaviour. It is fully expected.

However, when you stop trying to load the page Coldfusion will be able to continue processing other pages (or the same page after you fix your SQL errors). Roxen on the other hand will not respond to any further requests. It is still tripping on the ODBC driver I assume. Perhaps a threading issue.

Assignee
Assign to
Time tracking