Skip to main content

HTTP 500 error on Blogger

This is something I never encountered before. Internal server error with Blogger.
java.lang.OutOfMemoryError!


Blogger HTTP Status 500

And no, I am certainly not playing Fools Day here. It may be April 1st today, but this error was for real. I wonder how often Blogger encounters these.

Comments

Martin said…
Yup, had one too, recently.

But I still love Google.

Cheers
Anonymous said…
I too saw this...
enginerd said…
We all love Google!
So what if Blogger continues deleting posts, or Orkut shows negative scraps, we'll always love Google :)
Anonymous said…
hey, last night there were socket errors n it refused from posting n publishing index and blog..
did ya c that?
enginerd said…
Nope, but it seems the guys at Blogger are having their fair share of problems.

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.