• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Client purge crashes CF

New Here ,
Nov 11, 2013 Nov 11, 2013

Copy link to clipboard

Copied

We're running ColdFusion 9.01 Enterprise, Windows Server 2008 R2 (OS version 6.1).  The good news is that the server autostarts very quickly after the crash, such that it is hardly noticable.

Beginning a few weeks ago, we noticed this behavior and we're not able to associate it with any change.  What we've found is that every 1 hour and 7 minutes when the client purge is executed, we get a module fault in CFRegistry.dll.  We've tried changing the purge interval and also have tried changing the storage from registry to MS SQL.  No matter, the crash still occurs.

Is this a known issue, or is it known under what conditions such a thing occurs?  Dump is below from our event log.

Thanks,

Chuck Wyatt

Faulting application name: jrun.exe, version: 4.0.7.43259, time stamp: 0x4a980f7e

Faulting module name: cfregistry.DLL, version: 0.0.0.0, time stamp: 0x4a794bf8

Exception code: 0xc00000fd

Fault offset: 0x000000000000ab57

Faulting process id: 0x200c

Faulting application start time: 0x01cedef0ae71595a

Faulting application path: C:\JRun4\bin\jrun.exe

Faulting module path: C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\cfregistry.DLL


Views

785

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 19, 2013 Dec 19, 2013

Copy link to clipboard

Copied

We have exactly the same issue. Have you found a solution?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 20, 2013 Dec 20, 2013

Copy link to clipboard

Copied

LATEST

I believe so.  You'll find this solution documented by various people in various places, for example:
http://www.coldfusionmuse.com/index.cfm/2009/10/27/registry.bad.datasource.good

So what we did was two things:  1) Change the Session storage from the registry to MS SQL.  2) Remove the reference in the XML file (neo-clientstore.xml) to registry session storage, as documented in the attached link.

That fixed it for us.  It's been over a month and so far so good.

Chuck

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation