JRUN error on long AskMe answers June 16, 2005 9:27 AM   Subscribe

Hey, you know what's fun? Getting a JRUN error when you try to submit a long answer to AskMe.
posted by keswick to Uptime at 9:27 AM (45 comments total)

Waaaah.

What's the point, exactly? Matt's working on it and things have improved.
posted by Mid at 9:32 AM on June 16, 2005


He's not complaining. He specifically said it was FUN. Yeesh.
posted by agropyron at 9:34 AM on June 16, 2005


Something I learned many, many, many years ago was: when entering lengthy posts directly into a website edit box, always select and copy before posting. Oh yes. Oh yes indeedy.
posted by Decani at 9:36 AM on June 16, 2005




posted by Smart Dalek at 9:37 AM on June 16, 2005


Posts I make on any website that are longer than a few sentences, I compose in a text editor first, then copy and paste.
posted by nitsuj at 9:39 AM on June 16, 2005


Yeah, sorry about that. Still working on things.
posted by mathowie (staff) at 9:53 AM on June 16, 2005


What are you doing posting long answers to AskMe in the first place? Shouldn't you be dealing with those stacks of papers that are piled up all over your desk?
posted by weapons-grade pandemonium at 9:53 AM on June 16, 2005


Copy before you post. Quit yer bitchin'.
posted by Specklet at 9:56 AM on June 16, 2005


there's a certain length that just WONT ever go through? Or does it just sometimes fail?
posted by scarabic at 9:57 AM on June 16, 2005


Copy before you post. Quit yer bitchin'.

Note, oh fount of wisdom, that losing one's text might not be the issue at all. Not clear from keswick yet. If the submission rejects all posts beyond a certain length, backed up or not, that's a bug. And reporting bugs ain't bitchin'.

So quit yer preachin' until we have the facts.
posted by scarabic at 9:59 AM on June 16, 2005


scarabic, why would you think this is a bug report? It's posted to the 'uptime' category and not 'bug reports'. It includes no informational error message indicating a possible logic error in the server. And JRun errors are widely understood to indicate the site was down. So, yeah, Specklet's probably right. This is just keswick wanting people to see him bitch.
posted by nixerman at 10:03 AM on June 16, 2005


You know, if I were Matt, and I had so significantly improved the site's uptime in the past few days, then came in here and saw you whining about how your long post got eaten...I would NOT be as nice as to apologize to you.

We all know the site's buggy. We all know JRun eats posts at times. Do what everyone else is aware of: save your posts.
posted by ArsncHeart at 10:08 AM on June 16, 2005


paste from notepad.
posted by puke & cry at 10:23 AM on June 16, 2005


I've saved this post.
posted by OmieWise at 10:34 AM on June 16, 2005


I've saved this post.
posted by OmieWise at 10:34 AM PST on June 16 [!]

I saved Omie's post.
posted by docpops at 10:38 AM on June 16, 2005


At just $899 per CPU for a fully certified J2EE implementation, JRun 4 delivers commercial grade quality at a fraction of the cost of the alternatives.
posted by moift at 10:41 AM on June 16, 2005


So, yeah, Specklet's probably right. This is just keswick wanting people to see him bitch.

Yeah. Neener neener.
posted by Specklet at 10:50 AM on June 16, 2005


At just $899 per CPU for a fully certified J2EE implementation, JRun 4 delivers commercial grade quality at a fraction of the cost of the alternatives.

clearly, we need more CPUs.
posted by quonsar at 10:57 AM on June 16, 2005


keswick, you must have missed the meta thread where it was divulged that JRUN had been given an AI utility that allowed it to differentiate good advice vs. bad advice on AskMe.

This is no mere bug you experienced…
posted by naxosaxur at 11:05 AM on June 16, 2005


poor widdle keswicky
posted by xmutex at 11:13 AM on June 16, 2005


AskMe editbot deleted Keswick? Scary...
posted by Cranberry at 11:14 AM on June 16, 2005


I've had the same happen to me but usually just hitting the back button a couple times allows me to go reselect the text and save it for another time. Is that not possible on some browsers/systems?
posted by KevinSkomsvold at 11:16 AM on June 16, 2005


Does this mean we can blame Keswick for today's JRun downtime?
posted by five fresh fish at 11:21 AM on June 16, 2005


Maybe the JRun thought your comment was too wordy and thought you should restate it more succinctly?

Its a feature!
posted by fenriq at 11:21 AM on June 16, 2005


Blame all of us, fff. Bitching about JRun bitchers is even more recursive and self-fulfilling than learning about brains.
posted by weapons-grade pandemonium at 11:50 AM on June 16, 2005


This thread is closed to new comments.
posted by erebora at 12:41 PM on June 16, 2005


