Users sees this error: Can Not Connect to JRUN Server

Been having this problem repeatedly lately.
(Basic client environment is CFMX on 2K SP4 against SQL Server on
separate machine)

They are concluding updating Session and Application variable access to
use CFLOCK, as well as running Jrun from a cmd prompt, which cycles at a
certain interval. 
(Sorry I forgot who to credit for this script; uses kill.exe 2x etc)
Apparently though, if JRun has already gone loopy, this script fails)

I was able to determine that JRUN threw some sort of an out of memory
error prior to going haywire. The load on the machine was not that high
at the time though, and there was plenty of allocated memory available. 

Has anyone switched to a different java version with successful results?
(Someone suggested this; no knowledge on results)

Someone else suggested this problem might have to do with the way CFMX
handles Datasource connections. I tried unchecking the "maintain
database connection" as they suggested, but other than increasing the
calls to create connections etc, it still crashed after maybe 2 hours
up.

Just to make things worse, sometimes it will go days with no problems.

I was wondering if anyone has run into this situation before, and if so
what
They might have done additionally to correct this problem.

I am contemplating recommending my major clients dump CFMX at this point
and start migrating everything to Java. 
(Not their favorite choice due to time/$ considerations)

Really would be a disappointment though.

Thanks guys; any thoughts would be helpful.

Marc


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Get the mailserver that powers this list at 
http://www.coolfusion.com

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to