Question
Reporting a bug in Sandboxing
Since I don't see any way to submit a bug report to the
ColdFusion development team, I figure I might as well do it here:
Almost immediately after turning on sandboxing, various instances started randomly crashing with the error
Could not initialize class jrunx.cluster.ServerInfo
This would happen with different instances with a frequency of about one or two hits a day for several weeks. I would repeatedly attempt to restart the instance and after one, two, or a few tries, it would successfully restart. (I used "Stop" followed by "Start".)
I got my ColdFusion Guru to work with me on the problem with no results. He was the one who also helped me set up Sandboxing.
A little over a week ago I turned off sandboxing and since then there have been no JRun issues!
Before turning it off I noticed a pattern. One of the instances got the problem and I was unable to restart it after almost an hour of steady attempts. At the same time, one of the domains in the instance was undergoing a barrage of hits from an IP out of France (?). I stopped that domain and on the very next attempt, the instance started successfully. (I permanently blocked that IP and then restarted the domain.)
The next time I got the JRun error, I restarted the instance and then waited a minute before trying it with CFAdmin. It worked.
To shorten the story: by experimentation I’m pretty sure it is a timing issue. If a request hits CF too soon after it starts back up while sandboxing is on, it fails with the JRun error. If it has a chance to come up “completely” before the first request, then it is successful.
This meets my definition of a bug. What do you think?
Almost immediately after turning on sandboxing, various instances started randomly crashing with the error
Could not initialize class jrunx.cluster.ServerInfo
This would happen with different instances with a frequency of about one or two hits a day for several weeks. I would repeatedly attempt to restart the instance and after one, two, or a few tries, it would successfully restart. (I used "Stop" followed by "Start".)
I got my ColdFusion Guru to work with me on the problem with no results. He was the one who also helped me set up Sandboxing.
A little over a week ago I turned off sandboxing and since then there have been no JRun issues!
Before turning it off I noticed a pattern. One of the instances got the problem and I was unable to restart it after almost an hour of steady attempts. At the same time, one of the domains in the instance was undergoing a barrage of hits from an IP out of France (?). I stopped that domain and on the very next attempt, the instance started successfully. (I permanently blocked that IP and then restarted the domain.)
The next time I got the JRun error, I restarted the instance and then waited a minute before trying it with CFAdmin. It worked.
To shorten the story: by experimentation I’m pretty sure it is a timing issue. If a request hits CF too soon after it starts back up while sandboxing is on, it fails with the JRun error. If it has a chance to come up “completely” before the first request, then it is successful.
This meets my definition of a bug. What do you think?
AdChoices