Coldfusion Stack Overflow Error
Contents |
ColdFusion JRUN Stack Overflow Error By Ben Nadel on August 11, 2010 Tags: ColdFusion This morning, I was
Stack Overflow Error C++
doing some local ColdFusion development as I am normally; and, everything fix stack overflow error was working fine until I suddenly started getting this ColdFusion JRUN error:java.lang.StackOverflowError at coldfusion.compiler.ExprAssembler.assembleExpr(ExprAssembler.java:144) at coldfusion.compiler.ExprAssembler.cast(ExprAssembler.java:1108) stack overflow error windows xp at coldfusion.compiler.StmtAssembler.cast(StmtAssembler.java:362) at coldfusion.compiler.ExprAssembler.assembleExpr(ExprAssembler.java:163) at coldfusion.compiler.ExprAssembler.assembleExpr(ExprAssembler.java:321) at coldfusion.compiler.ExprAssembler.cast(ExprAssembler.java:1108) at coldfusion.compiler.StmtAssembler.cast(StmtAssembler.java:362) at .... etc.I was in the middle of making a few updates across various files so, I
Stack Overflow Error Windows 7
just assumed that I must have changed something that created a weird memory leak. After commenting out a whole lot of code, I finally narrowed down the cause of the problem to an enormous, compound CFIF statement. This particular CFIF statement had well over 200 conditionals (don't ask), so I could maybe see that it
Stack Overflow Javascript Error
was taking a bunch of memory; but, not only did I not believe that it was killing all of the RAM, it wasn't even part of the code that I was updating.Starting to suspect that my code was not the culprit at all, I took a look at the Activity Monitor. There, I found out that JRUN was only using about 120MB or RAM. That might sound like a lot, but this sexy beast typically muscles ahead at close to 600MB of RAM. For one reason or another this computer decided to knock JRUN's legs out from under it?Anyway, I restarted the JRUN server and the RAM went back up to about 570MB. The random stack overflow error was gone. I have no idea what caused it; but, I'm throwing it out there in case anyone else runs into the same thing. Tweet This Fascinating post by @BenNadel - Strange ColdFusion JRUN Stack Overflow Error Thanks my man — you
will appear to come out of no-where.One day everything will work fine and, the next, without any change you can think of, you see your site stop to respond.Upon digging into the exception.log stack overflow line error file you see something like this:"Error","jrpp-0","04/20/10","17:33:53",,"'' The specific sequence of files included or
Stack Overflow Line 0 Error
processed is: C:\Webroot\Test4\TestFile.cfm'' "java.lang.StackOverflowError at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2263)This for me occurred when serializing/de-serializing data. But anytime you run into this you have to stack overflow error java ask yourself one primary question.Did this happen because of my logic? If yes, go revise your logic first.If you are certain your stuff is solid, you need to increase the Stack Size by http://www.bennadel.com/blog/1982-strange-coldfusion-jrun-stack-overflow-error.htm providing the -Xss directive to the jvm upon ColdFusion startup.I would bump it four fold; while the default seems to be slightly different based on OS, it is normally in the 300-400kb range.I bumped mine up first to 10MB, then, reduced it to find out exactly what was workable.The -Xss argument can be specified in kb e.g. -Xss512k or in mb, e.g. -Xss1m.here is an image with configured http://boncode.blogspot.com/2011/04/cf-coldfusion-javalangstackoverflowerro.html jvm:Cheers,B. Posted by bman at 12:38 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Reactions: 2 comments: Dubai said... Excellent pieces. Keep posting such kind of information on your blog. I really impressed by your blog. Vee Eee Technologies December 9, 2011 at 5:24 AM Ryan said... So what did you end up setting it to? August 21, 2015 at 2:35 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2016 (3) ► September (2) ► April (1) ► 2015 (3) ► November (1) ► July (1) ► May (1) ► 2014 (2) ► November (1) ► June (1) ► 2013 (5) ► October (1) ► June (1) ► April (1) ► February (1) ► January (1) ► 2012 (17) ► November (2) ► October (2) ► September (2) ► August (1) ► July (1) ► June (3) ► May (1) ► April (2) ► January (3) ▼ 2011 (20) ► December (3) ► November (1) ► October (3) ► September (2) ► August (3) ► July (2) ▼ April (2) CF: Coldfusion java.lang.StackOverflowError inno: converting Ansi string to string ► March (1) ► February (2) ► January (1) ► 2010 (14)
when testing Mockbox 2.1. Testing it to see if we could http://blog.adamcameron.me/2013/07/yeah-so-it-wouldnt-be-my-working-week.html upgrade to it (no, not until this is fixed). We already could not upgrade to 2.0 due to another issue (MOCKBOX-6), so on 1.3 we stay for http://serverdefects.com/Coldfusion-Stack-Overflow-Error~JVRGv8yc38FqhjUmz25daYSG5aAZ7HIdnPN5uOyGiuc=.html the time being. Both of these issues have been ColdFusion problems that Mockbox has been victim of though. Which sucks a bit for Luis & co. Anyway, stack overflow here's the latest one. It's quick and easy. Consider this code: function f(){ } st = { f = f }; s = serializeJson(st); writeDump(variables); Here I have a struct which has a function reference within it. And when I try to serialise that, I get a 500 error, and this in my exception.log: "Error","jrpp-0","07/12/13","16:34:44",,"'' stack overflow error The specific sequence of files included or processed is: D:\websites\www.scribble.local\hb\mockbox\functionbug\serializeJsonBug.cfm'' " java.lang.StackOverflowError at java.lang.Class.isInstance(Native Method) at coldfusion.runtime.dotnet.DotNetServiceImpl.isDotNetObject(DotNetServiceImpl.java:222) at coldfusion.runtime.StructBean.shouldConvertMethodsToFields(StructBean.java:367) at coldfusion.runtime.StructBean.getNames(StructBean.java:317) at coldfusion.runtime.Scope$ScopeSet.iterator(Scope.java:231) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:329) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:297) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:349) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:297) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:349) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:297) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:349) at coldfusion.runtime.JSONUtils.serializeJSON(JSONUtils.java:297) And that goes on for about 140kB. This is on CF9.0.1. On Railo it serialises OK, but as a struct. Now I have no expectations for this to work, but I don't expect it to cause a stack overflow. I've just run it on CF10, and I get this: { "F":{ "REMOTE":3, "PACKAGE":2, "SuperScope":null, "PUBLIC":0, "Access":0, "MethodAttributes":[], "PagePath":"C:\\ColdFusion10\\cfusion\\wwwroot\\shared\\junk\\junk.cfm", "next":null, "Metadata":{ "PARAMETERS":[], "NAME":"f" }, "PRIVATE":1, "FunctionNameKey":{ "SERIALIZABLE":{ "SERIALIZABLE":{ "SERIALIZABLE":{ "SERIALIZABLE":{ "SERIALIZABLE":{ "SERIALIZABLE":{ (and that continues for another 120kB of "SERIALIZABLE") So... err... don't try to serialise functions on ColdFusion, I guess! I'll raise a bug: 3594386. And then go to the pub. -- Adam Posted by Adam Cameron at 17:02 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Bugs, ColdFusion, JSON Newer