I, for one, feel sorry for keswick.
posted by _sirmissalot_ at 1:37 PM on June 16, 2005


maybe we should switch to tomcat.
posted by delmoi at 1:41 PM on June 16, 2005


"Getting a JRUN error when you try to submit a long answer to AskMe."

My question is: why does he mention "long answer?"

Is it because losing a comment to a normal uptime issue just sucks *more* when it's a long comment?

Or is there something about long comments that crashes JRun? I've worked in web QA and I've seen issues before with long strings passed through a search engine or form submitter, where short strings do fine. If it is a crasher bug, then "uptime" applies. Have you ever wondered *why* the site goes down? Maybe there's a bug that brings it down when very long comments are entered. I have been *asking* whether this is what keswick is trying to report.

So again: my point is that you don't call someone names before you even understand what they're saying. But by all means, continue thinking you're smart before you know what you're talking about. That's what this place is all about.
posted by scarabic at 1:47 PM on June 16, 2005


I think it's rather safe to assume that keswick is annoyed that he/she "lost" a lengthy post, that took a while put together. Annoying? Yes. Understandably so. But uhh... whining about it here doesn't really do any good.

Since keswick hasn't returned to add any new information to this topic, I think your continued over-the-top benefit-of-the-doubt and brainstorm of possible alternative motives, coupled with your staunch defense of these actions... well, it's all just a bit silly scarabic.
posted by Necker at 2:01 PM on June 16, 2005


Is it because losing a comment to a normal uptime issue just sucks *more* when it's a long comment?

Yes.
posted by keswick at 2:25 PM on June 16, 2005


And I've seen numerous multi-screen comments successfully post to AskMe, so I'd be really surprised if it was the length of the reply that caused the problem. Just unfortunate timing, I suspect.
posted by raedyn at 2:37 PM on June 16, 2005


But by all means, continue thinking you're smart before you know what you're talking about.


Ah, the irony. Everyone else in this post understood what keswick was saying except you.
posted by jonson at 2:40 PM on June 16, 2005


And now I'm feeling sorry for scarabic.
posted by _sirmissalot_ at 2:52 PM on June 16, 2005


I'm feeling sorry for myself, as usual.
posted by ori at 3:17 PM on June 16, 2005


How does one subscribe to scarabic's snark-deflecting service? Are the rates good?
posted by catachresoid at 4:09 PM on June 16, 2005


usually just hitting the back button a couple times allows me to go reselect the text and save it for another time.

What he said.
posted by mediareport at 7:55 PM on June 16, 2005


This thread was worth it just to see Smart Dalek's Waaaaaaambulance!
posted by Steve_at_Linnwood at 8:38 PM on June 16, 2005


"What he said."

Me, too. Almost without exception if I get a posting error I can "back" the browser to the input form and, voila!, my text is still there. On IE, on Firefox, whatever. Hell, I'm typing this now on K-Meleon. Let's try... Well, it worked backspacing from preview. I'll try backspacing after I hit "post", too.
posted by Ethereal Bligh at 8:42 PM on June 16, 2005


"What he said."

Me, too. Almost without exception....


Ah. See? I'm at a loss to understand why this doesn't work for other people. Is it just that they don't know they can do this?
posted by Ethereal Bligh at 8:43 PM on June 16, 2005


I'm perturbed to be cast as defending keswick but glad to have an answer to my question. The downtime sucks for many reasons, but I agree that there's no excuse for totally losing a long comment. Keswick: save your work or I'll have to fire you.
posted by scarabic at 8:49 PM on June 16, 2005


I'm at a loss to understand why this doesn't work for other people.
This doesn't work for me at work if I use IE - I assume because of cache settings. It does work if I use Firefox, but I run that from a USB drive with my own cache settings. Don't assume that everyone operates in the same environment that you do.
posted by dg at 10:13 PM on June 16, 2005


I'm so glad someone brought this up.




















really.
posted by shmegegge at 2:21 AM on June 17, 2005


I was going to post a long snarky comment here, but a JRUN error edited it all down to this one line. Should I start a new thread?
posted by caution live frogs at 5:46 AM on June 17, 2005


If the Back button option doesn't seem to work for you in IE, you can go to File and choose Work Offline first. This will force IE to use its cached copy, if it has one, when you hit Back. If this still doesn't work, then there just isn't a cached copy, but it is worth trying. I hate losing posts on webpages. Does javascript have access to the system clipboard? What about letting a small script reside in the composition page that, when run, copies the comment text into your clipboard before trying to load the actual "post this comment" page from the server?
posted by odinsdream at 6:25 AM on June 17, 2005


« Older View all comments/posts by this user   |   See? We CAN have nice things! Newer »

You are not logged in, either login or create an account to post comments